-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support US Census Reverse Geocoding #172
Comments
Hi Jesse, |
Hi @LizBlackman, unfortunately I don't think I'll have availability in the near future so probably not. However, you are welcome to install the branch I was working with and try it out: devtools::install_github("jessecambon/tidygeocoder", ref = "census-reverse-geocoding") You should then be able to use Alternatively, you could use the script referred to in the link above to reverse geocode with the census service directly (ie. not using tidygeocoder). Hope that helps and feel free to give some feedback on output data format/etc. |
Hi @jessecambon! Thank you for the quick response! I worked on this for quite some time on Friday and went through stack overflow to find a way to clean up the output that I got back from the alltypes<- unique(unlist(sapply(c(1:length(GEOID1)), function(x){ all.values <- lapply(c(1: length(GEOID1)), function(x){ all.values <- do.call("rbind", all.values) lat_long1[, alltypes]<-NA Assistance came from this stack overflow entry |
Awesome, glad you got it working. I'm assuming you may not be able to share these coordinates you are using, but could you possibly provide an end-to-end example that I could run with a few sample coordinates that shows the end data format? You could use something like reprex or whatever is easiest. Also, just to confirm - you are using the |
Hi Jesse, I learned how to use reprex just for you. Let me know if what i shared works, it should...
|
The US Census service supports reverse geocoding through searchtype='coordinates'. See code example and data output format here.
We could potentially support this in tidygeocoder, but the output format is quite different from other geocoding services so it would require some data formatting to work properly within the package.
The text was updated successfully, but these errors were encountered: