https://github.com/jessecambon/tidygeocoder
Geocoding Made Easy
https://github.com/jessecambon/tidygeocoder
geocoding r rspatial rstats tidyverse
Last synced: about 1 month ago
JSON representation
Geocoding Made Easy
- Host: GitHub
- URL: https://github.com/jessecambon/tidygeocoder
- Owner: jessecambon
- License: other
- Created: 2019-09-19T21:11:45.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2024-04-06T14:25:19.000Z (about 1 year ago)
- Last Synced: 2024-09-20T07:36:05.330Z (7 months ago)
- Topics: geocoding, r, rspatial, rstats, tidyverse
- Language: R
- Homepage: https://jessecambon.github.io/tidygeocoder
- Size: 19 MB
- Stars: 283
- Watchers: 5
- Forks: 20
- Open Issues: 18
-
Metadata Files:
- Readme: README.Rmd
- License: LICENSE
Awesome Lists containing this project
- jimsghstars - jessecambon/tidygeocoder - Geocoding Made Easy (R)
README
---
output: github_document
---
```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
fig.path = "man/figures/README-",
fig.width = 8,
fig.height = 5,
fig.align = 'center'
)
options(tibble.print_min = 5, tibble.print_max = 5)
```
# tidygeocoder
[](https://doi.org/10.21105/joss.03544)
[](https://github.com/jessecambon/tidygeocoder/blob/master/LICENSE.md)
[](https://cran.r-project.org/package=tidygeocoder)
[](https://CRAN.R-project.org/package=tidygeocoder)
[](https://cran.r-project.org/package=tidygeocoder)
[](https://lifecycle.r-lib.org/articles/stages.html#stable)
[](https://github.com/jessecambon/tidygeocoder/actions?workflow=R-CMD-check)
[](https://doi.org/10.5281/zenodo.5627341)
Tidygeocoder makes getting data from geocoding services easy. A unified high-level interface is provided for a selection of [supported geocoding services](https://jessecambon.github.io/tidygeocoder/articles/geocoder_services.html) and results are returned in [tibble](https://tibble.tidyverse.org/) (dataframe) format.
Note that you should exercise due diligence when geocoding sensitive data as tidygeocoder utilizes third party web services to perform geocoding. Refer to the documentation on your selected geocoding service for information on how your data will be utilized and stored. See further information on this subject [here](https://jessecambon.github.io/tidygeocoder/articles/geocoder_services.html#data-privacy).
**Features:**
- Forward geocoding (addresses ⮕ coordinates)
- Reverse geocoding (coordinates ⮕ addresses)
- Batch geocoding (geocoding multiple addresses or coordinates in a single query) is automatically used if applicable.
- Duplicate, NA, and blank input data is handled elegantly; only unique inputs are submitted in queries, but the rows in the original data are preserved by default.
- The maximum rate of querying is automatically set according to the usage policies of the selected geocoding service.
In addition to the usage examples below, see the [Getting Started Vignette](https://jessecambon.github.io/tidygeocoder/articles/tidygeocoder.html) and [blog posts on tidygeocoder](https://jessecambon.github.io/tag/tidygeocoder).
## Installation
To install the stable version from CRAN (the official R package servers):
```{r, eval = FALSE}
install.packages('tidygeocoder')
```
Alternatively, you can install the latest development version from GitHub:
```{r, eval = FALSE}
devtools::install_github("jessecambon/tidygeocoder")
```
## Usage
In this first example we will geocode a few addresses using the `geocode()` function and plot them on a map with ggplot.
```{r}
library(dplyr, warn.conflicts = FALSE)
library(tidygeocoder)
# create a dataframe with addresses
some_addresses <- tibble::tribble(
~name, ~addr,
"White House", "1600 Pennsylvania Ave NW, Washington, DC",
"Transamerica Pyramid", "600 Montgomery St, San Francisco, CA 94111",
"Willis Tower", "233 S Wacker Dr, Chicago, IL 60606"
)
# geocode the addresses
lat_longs <- some_addresses %>%
geocode(addr, method = 'osm', lat = latitude , long = longitude)
```
The `geocode()` function geocodes addresses contained in a dataframe. The [Nominatim ("osm")](https://nominatim.org/) geocoding service is used here, but other services can be specified with the `method` argument. Only latitude and longitude are returned from the geocoding service in this example, but `full_results = TRUE` can be used to return all of the data from the geocoding service. See the `geo()` function documentation for details.
```{r, echo = FALSE}
knitr::kable(lat_longs)
```
Now that we have the longitude and latitude coordinates, we can use ggplot to plot our addresses on a map.
```{r usamap}
library(ggplot2)
ggplot(lat_longs, aes(longitude, latitude), color = "grey99") +
borders("state") + geom_point() +
ggrepel::geom_label_repel(aes(label = name)) +
theme_void()
```
To perform reverse geocoding (obtaining addresses from geographic coordinates), we can use the `reverse_geocode()` function. The arguments are similar to the `geocode()` function, but now we specify the input data columns with the `lat` and `long` arguments. The input dataset used here is the results of the geocoding query above.
The single line address is returned in a column named by the `address` argument and all columns from the geocoding service results are returned because `full_results = TRUE`. See the `reverse_geo()` function documentation for more details.
```{r}
reverse <- lat_longs %>%
reverse_geocode(lat = latitude, long = longitude, method = 'osm',
address = address_found, full_results = TRUE) %>%
select(-addr, -licence)
```
```{r, echo = FALSE}
knitr::kable(reverse)
```
## In the Wild
For inspiration, here are a few articles (with code) that leverage tidygeocoder:
- [Exercises: Spatial Data Wrangling with sf](http://www2.stat.duke.edu/courses/Spring21/sta323.001/exercises/lec_12.html) - part of a [statistical computing course](http://www2.stat.duke.edu/courses/Spring21/sta323.001/) at Duke
- [Geocoding the Minard Map](https://www.jla-data.net/eng/minard-map-tidygeocoder/) - recreating a famous infographic with geocoding
- [Mapping a network of women in demography](https://www.monicaalexander.com/posts/2021-21-02-mapping/) - using rvest and tidygeocoder to map Google Scholar data
- [Mapping Routes](https://bensstats.wordpress.com/2021/10/21/robservations-15-i-reverse-engineered-atlas-co-well-some-of-it/) - mapping routes with tidygeocoder and osrm
- [Road Routing in R](https://www.jla-data.net/eng/routing-in-r-context/) - demonstration of three different routing APIs
- [Mapping Texas Ports With R](https://www.sharpsightlabs.com/blog/mapping-texas-ports-with-r-part1/) - mapping the Texas coast with rnaturalearth and sf
## Contributing
Contributions to the tidygeocoder package are welcome. File [an issue](https://github.com/jessecambon/tidygeocoder/issues) for bug fixes or suggested features. If you would like to contribute code such as adding support for a new geocoding service, reference the [developer notes](https://jessecambon.github.io/tidygeocoder/articles/developer_notes.html) for instructions and documentation.
## Citing tidygeocoder
Use the `citation()` function:
``` r
citation('tidygeocoder')
```
```{r, comment = '', echo = FALSE}
citation('tidygeocoder')
```
Or refer to the [citation page](https://jessecambon.github.io/tidygeocoder/authors.html).