Closed ouroukhai closed 10 months ago
It was a mistake on my end regarding the chosen resolution for creating the chm file. By increasing the pixel size, the number of NA values, in the treeID variable, was decreased.
Your problem is resolved?
I still Observe some NA values but not in the same frequency as before. For reference, I work on ~9.5 points/m^2 and I resolve the problem by going up to 1m x 1m pixels. If the only reason that NA values are introduced is because of empty pixels, then I am okay. I guess the 9.5 points density is estimated and not exact, so having some empty pixels is expected? It is really strange though to see whole trees classified as NAs.
If the CHM has NA i guess the map of the trees will have NAs at the same locations.
Ok thank you I think I have my answer
Hello and good morning,
I created the attached file by using the following code (fws ais mentioned in the sequel):
I have also attached the chm file that I used for the separation of tree tops. The fws is used as a draft function to reproduce the bug, as I have the same problem with other functions. It can be found in the following code block:
My problem is that the algorithm returns NA values of treeID on clearly high-vegetation trees. I saw no mention in the documentation of why the algorithm would return NA values; that's why it troubles me. files.zip Note: The file is a clipped circle (150m radius, xcenter = 309300, ycenter = 4322500) on the original file to avoid upload size issues. The chm is a 1kmx1km region containing the circle. Data come from NEON 2019 UKFS region. Please let me know if the original file is needed to add a link. Thank you for your time!