osmextract (development version)
MAJOR CHANGES
- Fixed a bug in
oe_match()
that occurred every timeoe_match()
found an exact match between the inputplace
and a non-default OSM data provider (i.e. non Geofabrik). In those cases, the downloaded file was named asgeofabrik_xyz.osm.pbf
instead ofdifferent-provider_xyz.osm.pbf
. Reported by @GretaTimaite, thanks. See #246. This is a quite major bug, and we suggest you erase all.pbf
and.gpkg
files stored in the persistent download directory (see also?oe_clean
). - Fixed a bug in
oe_get_keys()
that occurred when the value for a given key was either empty or equal to\n
(#250).
MINOR CHANGES
- The
boundary
argument can be specified usingbbox
objects. Thebbox
object is converted tosfc
object withsf::st_as_sfc
and preserves the same CRS. - Added a more informative error message when
oe_get()
oroe_read()
are run with empty or unnamed arguments in...
(#234 and #241). - The function
oe_get_keys()
gains a new argument nameddownload_directory
that can be used to specify the path of the directory that stores the.osm.pbf
files. - Included a new function named
oe_clean()
to remove all.pbf
and.gpkg
files stored in a given directory. Default value isoe_download_directory()
. - Added a message to
oe_download()
and removed a warning fromoe_read()
. The message is printed every time a user downloads a new OSM extract from a certain provider, whereas the warning used to be raised when a givenquery
selected a layer different from thelayer
argument (#240). - Added two new parameters to
oe_find
namedreturn_pbf
andreturn_gpkg
. They can be used to select which file formats should the function return (#253). - Added a more informative error message in case
oe_download()
fails explaining that partially downloaded.pbf
files should be removed to avoid problems while running other functions (#221). - We are experimenting with the new features of
testthat
and we implemented the so-called test-fixtures to run tests in a more isolated environment (#255). This is however still experimental for us. - Added more informative error and warning messages to
oe_get_keys()
(#251). - The file path returned by
oe_download()
is specified using/
instead of\\
separator on Windows.
osmextract 0.4.0
CRAN release: 2021-10-27
MAJOR CHANGES
- Import two new packages:
httr
andjsonlite
(#231, #232). - Improved the approach adopted to download files from the web. In particular, the functions
oe_download()
andoe_search()
now take advantage ofhttr
functionalities. They return informative messages in case of errors (#231, #232). - Vignettes and examples do not require internet connection.
BUG FIXES
- Fixed a bug in
oe_vectortranslate()
that occurred when readingmultilinestrings
orother_relations
layers with one or more extra tags (#229). - Fixed a bug in
oe_get()
/oe_read()
that could return a warning message when reading an existing GPKG file with aquery
argument.
MINOR CHANGES
- The duplicated fields in
extra_tags
are now removed before modifying theosmconf.ini
file. Duplicated tags means something likeextra_tags = c("A", "A")
or even fields that are included by default (i.e.extra_tags = "highway"
for thelines
layer). See discussion in #229.
osmextract 0.3.1
CRAN release: 2021-07-27
MAJOR CHANGES
- Added a new (but still experimental) function named
oe_get_network()
to import a road network used by a specific mode of transport. For the moment, we support the following modes of transport: cycling (default), walking, and driving. Check?oe_get_network
for more details and examples (#218).
MINOR CHANGES
- The
layer
argument is now converted to lower case before checking if the required layer is admissible. - Adjusted the code behind
oe_get()
andoe_vectortranslate()
forsf
v1.0.2. - Remove the call to
suppressMessages()
inoe_match()
(#217).
osmextract 0.3.0
CRAN release: 2021-06-10
MAJOR CHANGES
- The
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 inputzone
with one of the OSM extracts previously downloaded (#201 and #196). - If the parameter
place
represents ansf
/sfc
/bbox
object with missing CRS, thenoe_match()
raises a warning message and setsCRS = 4326
. This has relevant consequences on other functions (likeoe_get()
) that wrapoe_match()
. - Starting from
sf
> 0.9.8, the functionoe_vectortranslate()
stops with an error when there is a problem in the argumentvectortranslate_options
andquiet = FALSE
(instead of raising a warning or crashing theR
session). See here for more details. - The options
c("-f", "GPKG", "-overwrite", "-oo", "CONFIG_FILE=", path-to-config-file, "-lco", "GEOMETRY_NAME=geometry", layer)
are always appended at the end ofvectortranslate_options
argument unless the user explicitly sets different default parameters for the arguments-f
,-oo
and-lco
(#200). We believe those are sensible defaults and can help users creating less verbose specifications forogr2ogr
utility. - We create two new arguments in
oe_vectortranslate()
(therefore also inoe_get()
andoe_read()
) namedboundary
andboundary_type
. They can be used to create an ad-hoc spatial filter during the vectortranslate operations (and create even less verbose specifications invectortranslate_options
argument). See docs and introductory vignette for more details. - The argument
provider
was removed fromoe_match_pattern()
since the function automatically checks all available providers (#208).
BUG FIXES
- The parameter
force_vectortranslate
is checked before reading the layers of an existinggpkg
file. Ifforce_vectortranslate
isTRUE
, thenoe_vectortranslate()
doesn’t check the existing layers. This is important for user that runoe_vectortranslate()
after stopping the vectortranslate process. - The arguments
extra_tags
andosmconf_ini
are not ignored whenvectortranslate_options
is notNULL
(#182). - Fix the provider’s data objects for
sf
v1.0 (#194).
MINOR IMPROVEMENTS
- The arguments passed to
oe_read()
via...
are compared with the formals ofst_read.character
,st_as_sf.data.frame
, andread_sf
. - Added a new method to
oe_match
forbbox
objects (#185). - The
oe_get_keys()
function can be applied to.osm.pbf
objects (#188).
DOCUMENTATION FIXES
- Improved several examples and fixed a small bug in the documentation of
oe_match()
. - Fix several typos in the vignettes and docs.
OTHERS
- Created a new space in the github repo named Discussion to have conversations, ask questions and post answers without opening issues. Link: https://github.com/ropensci/osmextract/discussions.
- Tests that require an internet connection are now skipped on CRAN (#189).
osmextract 0.2.1
CRAN release: 2021-02-15
This is a minor release.
- We modified several examples and tests to fix several errors noticed during CRAN tests (#175).
osmextract 0.2.0
CRAN release: 2021-02-11
Published on CRAN!
NEW FEATURES
- Add a
level
parameter tooe_match()
. It is used to choose between multiple hierarchically nested OSM extracts. The default behaviour is to select the smallest administrative unit (#160). - Modify the behaviour of
oe_match()
. The function checks all implemented providers in case the inputplace
is not matched with any geographical zone for the chosen provider (#155). - Add a simple interface to Nominatim API that enables
oe_match()
to geolocate text strings that cannot be found in the providers (#155).
DOCUMENTATION FIXES
- Simplify several warning messages in case of spatial matching
- Simplify startup message (#156)
- Add more details related to download timeouts (#145)
- Documented values returned by
oe_find()
andoe_search()