3D tiles and textured DSM : performance feedback?

Dear all,

As part of a state of art about Textured Digital Surface Model (3D geospatial modeling) formats, we have identified some candidates formats whose 3Dtiles.
As far as i understand, 3Dtiles have several capacities and supports : texture, semantic, metadata mecanism, Level od Detail,etc.

I 'm looking for information regarding performances and limitations 's 3Dtiles (tests, implementations feedback) about especially:

  1. data access

  2. data storage

  3. volumetry/data volume (semantic, mesh geometries, textures,)

  4. Data compression

  5. Interchange/diffusion data (Client-Server architecture 's adaptibilities /bandwith optimization,etc.)

  6. Interoperability

  7. Display/rendering

  8. Ability to associate TIN/Mesh (as 3D model) with Points clouds ?

  9. Is there a roadmap 's 3Dtiles in order to know futur works/expected improvements (qgis GIS 's support especially?)

If you have any material (information, feedbacks, tests) ? Thanks a lot to throw light for us.

With kind regards.

Welcome to the Cesium community!

The best way to stay up to date with progress in the 3D Tiles ecosystem is by following our blog (specifically the 3D Tiles category: https://cesium.com/blog/categories/3dtiles/) for updates in the growing ecosystem and support in 3rd party tools, and the 3D Tiles repository for any updates or future work on the specification itself: https://github.com/CesiumGS/3d-tiles

There are a few benchmarks on compression/storage here:

Let me know if you have any specific questions about use cases you have for 3D Tiles. You may find the code examples on Sandcastle useful, for example here’s one showing a point cloud of Montreal on top of 3D terrain: https://sandcastle.cesium.com/index.html?src=Montreal%20Point%20Cloud.html&label=New%20in%201.70