open-simulation-interface
open-simulation-interface copied to clipboard
OpenSimulationInterface
ISO23150 compliance: Adding new states to [LaneBoundary – Classification - Type]
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 entries for osi_lane – LaneBoundary – Classification - Type to be compatible with AUTOSAR ADI RoadBoundaryType.
Describe the solution you would like
Add in osi_lane – LaneBoundary – Classification - Type the following entries: // The lane boundary is a fence. // TYPE_FENCE = 16;
// The lane boundary is a tension cable system. // TYPE_TENSION_CABLE_SYSTEM = 17;
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.2.102 Road boundary type @ThomasNaderBMW @jdsika @schmidtlorenz
Note that a wand is something wizards wield, not something commonly found on roads, so I'm rather hoping that ADI does not use this term...
In any case this is redundant to TYPE_STRUCTURE that we already have.
TYPE_FENCE and TYPE_TENSION_CABLE_SYSTEM might be added, though at least for the later it is likely debatable whether that is not for all practical purposes subsumed by guard rail, unless it is specified more clearly.
kWand is obviously a mistake in the ADI spec. We will change this, thanks.
