Closed kring closed 3 years ago
See https://github.com/CesiumGS/3d-tiles/pull/487 for a recent addition to the spec to specify geometric error at per-tile granularity.
Also check out https://github.com/CesiumGS/3d-tiles/tree/3d-tiles-next/specification/Metadata/Semantics - there are ways to override the default implicit tiling bounding volumes using per-tile metadata.
https://github.com/CesiumGS/3d-tiles/tree/3d-tiles-next/extensions/3DTILES_implicit_tiling
I think this extension should integrate pretty nicely with the implicit tiling support already in cesium-native. In short:
3DTILES_implicit_tiling
extension on the tile. Such a tile is known as an "implicit root".ImplicitTilingContext
for it and arrange for the tile's content URI to be the root subtree URI.ImplicitTilingContext
needs to be extended to capture more of the extension. In particular, it needs to capture the subtree URI,subtreeLevels
, andmaximumLevel
.availableTileRectangles
of theTileContentLoadResult
. Or - more likely - we'll need to define an alternative way to describe availability if the extension's availability can't be easily presented asavailableTileRectangles
. The availability inTileContentLoadResult
gets copied into theImplicitTilingContext
inTile::update
.That's a really quick and dirty summary, but hopefully enough to get you started @nithinp7 and I'll try to flesh it out a bit more tomorrow.