13.9 Object borders

In the current version of ASAM OpenDRIVE, object borders are only allowed for Traffic Islands. Objects of type "trafficIsland" may have a border, that is a frame of a defined width. Different border types are available, currently concrete and curb.

The <borders> element serves as a wrapper for the <border> element, which itself contains further attributes to describe the borders.

Elements in UML model

<borders> element

In ASAM OpenDRIVE, object borders are represented by the <borders> element within the <object> element.

UML class: t_road_objects_object_borders
XML tag:   <borders> (Multiplicity: 0..1)

Object borders are frames with a defined width, for example, to describe traffic islands.

Different border types are available.

<border> element

In ASAM OpenDRIVE, object borders are represented by the <border> element within the <borders> element.

UML class: t_road_objects_object_borders_border
XML tag:   <border> (Multiplicity: 1..*)

Specifies a border along certain outline points.

Table 101. Attributes of the <border> element
Name	Type	Use	Unit	Description
`outlineId`	nonNegativeInteger	required		ID of the outline to use
`type`	e_borderType	required		Appearance of border
`useCompleteOutline`	t_bool	optional		Use all outline points for border. “true” is used as default.
`width`	t_grEqZero	required	m	Border width

Rules

The following rules apply to object borders:

asam.net:xodr:1.7.0:road.object.borders.useCompleteOutline_true: If @useCompleteOutline is true, the <cornerReference> element shall not be defined.

If @useCompleteOutline is false, at least two <cornerReference> elements are mandatory.

asam.net:xodr:1.9.0:road.object.borders.different_outlineids: All <outline> elements of an <outlines> element shall have different @outlineId values.

Related topics