add a --fixbb option to compute an accurate bounding box #631
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should help with issue #429.
Bad (zero size) bounding boxes are generated by the Polycam iPhone app that can scan rooms with the inbuilt lidar.
It seems for such a trivial problem it shouldn't be necessary to invoke a whole different lasinfo app just to fix these 6 numbers, as advised in the error message.
https://github.com/potree/PotreeConverter/blob/develop/Converter/src/chunker_countsort_laszip.cpp#L247