Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Tidygeocoder v1.0.2 “Yodeling Yak” is now on CRAN. This release adds support for the popular Google geocoder service (thanks @chris31415926535) and also includes several bugfixes and enhancements. Refer to the changelog for details on the release and to the tidygeocoder homepage for a comparison of all supported geocoder services.
You can make use of the Google geocoder service by passing method = 'google'
to the geo()
and geocode()
functions. Note that the Google geocoder service requires registering for an API key and charges per query. The Google API key needs to be stored in the GOOGLEGEOCODE_API_KEY
environmental variable for use with tidygeocoder.
Also new in this release, US Census batch geocoding results will now return geographic FIPs codes in character format (instead of numeric) to preserve leading zeros (#47). The return_type = 'geographies'
query in the usage example shows the new data format.
Additionally, arguments passed to the geo()
and geocode()
functions that aren’t valid for the selected geocoder service (ie. the Census geocoder doesn’t have a country
argument) will now throw errors:
library(tidygeocoder) geo(city = 'Auckland', country = 'New Zealand', method = 'census') ## Error in geo(city = "Auckland", country = "New Zealand", method = "census"): The following parameter(s) are not supported for the "census" method: ## ## country ## ## See ?api_parameter_reference for more details.
If you’re interested in contributing to the package and would like to add support for other geocoder services, updated instructions on how to go about this are located here.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.