You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you very much for the Python API to your tools. We do tree species identification so we need to generate canopy height models using lidar DTM and DSM (I would love to be able to subtract the results of the two lidar_tin_gridding operations without saving the intermediate rasters but I digress!)
Is there a way to set the projection on the output rasters to the one from the input las files? I searched in the manual but could not find any information.
The text was updated successfully, but these errors were encountered:
@jfprieur I wanted to let you know that this is on my radar. Projections, particularly moving projection information from LiDAR to Raster to Vector datasets, is a bit challenging without the use of either raster (GDAL) or map projection (PROJ) libraries. The design of WhiteboxTools restricts my ability to easily incorporate these libraries into Whitebox development. As such, I have to re-implement these types of things, which is a bit of an enormous undertaking. I am aware of the need to improve support for projection information and hope to focus some development effort in this area in the future. It's a lot for one person to do though and my to-do list seems to be never ending! I'll come back to this issue when there is progress made. Thanks for raising the issue.
Hello,
First of all thank you very much for the Python API to your tools. We do tree species identification so we need to generate canopy height models using lidar DTM and DSM (I would love to be able to subtract the results of the two lidar_tin_gridding operations without saving the intermediate rasters but I digress!)
Is there a way to set the projection on the output rasters to the one from the input las files? I searched in the manual but could not find any information.
The text was updated successfully, but these errors were encountered: