The computational region of a LiDAR point file can be determined by scanning the file using the -s flag.
Optionally r.in.pdal creates an estimated vector footprint area map of the LAS file when using the footprint parameter (the footprint is generated by PDAL).
Since a new raster map is created during the binning, the binning of points depends on the computational region settings (extent and resolution) which is by default set to the extent of the LiDAR input file (see more about binning below). The resulting raster resolution can be specified with the parameter resolution.
r.in.pdal is designed for processing massive point cloud datasets, for example raw LiDAR or sidescan sonar swath data. It has been tested with large datasets.
For details concerning raster binning see the manual page of r.in.lidar.
# check metadata pdal info --summary lidar_raleigh_nc_spm_height_feet.las # scan extent and exit r.in.pdal input=lidar_raleigh_nc_spm_height_feet.las output=lidar_raleigh -s # scan extent (g.region style) and exit r.in.pdal input=lidar_raleigh_nc_spm_height_feet.las output=lidar_raleigh -s -g # import while aligning pixel geometry to existing "elevation" 10m res. raster map # specifying EPSG manually because SRS information is missing in this LAS file r.in.pdal input=lidar_raleigh_nc_spm_height_feet.las raster_reference=elevation \ resolution=10 output=lidar_raleigh method=mean proj_in=EPSG:3358 # optionally: footprint=lidar_raleigh_footprint # visualize d.mon wx0 g.list vector d.rast lidar_raleigh d.vect streets_wake # analyse differences between DEM and rasterized point cloud # LAS files come with height in US feet units r.mapcalc "diff = elevation - lidar_raleigh * 0.3048006096012192" r.univar -e diff
Documentation: Markus Neteler, mundialis GmbH & Co. KG
Last changed: $Date$