Skip to content

Releases: USEPA/elevatr

v0.99.0 rspatial refactor initial CRAN release

11 Sep 15:46
Compare
Choose a tag to compare
cran comments and news for 0.99 release

CRAN Release v0.4.5

12 Jun 20:01
Compare
Choose a tag to compare

Last release prior to v1 that switches to sf and terra.

CRAN Release v0.4.4

30 May 20:43
Compare
Choose a tag to compare
ready for resubmit

CRAN Release 0.4.2

29 Dec 22:23
Compare
Choose a tag to compare

elevatr 0.4.2 (2021-12-28)

Additions

  • OpenTopography now requires an API Key. This can be acquired form OpenTopography. You need to set it with elevatr using elevatr::set_opentopo_key(). After a restart, elevatr will use this key.
  • The "Introduction to elevatr" vignette has been updated to include chanage reflected in version 0.4.2 and also includes a new section on accessing data from OpenTopography and details on setting the API key.

Bug Fixes

  • The epqs server was occasionally returning an empty response (see #29) and would error. If that happens now, elevatr will retry up to 5 times (which usually fixes the issue). If still an empty response after 5 tries, NA is returned and a warning is issued indicating what happened.
  • Changing to future::plans was losing tempfiles on parallel downloads. Moved the change back to serial plan after creation of raster.
  • Changed get_tile_xy. My math was messing up in areas near 180/-180 longitude were trying to grab non-existent tiles. Now using slippymath::lonlat_to_tilenum instead.
  • NA's introduced with simultaneous gdal mosaic and project. Now uses two steps. Solves https://stackoverflow.com/questions/67839878/gridded-dot-artifacts-in-geom-raster-plot

CRAN v0.4.1 release

21 Jul 15:03
Compare
Choose a tag to compare

Release to skip testing on solaris.

Waiting on sp fix in rsbivand/sp to make its way to CRAN.

CRAN Release V0.4.0

19 Jul 20:27
Compare
Choose a tag to compare

elevatr 0.4.0 (2021-07-19)

Biggest Changes To Note

  • The prj argument relied on proj4string in the past. That support is going
    away in order to keep up with changes in PROJ and the rest of R Spatial
    ecosystem. Spatial reference will be pulled form "locations" if they have it
    defined or will be pulled from an acceptable SRS_string. EPSG codes in the
    form of "EPSG:4326" are a pretty safe bet. WKT strings work well on
    PROJ > 5.2.0.

Bug Fixes

  • Empty rasters were failing as elevatr was using nrow(locations) to get number
    of features. It still does that as the default behavior, but if
    nrow(locations) returns a null, it uses length(locations) instead. Thanks for
    the catch, Gengping Zhu!
  • Documentation fix on get_elev_raster, now correctly reports that the function
    returns a raster, not points. Thanks @AndyBunn!
  • sfc objects getting missing in coercion in loc_check. Not anymore!
  • epqs occasionally times out, but subsequent hits usually work fine. Added a
    second hit when that happens and if that second one doesn't work then it
    assigns elevation to NA and throws a warning, instead of erroring
  • Was suppressing messages (and thus progress bar) on get_elev_pt src = "aws".
    Turned that off so progress of building the DEM is tracked.
  • proj_expand was using buffers to expand. Not great for geographic
    projections.Now it adds the expansion to the max and subtracts from the min to
    expand the bbox by the expand value. For raster retrievals with a single
    point the resultant raster will be significant smaller than previous
    (approximate 1km by 1km). Multiple points should see no difference. Thanks to
    WithRegards on SO for helping me find this.
  • In tests with spTransform, changed SRS_string to
    CRS(SRS_string=paste0("EPSG:", ll_prj$epsg)). Details in
    #56. Thanks to rsbivand and
    Fonteh-Bonaventure for helping me with this.
  • Raster locations were not returning correctly, that is now fixed.

Added Functionality

  • Added access to OpenTopography Global Bathymetry SRTM15+ V2.1 with
    src = "srtm15plus"
  • serial loop for get_epqs was taking a long time (API returns are slow), so use
    furrr::future_map_dbl to paralellize the gets. Defaults to 1 minus available
    cores.
  • Added argument to get_eqps to control serial vs parallel API calls. Defaults
    to serial for 35 or fewer points, but can be set to TRUE for force serial.
  • Added overwrite argument to get_elev_point() to check for existence of
    elevation and elev_units columns. If either exist and overwrite not TRUE then
    errors.
  • Updated progress bars to use the progressr package.
  • Converted all coordinate reference system handling to pull from locations or
    an SRS string. Should take care of running on older versions of PROJ

Other Minor changes

  • Removed message that reported out CRS, was too verbose and not necessarily
    useful.
  • Cleaned up message on units.

CRAN Release v0.3.3

08 Jan 19:00
Compare
Choose a tag to compare

Fixed several bugs, including one throwing errors when rasters used as input locations

New CRAN Release v0.3.0

20 Nov 20:38
Compare
Choose a tag to compare
new URL for epqs

Latest CRAN release

16 Mar 14:45
Compare
Choose a tag to compare

Comments

This submission fixes a bug in the get_elev_raster function. The API key for mapzen had a typo. This also required some changes to testing the package. The package is now tested locally and via travis-ci. The tests are skipped on CRAN. Additionally, this corrects a problem with vignettes on a prior submission.

Test Environments

  • Ubuntu 12.04, travis-ci, R Under development (unstable) (2017-03-13 r72338)
  • Windows Server 2012 R2 x64 (build 9600), Appveyor, R version 3.3.3 Patched (2017-03-06 r72327)
  • Red Hat 6.8, local, R version 3.3.2 (2016-10-31)

R CMD check results

  • No ERRORS or WARNINGS

Downstream dependencies

There are currently no downstream dependencies