LiDAR input parameters

LiDAR in SURE

Input

 LiDAR point clouds are being part of the SURE workflow and currently the following requirements have to be met:

  • The user has the duty to check beforehand that the imported LiDAR data is well oriented and it lies in the same coordinate system as the imagery.
  • BETA version – currently, SURE is able to read data up to LAS Version 1.3 and will write point cloud data in LAS Version 1.2
  • The LiDAR data input can be .las  or .laz
  • SURE reads the first return from the LiDAR data (recommended for the user to be use as input) 
  • If the LiDAR data contains the classification of noise points as noise, then SURE will ignore those points. Else the LiDAR input data doesn't have to be classified into other classes such as Ground/Vegetation/etc.
  • For an optimized performance: the input LiDAR data should be clipped/tiled in accordance to the desired Tile size of the DSM, recommended for large data sets as well as for small ones.


Output sample overview 

DIM & LiDAR Point CloudsDSM based only on DIMDSM based on DIM and LiDAR

Source: Leica - Bordeaux dataset



LiDAR workflow optimization

Default Value: Enabled

If LiDAR data is provided as input during the project generation in SURE 3.0 - (BETA version), then LiDAR will be automatically integrated in the workflow by default. Thus the user does not have to change any other setting regarding the processing of the new input.

For an optimized performance the input LiDAR data shall be tiled in relation to the tile size of the DSM.  

Not Recommended  

                                                 Recommended

Not recommended

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 DSM tile the entire LiDAR strip.

For faster processing

If the user would clip the LiDAR strips in a way that it suits the size of the DSM tile then the processing of the DSM/TrueOrtho/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.






Source: Leica - Bordeaux dataset



CLI parameters
In the DSM/3DMesh Modules the user can input the LiDAR data accordingly by typing the commands:

--lidar - Path to the LiDAR point clouds
--no_lidar - Disable usage of LiDAR data (modifies control files)

Key Features


Related topics:

Las format definition 

Project Setup