You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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#722Previous 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_compressionI'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.
The text was updated successfully, but these errors were encountered: