Max depth in output does not correspond with minimum depth parameter #18
Unanswered
AnneliesBroeckx
asked this question in
Q&A
Replies: 4 comments 6 replies
-
For 100 cm (1m), it should probably be |
Beta Was this translation helpful? Give feedback.
1 reply
-
Keep in mind that |
Beta Was this translation helpful? Give feedback.
1 reply
-
Could you share a small subset of your dataset for debugging? |
Beta Was this translation helpful? Give feedback.
3 replies
-
This seems to be a bug. The |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Many thanks to develop this package to detect nested depressions based on a DEM!
I have tested this out with a DEM (resolution 5 m) and height in cm. These were my parameters:
So I have set the minimum depth parameter equal to 100 cm. When I run the script in Python and view the output of the depressions_info.csv file, in order to examine all the detected depressions, I notice that the meximum depth of each polygon does not always correspond with the set minimum depth parameter of 100 cm. Many depressions (376 out of 452) have a maximum depth that is smaller than 100 cm. How is this possible?
I have used the example code (lidar-master\lidar\example.py).
Many thanks for your anwser!
Beta Was this translation helpful? Give feedback.
All reactions