Lanelet2 Traffic Rules

This package provides functionality for interpreting the traffic rules in a lanelet map depending on a country and a traffic participant.

It contains functionality to determine right of way, speed limits and legally reachable lanelets for a certain participant.

Usage

#include <lanelet2_traffic_rules/TrafficRulesFactory.h>
lanelet::traffic_rules::TrafficRulesPtr trafficRulesPtr =
  lanelet::traffic_rules::TrafficRulesFactory::create(lanelet::Locations::Germany, lanelet::Participants::Vehicle);
bool passable = trafficRulesPtr->canPass(myLanelet);
lanelet::traffic_rules::SpeedLimitInformation speedLimit = trafficRulesPtr->speedLimit(myLanelet);

Structure

This package offers the abstract TrafficRules class that is used as an interface to interpret the data in the map. It provides information whether a lanelet is usable/drivable, where lane changes are possible and what the speed limits are.

Derived from this is the abstract GenericTrafficRules class that implements the traffic rules based on the tagging specification. This class can then be derived to create traffic rules for individual countries and participants. This is especially important for the speed limits and interpreting country specific traffic signs.

After registering this class using RegisterTrafficRules, Lanelet2 is able to create instances of this traffic rule using the TrafficRuleFactory.

Hierarchical Structure of Participants

Some classes of participants, especially vehicles, follow a hierarchical structure. A traffic rule class that is registered for an upper level of this class is expected to handle all specializations for this class. For example if a TrafficRules implementation is registered for vehicle, it can also be instanciated for vehicle:car, but not vice versa.

When lanelets/areas have tags for specialized participants, e.g. have “participant:vehicle:car=no”, the TrafficRule class must handle this appropriately. If these tags are too specialized for an instance, the result should be as conservative as possible. This means that if a TrafficRule instance for vehicle finds a participants:vehicle:car=no and participants:vehicle:bus=yes, the lanelet is not passable.

However if it was instanciated for vehicle:bus instead of just vehicle the lanelet would be reported as passable.

Changelog for package lanelet2_traffic_rules

1.2.2 (2024-10-25)

• Build documentation with mkdocs (#321)
• Contributors: DavUhll

1.2.1 (2023-05-10)

1.2.0 (2023-01-30)

• Add signs for German zone 30 and zone 20 (#264)
• Add CI using GitHub Actions (#256)
• fix bug with explicitly defined lange change tags
• Fixed TrafficRulesFactory ignoring exact registry matches in case of vehicle subtypes (closes #202)
• Contributors: Maximilian Naumann, Patrick Peltzer, Fabian Immel, mitsudome-r

1.1.1 (2020-09-14)

1.1.0 (2020-09-06)

• Add experimental support for building with colcon on ros2 and ament_cmake
• Reorder includes with clang-format
• Making all includes in lanelet2_traffic_rules consistent.
• Updating package.xml files to format 3.
• Contributors: Fabian Poggenhans, Joshua Whitley

1.0.1 (2020-03-24)

• Make sure lanelet2 buildtool_export_depends on mrt_cmake_modules
• Add changelogs
• Contributors: Fabian Poggenhans

1.0.0 (2020-03-03)

• Bump version to 1.0
• Started traffic rules refactoring, bugfixing in traffic rules and extend unittests
• Fix compiler errors with gcc 5
• Initial commit
• Contributors: Fabian Poggenhans, Maximilian Naumann