Replies: 3 comments
-
Without reproducing I'd say that your files have invalid CRS that were parsed anyway when CRS were handled with Please share a link a problematic file (not to shaded DTMs) so I can investigate futher. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This link will hopefully allow you to download two of the tiles from the 2016 King County lidar acquisition. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Bug confirmed #561 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, when running the following code:
on lidar tiles downloaded from the Washington DNR lidar portal (https://lidarportal.dnr.wa.gov/) I am getting this error:
I had been using
grid_terrain
and I am trying to update workflows per the suggestions in the lidR documentation however,grid_terrain
works and I can't seem to getrasterize_terrain
to work on aLAScatalog
. Am I missing some additional input required forrasterize_terrain
?I have tried adjacent tiles from 3 different acquisitions on two different machines and I have gotten the same error. I have run this code in the past (using 'grid_terrain') with no issues at all. I assume that perhaps with the recent updates to lidR that something has changed? I also assume that the error is related to user-defined information included in the laz header. To reproduce the error you should be able to download any two adjacent tiles from the 2016 king county lidar aquistion over Seattle.
Beta Was this translation helpful? Give feedback.
All reactions