Get DEMs and orthoimagery from the USGS National Map, georeference your images and merge rasters, and visualize with Unity 3D
More tests are flagged to skip on CRAN, or when run offline
georeference_overlay
should give fewer useless warnings
HRO
, which provides orthoimagery for
non-CONUS US domains, and USGSNAIPImagery
, which only returns NAIP
(whereas USGSNAIPPlus
, the default for ortho
, will use HRO
where
appropriate).geom_spatial_rgb()
about "dropped aesthetics".govunits
test.ggplot2
now requires a minimum of 3.4.0merge_rasters
no longer warns that options aren't respected when using
the fallback method before immediately passing said options to gdalwarp
.rlang
with string interpolation
via glue
.rlang
and glue
have been added to Importsraster
now requires a minimum version of 3.5-19.make_unity
is a new function which uses the new unifir
package to
automatically create Unity scenes, no clicking necessary.make_manifest
, transform_elevation
, and transform_overlay
no longer
error when providing non-standard side lengths; they now warn as intended.make_manifest
, transform_elevation
, and transform_overlay
should no longer give warnings about nodata values in most cases.
being clamped to 0.transform_overlay
(and by extension, every Unity overlay importer) now
tries to automatically guess the scale of the input raster. Values under
1 are scaled from 0-1, integers under 255 are scaled 0-255, and integers
under 65535 are scaled 0-65536. The main effect of this is more realistic
coloring when importing terrain. Floats above 1 won't be affected.terra
is now included as an Import (had been recursively imported
through raster
previously).raster
and rgdal
are now in Suggests (used temporarily in
Raster*
methods for get_tiles
and add_bbox_buffer
, until the new
version of raster
hits CRAN).raster_to_raw_tiles
is now a thin wrapper around the functions
transform_overlay
and transform_elevation
. It is no longer tested;
it will be removed entirely in the next release (see deprecation notice
in terrainr 0.5.0).transform_elevation
and transform_overlay
, should
now provide raster transformation functions that were possible with
raster_to_raw_tiles
but not with make_manifest
. As an added bonus, the
internal code to handle tiling is now dramatically simpler.make_manifest
will now overwrite any file at importer_path
, in line
with documented behavior. Previous versions would never overwrite
importer_path
.merge_rasters
' fallback method now runs much fastergdalUtils
has been removed from dependencies following CRAN directionsrgdal
is now an explicit dependency (had previously been imported via
gdalUtils
)ecosystems
, has been added to get_tiles
and
hit_national_map_api
.merge_rasters
gains an argument, overwrite
, which allows you to
specify whether or not to overwrite output_raster
if it exists. Previous
versions expected you to pass "-overwrite" to options
. If a file exists
at output_raster
and overwrite
is FALSE, merge_rasters
will throw an
error.sf
now has a minimum dependency of 1.0-5, to take advantage of an
upstream bug fix (relating to merge_rasters
overwrite)(This time for real -- this release matches the one published to CRAN)
make_manifest
, now helps automate the import of terrain
and imagery to Unity. It fully replaces raster_to_raw_tiles
(see
Deprecations below). Documentation updates are forthcoming.raster_to_raw_tiles
is now deprecated and will be removed in a future
release (no earlier than 2022). Use make_manifest
instead.get_tiles.list
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 sf
object instead.bbox
argument to hit_national_map_api
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).get_tiles
no longer mangles data with projected coordinates (via a
fix to the internal function split_bbox
). If for some reason you want
the old behavior back, set the new argument projected
to FALSE
while
providing projected data.add_bbox_buffer
and set_bbox_side_length
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.merge_rasters
gives when using the fallback method
have been fixed.merge_rasters
gains an argument force_fallback
which, if TRUE, will
use the older, slower method for merging tiles. This is not recommended,
but is useful for testing.terrainr_*
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 split_bbox
function responsible for tiling get_tiles
requests.split_bbox
should now run faster, particularly for large tile sets, as
some nested loops have been vectorized.(Note: this is a pre-release to get a Zenodo DOI; it may not match the version published to CRAN)
make_manifest
, now helps automate the import of terrain
and imagery to Unity. It fully replaces raster_to_raw_tiles
(see
Deprecations below). Documentation updates are forthcoming.raster_to_raw_tiles
is now deprecated and will be removed in a future
release (no earlier than 2022). Use make_manifest
instead.get_tiles.list
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 sf
object instead.bbox
argument to hit_national_map_api
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).get_tiles
no longer mangles data with projected coordinates (via a
fix to the internal function split_bbox
). If for some reason you want
the old behavior back, set the new argument projected
to FALSE
while
providing projected data.add_bbox_buffer
and set_bbox_side_length
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.merge_rasters
gives when using the fallback method
have been fixed.merge_rasters
gains an argument force_fallback
which, if TRUE, will
use the older, slower method for merging tiles. This is not recommended,
but is useful for testing.terrainr_*
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 split_bbox
function responsible for tiling get_tiles
requests.split_bbox
should now run faster, particularly for large tile sets, as
some nested loops have been vectorized.