bounding box check using min/max, not scaled value in [0,1]

[fq]

I have a LAZ file being rejected due to the bounding box check. I did verified the bounding box using lasinfo which shows no point is outside bounding box.

The bounding box check code did not compare xyz to the original min/max, instead it compared scaled ux/uy/uz to [0,1]. Due to the double decimal precision, a tiny error could be introduced and make ux>1 causing converter reject the LAZ file. Even the x is inside the original min/max, and no error reported by lasinfo.

It would make sense to check the bounding box to use min/max to avoid any decimal precision error introduced using the scaled values.

[gibtree]

I had the same issue and successfully used this code to get around it.