ASAM OSI - WP4: Harmonization with OpenX

 

Notes

  • OpenDRIVE
    • What information do we need in Junctions for agent models
      • Extend reference line
  • Need a way of transporting typical trajectories to agents


Use Cases

Use case 11. Associating or identifying an object across the different OpenX standards

Description

Example
A road sign in OpenDRIVE is represented differently in OSI vs. OpenDRIVE

  • The IDs in OpenDRIVE are only unique within a road segment
  • IDs in OSI are globally unique
  • IDs cannot be mapped to each other

→ A way of transporting IDs across the standards is needed

ActorsProvide list of specific actors (i.e. company departments, end-users, tools, etc.)

Use case 12. Extending OSI for driver models

DescriptionWrite a brief description for the use-case.
ActorsProvide list of specific actors (i.e. company departments, end-users, tools, etc.)

Use case 13. Extending OSI for traffic participant models (similar to WP2, Use Case 9 "Model a traffic participant that includes OSI messages" )

DescriptionWrite a brief description for the use-case.
ActorsProvide list of specific actors (i.e. company departments, end-users, tools, etc.)

Use case 14. Extending OSI for vehicle models

DescriptionWrite a brief description for the use-case.
ActorsProvide list of specific actors (i.e. company departments, end-users, tools, etc.)

Use case 15. Extending OSI for autonomous driving functions

DescriptionWrite a brief description for the use-case.
ActorsProvide list of specific actors (i.e. company departments, end-users, tools, etc.)

 

 

WP1: Sensor Modeling

WP 2: Traffic Participants & Infrastructure

WP3: Performance & Packaging 

 

 

Back to ASAM OSI Project Page