Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds feature table support to b3dm tiles. With future enhancements like explicit tiling schemes, per-feature bounding volumes, and others down the road, it will be important for b3dm to have a feature table to store per-feature information that cannot be contained within the glTF model. This means
batchIds
are still part of the glTF, but per-feature bounding volumes (for example) would be part of the feature table.New layout:
The
batchLength
item in the header is removed and now moved to aBATCH_LENGTH
property of the feature table. This is similar toINSTANCES_LENGTH
for i3dm andPOINTS_LENGTH
/BATCH_LENGTH
for pnts.There was some discussion in the past regarding glTF byte alignment, since 28 is not on an even 8-byte split. The normal recommendation would still apply here, just pad the feature table or, if it exists, the batch table.
In the Cesium implementation we will continue to detect legacy headers, so old tilesets will still work for the time being.