Update 3DTILES_implicit_tiling and 3DTILES_subtree#114
Open
lilleyse wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates
3DTILES_implicit_tilingand3DTILES_subtree.There are two main differences between this and 3D Tiles 1.1:
TILE_BOUNDING_VOLUMEthat were previously stored in a property table are now stored in anattributesobject. This helps distinguish structural attributes from application-specific properties. More motivation behind that here: Semantics vs. extensions 3d-tiles#782 (comment).EXT_structural_metadatato store application-specific properties.Example of what it looks like now:
There is still a TODO list at the bottom of each extension, but I think this could be merged as a first draft.