Issue with EXT_structural_metadata and EXT_mesh_features in 3D Tiles Models

CesiumJS
1

Hi everyone,

I’m currently encountering an issue with the EXT_structural_metadata and EXT_mesh_features extensions in my 3D Tiles models. It seems like only the index 0 of propertyTable is being used.

I came across a similar post on the forum:

However, I’m not entirely sure if it’s the same issue in my case. Could someone confirm or provide more insights?

I’ve attached an example file here for reference:

N43E005_D101_S001_T001_L2_U1_R0.gltf (260.7 KB)

Thank you in advance for your help!

2

The issue that the other thread links to (EXT_mesh_features extension ignoring my class/table definitions, always looking up in propertyTable at index 0 · Issue #11683 · CesiumGS/cesium · GitHub) might be related, but I’m not entirely sure. You said

It seems like only the index 0 of propertyTable is being used.

The glTF file that you attached seems to have only one class and one propertyTable, so it might not be exactly the same issue.

Can you describe in more detail what you expect and what the actual (unexpected) behavior is?

3

I have a glTF file with three distinct sets of metadata, (witch come from 3 PointFeatures of a shapefile) and I want to assign each set to different primitive. However, no matter how I try assign the metadata with EXT_mesh_features, when I load the model in CesiumJS, all the primitives seem to use only the metadata from propertyTable index 0.
I’m wondering if i misunderstood how to correctly assign the metadata or if it’s something else.