Issues geocoding large datasets about censusxy HOT 5 CLOSED

Thanks for opening an issue @plnnr ,

All that I can speculate is that your data returns a non-standard response from the Census bureau's API at some point. This specific error occurs because the response does not have a column containing the original address.

Would it be possible to provide a sample of your data?

Alternatively, if you are able to split the data yourself and send smaller batches, you could ensure that progress isn't lost also while helping locate the problem data.

from censusxy.

I ended up splitting the data, and there were no errors strangely (even though the subsets contained all of the records as the more massive pull). I am unable to provide a sample because it's sensitive/personal data (voter registration records). Although splitting worked, it doesn't make sense why.

from censusxy.

Curious, @plnnr. What sized chunks did you split the data into?

from censusxy.

@chris-prener My data had ZIP codes, so I split on that. Each ZIP code had 17k to 37k records.

from censusxy.

Gotcha. Yeah, this seems like some kind of non-standard API response, perhaps due to a timeout and perhaps due to the volume of records you're looking at. Either way, I'm glad it worked with splitting via zip code! I'm going to go ahead and close this now since the package itself appears to be performing as expected.

from censusxy.