6.2 Road networks and environment models
A scenario description may require references to a specific road network as well as inclusion of specific 3D models that represent the simulated environment visually.
The definition of road network logic and/or environment 3D models is optional of ASAM OpenSCENARIO.
Those references are established within the RoadNetwork language element.
As an example, the ASAM OpenDRIVE file format is common when it comes to describing road network logic.
Scenario authors often need to refer to items defined in the road network, for example, to instruct a vehicle to drive in a specific lane. ASAM OpenSCENARIO does not impose its own naming system for these items; they should be referred with the names allocated by their own file format.
The following features of the road network may be addressed using ASAM OpenSCENARIO:
-
Individual road
-
Lane within a road
-
Traffic signal
-
Traffic signal controller
-
Road object
As mentioned before, a road network description supported by ASAM OpenSCENARIO is the ASAM OpenDRIVE format.
This format describes the logical information related to road structure, such as road id, lane id, and road geometry.
This information may be used to locate and position instances of Entity acting on the road and to position traffic participants.
If ASAM OpenDRIVE is used to represent the road network, the ASAM OpenSCENARIO file should follow the ASAM OpenDRIVE conventions for numbering lanes.
In addition to the road network description, 3D models representing the environment may be referenced in a scenario description. Files containing 3D models provide the geometric and visual representation, like mesh and textures for elements of the virtual environment including the road surface. Use cases for 3D models referenced from scenarios are rendering, physical modeling, and sensor simulation. Files containing 3D models are considered to be external elements to the ASAM OpenSCENARIO format.
It is also possible to outsource some parts of the scenario description to an external Catalog file.
The process for referencing external scenario parts is described in Section 9.4, "Catalogs"
|
6.2.1 Assigning entities to roads and lanes
Entities that are placed on a road by an action, for example AddEntityAction or TeleportAction, are assigned to the underlying lane at that position.
The underlying lane is the lane that is closest to and below or at the position of the entity.
Any subsequent action that does not explicitly overwrite the position must respect this assignment.
Roads can have up to two lane layers: the permanent and the temporary lane layer. The temporary lane layer is used to model temporary lanes leading through roadworks sections. If both the permanent and the temporary layer are present for a position and the entity placing action does not specify the lane layer, the entity shall be assigned to the lane on the temporary layer.