OpenX Proposal: Parking lots and garages

Description: Add harmonized support for identifiable parking spaces across standards

Project Type: Implementation

Detailed Background:

Parking spaces in a parking Garage often have an identifier defined by the owner used to manage the parking garage/parking area as well as by the customers to find their vehicle after returning from their activity. The identifier is usually a number, letter or a combination of both. As with OpenDRIVE 1.8 this information cannot be stored, there are only attributes for access and restriction information. Therefore, we suggest adding an additional attribute with a name such as “managementId” or similar. This is laying the foundation of anchoring standardized parking actions to the parking lot definition. Then, ASAM OpenSCENARIO can reference the parking spots in a human readable way. And scenarios with parking actions/maneuvers can be implemented. Furthermore, the parking spot identifier can be visualized in a simulation tool, too. It also helps to avoid breaking scenario descriptions while re-exporting the OpenDRIVE file which can lead in many tools to a change in the IDs of OpenDRIVE objects. Related information can be found in this issue:

The input of what will be required will come from the ASAM Harmonization Group and ASAM OpenSCENARIO project(s).

Related Issues:

• ASAM OSI:
  • https://github.com/OpenSimulationInterface/open-simulation-interface/issues/714
  • https://github.com/OpenSimulationInterface/open-simulation-interface/issues/797
  • https://github.com/OpenSimulationInterface/open-simulation-interface/issues/798
• ASAM OpenSCENARIO XML
  • simulation/openscenario/openscenario-xml#585 (for trajectory based reference examples)

Affected Standards: OpenDRIVE, OpenSCENARIO XML, OpenSCENARIO DSL, OSI

Backwards Compatibility:

Feature shall be defined as backwards compatible as possible, for inclusion in minor releases of the affected standards. Where breaking changes are deemed necessary for the medium term, such proposals shall be developed separately, for future inclusion in major revisions.

Completion Criteria / Deliverables: All related issues have a defined solution harmonized across standards as PRs ready for integration.

Initiating Companies: CARIAD, PMSF,

ASAM Office Responsible (OR):

Assignee: Assign the project lead.

Estimated Start Date:

Estimated End Date: Due date

Budget Request:

Budget Use:

Enrollment: https://forms.office.com/e/AznN9f25p4