Type: | Package |
Title: | Geocoding Made Easy |
Version: | 1.0.6 |
Description: | An intuitive interface for getting data from geocoding services. |
License: | MIT + file LICENSE |
URL: | https://jessecambon.github.io/tidygeocoder/, https://github.com/jessecambon/tidygeocoder |
BugReports: | https://github.com/jessecambon/tidygeocoder/issues |
Depends: | R (≥ 3.5) |
Imports: | tibble, dplyr, httr, jsonlite, progress |
Suggests: | knitr, rmarkdown, ggplot2, ggrepel, maps, testthat (≥ 3.0.2), spelling |
VignetteBuilder: | knitr |
Encoding: | UTF-8 |
LazyData: | true |
RoxygenNote: | 7.3.2 |
Language: | en-US |
NeedsCompilation: | no |
Packaged: | 2025-03-31 12:48:35 UTC; cambonator |
Author: | Jesse Cambon |
Maintainer: | Jesse Cambon <jesse.cambon@gmail.com> |
Repository: | CRAN |
Date/Publication: | 2025-03-31 13:30:02 UTC |
The tidygeocoder package makes getting data from geocoder services easy.
Description
The geocode and geo functions are for forward geocoding while
the reverse_geocode and reverse_geo functions are for reverse geocoding.
Refer to the documentation on the method
argument in the geo and reverse_geo functions
for more details on the available geocoding services. Also see vignette("tidygeocoder")
for example usage.
Author(s)
Maintainer: Jesse Cambon jesse.cambon@gmail.com (ORCID)
Authors:
Diego Hernangómez diego.hernangomezherrero@gmail.com (ORCID)
Christopher Belanger christopher.a.belanger@gmail.com (ORCID)
Daniel Possenriede possenriede+r@gmail.com (ORCID)
Other contributors:
Otto Hansen otto@uchicago.edu (ORCID) [contributor]
See Also
Useful links:
Report bugs at https://github.com/jessecambon/tidygeocoder/issues
Geocoding service links and information
Description
This dataset is used for generating package documentation.
Usage
api_info_reference
Format
A tibble dataframe
- method
Geocoding service name
- method_display_name
Geocoding service display name
- site_url
Link to the main site of the geocoding service
- api_documentation_url
Link to API documentation
- api_usage_policy_url
Link to the usage policy
API key environmental variables
Description
API keys are obtained from environmental variables. The geo and reverse_geo functions use this dataset to know which environmental variable to use for each geocoding service.
Usage
api_key_reference
Format
A tibble dataframe
- method
Geocoding service name
- env_var
Environmental variable name
See Also
Geocoding service API parameter reference
Description
This dataset contains the mapping that allows this package to use a universal syntax to specify parameters for different geocoding services. Note that latitude and longitude input parameters for reverse geocoding are not in this dataset and are instead handled directly by the reverse_geo function.
The generic_name
column is a universal parameter name that is shared between services.
The api_name
column is the parameter name for the given geocoding service specified by the
method
column. When generic_name
is missing
this means the parameter is specific to that geocoding service.
While the "census" and "google" services do not have a limit
argument in their APIs, tidygeocoder provides a passthrough so you can still
use the limit
argument in geo and reverse_geo to limit the
number of results per input.
Note that some geocoding services only use the limit
argument for forward geocoding.
Refer to API documentation of each service for more information.
Reference the documentation for geo and reverse_geo for more information.
Also reference vignette("tidygeocoder")
for more details on constructing API queries.
Usage
api_parameter_reference
Format
A tibble dataframe
- method
Geocoding service name
- generic_name
Universal parameter name
- api_name
Name of the parameter for the specified geocoding service
- default_value
Default value of the parameter
- required
Is the parameter required by the specified geocoding service?
Details
The API documentation for each service is linked to below:
See Also
geo reverse_geo get_api_query query_api min_time_reference batch_limit_reference
Geocoding batch size limits
Description
The geo and reverse_geo functions use this dataset to set the maximum batch query size for each service.
Usage
batch_limit_reference
Format
A tibble dataframe
- method
Geocoding service name
- batch_limit
The maximum number of addresses or coordinates allowed per batch
See Also
Extract forward geocoding results
Description
Parses the output of the query_api function for single address geocoding (ie. not batch geocoding). Latitude and longitude are extracted into the first two columns of the returned dataframe. Refer to query_api for example usage.
Usage
extract_results(
method,
response,
full_results = TRUE,
flatten = TRUE,
limit = 1
)
Arguments
method |
method name |
response |
content from the geocoding service (returned by the query_api function) |
full_results |
if TRUE then the full results (not just latitude and longitude) will be returned. |
flatten |
if TRUE then flatten any nested dataframe content |
limit |
only used for "census" and "google" methods. Limits number of results per address. |
Value
geocoding results in tibble format
See Also
Extract reverse geocoding results
Description
Parses the output of the query_api function for reverse geoocoding. The address is extracted into the first column of the returned dataframe. This function is not used for batch geocoded results. Refer to query_api for example usage.
Usage
extract_reverse_results(
method,
response,
full_results = TRUE,
flatten = TRUE,
limit = 1
)
Arguments
method |
method name |
response |
content from the geocoding service (returned by the query_api function) |
full_results |
if TRUE then the full results (not just an address column) will be returned. |
flatten |
if TRUE then flatten any nested dataframe content |
limit |
only used for the "google" method(s). Limits number of results per coordinate. |
Value
geocoding results in tibble format
See Also
get_api_query query_api reverse_geo
Geocode addresses
Description
Geocodes addresses given as character values. The geocode
function utilizes this function on addresses contained in dataframes.
See example usage in vignette("tidygeocoder")
.
Note that not all geocoding services support certain address component parameters. For example, the Census geocoder only covers the United States and does not have a "country" parameter.
Refer to api_parameter_reference, min_time_reference, and batch_limit_reference for more details on geocoding service parameters and usage.
This function uses the get_api_query, query_api, and extract_results functions to create, execute, and parse geocoder API queries.
Usage
geo(
address = NULL,
street = NULL,
city = NULL,
county = NULL,
state = NULL,
postalcode = NULL,
country = NULL,
method = "osm",
lat = "lat",
long = "long",
limit = 1,
full_results = FALSE,
mode = "",
unique_only = FALSE,
return_addresses = TRUE,
min_time = NULL,
progress_bar = show_progress_bar(),
quiet = getOption("tidygeocoder.quiet", FALSE),
api_url = NULL,
timeout = 20,
flatten = TRUE,
batch_limit = NULL,
verbose = getOption("tidygeocoder.verbose", FALSE),
no_query = FALSE,
custom_query = list(),
api_options = list()
)
Arguments
address |
single line address (ie. '1600 Pennsylvania Ave NW, Washington, DC').
Do not combine with the address component arguments below
( |
street |
street address (ie. '1600 Pennsylvania Ave NW') |
city |
city (ie. 'Tokyo') |
county |
county (ie. 'Jefferson') |
state |
state (ie. 'Kentucky') |
postalcode |
postalcode (ie. zip code if in the United States) |
country |
country (ie. 'Japan') |
method |
the geocoding service to be used. API keys are loaded from environmental variables. Run
|
lat |
latitude column name. Can be quoted or unquoted (ie. |
long |
longitude column name. Can be quoted or unquoted (ie. |
limit |
maximum number of results to return per input address. For many geocoding services the maximum value of the limit parameter is 100. Pass |
full_results |
returns all available data from the geocoding service if TRUE. If FALSE (default) then only latitude and longitude columns are returned from the geocoding service. |
mode |
set to 'batch' to force batch geocoding or 'single' to force single address geocoding (one address per query). If not specified then batch geocoding will be used if available (given method selected) when multiple addresses are provided; otherwise single address geocoding will be used. For the "here" and "bing" methods the batch mode should be explicitly specified with |
unique_only |
only return results for unique inputs if TRUE |
return_addresses |
return input addresses with results if TRUE. Note that
most services return the input addresses with |
min_time |
minimum amount of time for a query to take (in seconds). If NULL then min_time will be set to the default value specified in min_time_reference. |
progress_bar |
if TRUE then a progress bar will be displayed
for single input geocoding (1 input per query). By default the progress bar
will not be shown for code executed when knitting R Markdown files or code within
an RStudio notebook chunk. Can be set permanently with |
quiet |
if TRUE then console messages that are displayed by default
regarding queries will be suppressed. FALSE is default.
Can be set permanently with |
api_url |
custom API URL. If specified, the default API URL will be overridden. This parameter can be used to specify a local Nominatim server, for instance. |
timeout |
query timeout (in minutes) |
flatten |
if TRUE (default) then any nested dataframes in results are flattened if possible. Note that in some cases results are flattened regardless such as for Geocodio batch geocoding. |
batch_limit |
limit to the number of addresses in a batch geocoding query.Defaults to the value in batch_limit_reference if not specified. |
verbose |
if TRUE then detailed logs are output to the console. FALSE is default. Can be set
permanently with |
no_query |
if TRUE then no queries are sent to the geocoding service and verbose is set to TRUE. Used for testing. |
custom_query |
API-specific parameters to be used, passed as a named list
(ex. |
api_options |
a named list of parameters specific to individual services.
(ex.
|
Value
tibble (dataframe)
See Also
geocode api_parameter_reference min_time_reference batch_limit_reference
Examples
options(tidygeocoder.progress_bar = FALSE)
geo(
street = "600 Peachtree Street NE", city = "Atlanta",
state = "Georgia", method = "census"
)
geo(
address = c("Tokyo, Japan", "Lima, Peru", "Nairobi, Kenya"),
method = "osm"
)
geo("100 Main St New York, NY",
full_results = TRUE,
method = "census", api_options = list(census_return_type = "geographies")
)
geo(
county = "Jefferson", state = "Kentucky", country = "US",
method = "osm"
)
Combine multiple geocoding queries
Description
Passes address inputs in character vector form to the geocode_combine function for geocoding.
Note that address inputs must be specified for queries either with the queries
parameter (for each query)
or the global_params
parameter (for all queries). For example global_params = list(address = 'address')
passes addresses provided in the address
parameter to all queries.
Usage
geo_combine(
queries,
global_params = list(),
address = NULL,
street = NULL,
city = NULL,
county = NULL,
state = NULL,
postalcode = NULL,
country = NULL,
lat = lat,
long = long,
...
)
Arguments
queries |
a list of queries, each provided as a list of parameters. The queries are, executed by the geocode function in the order provided., (ex. |
global_params |
a list of parameters to be used for all queries, (ex. |
address |
single line address (ie. '1600 Pennsylvania Ave NW, Washington, DC').
Do not combine with the address component arguments below
( |
street |
street address (ie. '1600 Pennsylvania Ave NW') |
city |
city (ie. 'Tokyo') |
county |
county (ie. 'Jefferson') |
state |
state (ie. 'Kentucky') |
postalcode |
postalcode (ie. zip code if in the United States) |
country |
country (ie. 'Japan') |
lat |
latitude column name. Can be quoted or unquoted (ie. |
long |
longitude column name. Can be quoted or unquoted (ie. |
... |
arguments passed to the geocode_combine function |
Value
tibble (dataframe)
See Also
Examples
options(tidygeocoder.progress_bar = FALSE)
example_addresses <- c("100 Main St New York, NY", "Paris", "Not a Real Address")
geo_combine(
queries = list(
list(method = "census"),
list(method = "osm")
),
address = example_addresses,
global_params = list(address = "address")
)
geo_combine(
queries = list(
list(method = "arcgis"),
list(method = "census", mode = "single"),
list(method = "census", mode = "batch")
),
global_params = list(address = "address"),
address = example_addresses,
cascade = FALSE,
return_list = TRUE
)
geo_combine(
queries = list(
list(method = "arcgis", address = "city"),
list(method = "osm", city = "city", country = "country")
),
city = c("Tokyo", "New York"),
country = c("Japan", "United States"),
cascade = FALSE
)
Geocode addresses in a dataframe
Description
Takes a dataframe containing addresses as an input and returns
the results from a specified geocoding service in a dataframe format using the
geo function. See example usage in vignette("tidygeocoder")
.
This function passes all additional parameters (...
) to the
geo function, so you can refer to its documentation for more details
on possible arguments.
Note that the arguments used for specifying address columns (address
,
street
, city
, county
, state
, postalcode
, and country
) accept either
quoted or unquoted column names (ie. "address_col"
and address_col
are
both acceptable).
Usage
geocode(
.tbl,
address = NULL,
street = NULL,
city = NULL,
county = NULL,
state = NULL,
postalcode = NULL,
country = NULL,
lat = "lat",
long = "long",
return_input = TRUE,
limit = 1,
return_addresses = NULL,
unique_only = FALSE,
...
)
Arguments
.tbl |
dataframe containing addresses |
address |
single line street address column name. Do not combine with
address component arguments ( |
street |
street address column name |
city |
city column name |
county |
county column name |
state |
state column name |
postalcode |
postal code column name (zip code if in the United States) |
country |
country column name |
lat |
latitude column name. Can be quoted or unquoted (ie. |
long |
longitude column name. Can be quoted or unquoted (ie. |
return_input |
if TRUE then the input dataset will be combined with the geocoder query results and returned. If FALSE only the geocoder results will be returned. |
limit |
maximum number of results to return per input address. For many geocoding services the maximum value of the limit parameter is 100. Pass |
return_addresses |
if TRUE return input addresses. Defaults to TRUE if |
unique_only |
if TRUE then only unique results will be returned and return_input will be set to FALSE. |
... |
arguments passed to the geo function |
Value
tibble (dataframe)
See Also
Examples
library(dplyr, warn.conflicts = FALSE)
sample_addresses %>%
slice(1:2) %>%
geocode(addr, method = "arcgis")
louisville %>%
head(2) %>%
geocode(
street = street, city = city, state = state,
postalcode = zip, method = "census", full_results = TRUE
)
sample_addresses %>%
slice(8:9) %>%
geocode(addr,
method = "osm", limit = 2,
return_input = FALSE, full_results = TRUE
)
sample_addresses %>%
slice(4:5) %>%
geocode(addr,
method = "arcgis",
lat = latitude, long = longitude,
full_results = TRUE
)
Combine multiple geocoding queries
Description
Executes multiple geocoding queries on a dataframe input and combines
the results. To use a character vector input instead, see the geo_combine function.
Queries are executed by the geocode function. See example usage
in vignette("tidygeocoder")
.
Query results are by default labelled to show which query produced each result. Labels are either
placed in a query
column (if return_list = FALSE
) or used as the names of the returned list
(if return_list = TRUE
). By default the method
parameter value of each query is used as a query label.
If the same method
is used in multiple queries then a number is added according
to the order of the queries (ie. osm1
, osm2
, ...). To provide your own custom query labels
use the query_names
parameter.
Usage
geocode_combine(
.tbl,
queries,
global_params = list(),
return_list = FALSE,
cascade = TRUE,
query_names = NULL,
lat = "lat",
long = "long"
)
Arguments
.tbl |
dataframe containing addresses |
queries |
a list of queries, each provided as a list of parameters. The queries are, executed by the geocode function in the order provided., (ex. |
global_params |
a list of parameters to be used for all queries, (ex. |
return_list |
if TRUE then results from each service will be returned as separate dataframes. If FALSE (default) then all results will be combined into a single dataframe. |
cascade |
if TRUE (default) then only addresses that are not found by a geocoding service will be attempted by subsequent queries. If FALSE then all queries will attempt to geocode all addresses. |
query_names |
optional vector with one label for each query provided
(ex. |
lat |
latitude column name. Can be quoted or unquoted (ie. |
long |
longitude column name. Can be quoted or unquoted (ie. |
Value
tibble (dataframe)
See Also
Examples
library(dplyr, warn.conflicts = FALSE)
sample_addresses %>%
geocode_combine(
queries = list(list(method = "census"), list(method = "osm")),
global_params = list(address = "addr"), cascade = TRUE
)
more_addresses <- tibble::tribble(
~street_address, ~city, ~state, ~zip_cd,
"624 W DAVIS ST #1D", "BURLINGTON", "NC", 27215,
"201 E CENTER ST #268", "MEBANE", "NC", 27302,
"100 Wall Street", "New York", "NY", 10005,
"Bucharest", NA, NA, NA
)
more_addresses %>%
geocode_combine(
queries = list(
list(method = "census", mode = "batch"),
list(method = "census", mode = "single"),
list(method = "osm")
),
global_params = list(
street = "street_address",
city = "city", state = "state", postalcode = "zip_cd"
),
query_names = c("census batch", "census single", "osm")
)
more_addresses %>%
geocode_combine(
queries = list(
list(
method = "census", mode = "batch", street = "street_address",
city = "city", state = "state", postalcode = "zip_cd"
),
list(method = "arcgis", address = "street_address")
),
cascade = FALSE,
return_list = TRUE
)
Construct a geocoder API query
Description
The geocoder API query is created using universal "generic" parameters and optional api-specific "custom" parameters. Generic parameters are converted into api parameters using the api_parameter_reference dataset.
The query_api function executes the queries created by this function.
Usage
get_api_query(method, generic_parameters = list(), custom_parameters = list())
Arguments
method |
the geocoding service name (ie. 'census') |
generic_parameters |
universal "generic" parameters |
custom_parameters |
custom api-specific parameters |
Value
API parameters as a named list
See Also
query_api api_parameter_reference geo reverse_geo
Examples
get_api_query("osm", list(address = "Hanoi, Vietnam"))
get_api_query(
"census", list(street = "11 Wall St", city = "NY", state = "NY"),
list(benchmark = "Public_AR_Census2010")
)
Louisville, Kentucky street addresses
Description
Louisville, Kentucky street addresses
Usage
louisville
Format
A tibble dataframe with component street addresses
- street
Description of the address
- city
Single line address
- state
state
- zip
zip code
Source
Downloaded from OpenAddresses.io on June 1st 2020
Minimum time required per query
Description
The geo and reverse_geo functions use this dataset to set the maximum query rate for each geocoding service. This rate is based on the usage restriction policies for each geocoding service.
Usage
min_time_reference
Format
A tibble dataframe
- method
Geocoding service name
- min_time
The minimum number of seconds required per query to comply with usage restrictions
- description
A description of the usage rate restriction
Details
Links to the usage policies of each geocoding service are below:
See Also
Execute a geocoder API query
Description
The get_api_query function can create queries for this function to execute.
Usage
query_api(
api_url,
query_parameters,
mode = "single",
batch_file = NULL,
input_list = NULL,
content_encoding = "UTF-8",
timeout = 20,
method = ""
)
Arguments
api_url |
Base URL of the API. query parameters are appended to this |
query_parameters |
api query parameters in the form of a named list |
mode |
determines the type of query to execute
|
batch_file |
a csv file of input data to upload (for |
input_list |
a list of input data (for |
content_encoding |
Encoding to be used for parsing content |
timeout |
timeout in minutes |
method |
if 'mapquest' or 'arcgis' then the query status code is changed appropriately |
Value
a named list containing the response content (content
) and the HTTP request status (status
)
See Also
get_api_query extract_results extract_reverse_results geo reverse_geo
Examples
raw1 <- query_api(
"http://nominatim.openstreetmap.org/search",
get_api_query("osm", list(address = "Hanoi, Vietnam"))
)
raw1$status
extract_results("osm", jsonlite::fromJSON(raw1$content))
raw2 <- query_api(
"http://nominatim.openstreetmap.org/reverse",
get_api_query("osm", custom_parameters = list(lat = 38.895865, lon = -77.0307713))
)
extract_reverse_results("osm", jsonlite::fromJSON(raw2$content))
Reverse geocode coordinates
Description
Reverse geocodes geographic coordinates (latitude and longitude) given as numeric values.
Latitude and longitude inputs are limited to possible values. Latitudes must be between -90 and 90 and
longitudes must be between -180 and 180. Invalid values will not be sent to the geocoding service.
The reverse_geocode function utilizes this function on coordinates contained in dataframes.
See example usage in vignette("tidygeocoder")
.
Refer to api_parameter_reference, min_time_reference, and batch_limit_reference for more details on geocoding service parameters and usage.
This function uses the get_api_query, query_api, and extract_reverse_results functions to create, execute, and parse geocoder API queries.
Usage
reverse_geo(
lat,
long,
method = "osm",
address = "address",
limit = 1,
full_results = FALSE,
mode = "",
unique_only = FALSE,
return_coords = TRUE,
min_time = NULL,
progress_bar = show_progress_bar(),
quiet = getOption("tidygeocoder.quiet", FALSE),
api_url = NULL,
timeout = 20,
flatten = TRUE,
batch_limit = NULL,
verbose = getOption("tidygeocoder.verbose", FALSE),
no_query = FALSE,
custom_query = list(),
api_options = list()
)
Arguments
lat |
latitude values (input data) |
long |
longitude values (input data) |
method |
the geocoding service to be used. API keys are loaded from environmental variables. Run
|
address |
name of the address column (in the output data) |
limit |
maximum number of results to return per input coordinate. For many geocoding services the maximum value of the limit parameter is 100. Pass |
full_results |
returns all available data from the geocoding service if TRUE. If FALSE (default) then only a single address column is returned from the geocoding service. |
mode |
set to 'batch' to force batch geocoding or 'single' to force single coordinate geocoding (one coordinate per query). If not specified then batch geocoding will be used if available (given method selected) when multiple coordinates are provided; otherwise single address geocoding will be used. For the "here" and "bing" methods the batch mode should be explicitly specified with |
unique_only |
only return results for unique inputs if TRUE |
return_coords |
return input coordinates with results if TRUE. Note that
most services return the input coordinates with |
min_time |
minimum amount of time for a query to take (in seconds). If NULL then min_time will be set to the default value specified in min_time_reference. |
progress_bar |
if TRUE then a progress bar will be displayed
for single input geocoding (1 input per query). By default the progress bar
will not be shown for code executed when knitting R Markdown files or code within
an RStudio notebook chunk. Can be set permanently with |
quiet |
if TRUE then console messages that are displayed by default
regarding queries will be suppressed. FALSE is default.
Can be set permanently with |
api_url |
custom API URL. If specified, the default API URL will be overridden. This parameter can be used to specify a local Nominatim server, for instance. |
timeout |
query timeout (in minutes) |
flatten |
if TRUE (default) then any nested dataframes in results are flattened if possible. Note that in some cases results are flattened regardless such as for Geocodio batch geocoding. |
batch_limit |
limit to the number of coordinates in a batch geocoding query.Defaults to the value in batch_limit_reference if not specified. |
verbose |
if TRUE then detailed logs are output to the console. FALSE is default. Can be set
permanently with |
no_query |
if TRUE then no queries are sent to the geocoding service and verbose is set to TRUE. Used for testing. |
custom_query |
API-specific parameters to be used, passed as a named list
(ex. |
api_options |
a named list of parameters specific to individual services.
(ex.
|
Value
tibble (dataframe)
See Also
reverse_geocode api_parameter_reference min_time_reference batch_limit_reference
Examples
options(tidygeocoder.progress_bar = FALSE)
reverse_geo(lat = 38.895865, long = -77.0307713, method = "osm")
reverse_geo(
lat = c(38.895865, 43.6534817, 300),
long = c(-77.0307713, -79.3839347, 600),
method = "osm", full_results = TRUE
)
Reverse geocode coordinates in a dataframe
Description
Takes a dataframe containing coordinates (latitude and longitude) and returns
the reverse geocoding query results from a specified service by using the
reverse_geo function. See example usage in vignette("tidygeocoder")
.
This function passes all additional parameters (...
) to the
reverse_geo function, so you can refer to its documentation for more details
on possible arguments.
Usage
reverse_geocode(
.tbl,
lat,
long,
address = "address",
return_input = TRUE,
limit = 1,
return_coords = NULL,
unique_only = FALSE,
...
)
Arguments
.tbl |
dataframe containing coordinates |
lat |
latitude column name (input data). Can be quoted or unquoted (ie. lat or 'lat'). |
long |
longitude column name (input data). Can be quoted or unquoted (ie. long or 'long'). |
address |
address column name (output data). Can be quoted or unquoted (ie. addr or 'addr'). |
return_input |
if TRUE then the input dataset will be combined with the geocoder query results and returned. If FALSE only the geocoder results will be returned. |
limit |
maximum number of results to return per input coordinate. For many geocoding services the maximum value of the limit parameter is 100. Pass |
return_coords |
if TRUE return input coordinates. Defaults to TRUE if |
unique_only |
if TRUE then only unique results will be returned and return_input will be set to FALSE. |
... |
arguments passed to the reverse_geo function |
Value
tibble (dataframe)
See Also
Examples
library(tibble)
library(dplyr, warn.conflicts = FALSE)
tibble(
latitude = c(38.895865, 43.6534817),
longitude = c(-77.0307713, -79.3839347)
) %>%
reverse_geocode(
lat = latitude,
long = longitude,
method = "osm",
full_results = TRUE
)
louisville %>%
head(3) %>%
reverse_geocode(
lat = latitude, long = longitude,
method = "arcgis"
)
louisville %>%
head(2) %>%
reverse_geocode(
lat = latitude, long = longitude,
method = "osm",
limit = 2, return_input = FALSE
)
Sample addresses for testing
Description
Sample addresses for testing
Usage
sample_addresses
Format
A tibble dataframe with single line addresses
- name
Description of the address
- addr
Single line address