A LAScatalog
object is a representation of a set of las/laz files, since a computer cannot load
all the data at once. A LAScatalog
is a simple way to manage the entire file by reading only
the headers. A LAScatalog
enables the user to process a large area or to selectively clip data
from a large area without loading the large area itself. A LAScatalog
can be built with the
function catalog. Also a LAScatalog
contains extra information that enables users to
control how the catalog is processed.
data
data.table. A table representing the header of each file.
crs
A CRS object.
cores
integer. Numer of cores used to make parallel computations in compatible functions that
support a LAScatalog
as input. Default is 1.
buffer
numeric. When applying a function to an entire catalog by sequentially processing sub-areas (clusters) some algorithms (such as grid_terrain) require a buffer around the area to avoid edge effects. Default is 15 m.
progress
logical. Display an estimation of progress while processing. Default is TRUE.
by_file
logical. This option overwrites the option tiling_size
. Instead of processing
the catalog by arbitrary split areas, it forces processing by file. Buffering is still available.
Default is FALSE.
tiling_size
numeric. To process an entire catalog, the algorithm splits the dataset into several square sub-areas (clusters) to process them sequentially. This is the size of each square cluster. Default is 1000 (1 km^2).
vrt
character. Path to a folder. In grid_*
functions, for large outputs, the functions
can return a lightweight virtual raster mosaic (VRT).
opt_changed
Internal use only for compatibility with older deprecated code.