Closed mcoghill closed 1 year ago
Fixed. unormalize_height()
now cleans the VLRs. For the documentation there is a good reason why it is not documented. It seems I did it on purpose but I don't know why. I will consider documenting it back (it was documented in the past)
In my workflow, I'm working with a large LAS catalog to segment trees. The process for doing this involves normalizing the LAS tiles, then segmenting the trees, and then unnormalizing the tiles at the end. Because of the steps involved, I have to specify in the
normalize_height()
function theadd_lasattribute
argument to be TRUE because if it's not and a LAS tile is saved, then I cannot unnormalize it later on. What I am finding is when theadd_lasattribute
argument is set to TRUE, and then the tile is unnormalized and then you try to write the tile to a new file, an error occurs due to extra bytes in the header. Here is a reproducible example:My current workaround is to put the unnormalization step for my catalog into a custom
catalog_apply
function which manually removes the extra bytes from the header after the unnormalization. I am wondering if this behaviour could be modified in theunnormalize_height()
function so that the header information is being properly updated to remove the extra bytes that are added due to theadd_lasattribute = TRUE
argument in thenormalize_height()
function?Additionally, would it be possible to add documentation to the
normalize_height()
function such that it includes theadd_lasattribute
andWdegenerated
arguments? I noticed these get passed on as...
in the function itself, but they don't show up in the help file when called with?normalize_height
.Many thanks for your help!