AuditASAM OpenDRIVE

OpenDRIVE

The standard OpenDRIVE is used to describe road networks at lane-level accuracy for simulation applications. It is developed by the ASAM consortium, which has over 400 active members from the automotive sector and offers a whole collection of open standards for interoperable exchange.

Schema compliance

The schema defines the structure of an OpenDRIVE file and is officially published by ASAM. Applications rely on adherence to the schema and violations can lead to undefined behavior.

XSD
<xs:complexType name="t_road_objects_object">
    <!-- ... -->
    <xs:attribute name="id" use="required" type="xs:string">
        <xs:annotation>
            <xs:documentation>Unique ID within database</xs:documentation>
        </xs:annotation>
    </xs:attribute>
    <!-- ... -->
    <xs:attribute name="s" use="required" type="t_grEqZero">
        <xs:annotation>
            <xs:documentation>s-coordinate of object's origin</xs:documentation>
        </xs:annotation>
    </xs:attribute>
    <!-- ... -->
</xs:complexType>

The schema excerpt, for example, tells us that each road object requires an attribute id of type String. Moreover, it must have an attribute s of a special type named t_grEqZero, which is a constrained double.

In the first step, Envis Audit checks whether the OpenDRIVE file complies to the schema and reports any violation. OpenDRIVE version 1.1 to version 1.7 are supported.

Specification compliance

While the schema defines very well the types and required attributes, it still leaves a few degrees of freedom. In the upper schema excerpt, the documentation indeed states that the attribute id should be unique within the database. However, this is human-readable rule and is not a strict constraint by the schema.

In the second step, Envis Audit checks whether the modelling rules formulated in the specification and not covered by the schema are respected. Again, rule violations are also reported.

See also

Audit