OpenDRIVE (.xodr)
May 25,2026

GISBox is a one-stop 3D GIS data editing, conversion and publishing platform that supports editing in multiple GIS formats such as OSGB/GEOTIFF/RVT, converting to 3DTiles/Terrain and publishing.

Introduction

OpenDRIVE (.xodr) is an open standard file format used to describe static road networks in autonomous driving simulation. Based on the XML structure, it can precisely represent critical information such as road geometry, lane layout, and traffic signs. Maintained by the ASAM organization, it is primarily used in high‑definition maps and driving simulators, supporting data exchange between different simulation platforms and ensuring high realism and interoperability when testing and validating autonomous driving systems in virtual environments.

Snipaste_2026-05-19_09-21-58_1779153730139.jpg

File Structure

The OpenDRIVE (.xodr) file is an XML‑based standardized format used to accurately describe road networks for autonomous driving simulation. Its file structure mainly consists of the following core components:

  • <OpenDRIVE> root element: The outermost container of every .xodr file. All other elements are nested within it, forming a complete road network description.
  • <header> metadata: Located at the beginning of the file, containing metadata such as version numbers (revMajor/revMinor), file name, creation date, author, geographic boundaries (south/north/west/east), and coordinate reference system (e.g., UTM projection).
  • <road> element: The core unit describing an individual road, each with a unique ID.
  • <junction> intersection: Describes the connection logic between multiple roads, defining the drivable path combinations at intersections and supporting complex traffic flow simulations.
  • Extensions and data precision: All floating‑point numbers use the IEEE 754 double‑precision format, with 17 significant digits recommended to ensure precision. Users can also define custom extension fields via <userData> to enhance flexibility.

Pros

  1. Strong standardization and interoperability: Maintained by the ASAM organization, OpenDRIVE has become a de facto industry standard, enabling seamless exchange of road data between different simulation platforms (e.g., CARLA, PreScan).
  2. High description accuracy: Capable of precisely modeling road geometry (e.g., clothoids, curvature changes), elevation, lateral slopes, and lane‑level details, meeting the high demands of autonomous driving perception and planning for environmental modeling.
  3. Flexible and structured design: Supports complex road topologies, including loops, branches, merges, and multi‑level interchanges, with refined intersection connection logic implemented through <junction>.
  4. Good extensibility: Allows custom fields via <userData> to adapt to specific system requirements (e.g., Apollo’s extensions to OpenDRIVE).
  5. Compatible with both real and synthetic data: Can be used both for high‑definition road networks built from real maps and for generating virtual test scenarios, serving algorithm validation and extreme‑condition simulation.

Cons

  1. Large file size and low parsing efficiency: Due to the XML format, data redundancy is significant. A one‑kilometer highway segment can generate tens of megabytes of data, affecting real‑time parsing performance on the vehicle side.
  2. High production barrier: Editing typically relies on professional commercial software (e.g., RoadRunner). Open‑source toolchains have limited functionality, leading to high data production costs.
  3. Static nature: Describes only static road information (e.g., lanes, signs) and does not include dynamic traffic participants or behavioral logic. It must be supplemented with standards such as OpenSCENARIO.
  4. Poor planning‑friendliness: Its data structure is more oriented toward simulation rendering and sensor simulation than toward efficient topology queries and semantic expression required for autonomous driving decision‑making.
  5. Complex coordinate system: Uses a hybrid of track coordinates (s, t, h) and inertial coordinates, increasing the learning and conversion overhead for developers.

Application Scenario

OpenDRIVE (.xodr) is primarily used in virtual simulation testing, high‑definition map construction, and path planning for autonomous driving, providing a precise static road network model for the system. It is widely adopted in simulation platforms such as CARLA, PreScan, and MATLAB, supporting digital modeling of complex urban roads, highways, and intersections. This ensures high realism and repeatability when validating perception, decision‑making, and control algorithms in virtual environments. Additionally, OpenDRIVE is used in the design and testing of cooperative vehicle‑infrastructure systems and intelligent transportation infrastructure.

Example

1. Visualizing an .xodr file using matplotlib.

Snipaste_2026-05-19_09-24-49_1779153926660.jpg


2. In OpenDRIVE, a parametric cubic curve is represented using the <paramPoly3> element inside the <geometry> element.

Snipaste_2026-05-19_09-28-54_1779154193363.jpg

File Opening Mode

1. Online viewer for .xodr high‑definition maps.

Snipaste_2026-05-19_09-36-58_1779154650837.jpg

Related GIS files

PDS Design Review

MicroStation

Inventor

IGES

References

  1. https://gdal.org/en/stable/drivers/vector/xodr.html
  2. https://en.wikipedia.org/wiki/OpenDRIVE_(specification)
  3. https://github.com/DLR-TS/xodr