Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]
Messages
Services
Plugins
Recent questions tagged autoware_lidar_marker_localizer at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-28 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Yamato Ando
Authors
- Eijiro Takeuchi
- Yamato Ando
- Shintaro Sakoda
LiDAR Marker Localizer
LiDARMarkerLocalizer is a detect-reflector-based localization node .
Inputs / Outputs
lidar_marker_localizer node
Input
| Name | Type | Description |
|---|---|---|
~/input/lanelet2_map |
autoware_map_msgs::msg::HADMapBin |
Data of lanelet2 |
~/input/pointcloud |
sensor_msgs::msg::PointCloud2 |
PointType: PointXYZIRC is recommended in Autoware, but PointXYZIRADRT are also supported in this node.1
|
~/input/ekf_pose |
geometry_msgs::msg::PoseWithCovarianceStamped |
EKF Pose |
Output
| Name | Type | Description |
|---|---|---|
~/output/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
Diagnostics outputs |
For debug
| Name | Type | Description |
|---|---|---|
~/debug/pose_with_covariance |
geometry_msgs::msg::PoseWithCovarianceStamped |
Estimated pose |
~/debug/marker_detected |
geometry_msgs::msg::PoseArray |
Detected marker poses |
~/debug/marker_mapped |
visualization_msgs::msg::MarkerArray |
Loaded landmarks to visualize in Rviz as thin boards |
~/debug/marker_pointcloud |
sensor_msgs::msg::PointCloud2 |
PointCloud of the detected marker |
~/debug/center_intensity_grid |
nav_msgs::msg::OccupancyGrid |
Center intensity grid for debug |
~/debug/positive_grid |
nav_msgs::msg::OccupancyGrid |
Positive match grid for debug |
~/debug/negative_grid |
nav_msgs::msg::OccupancyGrid |
Negative match grid for debug |
~/debug/matched_grid |
nav_msgs::msg::OccupancyGrid |
Matched pattern grid for debug |
~/debug/vote_grid |
nav_msgs::msg::OccupancyGrid |
Vote grid for marker detection debug |
Parameters
{{ json_to_markdown(“localization/autoware_landmark_based_localizer/autoware_lidar_marker_localizer/schema/lidar_marker_localizer.schema.json”) }}
How to launch
When launching Autoware, set lidar-marker for pose_source.
ros2 launch autoware_launch ... \
pose_source:=lidar-marker \
...
Design
Flowchart
```plantuml @startuml
group main process start if (Receive a map?) then (yes) else (no) stop endif
:Interpolate based on the received ego-vehicle’s positions to align with sensor time;
if (Could interpolate?) then (yes) else (no) stop endif
:Detect markers (see “Detection Algorithm”);
:Calculate the distance from the ego-vehicle’s positions to the nearest marker’s position on the lanelet2 map;
if (Find markers?) then (yes) else (no) if (the distance is nearby?) then (yes) stop note : Error. It should have been able to detect marker else (no) stop note : Not Error. There are no markers around the ego-vehicle endif endif
:Calculate the correction amount from the ego-vehicle’s position;
if (Is the found marker’s position close to the one on the lanelet2 map?) then (yes) else (no) stop note : Detected something that isn’t a marker endif
:Publish result;
stop
File truncated at 100 lines see the full file
-
Assumed
ringofPointXYZIRADRTaschannelofPointXYZIRC. ↩
Changelog for package autoware_lidar_marker_localizer
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- refactor(localization): move node design files into each package (#13101) Co-authored-by: Claude Opus 5 (1M context) <<noreply@anthropic.com>>
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(lidar_marker_localizer): extend lidar-marker localization to enhance flexibility and debugging capabilities (#11574)
- feat: parse landmarks only in target id list
- feat: Add a y-axis condition to marker selection around the vehicle
- feat: correct z axis of self pose
- feat: reference a certain ring
* feat: make detect_landmarks function templated for using PointType in both PointXYZIRC and PointXYZIRADRT
- feat: make detect_landmarks ring loop robust to empty pointclouds
- Add check to skip empty ring pointclouds in detect_landmarks
- Prevent unnecessary processing and possible errors when a ring has no points
- feat: make save_intensity function for csv output
- Enable generic processing for multiple point cloud types
- Prepare for future multi-LiDAR marker localization support
- refactor: fix member function declarations and add const qualifiers
- feat: add debug outputs for marker detection process
- feat: make queue sizes for output pose configurable
- doc: Add a y-axis condition to marker selection around the vehicle
- doc: add marker_height_from_ground to lidar_marker_localizer.schema.json
* feat: add "lidar-marker" pose estimator to pose_estimator_airbiter # Conflicts: # launch/tier4_localization_launch/launch/localization.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/lidar_marker_localizer.launch.xml # launch/tier4_localization_launch/launch/pose_twist_estimator/pose_twist_estimator.launch.xml
- feat: make initial ring id range configurable
- doc: update for ndt_lidar-maker mode
- doc: update for new features in lidar-marker localizer
* doc: fix indent To indicate the contributor's affiliation
- refactor: update autoware_utils dependency
- style(pre-commit): autofix
- doc: update schema.json
- style(pre-commit): autofix
- fix: debug topics table and wrong condition to output
- style(pre-commit): autofix
- fix: diagnostics_interface dependency
- chore: remove codes commented out
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
-
Contributors: Motz, github-actions
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- feat: localization related packages support jazzy (#11419)
- Contributors: Ryohsuke Mitsudome, 心刚
0.49.0 (2025-12-30)
0.48.0 (2025-11-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(autoware_lidar_marker_localizer): fix deprecated autoware_utils header (#10514)
- fix autoware_utils header
- style(pre-commit): autofix
* fix: remove not used library ---------Co-authored-by:
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| autoware_localization_launch |
Launch files
- launch/lidar_marker_localizer.launch.xml
-
- param_file [default: $(find-pkg-share autoware_lidar_marker_localizer)/config/lidar_marker_localizer.param.yaml]
- input_lanelet2_map [default: ~/input/lanelet2_map]
- input_ekf_pose [default: ~/input/ekf_pose]
- input_pointcloud [default: ~/input/pointcloud]
- output_pose_with_covariance [default: ~/output/pose_with_covariance]
- service_trigger_node_srv [default: ~/service/trigger_node_srv]