LAScatalog class is a representation in R of a file or a set of las files not loaded in memory. Indeed, a regular computer cannot load the entire point cloud in R if it covers a broad area. For very high density datasets it can even fail loading a single file (see also the “LAS formal class” vignette). In lidR, we use a
LAScatalog to process datasets that cannot fit in memory.
LAScatalog inherits a
SpatialPolygonsDataFrame. Thus, it has the structure of a
SpatialPolygonsDataFrame plus some extra slots that store information relative to how the
LAScatalog will be processed.
data of a
LAScatalog object contains a
data.frame with the most important information read from the header of .las or .laz files. Reading only the header of the file provides an overview of the content of the files very quickly without actually loading the point cloud. The columns of the table are named after the LAS specification version 1.4
The other slots are well documented in the documentation ?`LAScatalog-class` so they are not described in this vignette.
LAScatalog is formally a SpatialPolygonsDataFrame although its purpose is not to manipulate spatial data in R. The purpose of a
LAScatalog is to represent a set of existing las/laz files. Thus a
LAScatalog cannot be modified because it must be related to the actual content of the files. The following throws an error:
Obviously it is always possible to modify an R object by bypassing such simple restrictions. In this case the user will break something internally and a correct output is not guaranteed.
However it is possible to add and modify the attributes using a name that is not reserved. The following is allowed:
Users commonly report bugs arising from the fact that the point cloud is invalid. This is why we introduced the function
las_check() to perform an inspection of the
LAScatalog objects. This function checks if a
LAScatalog object is consistent (files are all of the same type for example). For example, it may happen that a catalog mixes files of type 1 with files of type 3 or files with different scale factors.
las_check(ctg) #> #> Checking headers consistency #> - Checking file version consistency... ✓ #> - Checking scale consistency... ✓ #> - Checking offset consistency... ✓ #> - Checking point type consistency... ✓ #> - Checking VLR consistency... ✓ #> - Checking CRS consistency... ✓ #> Checking the headers #> - Checking scale factor validity... ✓ #> - Checking Point Data Format ID validity... ✓ #> Checking preprocessing already done #> - Checking negative outliers... #> ⚠ 2 file(s) with points below 0 #> - Checking normalization... no #> Checking the geometry #> - Checking overlapping tiles... #> ⚠ Some tiles seem to overlap each other #> - Checking point indexation... no
las_check when applied to a catalog does not perform a deep inspection of the point cloud unlike when applied to a
LAS object. Indeed the point cloud is not actually read.
lidR provides a simple
plot() function to plot a
mapview = TRUE displays the catalog on an interactive map with pan and zoom and allows the addition of a satellite map in the background. It uses the package
mapview internally. It is often useful to check if the CRS of the file are properly registered. The epsg code of the las file appears to be often incorrect, according to our own experience.
Being a SpatialPolygonsDataFrame, the function
sp can be used on a
LAScatalog to check the content of the files. In the following we can immediately see that the catalog is not normalized and is likely to contain outliers:
Most of lidR functions are compatible with a
LAScatalog and work almost like with a single point cloud loaded in memory. In the following example we use the function
grid_metrics() to compute the mean elevation of the points. The output is a continuous wall-to-wall RasterLayer. It works exactly as if the input was a LAS object.
However, processing a
LAScatalog usually requires some tuning of the processing options to get better control of the computation. Indeed, if the catalog is huge the output is likely to be huge as well, and maybe the output cannot fit in the R memory. For example,
normalize_height() throws an error if used ‘as is’ without tuning the processing options. Using
normalize_height() like in the following example the expected
output would be a huge point cloud loaded in memory. The lidR package forbids such a call:
Instead, one can use the processing option
opt_output_files(). Processing options drive how the big files are split in small chunks and how the outputs are either returned into R or written on disk into files.
Here the output is not a point cloud but a
LAScatalog pointing to the newly created files. The user can check how the catalog will be processed by calling
summary(ctg) #> class : LAScatalog (v1.2 format 1) #> extent : 883166.1, 895250.2, 625793.6, 639938.4 (xmin, xmax, ymin, ymax) #> coord. ref. : NAD83 / BC Albers #> area : 111.1 km² #> points : 696.54 million points #> density : 6.3 points/m² #> num. files : 62 #> proc. opt. : buffer: 30 | chunk: 0 #> input opt. : select: * | filter: #> output opt. : in memory | w2w guaranteed | merging enabled #> drivers : #> - Raster : format = GTiff NAflag = -999999 #> - LAS : no parameter #> - Spatial : overwrite = FALSE #> - SimpleFeature : quiet = TRUE #> - DataFrame : no parameter
plot function can displays the chunks pattern i.e. how the dataset is split into small chunks that will be sequentially processed
From lidR v2.2.0 is it possible to flag some file that will not be processed but that will be used to load a buffer if required. In the following example only the central files will be processed but the others one were not removed and they will be used to buffer the processed files.
Load a catalog. Process each file sequentially. Returns a RasterLayer into R.
Load a catalog. Process each file sequentially. For each file write a raster on disk named after the name of the processed files. Returns a lightweight virtual raster mosaic.
Load a single big file too big to be actually loaded in memory. Process small chunks of 100 x 100 meters at a time. Returns a RasterLayer into R.
Load a catalog. Process small chunks of 200 x 200 meters at a time. Each chunk is loaded with an extra 20 m buffer. Returns a Shapefile into R.
This is forbidden. The output would be too big.
Load a catalog. Process small chunks of 500 x 500 meter sequentially. For each chunk write a laz file on disk named after the coordinates of the chunk. Returns a lightweight
LAScatalog. Note that the original catalog has been retiled.
Load a catalog. Load a shapefile of plot centers. Extract the plots. Returns a list of extracted point clouds in R.
Load a catalog. Load a shapefile of plot centers. Extract the plots and immediately write them into a file named after the coordinates of the plot and an attributes of the shapefile (here
PLOTID if such an attribute exists in the shapefile). Returns a lightweight