Turn a LiDAR bag into an Autoware-compatible pointcloud map.
lidarslam_ros2 pairs the RKO-LIO frontend with the
graph_based_slam backend, then writes a validated
pointcloud_map/ and map_projector_info.yaml.
New here? The Docker one-liner needs no ROS 2 workspace.
Pick your path¶
Just see a map
Run a pinned Docker image on a sample MID-360 bag. No build, no ROS install.
02Map my own bag
Check topics and calibration with lidarslam-map doctor, then map it.
Build from source
Build the current release from source, run benchmarks, or contribute.
Quick start¶
mkdir -p "$PWD/lidarslam_output"
docker run --rm \
-e LIDARSLAM_HOST_UID="$(id -u)" \
-e LIDARSLAM_HOST_GID="$(id -g)" \
-v "$PWD/lidarslam_output:/lidarslam_ws/output" \
ghcr.io/rsasaki0109/lidar_slam_ros2:v0.10.0-humble
On Ubuntu 24.04 use v0.10.0-jazzy. The map lands in
lidarslam_output/mid360_demo.
What you get¶
A run produces a portable map bundle that Autoware tooling can load directly:
output/my_map/
├── pointcloud_map/ # tiled PCD map
├── map_projector_info.yaml # local map projection
└── ... # trajectory, config, and verification reports
Open the result in the browser-first Autoware Foxglove path or read the Autoware-Compatible Map Authoring guide.
Learn more¶
Autoware map authoring
The supported public path from bag to validated map bundle.
Operator workflows
Required topics, optional GNSS, packet paths, and map-save flows.
Degeneracy guide
Recover tunnels, fog, and corridors where LiDAR-only SLAM can drift.
Benchmarking
Run the tracked benchmark suite and reproduce published reports.
Comparison
Current public position and benchmark-backed configuration summary.
Product contract
Supported inputs, outputs, entrypoints, and explicit non-goals.
At a glance¶
| Area | Current public position |
|---|---|
| Main path | RKO-LIO + graph_based_slam |
| Map output | pointcloud_map/ + map_projector_info.yaml |
| Long-loop evidence | MID360 |
| Ground-truth benchmark | NTU VIRAL tnp_01 |