oe_search()now take advantage of
httrfunctionalities. They return informative messages in case of errors (#231, #232).
extra_tagsare now removed before modifying the
osmconf.inifile. Duplicated tags means something like
extra_tags = c("A", "A")or even fields that are included by default (i.e.
extra_tags = "highway"for the
lineslayer). See discussion in #229.
oe_get_keys()function can be used to extract the values associated with all or some keys. We also defined an ad-hoc printing method and fixed several bugs. The examples were improved. Moreover, the function tries to match an input
zonewith one of the OSM extracts previously downloaded (#201 and #196).
bboxobject with missing CRS, then
oe_match()raises a warning message and sets
CRS = 4326. This has relevant consequences on other functions (like
oe_get()) that wrap
sf> 0.9.8, the function
oe_vectortranslate()stops with an error when there is a problem in the argument
quiet = FALSE(instead of raising a warning or crashing the
Rsession). See here for more details.
c("-f", "GPKG", "-overwrite", "-oo", "CONFIG_FILE=", path-to-config-file, "-lco", "GEOMETRY_NAME=geometry", layer)are always appended at the end of
vectortranslate_optionsargument unless the user explicitly sets different default parameters for the arguments
-lco(#200). We believe those are sensible defaults and can help users creating less verbose specifications for
oe_vectortranslate()(therefore also in
boundary_type. They can be used to create an ad-hoc spatial filter during the vectortranslate operations (and create even less verbose specifications in
vectortranslate_optionsargument). See docs and introductory vignette for more details.
providerwas removed from
oe_match_pattern()since the function automatically checks all available providers (#208).
force_vectortranslateis checked before reading the layers of an existing
oe_vectortranslate()doesn’t check the existing layers. This is important for user that run
oe_vectortranslate()after stopping the vectortranslate process.
osmconf_iniare not ignored when
This is a minor release.
Published on CRAN!
oe_match(). It is used to choose between multiple hierarchically nested OSM extracts. The default behaviour is to select the smallest administrative unit (#160).
oe_match(). The function checks all implemented providers in case the input
placeis not matched with any geographical zone for the chosen provider (#155).
oe_match()to geolocate text strings that cannot be found in the providers (#155).