-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Batch Table hierarchy to an extension #305
Conversation
45f11b8
to
f0e031b
Compare
Hm good question... maybe core extensions should have the |
Just include me and Patrick. |
Check what glTF does - but I'm ok either way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
TileFormats/BatchTable/README.md
Outdated
@@ -167,342 +158,6 @@ var geographicArray = new Float64Array(batchTableBinary.buffer, byteOffset, geog | |||
var geographicOfFeature = positionArray.subarray(batchId * numberOfComponents, batchId * numberOfComponents + numberOfComponents); // Using subarray creates a view into the array, and not a new array. | |||
``` | |||
|
|||
## Batch Table Hierarchy | |||
|
|||
The standard batch table is suitable for datasets composed of features with the same sets of properties. However, some datasets have more complex metadata structures such as feature types or feature hierarchies that are not easy to represent as parallel arrays of properties. The Batch Table Hierarchy provides more flexibility for these cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worthwhile to keep just this section but point to the extension for more details.
|
||
```json | ||
{ | ||
"CESIUM_batch_table_hierarchy" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CESIUM_batch_table_hierarchy
should be contained within an extensions
objects.
|
||
```json | ||
{ | ||
"HIERARCHY" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use extensions
and CESIUM_batch_table_hierarchy
objects.
|
||
```json | ||
{ | ||
"HIERARCHY" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment.
"Height" : [...], | ||
"Longitude" : [...], | ||
"Latitude" : [...], | ||
"HIERARCHY" : {...} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment - and change the name in the description above.
Thanks @lilleyse ! Updated, and also updated the figures to reflect the changes. |
* [Overview](#overview) | ||
* [Motivation](#motivation) | ||
* [Batch table JSON schema updates](#batch-table-json-schema-updates) | ||
* [3DTILES_batch_table_hierarchy](#3DTILES_batch_table_hierarchy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link isn't working, it should be lower case.
|
||
Batch Table Hierarchy, parking lot: | ||
|
||
![batch table hierarchy parking lot](figures/batch-table-hierarchy-parking-lot.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh good catch about the pictures!
The json formatting is a little off on this picture. The other picture looks good.
Thanks @lilleyse, fixed! |
👍 |
Fixes #303
CESIUM_batch_table_hierarchy
the name of the extension we would like to use? Is this a vendor extension? What prefix should we use for core extensions otherwise?additionalProprties
field? or is that covered byextensions
andextras
now?