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

Consideration of OpenSCENARIO DSL Use Cases. #183

Open Norihito-Hiruma opened 1 week ago

Norihito-Hiruma commented 1 week ago

This matter has been temporarily closed in Issue #168, but if we think about i linkage with OpenSCENARIO, I think we’d better allow linking multiple attribute files (asset files in this case) to one 3D shape file. We have launched this issue. Referring to the scenario structure sample in OpenSCENARIO DSL, the instruction is in the form of "3D shape file + color attributes".

OpenSCENARIO_concrete_scenario_2 OpenSCENARIO_logical_scenario_2 https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_DSL/latest/conceptual-overview/scenario-abstraction.html#_concrete_scenario

The above means that there is a use case where you want multiple attribute variations for one geometry, and I think that it is different from the current direction of MaterialMapping in OpenMATERIAL, which is to link only one asset files and shape file under the same file name.

It is the same as the previous issue (issue #168), but I would like to re-propose the following two additions so that to make it possible to assign multiple attributes to one shape file.

  1. Make it possible to describe the 3D shape data to be referenced in the asset file. If this is not described, then refer to a 3D shape data file having the same file name.
  2. In the asset file, the assignment information of the material name in the 3D shape data (hereinafter referred to as the 3D material name) and the material name in the material mapping file (hereinafter referred to as the mapping material name) can be described. The 3D material name and the mapping material name without assignment information are treated as the same.

From the point of description, the above two functions are the same as the current specifications unless otherwise stated. We believe that supporting such features will improve data efficiency and increase the availability and reusability of test contents. Material_Mapping_issue_00