Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking PotreeConverter export to OGC 3D Tiles #671

Open
jo-chemla opened this issue Dec 20, 2024 · 0 comments
Open

Tracking PotreeConverter export to OGC 3D Tiles #671

jo-chemla opened this issue Dec 20, 2024 · 0 comments

Comments

@jo-chemla
Copy link

PotreeConverter v2 is probably the fastest pointcloud tiler I've come across. It would be great for it to support tiling a (eventually set of) pointcloud to the OGC 3D-tiles specification. Note there are already nice pointcloud tilers to 3D-tiles alternatives like mfbonfigli/gocesiumtiler and py3dtiles, although lowest throughput of M-points-per-second.

There are also single-file OGC 3D-tiles tilesets standard formats, akin to the v2 vs v1 potree format - quick discussion about .3dtiles vs .3tz here NASA-AMMOS/3DTilesRendererJS#722

Previous OGC 3D-tiles versions stored tiles as custom pnts tile files (~glTF wrapper), but version 1.1 of the specification simply stores them as glTF POINTS primitive mode. Compression is made available by using glTF KHR khronos extensions - like presented by Cesium team in this thread about 3D gaussian-splats, like EXT_mesh_quantization + EXT_meshopt_compression

I'm opening this issue thread to gauge whether this would be a direction you'd be interested in, as well as tracking interest by the community. Eventually someone could tackle that challenge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant