-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lidar_digital_surface_model extent changed #399
Comments
My current workaround is: export to a raster of half the resolution.Than read the extent from the lidar file and manually reproject to the new affine, I calculate from the final resolution and extent. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When converting a single LIDAR file with
lidar_digital_surface_model
to a surface model, the extent seams not to be treated 100 % correct for my current example.The example is in the epsg 25832 region (although not included in the headers). The length is 1000 m. I want to export in a resolution of 1 meter.
When I overlay the DSM with the original point cloud in QGIS I see the following effect:
The extent of the LIDAR file is:
520999.9899999999906868,5399999.9900000002235174 : 522000.0000000000000000,5400999.9900000002235174
The extent of the DSM raster is:
520999.9899999999906868,5399999.9900000002235174 : 522000.9899999999906868,5400999.9900000002235174
I marked the difference.
This leads to the problems that, the mosaics, that are generated from files, generated this way, have gaps of 1 meter width.
When using lidar_digital_surface_model with
set_working_dir
and not single file names. It seems to close this gap, but takes 3 times longer, because it does not use the CPU to a full maximum. Most of the time a single core is used!The text was updated successfully, but these errors were encountered: