Make sure PDAL filtering and Co-registration/ DEM production can be executed separately

[naniciafone]

We want the different components of IRC to be independently accessible so that the user does not need to run the full workflow if it’s not needed. Primarily, that looks like (1) PDAL point cloud filtering and segmentation (https://github.com/cryogars/ice-road-copters/blob/main/scripts/laz2dem.py) and (2) co-registration and production of final GeoTIFFS. This may just involve making sure the python scripts are not broken (I’ve had issues running laz2dem.py independently) and updating the readme to point the user to these scripts. [ ] Use branch (https://github.com/cryogars/ice-road-copters/tree/issue-24-PDAL/DEM)

Tasks

• [ ]

[naniciafone]

I think the best way to achieve the first part of this- enabling the user to run IRC up to co-registration- would be to have IRC stop here, right before laz_align-

ice-road-copters/scripts/ice-road-pipeline.py

Line 155 in ac5cade

.

I need to create bare earth maps from our recent snow off surveys, which is underscoring the utility of being able to run DEM creation and co-registration separately. I've been advised that it's best to filter / segment the reference map in the same way the snow-on map is filtered and segmented.

[naniciafone]

Using ice-roads to mosaic, filter, classify, and create canopy LAZ and grounds LAZ/TIF is now possible with issue-24 branch