Can be associated with tiles/tilesets in the tileset.json
Implicit Tiling
glTF Contents
Multiple glTF contents can be associated to each tile. Semantic data can be attached to a content group.
Tiles will refer to .gltf or .glb files (instead of .b3dm, .i3dm or pnts). This will allow 3D Tiles community to benefit from glTF community's work (validators, converters, pipelines, modeling tools, loaders, etc).
3D Tiles Next will use glTF extensions to store the metadata in the content files. Batched 3D Models will use 2 extensions:
EXT_mesh_features: indicates to which model a vertex belongs. It allows to have many models in a single mesh. It replaces the batchIDs from 3D Tiles 1.0.
EXT_structural_metadata: stores structured metadata. This data can be associated to features, groups of features or to a whole tile. It replaces the feature table and batch table from 3D Tiles 1.0.
Compression
Using .glb or .gltf files instead of .b3dm will allow compression without losing metadata.
3D Tiles Next
Semantic Metadata
Large emphasis on metadata:
tileset.jsonImplicit Tiling
glTF Contents
Multiple glTF contents can be associated to each tile. Semantic data can be attached to a content group.
Tiles will refer to
.gltfor.glbfiles (instead of.b3dm,.i3dmorpnts). This will allow 3D Tiles community to benefit from glTF community's work (validators, converters, pipelines, modeling tools, loaders, etc).3D Tiles Next will use glTF extensions to store the metadata in the content files. Batched 3D Models will use 2 extensions:
Compression
Using
.glbor.gltffiles instead of.b3dmwill allow compression without losing metadata.See compression issue.