feat: add support for area for route planning#993
Open
emmeyteja wants to merge 7 commits intoautowarefoundation:mainfrom
Open
feat: add support for area for route planning#993emmeyteja wants to merge 7 commits intoautowarefoundation:mainfrom
emmeyteja wants to merge 7 commits intoautowarefoundation:mainfrom
Conversation
|
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Author
|
@mitsudome-r @soblin Could you please review this PR? |
mitsudome-r
reviewed
Apr 3, 2026
Member
There was a problem hiding this comment.
There are multiple changes included in this PR.
Could you split the PRs into the following?
- adding visualization support of Area
- adding support of area for route_manager
- adding support for area for route_handler
It helps us to make the review easier and also easier to revert only the necessary parts when there is an issue.
Author
@mitsudome-r as we spoke in slack, I am going to split this PR into two PRs. One for routing search through Area primitive and publish in the route, second PR for visualizations of Area primitives. Please review. |
Signed-off-by: Ryohsuke Mitsudome <ryohsuke.mitsudome@tier4.jp>
…e segments Signed-off-by: emmeyteja <emmeyteja@gmail.com>
Signed-off-by: emmeyteja <emmeyteja@gmail.com>
Signed-off-by: emmeyteja <emmeyteja@gmail.com>
3853724 to
d6f070f
Compare
mitsudome-r
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Enable global routing through Lanelet2 Areas by registering
AutowareVehicletraffic rules (Areas passable per GenericTrafficRules / participant tags) and extendingRouteHandlerto plan withshortestPathIncludingAreas, buildLaneletSegments withprimitive_type == "area", and support drivable-lane fallbacks where needed. Areas are connectors in the routing graph only—no centerline or path inside the Area; lane legs stay lanelet-based.Related Links
Related PRs
Issues
TierIV Internal Issue Link
Design Documents
Tier IV Internal Design Document: Area Visualization
Tier IV Internal Design Document: Route Serach through Areas
How was this PR tested?
autoware_lanelet2_extension,autoware_route_handler, and dependents as needed).Notes for reviewers
None.
Interface changes
No new ROS topics or parameters in core. C++ RouteHandler (and related headers) gain overloads and helpers for area-inclusive paths and segment construction. Downstream LaneletRoute.segments may include primitive_type == "area" once the mission planner uses this pipeline (that wiring may be a separate PR).
Effects on system behavior
Routes can traverse Areas as graph links, so some maps become plannable that were not before.
Lane-only routes and maps without area-inclusive paths should match prior behavior.