E57 bounding box inconsistencies

[rapper]

I have an E57 file provided by others which contains two scans. When viewing it in CC the bounding boxes are correct (they envelop the points). However, when using another tool the bounding boxes don't envelop their points. I'm trying to determine the reason for the differences to avoid such issues in the future. I believe the other tool may be reading the scan bounding box extents and offsets from the file's XML data.
My question is, does CC ignore the provided bounds and offsets data, and instead read all the points to determine the bounding boxes? If so, that would explain why CC gets it right and the other tool doesn't (although it wouldn't explain why the data is wrong in the E57's XML data).

[rapper]

Is it known how CloudCompare gets its bounding box from the E57 file? Is it from the file's summary data or by iterating all points?

[daniel]

Oh yes, you are right, the bounding-box is computed by CC (by iterating over the points). We don't trust the one in the description.