3D-Tiles 1.1 voxel about 3d-tiles

[j9liu]

Hey @cjhdsg,

If you pair the voxel data with a tileset metadata schema, you can specify a noData value to compare the empty voxels to. This example is taken from the extension README.

"schema": {
  "classes": {
    "voxel": {
      "properties": {
        "temperature": {
          "type": "SCALAR",
          "componentType": "FLOAT32",
          "noData": 999.9
        },
        "salinity": {
          "type": "SCALAR",
          "componentType": "UINT8",
          "normalized": true,
          "noData": 255
        }
      }
    }
  }
}

Then it would be a matter of comparing the values to this noData value. Hope this helps!

[cjhdsg]

Yes, I've added "noData" field, and wrote corresponding value in binary chunk. But it seemed not working. Here is my test dataset.

test-dataset.zip

[javagl]

Some aspects of that test data set are nor entirely clear, and I'd have to look at some aspects of the voxel extension specification and other test data here.

But the given tileset contains

    "implicitTiling" : {
      "subdivisionScheme" : "OCTREE",
      "subtreeLevels" : 1,
      "availableLevels" : 1,
      "subtrees" : {
        "uri" : "subtrees/{level}.{x}.{y}.{z}.subtree"
      }
    }

Defining availableLevels: 1 does not seem to make sense for the given data set. Can you provide an example data that works and is valid, and that shows the problem that you are encountering? (Once we have this data, we can have a closer look at how to sensibly hide/omit certain cells - but we should start with a data set that works...)

(We will then still have to carefully check whether any unexpected behavior that you are observing is related to CesiumGS/cesium#12001 , which you brought up in https://community.cesium.com/t/3d-tiles-1-1-voxel/32239 ...)