ghost
commented
5 years ago This issue is not limited to HOV lanes and corresponding traffic signs / lane markings. In its current state, OSI is not ready for US (highway) use.
Following steps are required to enable this:
- add country specific traffic signals
- add country specific lane definitions
- add country specific lane markings
An alternative would be the replacement of the actual traffic sign enums by a country specific taxonomy and the transmission of the corresponding codes, only (as they are defined in e.g. OpenDRIVE Specification 1.5) This is a task that has not yet been adressed by anybody. A comprehensive set of lane types may be found in the OpenDRIVE Specification 1.5) (see chapter 6.5). Nevertheless, HOV lane type has been added in this (latest) version. Most of the existing maps still comply to the 1.4 version, only. Version 1.5 is not very well tested and will be replaced by ASAM OpenDRIVE version 1.6 by the end of the year. Consolidation of OSI with OpenDRIVE should be postponed until this version is released.
In order to accurately provide simulation data for US highway scenarios, it is necessary that information about HOV or carpool lanes is provided. This information is provided via traffic signs, road markings, and lane boundary markings. These can be seen in the images below.
Current problem:
While it is possible to setup the lane boundaries, the road markings (diamond shape) is very specific to this lane type and would probably need a concrete type. The traffic signs needed for HOV lanes do not exist in a state which is usable, as the bus lane would not allow vehicles containing 2 or more passengers to use them.
Suggestion:
A mapping between the road signs defined and taken from the StvO and FHWA should be performed Missing signs specific to the FWHA catalogue which are currently relevant are added to the
osi_trafficsigndefinition.