Sean Lilley

Per-feature bounding volumes could be stored in feature metadata in [EXT_mesh_features](https://github.com/CesiumGS/glTF/tree/3d-tiles-next/extensions/2.0/Vendor/EXT_mesh_features) with new semantics

Closed this a bit hastily. The low-level capability is there, but a new feature semantic would need to be defined in the [3D Metadata Semantics Reference](https://github.com/CesiumGS/3d-tiles/tree/main/specification/Metadata/Semantics) or some other semantic...

> all tile contents share the same Property Table buffer I've been thinking about this is well for global feature ids https://github.com/CesiumGS/3d-tiles/issues/265. Ideally we'd want to have spatial locality of...

Here's a few workflows I've been thinking about: * **Export workflow**: USD is exported as 3D Tiles with no common spatial hierarchy between the two. The layers are "baked" into...

Also CC https://github.com/CesiumGS/3d-tiles/issues/558. This issue is essentially a superset of that.

Also see [TileDB](https://docs.tiledb.com/main/) which has tiling scheme built around the concepts of "chunks" with support for sparse data and time dynamic data. The data conforms to a schema with a...

Metadata quantization is now better supported with the introduction of `offset` and `scale` properties which can be used to remap quantized values to their original range. These may be specified...

Hm we might need to dig into wetzel a bit for these. > The [Replaced single-element allOf with ref](https://github.com/CesiumGS/3d-tiles/pull/677/commits/1c1cad475e54a4c54e27d9423c176671d0a29e34) commit turns out to be an issue for wetzel as well....

A spatial subdivision within the content could also accelerate picking and height queries. We'll need to determine if this is worth including in the payload or computing at runtime. CC...

@runaas - that is definitely of interest but would be part of the CesumJS roadmap unless there are specifics that need to make their way into the spec. See https://github.com/CesiumGS/cesium/issues/7591...