Using LiDAR in SURE
Integrating LiDAR into the SURE 2.5D and 3D workflows can greatly improve the quality of the final products (DSM, True Ortho, 2.5D Mesh, 3D Mesh). In this page we demonstrate how to upload your LiDAR data into SURE in order to complement the image data for a more robust solution. To learn more about the benefits of using LiDAR in SURE please visit our LiDAR Integration in SURE page.
LiDAR data can be provided within the SURE Project definition wizard or through the CLI, as well as in custom workflows using either the 2.5D Tool or the Command Line Modules.
Include LiDAR in SURE Project Definition
The LiDAR point clouds are provided by specifying the parent directory of the .las/.laz files. Alternatively, the user can specify a list text file with each entry pointing to the individual LiDAR .las/.laz files.
The LiDAR Trajectory file is provided as the path to the respective file.
Lidar can also be added through the CLI. See additional information at Project Setup article.
Include LiDAR in SURE Custom Workflows
Include LiDAR in Command Line Modules
Processing with LiDAR
If LiDAR data is provided as input during the project generation in SURE (versions post 3.0), then LiDAR will be automatically integrated into the workflow by default. Thus, the user does not have to change any other setting regarding the processing of the new input. It is also possible to turn off the usage of LiDAR by disabling the ‘Use Lidar data’ in the GUI in the Advanced Settings dialog in the GUI or by using the --no-lidar-clouds command line flag.
It is recommended that the LiDAR point clouds are tiled in a scheme similar to the one employed in the SURE project. During the DSM step and the 3D Mesh step, the data is processed per tile. As such, SURE will load in memory all the necessary files that contain data which overlap with the currently processed tile. If the LiDAR data usage is enabled, this will include the DIM data, as well as the LiDAR data. Therefore the most optimal configuration - with minimum impact on processing time - will have the LiDAR point clouds tiled exactly as the DIM data. See also Georeferencing and Tiling.
The principle is illustrated below:
In the example below, it can be seen that the LiDAR Point Cloud Strips are much larger than the Area of Interest and thus SURE would have to load for every DIM tile the entire LiDAR strip.
Source: Leica - Bordeaux dataset
If the user would clip the LiDAR strips in a way that it suits the size of the DIM tile, then the processing of the DSM / Mesh will run faster (also less disk space will be used if Distributed processing is enabled). In the example below the LiDAR strips were clipped and exported as 8 individual smaller parts as the size of the DSM tile. Then a list containing the paths to these clouds was created and used as input in SURE.