search

OpenSimulationInterface / open-simulation-interface

A generic interface for the environmental perception of automated driving functions in virtual scenarios.
Other
267 stars 125 forks source link

ISO23150 compliance: Adding one new vehicle type to [MovingObject - VehicleClassification - Type] #639

Open FlorianMueller87 opened 2 years ago

FlorianMueller87 commented 2 years ago

Describe the feature

ASAM OSI and ISO 23150 or AUTOSAR ADI have a common history. Unfortunately, the inner structure, the naming and the definitions of the standards are differentiated from each other. This makes the work of developers unnecessary complicated for mostly no technical reasons. All sides should strive to reduce inequality.

ASAM OSI need the entry TYPE_TRICYCLE for osi_objects – MovingObject - VehicleClassification – Type to be compatible with AUTOSAR ADI PotentiallyMovingObjectClassificationType.

Describe the solution you would like

Add in osiobjects – MovingObject – VehicleClassification - Type the following entry: // Object is a Tricycle. // TYPE TRICYCLE = 16;

Describe alternatives you have considered

No alternative was considered.

Describe the backwards compatibility

The adding of the elements will not lead to backward compatibility issues.

Additional context

ISO23150:2021 A.76 Enumeration: Potentially moving object classification type

@ThomasNaderBMW @jdsika @schmidtlorenz

pmai commented 2 years ago

BTW it would be nice to consult with ISO 23150 and AUTOSAR groups whether tricycle should include e.g. motorcycle with sidecar. In general the definitions need to be much more clearly specified in all of these standards to be suitable for exchange ... Which is much more of a concern than missing/differing enums, where at least the mismatch is apparent (and OSI allows custom extensions anyway)...

FlorianMueller87 commented 2 years ago

I will ask this at the AUTOSAR ADI board. I see the same problem. In some cases the describtions need to be more specific. I will address this as well.