`py3dtiles` merge screws up correctly geolocated tilesets - Githubissues

PermafrostDiscoveryGateway / viz-points

Python package for post-processing point-cloud data for 3D visualization

Apache License 2.0

0 stars 1 forks source link

`py3dtiles` merge screws up correctly geolocated tilesets #8

Closed iannesbitt closed 1 year ago

iannesbitt commented 1 year ago

To reproduce:

Start with two perfectly good tilesets in subfolders
- ./3dtiles/ts1/tileset.json, ./3dtiles/ts2/tileset.json
- Each displays in Cesium correctly on its own
Run py3dtiles merge or py3dtiles.merger.merge_from_files(['./3dtiles/ts1/tileset.json','./3dtiles/ts2/tileset.json']) on both tileset.jsons
- Get ./3dtiles/tileset.json
- Merged dataset ends up somehow inside the earth model, in the wrong place

Theories:

boundingVolume or transform calculations are done incorrectly

Things to try:

Messing around with the existing merge function
A different merge function
Merge using different software
Attempt to merge using my own code
Reproduce steps of merge function to find error location and correct; offer PR to Oslandia

iannesbitt commented 1 year ago

Adding force_universal_merger=True to merge_from_files() seems to fix the issue...documentation is nil though so I have very little idea what I just did...

Here's a screenshot showing a merger of two tilesets, one offset z=-10 m from the other: