-
Notifications
You must be signed in to change notification settings - Fork 29
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
This PR adds support for 3D Tiles Next #58
base: main
Are you sure you want to change the base?
Conversation
The feature table property |
GTModels have a |
For San Diego - what is the |
|
descriptions["FSC"] = "This code, in conjunction with the FACC is used to distinguish and categorize features within a dataset."; | ||
descriptions["HGT"] = "Distance measured from the lowest point of the base at ground (non-floating objects) or water level (floating objects downhill side/downstream side) to the tallest point of the feature above the surface. Recorded values are positive numbers. In the case of roads and railroads, HGT corresponds to the elevation of the road/railroad wrt terrain in its immediate vicinity."; | ||
descriptions["MLOD"] = "The level of detail of the 3D model associated with the point feature. When used in conjunction with MODL, the MLOD attribute indicates the LOD where the corresponding MODL is found. In this case, the value of MLOD can never be larger than the LOD of the Vector Tile-LOD that contains it. When used in the context of Airport and Environmental Light Point features, the value of MLOD, if present, indicates that this light point also exist in a 3D model found at the specified LOD. In such case, the value of MLOD is not constrained and can indicate any LOD."; | ||
descriptions["MODL"] = " A string reference, the model name, which stands for the modeled geometry of a feature; in the case of buildings, this includes both its external shell and modeled interior. Usage Note: Needed for Point features, Road Figure Point features, Railroad Figure Point features, Pipeline Figure Point features and Hydrography Figure Point features that are modeled as OpenFlight or as RCS (Shape). MODL can also be used with Road Lineal features, Railroad Lineal features, Pipeline Lineal features and Hydrography Lineal and Areal features. Note that it is not permitted to specify a value for MODL simultaneously with a value for MMDC."; |
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.
descriptions["MODL"] = " A string reference, the model name, which stands for the modeled geometry of a feature; in the case of buildings, this includes both its external shell and modeled interior. Usage Note: Needed for Point features, Road Figure Point features, Railroad Figure Point features, Pipeline Figure Point features and Hydrography Figure Point features that are modeled as OpenFlight or as RCS (Shape). MODL can also be used with Road Lineal features, Railroad Lineal features, Pipeline Lineal features and Hydrography Lineal and Areal features. Note that it is not permitted to specify a value for MODL simultaneously with a value for MMDC."; | |
descriptions["MODL"] = "A string reference, the model name, which stands for the modeled geometry of a feature; in the case of buildings, this includes both its external shell and modeled interior. Usage Note: Needed for Point features, Road Figure Point features, Railroad Figure Point features, Pipeline Figure Point features and Hydrography Figure Point features that are modeled as OpenFlight or as RCS (Shape). MODL can also be used with Road Lineal features, Railroad Lineal features, Pipeline Lineal features and Hydrography Lineal and Areal features. Note that it is not permitted to specify a value for MODL simultaneously with a value for MMDC."; |
options.add_options("hidden") | ||
("3d-tiles-next", | ||
"Experimental convert to 3DTiles with 3DTILES_content_gltf, 3DTILES_implicit_tiling, and EXT_feature_metadata extensions.", | ||
cxxopts::value<bool>()->default_value("false")) | ||
("external-schema", | ||
"Use external schema file for Feature Metadata.", | ||
cxxopts::value<bool>()->default_value("false")) | ||
("subtree-levels", | ||
"The number of levels in each subtree for implicit tiling.", | ||
cxxopts::value<int>()->default_value("7")); |
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.
These don't need to be hidden options.
("external-schema", | ||
"Use external schema file for Feature Metadata.", | ||
cxxopts::value<bool>()->default_value("false")) |
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.
I think schemas should be external by default to help cut down on glb sizes. Maybe then the option would be renamed to --embedded-schema
@sanjeetsuhag I forget, are we able to post a sandcastle demo for Yemen? It would be great to show off the feature id textures |
@sanjeetsuhag @ErixenCruz that's my first pass over the CLI, README, and inspecting the tileset output. I'll probably do a quick code pass later. So far seems pretty good! |
For #39 I think it would not be too much work. We already have that branch that is mentioned in the issue that has most of the changes needed to calculate the tighter bounding region. For implicit, only the non positive levels would be affected. |
I believe originally for multicontent, we were going to need per-content availability, and we thought it made more sense to store availability binaries within their respective content folder instead of smashing them all on the end of the subtree file. Multicontent was abandoned, but that decision was not revisited |
Yes. the Sandcastle can be found here. |
An optimization for creating bounding volumes for instanced models would be to add the min and max of the |
I pushed a commit that fixes the 3D Tiles Next links. See CesiumGS/3d-tiles#478 |
@sanjeetsuhag is there any top-level metadata (provenance information like author, date, etc) that should get carried over into tileset metadata? And more generally is there any other CDB metadata that's not getting carried through into the tileset? CC @bradyjmoore |
@lilleyse From what I recall, the problem here is that the CDB datasets we have kinda follow rules of their own in terms of what they put in the top level Metadata folders. I remember the LA CDB had a completely different set of namespaces in its Metadata.XML compared to the San Diego one. That being said, I don't think we've looked at the CDB spec either about what the typical way of doing this is. |
update glbLength and jsonChunkLength before references are invalidated by glbStr.insert
Before this is merged, we should implement support for propagating feature ID textures to higher LODs where the |
Fixed glb padding issue
Fix padding in combineGltfs
3D Tiles Next is a set of capabilities for the future of 3D Tiles. Read the overview document for more details.
This PR adds support for the following extensions:
This PR also adds support for the RMTexture and RMDescriptor datasets.