maliput_malidrive

Description

maliput_malidrive package is a Maliput backend implementation. Its underlying format specification is based on OpenDRIVE format. Allowing the users to load a road network out of a XODR file description.

Please go to XODR Parser capabilities for further information about OpenDRIVE’s parser.

Note: For full information about Maliput please visit Maliput Documentation.

Resources

maliput_malidrive provides several map resources at maliput_malidrive/resources. These resources are:

• XODR files for describing different road networks using OpenDRIVE format specification.
• YAML files for describing maliput’s road network information of type: Range Value Rules, Discrete Value Rules, Traffic Lights, Phase Rings, Intersections, etc.

Resources are installed natively, so the users are able to use them for their own interest. In order to get the installation path check the environment variable: MALIPUT_MALIDRIVE_RESOURCE_ROOT.

API Documentation

Refer to Maliput Malidrive’s Online API Documentation.

Examples

Getting Started page is a good place for starting to see Maliput’s capabilities and how to use a Maliput backend for getting a road network.

• maliput_malidrive’s applications: This package provides some applications to validate a XODR file. See maliput_malidrive’s tutorials.
• maliput_integration: Concentrates applications created for maliput. See maliput_integration’s tutorials. These applications allow to select maliput_malidrive as the backend.

Installation

Supported platforms

Ubuntu Focal Fossa 20.04 LTS.

Binary Installation on Ubuntu

See Installation Docs.

Source Installation on Ubuntu

Prerequisites

sudo apt install python3-rosdep python3-colcon-common-extensions

Build

1. Create colcon workspace if you don’t have one yet.

    mkdir colcon_ws/src -p
    

1. Clone this repository in the src folder

    cd colcon_ws/src
    git clone https://github.com/maliput/maliput_malidrive.git
    

1. Install package dependencies via rosdep

    export ROS_DISTRO=foxy
    

    rosdep update
    rosdep install -i -y --rosdistro $ROS_DISTRO --from-paths src
    

1. Build the package

    colcon build --packages-up-to maliput_malidrive
    

**Note**: To build documentation a `-BUILD_DOCS` cmake flag is required:

    colcon build --packages-select maliput_malidrive --cmake-args " -DBUILD_DOCS=On"
    

More info at [Building Documentation](https://maliput.readthedocs.io/en/latest/developer_guidelines.html#building-the-documentation).

For further info refer to Source Installation on Ubuntu

For development

It is recommended to follow the guidelines for setting up a development workspace as described here.

Contributing

Please see CONTRIBUTING page.

License

Changelog for package maliput_malidrive

0.26.1 (2026-06-19)

• Using correct db mapper for RoadMarkings (#499)
• Contributors: Juan Carosella

0.26.0 (2026-06-17)

• Reworking road marking types to be more generic (#497)
• Implement dependent_signs API. (#496)
• Contributors: Juan Carosella, Santiago Lopez

0.25.1 (2026-06-12)

• Setting author email and name (#494)
• Fix XODR signals and objects z position. (#492)
• Setting wildcard as default db value for objects (#491)
• Updating Bazel release process (#490)
• Contributors: Juan Carosella, Santiago Lopez

0.25.0 (2026-06-10)

• Map XODR object barrier to kGuardRail, kGuardWall, kBarrier based on subtype. (#487)
• Add mapping for new TrafficSignTypes. (#486)
• Support traffic_control_device databases in string format. (#485)
• Contributors: Santiago Lopez

0.24.1 (2026-06-08)

• Adding epsilon comparison to VerifyValidXodrLanePosition (#473)
• Contributors: Juan Carosella

0.24.0 (2026-06-05)

• Implementing is_dynamic/movable API (#482)
• Adding signs properties from XODR (#480)
• Adding three new sign types (#479)
• Make comparison epsilon a bit less strict. (#481)
• Keeping a consistent format in DB naming (#478)
• Optional odr_representation fields are defaulted to wildcard string. (#477)
• Contributors: Juan Carosella, Santiago Lopez

0.23.0 (2026-06-03)

• New TrafficControlDeviceBooks builder (#469) Co-authored-by: JCarosella <<juancarosella96@ekumenlabs.com>>
• RoadMarkingBuilder (#468)
• Empty RoadMarkingBook and RoadObjectType deprecation (#467)
• Support odr_object_types entries in traffic_control_device database (#464)
• Implement TrafficSign::GetValue interface. (#462)
• Align signal's orientation with the s-direction traffic comes from. (#463)
• TrafficControlDevice supports new TrafficLights field values. (#459)
• TrafficControlDevice database wildcard matching (#456) Co-authored-by: Santiago Lopez <<santiago.lopez@ekumenlabs.com>>
• Update traffic control device database structure. (#452)
• Rename traffic_signal module and elements to traffic_control_device. (#450)
• Contributors: Santiago Lopez

0.22.0 (2026-04-21)

• Refactor traffic sign mapper while adding new sign type no_overtaking. (#441)
• Treat XODR roadMark objects as stopLines if their name state so. (#440)
• Support unknown traffic signs in the database. (#438)
• Implement RoadObject API (#434)
• Build [TrafficSignBook]{.title-ref} and fill it with [TrafficSign`s (]{.title-ref}#421

File truncated at 100 lines see the full file