Best-Practice Guide

[DerBaertige]

Describe the feature

The standard should and cannot define everything, which can occur during a real world implementation. In many projects, in addition to the actual standard, the user is given additional information that is intended to simplify use. During the discussion of the Pull-Request #465 the idea of "Best-Practice Guide" grows, which describes different good/tested solutions, which cannot/should not be added to the standard directly.

Describe the solution you would like

This issue should be the start a collection of the usage of OSI, which facilitate the usage of different parts and the interaction with different standards, not restricted to ASAM standards.

Describe the backwards compatibility

There should be no issues regarding to backwards compatibility, as it is an additional extension to the documentation.

The first idea was, that the guide should be part of the OSI-Documentation, where the different parts of OSI and its tools are combined.

First Input for the Best-Practice Guide

Mapping of OpenDrive Roads and OSI Lanes

Based on both standards, a transfer of the road network to each other has to implemented. As OpenDrive and the OSI usees different paradigms to represent the network, a direct assignment is not possible. For simplicity and traceability a direct mapping of the t_road → t_road_lanes_laneSection → t_road_lanes_laneSection segments to the message Lane should be performed.

[HendrikAmelunxen]

Laneboundary Height and Width In Add Longitudinal Rotation of Lane Boundaries #436 examples are given, how laneboundaries with height and width should be described. This could be useful in a best practice guide.

[clemenshabedank]

Explain usage of DASH_GAP if https://github.com/OpenSimulationInterface/open-simulation-interface/pull/573 gets merged.