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
There are several different metadata capabilities in 3D Tiles Next and several possible methods
of accessing the metadata (mainly custom shaders, picking, and styling). It's admittedly confusing what is supported where, so we thought it would be helpful to make a table.
Key:
🟢 - currently implemented (sometimes with limitations)
🔴 - not yet implemented.
Only one set of feature IDs can be used at a time for picking/styling. This is selected with the featureIdLabel/instanceFeatureIdLabel properties of a tileset/model
The "Styling" column for the first 4 rows suggests that Styling based on Metadata was supported. Maybe I didn't fully understand the footnote 1, but it seems like this is not the case, as of #11758
Beyond that, just to keep track of some related forum threads:
There are several different metadata capabilities in 3D Tiles Next and several possible methods
of accessing the metadata (mainly custom shaders, picking, and styling). It's admittedly confusing what is supported where, so we thought it would be helpful to make a table.
Key:
🟢 - currently implemented (sometimes with limitations)
🔴 - not yet implemented.
3D Tiles 1.1
/3DTILES_metadata
(legacy extension)EXT_mesh_features
/EXT_instance_features
EXT_structural_metadata
Footnotes:
Cesium3DTileFeature.getPropertyInherited
. This has some limitations, see Streamline the API for accessing tileset/tile metadata when picking #10015featureIdLabel
/instanceFeatureIdLabel
properties of a tileset/modelModel
EXT_mesh_features: handle feature IDs without a property table #9884The text was updated successfully, but these errors were encountered: