-
Notifications
You must be signed in to change notification settings - Fork 131
Draft for discussion: Added element tricycle #663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft for discussion: Added element tricycle #663
Conversation
Issue: OpenSimulationInterface#639 Signed-off-by: FlorianMueller87 <florian.b.mueller@gmx.de>
Signed-off-by: FlorianMueller87 <florian.b.mueller@gmx.de>
d56e646
to
ffd2730
Compare
Questions:
TODO:
IMPORTANT: Apart from these remarks I do not see a reason to not include this suggestion. |
Harmonization discussion:
Please clarify it in more detail. |
Clarification:
|
OtherModels and Harmonization feedback: Closed. Basically it would be a good approach to harmonize all OpenX standards according to vehicle types. E.g. to avoid problems with traffic signs targeting some vehicle type group, and the vehicle types of OSI. If needed, reopen, or create new PR with further description and reference this PR. |
Reference to a related issue in the repository
Issue: #639
Add a description
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.
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
Additional context
ISO23150:2021 A.76 Enumeration: Potentially moving object classification type
@ThomasNaderBMW @jdsika @schmidtlorenz