search

asam-ev / OpenMATERIAL

3D model exchange format with physical material properties for virtual development, test and validation of automated driving.
https://asam-ev.github.io/OpenMATERIAL/
Mozilla Public License 2.0
14 stars 7 forks source link

Resolve open questions from 3D asset file section (7.2.4) #117

Open LudwigFriedmann opened 2 months ago

LudwigFriedmann commented 2 months ago

Is your feature request related to a problem? Please describe. Currently, the section contains open questions:

  1. Metadata
  2. Material mapping (with possibility to easily change assignment)
  3. Optional link to another asset file to facilitate instancing (same asset file for different 3D models)
  4. Semantic information (labels) for sub-meshes ?
  5. Description of coordinates, pivot points and so on instead of hierarchy in 3D model file ?
  6. Assigning data streams (for example, wheel rotation) to certain sub-meshes ?

Describe the solution you'd like Within the geometry subgroup meeting on 2024-09-26, we have decided to answer them as follows:

  1. 1-2 sentences and a link to the metadata section of the geometry documentation should go here
  2. 1-2 sentences and a link to the material mapping section of the geometry documentation should go here
  3. Referencing of other assets (asset files) would require a proper concept. Let's postpone this for now.
  4. Semantic information is provided by the node structure. Therefore, an aditional labeling (apart from the OpenMATERIAL object class) is postponed for now.
  5. Coordinate frames in general are defined in the general section. Position and orientation of node-specific (local) coordinate frames should be defined in the object class section, individually for object classes.
  6. Ways to assign data streams should be defined in the object class section, individually for object classes.

Describe alternatives you've considered

Additional context

LudwigFriedmann commented 1 month ago

As indicated in #136 , it should be checked if the asset file documentation and the metadata documentation can be derived from a corresponding json schema file.