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
According to the specification, it should be possible to define feature ID attributes without property tables,
When feature IDs are associated with property tables, then every propertyTables index must have an associated featureIds definition. The propertyTables entry at index i corresponds to the featureIds entry at the same index. As a result, the length of the featureIds array must be greater than or equal to the length of the propertyTables array.
This does not seem to be considered in the current implementation, which directly accesses the propertyTablesArray (which is rather a propertyTableIdsArray, or maybe even a propertyTableIndicesArray, by the way), regardless of whether this array is defined or has the appropriate length.
I tried to address this, to some extent, via javagl@80af1d1 , but the implications of this go into technical details... (BatchTexturePipelineStage#process ... what?!) ... so that I have to give up on that one for now...
The text was updated successfully, but these errors were encountered:
According to the specification, it should be possible to define feature ID attributes without property tables,
This does not seem to be considered in the current implementation, which directly accesses the
propertyTablesArray
(which is rather apropertyTableIdsArray
, or maybe even apropertyTableIndicesArray
, by the way), regardless of whether this array is defined or has the appropriate length.A glTF asset and the associated tileset are here:
QuadWithFeatureIds.gltf
tileset.json
Sandcastle code
(Not cleaned up, just from my local tests...)
I tried to address this, to some extent, via javagl@80af1d1 , but the implications of this go into technical details... (
BatchTexturePipelineStage#process
... what?!) ... so that I have to give up on that one for now...The text was updated successfully, but these errors were encountered: