Curb stones have a different height than the adjacent drivable lanes.Įxit: Describes a lane that is used for sections that are parallel to the main road. Sidewalk: Describes a lane on which pedestrians can walk.Ĭurb: Describes curb stones. It is typically used to separate traffic in towns on large roads.īiking: Describes a lane that is reserved for cyclists. Median: Describes a lane that sits between driving lanes that lead in opposite directions. Parking: Describes a lane with parking spaces. Typically, the lane is separated with lines and often contains dotted lines as well. The lane has the same height as drivable lanes. Restricted: Describes a lane on which cars should not drive.
#Opendrive down driver#
None: Describes the space on the outermost edge of the road and does not have actual content Its only purpose is for applications to register that OpenDRIVE is still present in case the (human) driver leaves the road. Stop: Hard shoulder on motorways for emergency stops It has the same height as the drivable lane.ĭriving: Describes a "normal" drivable road that is not one of the other types. Shoulder: Describes a soft border at the edge of the road.īorder: Describes a hard border at the edge of the road. by NOT applying the SCALE_Z_GRID upon loading the CRG file, but doing the calculation outside the CRG library, so that multiple instantiations of the same file can share the data in the CRG library. This should be considered in the implementation, e.g. CRG file may be placed in mode genuine multiple times, with different zScale values). BORDER_MODE_U and BORDER_MODE_V) and decide which value is returned.ĬRG files may be referenced multiple times with different parameters (e.g. If the calculations of the CRG uv or xy coordinates leads to coordinates outside of the defined area of the CRG file, then the normal CRG mechanisms apply (e.g. Other roads will not be affected, even if the CRG file would overlap the road. Example: if one road references a CRG file in global mode, then only this road will be influenced by the CRG file. For compatibility with future versions, each road or junction should only contain one CRG file per s position and files only have an effect on those roads or junctions from which they are referenced (and only between sStart and sEnd on that road). In the future, multiple CRG files at one position may be combined. Since CRG data may only cover parts of a road’s surface, it must be made sure that outside the valid CRG area, the elevation information derived from OpenDRIVE data can still be used. Heading offset between CRG center line and reference line of the road (only allowed for mode genuine, default = 0.0)
Z-scale factor for the surface description (default = 1.0). Z-offset between CRG center line and reference line of the road (default = 0.0). T-offset between CRG center line and reference line of the road (default = 0.0)
S-offset between CRG center line and reference line of the road (default = 0.0) Physical purpose of the data contained in the CRG file if the attribute is missing, data will be interpreted as elevation data. Only allowed for mode attached and attached0.Īttachment mode for the surface data, see specification. Orientation of the CRG data set relative to the parent element. Start of the application of CRG data (s-coordinate)Įnd of the application of CRG (s-coordinate) Attributes of the road surface CRG element Properties for road sections and cross section Generating arbitrary road courses from geometry elements Summary of all available coordinate systems Backward compatibility to earlier releases Positioning of ASAM OpenDRIVE within ASAM activities
Normative and non-normative statements and deliverables Deliverables of the OpenDRIVE specification