GLTF Import - Metadata support #167
Labels
1. Data Exchange
Import/Export or iterating of the CAD data
2. Enhancement
New feature or request
5. Internal
Category
Data Exchange
Description
Implementing metadata support for GLTF format extends the functionality.
New metadata needs to be presented as a array of "key-value" attributes.
For the GLTF format there are a few ways to store metadata.
The easiest way to store them in the "nodes" section with "extras" section.
Some details from the forum by gkv311 n: https://dev.opencascade.org/node/87550#comment-25554
For the moment, RWGltf_CafReader will read"extras" within "asset" section of the file (e.g. as metadata for entire file) when 'file info' string-string map is passed to Perform() method.
For reading some metadata within node elements (if this is what you are talking about), the glTF reader has to be improved. Note that XCAF document stores such metadata in form of 'named data' attributes, so that glTF reader would better fetch information from there.
The way how to store metadata within glTF file is unclear, though. "extras" sections looks like the most simplest approach, but with unclear compatibility across readers and writers. There are also cumbersome extensions like KHR_xmp and its successor KHR_xmp_json_ld, which are rather more complex to implement.
File samples can be found by the next search request: https://github.com/search?q=path%3A*.gltf+extras&type=code&ref=advsearch
Some discussion:
KhronosGroup/glTF#1387
Use Case
Importing metadata, mirror of #79
Benefits
Full metadata support
Additional Context
Duplicate of https://tracker.dev.opencascade.org/view.php?id=33850
The text was updated successfully, but these errors were encountered: