Page 1 of 1
withheld bit ignored
Posted: Sat Jun 01, 2019 12:00 am
by bayesmap
Hi
It looks like the withheld bit is ignored when reading a LAS file.
The decompose option is checked and the log window displays "withheld flag values are the same(0)"
lasinfo reports " +-> flagged as withheld: 145" so the bits are set.
using version 2.10.2 on mac OS
Any ideas?
Andre
Re: withheld bit ignored
Posted: Sun Jun 02, 2019 6:52 am
by daniel
Can you share the file with us? (admin [at] cloudcompare.org)
Re: withheld bit ignored
Posted: Wed Jun 12, 2019 7:00 pm
by bayesmap
Here is a scanline.
I set the synthetic, keypoint and withheld to 1 for negative scan angle, 0 otherwise.
Corresponding LAS classification 20 and 0.
They show up on lasinfo but all 3 are ignored in CloudCompare (classification works fine).
histogram of classification of points:
1382 never classified (0)
1410 Reserved for ASPRS Definition (20)
+-> flagged as synthetic: 1410
+-> flagged as keypoints: 1410
+-> flagged as withheld: 1410
Re: withheld bit ignored
Posted: Fri Jun 14, 2019 3:44 pm
by daniel
Thanks for the data.
I was able to fix the bug and even improve the LAS I/O filter a little bit (it now handles the Offset flag for instance if you have point formats >= 6).
You can download the latest 2.11.alpha version (online).
Thanks for the feedback!
Re: withheld bit ignored
Posted: Sun Jan 10, 2021 3:04 am
by bayesmap
Hi,
I just tried the latest build on mac (2.11.1) and it still ignores the withheld flag.
The same version on linux works fine on the same file. So I guess the LAS I/O is somewhat different on mac?
Thanks,
André
Re: withheld bit ignored
Posted: Sun Jan 10, 2021 9:58 am
by daniel
Yes, and it's probably not the right version? Or have you compiled it yourself?
Re: withheld bit ignored
Posted: Wed Jan 20, 2021 1:52 am
by bayesmap
I used the latest version available for mac (2.11.1) downloaded from asmaloney.com
I can see this in the release notes for 2.11.2
LAS 1.3 or 1.4 (LASlib): Classification values and flags were not always loaded or saved properly
so I guess the mac version is too old and this fix is not available...