lidar-odometry

Estimate robot motion by matching consecutive laser scans into nav_msgs/Odometry.

18|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill lidar-odometry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lidar-odometry
Source: https://github.com/wimblerobotics/ros2-copilot-skills/tree/main/lidar-odometry
Command: npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill lidar-odometry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lidar odometry provides ego-motion estimates by matching consecutive laser scans or point clouds, delivering odometry data to supplement or replace wheel-based estimates.

Core Features & Use Cases

  • Backends supported: rf2o_laser_odometry (2D), kiss-icp (3D), and scan_tools (2D) for scan matching.
  • ROS 2 integration: outputs nav_msgs/Odometry and is designed to fuse with EKF or SLAM pipelines.
  • Use Case: enhances localization in low-slip or feature-rich environments where wheel odometry is unreliable or biased.

Quick Start

Configure and run the lidar-odometry workflow with rf2o_laser_odometry or kiss-icp and integrate its odometry output into your EKF-based localization.

Frequently Asked Questions about lidar-odometry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate robot motion using lidar scan matching in ROS 2?▼

You can estimate robot motion by configuring backends like rf2o_laser_odometry or kiss-icp to match consecutive scans. This Skill outputs nav_msgs/Odometry data designed to fuse with EKF or SLAM pipelines in ROS 2.

Why use lidar odometry instead of wheel odometry for robot localization?▼

Lidar odometry is used instead of wheel odometry to enhance localization in low-slip or feature-rich environments. It provides robust ego-motion estimates using scan matching when wheel-based estimates are unreliable or biased.

Can I generate 3D point cloud odometry using kiss-icp with this ROS 2 tool?▼

Yes, you can generate 3D point cloud odometry using the kiss-icp backend. The Skill supports cross-backend compatibility, allowing you to configure kiss-icp alongside 2D options like rf2o_laser_odometry and scan_tools.

What is the best way to fuse lidar odometry with an EKF localization pipeline?▼

The best way to fuse lidar odometry with an EKF pipeline is to output nav_msgs/Odometry from your configured scan matching backend and integrate it directly. The Skill is specifically designed for integration with EKF-based localization workflows.

Does ROS 2 lidar odometry support both 2D laser scans and 3D point clouds?▼

Yes, ROS 2 lidar odometry supports both 2D laser scans and 3D point clouds. It utilizes backends like rf2o_laser_odometry and scan_tools for 2D scenarios, and kiss-icp for 3D ego-motion estimation.

When should I not use scan matching for ego-motion estimation?▼

You should not use scan matching for ego-motion estimation in environments lacking geometric features or with extreme dynamic obstacles, as lidar odometry relies on matching consecutive point clouds to produce reliable nav_msgs/Odometry.