Fixed bug when GEOIDs are ordered differently in result chunks. #165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a large number of variables (>24) are passed into
get_acs
, results sometimes (perhaps rarely) contain errors (perhaps many). This is becauseget_acs
divides the variables into two or more requests, and then binds the returned results together into a dataframe, but GEOIDs may be ordered differently for each set of returned results. For example:The proposed fix uses
full_join
onGEOID
rather thanbind_cols
.