ropensci/terrainr: terrainr v 0.5.0

Michael W. Mahoney, actions-userZenodo 2021 · DOI

Abstract

(This time for real -- this release matches the one published to CRAN) New features: A new function, <code>make_manifest</code>, now helps automate the import of terrain and imagery to Unity. It fully replaces <code>raster_to_raw_tiles</code> (see Deprecations below). Documentation updates are forthcoming. Deprecations: <code>raster_to_raw_tiles</code> is now deprecated and will be removed in a future release (no earlier than 2022). Use <code>make_manifest</code> instead. The method <code>get_tiles.list</code> is now deprecated and will be removed in a future release (unexported in Fall 2021, removed no earlier than 2022). Convert your list to an <code>sf</code> object instead. The <code>bbox</code> argument to <code>hit_national_map_api</code> is now documented as "An object from [sf::st_bbox]." This is a change from the earlier options of a length 2 list or terrainr_bounding_box object. Those methods are currently still supported, but undocumented; they will be removed in a future release (no earlier than 2022). Improvements and bug fixes: <code>get_tiles</code> no longer mangles data with projected coordinates (via a fix to the internal function <code>split_bbox</code>). If for some reason you want the old behavior back, set the new argument <code>projected</code> to <code>FALSE</code> while providing projected data. The documentation for <code>add_bbox_buffer</code> and <code>set_bbox_side_length</code> now specifies that they should only be used with geographic coordinate systems. If you use these functions with projected data, they will warn; this may be upgraded to an error in future versions. The README images are now of beautiful Hyampom, California, a somewhat more appealing vista than the original Mt Marcy scene. The "Import to Unity" vignette has been rewritten to use make_manifest, as has the overview vignette and other documentation. Typos in the message <code>merge_rasters</code> gives when using the fallback method have been fixed. <code>merge_rasters</code> gains an argument <code>force_fallback</code> which, if TRUE, will use the older, slower method for merging tiles. This is not recommended, but is useful for testing. Internal changes: The slow removal of all <code>terrainr_*</code> custom classes marches on! These classes should no longer be present in any user-facing, non-deprecated code; the only functions still relying on custom classes are internal utilities and the <code>split_bbox</code> function responsible for tiling <code>get_tiles</code> requests. <code>split_bbox</code> should now run faster, particularly for large tile sets, as some nested loops have been vectorized. Improvements to test coverage and CI.
BibTeX
@inproceedings{mahoney2021ropensci,
  author = {Michael W. Mahoney and actions-user},
  title = {{ropensci/terrainr: terrainr v 0.5.0}},
  booktitle = {Zenodo},
  year = {2021},
  doi = {10.5281/zenodo.5163741},
}

Loading related content...

Figure