get_cafri_data.Rd
Retrieve spatial data from the CAFRI database.
An `sf` object representing the area to pull data for. Note that data is pulled for the full bounding box around `data`, not clipped to the shape.
The name of the data product to retrieve. See [autodog](https://github.com/cafri-labs/autodog) for a list of available Product/Nicknames.
The EPSG code for the CRS of your `sf` object. Default is to assume the CAFRI standard CRS, currently the non-EPSG value 900914.
The name for a region to retrieve data for. Note that if `region` is supplied, `data` is ignored. See [autodog](https://github.com/cafri-labs/autodog) for a list of available region names.
The file indices to retrieve data for. Note that if `indices` is supplied, both `region` and `data` are ignored.
The file name to save the data to.
The current IP or URL for the Labrador service - intended for development purposes only.
The current port used for the Labrador service - intended for development purposes only.
Options passed to [terrainr::merge_rasters] (which will then in turn be passed to [sf::gdal_utils] and then to `gdalwarp`). Note that this may cause your download to fail if downloading large products -- it is currently recommended to not provide options when downloading CHMs.
Will only overwrite existing path if TRUE.
logical or 'buildvrt': should the tiles be merged or downloaded individually? For large downloads, merging can be slow and so FALSE or 'buildvrt is recommended, but will result in many tiles. 'buildvrt' will keep the individual tiles, but construct a virtual raster that allows users to treat the mosaic of tiles as an individual raster.
`filename`, invisibly.