-
Notifications
You must be signed in to change notification settings - Fork 161
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
IndividualTreeDetection ignores the min_height parameter #349
Comments
This is odd for sure. Are you able to send me a sample data set for which you encountered this issue so that I can do some testing and hopefully figure out the cause for the problem? Just as a side note, I'm a little surprised that you're using WBT for Python scripting still given you have WbW. I find myself writing all my Wb-based scripts in WbW these days. |
Here is a link to my data. The reason why I am not using WbW for this is that I am doing this for someone else. The code will live in a docker image that others can use and I am not comfortable using my WbW license like that. |
Thanks for providing the data. Have you normalized your input point cloud using the NormalizeLidar tool beforehand? Otherwise the point z values are elevations and not height above ground, as you may desire. That makes perfect sense why you'd be using WbT for this rather than WbW. I was just worried if there was some deficiency that you might have found in WbW as to why this application wouldn't be better suited to it. But I guess that makes a lot of sense. Thanks for sharing. |
This data is the raw version of my data. sorry for not mentioning that. I did use the normalise lidar tool before applying the individual tree detection tool. The code is in the original message above. First I created a DEM from the laz file and then used that to normalize the data to elevation above ground. Finally I used the normalised data as input to the individual tree detection algorithm. |
Silly me, I should have noticed that. |
I did some more tests and seems to be related to setting a working directory instead of specifying an input file. This works:
But not this:
I want to use the excellent parallel processing and edge "fixing" that your lidar tools use when working with multiple files. |
That was the missing piece for figuring out the issue. Turns out that I was missing an if statement to filter out points with z < min_height for the batch processing branch. I've fixed it now and pushed to the repo. |
The output shapefile from IndividualTreeDetection contains points with very low values and sometimes even negative values even when the min_height parameter is set.
Here is my code:
The text was updated successfully, but these errors were encountered: