{
 "id": "epnjypxrr4",
 "slug": "lidar-odometry",
 "title": "LiDAR odometry",
 "updated": "2026-10-15",
 "topic_path": [
  {
   "id": "technology",
   "label": "Technology and the built world",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology"
  },
  {
   "id": "technology.computing",
   "label": "Computing and digital systems",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing"
  },
  {
   "id": "technology.computing.ai",
   "label": "Artificial intelligence and data",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.ai"
  },
  {
   "id": "technology.computing.ai.perception_language",
   "label": "Language and vision AI",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.ai.perception_language"
  },
  {
   "id": "technology.computing.ai.computer_vision",
   "label": "Computer vision",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.ai.computer_vision"
  },
  {
   "id": "technology.computing.ai.cv_methods",
   "label": "Vision methods and geometry",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.ai.cv_methods"
  },
  {
   "id": "technology.computing.ai.cv_methods.pose_estimation",
   "label": "Pose estimation and tracking of pose",
   "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.ai.cv_methods.pose_estimation"
  }
 ],
 "geo": [
  {
   "id": "geo.nongeo.t2001.technology.computing.ai.perception_language",
   "label": "Non-geographic · 2001 to 2020: Language and vision AI",
   "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001.technology.computing.ai.perception_language",
   "path": [
    {
     "id": "geo.nongeo",
     "label": "Non-geographic",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo"
    },
    {
     "id": "geo.nongeo.t2001",
     "label": "Non-geographic · 2001 to 2020",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001"
    },
    {
     "id": "geo.nongeo.t2001.technology",
     "label": "Technology and the built world",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001.technology"
    },
    {
     "id": "geo.nongeo.t2001.technology.computing",
     "label": "Computing and digital systems",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001.technology.computing"
    },
    {
     "id": "geo.nongeo.t2001.technology.computing.ai",
     "label": "Artificial intelligence and data",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001.technology.computing.ai"
    },
    {
     "id": "geo.nongeo.t2001.technology.computing.ai.perception_language",
     "label": "Language and vision AI",
     "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t2001.technology.computing.ai.perception_language"
    }
   ]
  }
 ],
 "excerpt": "LiDAR odometry is a robotics and computer vision method that estimates a sensor's 6-DoF motion by registering successive LiDAR point cloud scans, supporting localization, SLAM, and autonomous navigation.",
 "snippet": "LiDAR odometry is a robotics and computer vision method that estimates a sensor's 6-DoF motion by registering successive LiDAR point cloud scans, supporting localization, SLAM, and autonomous navigation.",
 "node": "technology.computing.ai.cv_methods.pose_estimation",
 "markdown": "# LiDAR odometry\n\nLiDAR odometry is a robotics and computer vision method that estimates a vehicle's or sensor's incremental 6-DoF motion by registering successive LiDAR point cloud scans. Its outputs are pose increments between scans, an integrated trajectory, and, when a map is maintained, a 3D reconstruction that supports localization, SLAM, and autonomous navigation.<sup>[1](https://arxiv.org/html/2407.20465v3)</sup><sup> • </sup><sup>[2](https://arxiv.org/abs/2409.10824)</sup> Because registration errors accumulate, long-term drift is typically corrected by post-processing such as loop closure.<sup>[2](https://arxiv.org/abs/2409.10824)</sup>\n\n| Key fact | Value |\n|---|---|\n| Quantity estimated | 6-DoF ego-motion between consecutive LiDAR scans, as a transform in SE(3)<sup>[2](https://arxiv.org/abs/2409.10824)</sup> |\n| Typical drift | On the order of 1 m per 1000 m traveled for LiDAR SLAM, strongly dependent on environment and scene dynamics<sup>[3](https://robots.ox.ac.uk/~mfallon/publications/2025CHAPTER_behley.pdf)</sup> |\n| LOAM accuracy (KITTI) | 0.57% average translation error, 0.0013 deg/m rotation error (as of Nov 2020)<sup>[4](https://arxiv.org/pdf/2104.05203)</sup> |\n| KISS-ICP accuracy (KITTI) | 0.50% average relative translational error with motion-compensated data<sup>[5](https://arxiv.org/pdf/2103.09708v3.pdf)</sup> |\n| LOAM processing split | Odometry at ~10 Hz, mapping at 1 Hz, integrated pose output at ~10 Hz<sup>[6](https://www.roboticsproceedings.org/rss10/p07.pdf)</sup> |\n| FAST-LIO runtime | 6.7 ms per frame, up to 50 Hz, drift below 0.3% on a 32 m quadrotor trajectory<sup>[7](https://ar5iv.labs.arxiv.org/html/2010.08196)</sup> |\n| Standard pipeline | Pre-processing, feature extraction, correspondence searching, transformation estimation, post-processing<sup>[8](https://ar5iv.labs.arxiv.org/html/2109.06120)</sup> |\n\n## How it works\n\nThe core principle is scan registration: given two point clouds, find the rigid transformation that best aligns them, and interpret that transformation as the sensor's motion. Pose estimation between received scans can be done by scan-to-scan matching or by scan-to-map matching, where the map is an aggregate of multiple scans often down-sampled using a voxel grid or kd-tree; most LiDAR odometry methods rely on some variant of the iterative closest point (ICP) algorithm.<sup>[9](https://www.cs.cmu.edu/~kaess/pub/Potokar25iros.pdf)</sup> ICP aligns two sets of points iteratively by minimizing the distance between corresponding points until a stopping criterion is met.<sup>[10](https://isprs-archives.copernicus.org/articles/XLII-2-W13/1681/2019/isprs-archives-XLII-2-W13-1681-2019.pdf)</sup>\n\nModern systems have replaced ICP's original closed-form least-squares formulation with robustified least squares and point-to-plane pairings, as in LOAM, Fast-LIO2, and MAD-SLAM.<sup>[1](https://arxiv.org/html/2407.20465v3)</sup> LOAM selects feature points on sharp edges and planar surface patches by evaluating smoothness, then uses point-to-edge and point-to-plane scan matching to recover the inter-scan transformation.<sup>[8](https://ar5iv.labs.arxiv.org/html/2109.06120)</sup> LiDAR-only odometry is classified by matching style into direct matching, feature-based matching, and deep learning-based matching.<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup> Feature-based methods are less sensitive to the initial guess and computationally lighter than point-wise G-ICP or NDT, but their convergence accuracy is theoretically worse because they use only part of the raw points.<sup>[4](https://arxiv.org/pdf/2104.05203)</sup>\n\n## How it is done\n\nA practitioner runs a five-stage pipeline: (1) pre-processing, (2) feature extraction, (3) correspondence searching, (4) transformation estimation, and (5) post-processing; correspondence search adopts point, distribution, or network correspondence, with ICP, RANSAC, and neural networks common for point correspondence.<sup>[8](https://ar5iv.labs.arxiv.org/html/2109.06120)</sup>\n\nDeskewing is a key pre-processing step. Because range measurements within one sweep are received at different times while the sensor moves, motion estimation errors can mis-register the resulting point cloud.<sup>[6](https://www.roboticsproceedings.org/rss10/p07.pdf)</sup> A point taken at time j within a scan stamped at time i is deskewed by applying the transformation between those times.<sup>[9](https://www.cs.cmu.edu/~kaess/pub/Potokar25iros.pdf)</sup> KISS-ICP's pipeline illustrates a minimal modern flow: deskew via motion prediction, subsample the scan, estimate correspondences against a local map with an adaptive threshold, register with robust point-to-point ICP, then update a down-sampled map.<sup>[5](https://arxiv.org/pdf/2103.09708v3.pdf)</sup>\n\n## Origin\n\nKISS-ICP was reported by Ignacio Vizzo and colleagues in [IEEE Robotics and Automation Letters](https://www.edgepedia.org/ieee-robotics-and-automation-letters) in 2023 as a return to classical point-to-point ICP with adaptive thresholds.<sup>[12](https://doi.org/10.1109/lra.2023.3236571)</sup><sup> • </sup><sup>[5](https://arxiv.org/pdf/2103.09708v3.pdf)</sup> LIO-SAM was reported by Tixiao Shan and colleagues in 2020 on arXiv, formulating tightly-coupled lidar-inertial odometry as a factor-graph smoothing-and-mapping problem built on LOAM's approach, exploiting preintegrated IMU measurements for deskewing.<sup>[13](https://doi.org/10.48550/arxiv.2007.00258)</sup> LOCUS 2.0 was reported by Andrzej Reinke and colleagues in IEEE Robotics and Automation Letters in 2022, adding adaptive multi-level point-cloud sampling for computationally efficient real-time 3D mapping.<sup>[14](https://doi.org/10.1109/lra.2022.3181357)</sup><sup> • </sup><sup>[1](https://arxiv.org/html/2407.20465v3)</sup>\n\n## Variants\n\nVariants differ mainly in how they match scans and what sensors they fuse. LeGO-LOAM uses [point cloud segmentation](https://www.edgepedia.org/point-cloud-segmentation) to classify ground points versus segmented points and leverages planar ground and edge features to determine a 6-DOF transformation; a two-step Levenberg-Marquardt optimization gives accuracy similar to LOAM with a 35% reduced runtime, and using detected ground points reduces altitude drift that affects LOAM.<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup><sup> • </sup><sup>[8](https://ar5iv.labs.arxiv.org/html/2109.06120)</sup><sup> • </sup><sup>[4](https://arxiv.org/pdf/2104.05203)</sup> CT-ICP interpolates the positions of individual points within a scan between starting and ending poses, giving a continuous-time estimate via scan-to-map matching.<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup> F-LOAM formulates LiDAR SLAM as scan-to-scan matching plus scan-to-map refinement and replaces iterative distortion compensation with a non-iterative two-stage method, reaching real-time performance up to 20 Hz on a low-power embedded computing unit.<sup>[15](https://dl.acm.org/doi/10.1109/IROS51168.2021.9636655)</sup>\n\nLoosely coupled systems use the IMU only for deskewing or initial guesses; tightly coupled systems fuse IMU and LiDAR measurements in a single state estimate. FAST-LIO fuses LiDAR feature points with IMU data through a tightly-coupled iterated extended [Kalman filter](https://www.edgepedia.org/kalman-filter), with a back-propagation process to compensate motion distortion; its Kalman gain computation depends on the state dimension rather than the measurement dimension.<sup>[7](https://ar5iv.labs.arxiv.org/html/2010.08196)</sup> [Benchmarking](https://www.edgepedia.org/benchmarking) of five LiDAR-only methods (LOAM, LeGO-LOAM, KISS-ICP, CT-ICP, and DLO) against LiDAR-inertial methods (LIO-SAM, FAST-LIO2, VoxelMap, DLIO, and Point-LIO) shows that LiDAR-inertial odometry handles aggressive motions, especially sudden rotations, better, and generally surpasses LiDAR-only systems in robustness, but still fails on long sequences prone to cumulative errors.<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup>\n\nOn the KITTI odometry benchmark, LOAM was ranked 2nd among evaluated methods as of November 2020, with average translation error of 0.57% and rotation error of 0.0013 deg/m over subsequences of 100 to 800 m.<sup>[4](https://arxiv.org/pdf/2104.05203)</sup> KISS-ICP reports 0.50% average relative translational error and 0.61 on the rotational metric with motion-compensated data, compared with IMLS-SLAM at 0.55/0.69, MULLS at 0.55/0.65, SuMa at 0.80/1.39, and F-LOAM at 0.84/1.87.<sup>[5](https://arxiv.org/pdf/2103.09708v3.pdf)</sup> Across systems, LiDAR SLAM achieves drift on the order of 1 m per 1000 m traveled, with performance highly dependent on the environment and the level of dynamics in the scene.<sup>[3](https://robots.ox.ac.uk/~mfallon/publications/2025CHAPTER_behley.pdf)</sup>\n\n## Applications\n\nThe integrated trajectory and, when maintained, the 3D map produced as by-products of odometry support localization, SLAM, and autonomous navigation.<sup>[1](https://arxiv.org/html/2407.20465v3)</sup><sup> • </sup><sup>[2](https://arxiv.org/abs/2409.10824)</sup> Since 2014, LOAM has become a cornerstone in autonomous driving and intelligent robotics.<sup>[16](https://www.ieee-jas.net/article/doi/10.1109/JAS.2025.125198)</sup>\n\n## Limitations and alternatives\n\nThe dominant failure mode is degenerate geometry. Feature-scarce, repetitive environments such as tunnels and long corridors cause ambiguity in scan matching because LiDAR odometry relies on geometry and neglects texture and color;<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup> LiDAR SLAM is also prone to failure in wide open spaces.<sup>[17](https://link.springer.com/article/10.1007/s10462-025-11187-w)</sup> In long corridors, highways, or caves, the system may fail to perceive environmental change and cannot estimate motion, a failure called LiDAR degeneracy; one mitigation runs an intermittent visual-inertial odometry only during recognized degeneracy, using dynamic thresholds.<sup>[18](https://ieeexplore.ieee.org/document/10776572)</sup>\n\nICP itself is susceptible to local minima, needs a reliable initial guess, is sensitive to noise such as dynamic objects, and can be computationally slow.<sup>[11](https://link.springer.com/article/10.1007/s11370-024-00515-8)</sup> Accumulated registration errors produce significant long-term drift, corrected by post-processing such as loop closure.<sup>[2](https://arxiv.org/abs/2409.10824)</sup> As an alternative sensing modality, a visual-lidar odometry and mapping method combining both sensors was ranked #1 on the KITTI benchmark with 0.75% relative position drift.<sup>[19](https://frc.ri.cmu.edu/~zhangji/publications/ICRA_2015.pdf)</sup> For comparison, vision-based entries on the KITTI leaderboard such as ESVO report 1.42% translation error and 0.0048 deg/m rotation.<sup>[20](https://www.cvlibs.net/datasets/kitti/table_odometry.php?mode=2)</sup> A comprehensive evaluation at IROS 2025 compares methods including LeGO-LOAM, MULLS, KISS-ICP, and CT-ICP under a common protocol.<sup>[9](https://www.cs.cmu.edu/~kaess/pub/Potokar25iros.pdf)</sup>\n\n## References\n\n1. [A flexible framework for accurate LiDAR odometry, map manipulation, and localization (2024)](https://arxiv.org/html/2407.20465v3)\n2. [Evaluating and Improving the Robustness of LiDAR Odometry and Localization Under Real-World Corruptions (2024)](https://arxiv.org/abs/2409.10824)\n3. [LiDAR SLAM (book chapter, Oxford robotics, 2025)](https://robots.ox.ac.uk/~mfallon/publications/2025CHAPTER_behley.pdf)\n4. [Point-wise or Feature-wise? Benchmark of LiDAR Odometry Methods](https://arxiv.org/pdf/2104.05203)\n5. [KISS-ICP: In Defense of Point-to-Point ICP – Simple, Accurate, and Robust](https://arxiv.org/pdf/2103.09708v3.pdf)\n6. [LOAM: Lidar Odometry and Mapping in Real-time (RSS 2014)](https://www.roboticsproceedings.org/rss10/p07.pdf)\n7. [FAST-LIO: A Fast, Robust LiDAR-inertial Odometry Package by Tightly-Coupled Iterated Kalman Filter](https://ar5iv.labs.arxiv.org/html/2010.08196)\n8. [LiDAR Odometry Methodologies for Autonomous Driving: A Survey](https://ar5iv.labs.arxiv.org/html/2109.06120)\n9. [A Comprehensive Evaluation of LiDAR Odometry Techniques (IROS 2025)](https://www.cs.cmu.edu/~kaess/pub/Potokar25iros.pdf)\n10. [Deep LiDAR Odometry (ISPRS 2019)](https://isprs-archives.copernicus.org/articles/XLII-2-W13/1681/2019/isprs-archives-XLII-2-W13-1681-2019.pdf)\n11. [LiDAR odometry survey: recent advancements and remaining challenges (Intelligent Service Robotics, Springer, 2024)](https://link.springer.com/article/10.1007/s11370-024-00515-8)\n12. [Ignacio Vizzo and colleagues (2023). KISS-ICP: In Defense of Point-to-Point ICP – Simple, Accurate, and Robust Registration If Done the Right Way. IEEE Robotics and Automation Letters.](https://doi.org/10.1109/lra.2023.3236571)\n13. [Shan, Tixiao and colleagues (2020). LIO-SAM: Tightly-coupled Lidar Inertial Odometry via Smoothing and Mapping. arXiv (Cornell University).](https://doi.org/10.48550/arxiv.2007.00258)\n14. [Andrzej Reinke and colleagues (2022). LOCUS 2.0: Robust and Computationally Efficient Lidar Odometry for Real-Time 3D Mapping. IEEE Robotics and Automation Letters.](https://doi.org/10.1109/lra.2022.3181357)\n15. [F-LOAM: Fast LiDAR Odometry and Mapping (IROS 2021, DOI page)](https://dl.acm.org/doi/10.1109/IROS51168.2021.9636655)\n16. [Innovations and Refinements in LiDAR Odometry and Mapping: A Comprehensive Review (IEEE/CAA Journal of Automatica Sinica, 2025)](https://www.ieee-jas.net/article/doi/10.1109/JAS.2025.125198)\n17. [LiDAR, IMU, and camera fusion for SLAM: a systematic review (Artificial Intelligence Review, 2025)](https://link.springer.com/article/10.1007/s10462-025-11187-w)\n18. [Intermittent VIO-Assisted LiDAR SLAM Against Degeneracy: Recognition and Mitigation (IEEE, 2024)](https://ieeexplore.ieee.org/document/10776572)\n19. [Visual-Lidar Odometry and Mapping: Low-Drift, Robust, and Fast (ICRA 2015)](https://frc.ri.cmu.edu/~zhangji/publications/ICRA_2015.pdf)\n20. [KITTI Odometry Benchmark Leaderboard](https://www.cvlibs.net/datasets/kitti/table_odometry.php?mode=2)\n\n---\n*Topic: Encyclopedia › Technology and the built world › Computing and digital systems › Artificial intelligence and data › Language and vision AI › Computer vision › Vision methods and geometry › Pose estimation and tracking of pose*\n\n*Initially written Sep 29, 2026 · Edited: Oct 15, 2026*\n\n*Copyright 2026 EdgeChat AI, a subsidiary of Biostate AI.*\n\nLicense: Edgepedia Community License 1.0, https://www.edgepedia.org/edgepedia/license\n",
 "same_as": [
  "https://www.cs.cmu.edu/~kaess/pub/Potokar25iros.pdf",
  "https://frc.ri.cmu.edu/~zhangji/publications/ICRA_2015.pdf"
 ],
 "url": "https://www.edgepedia.org/lidar-odometry",
 "markdown_url": "https://www.edgepedia.org/lidar-odometry.md",
 "license": {
  "name": "Edgepedia Community License 1.0",
  "url": "https://www.edgepedia.org/edgepedia/license",
  "summary": "Free with credit, commercial use included. AI training is open to everyone. For other uses, organizations over USD 100M in revenue or 100M monthly users license separately.",
  "spdx": "LicenseRef-Edgepedia-Community-1.0"
 },
 "credit": "\"LiDAR odometry\", Edgepedia (EdgeChat), https://www.edgepedia.org/lidar-odometry. Edgepedia Community License 1.0.",
 "credit_md": "\"[LiDAR odometry](https://www.edgepedia.org/lidar-odometry)\", Edgepedia (EdgeChat), [https://www.edgepedia.org/lidar-odometry](https://www.edgepedia.org/lidar-odometry). [Edgepedia Community License 1.0](https://www.edgepedia.org/edgepedia/license).",
 "credit_html": "\"<a href=\"https://www.edgepedia.org/lidar-odometry\">LiDAR odometry</a>\", Edgepedia (EdgeChat), <a href=\"https://www.edgepedia.org/lidar-odometry\">https://www.edgepedia.org/lidar-odometry</a>. <a href=\"https://www.edgepedia.org/edgepedia/license\">Edgepedia Community License 1.0</a>.",
 "speakable": "LiDAR odometry is a robotics and computer vision method that estimates a sensor's 6-DoF motion by registering successive LiDAR point cloud scans, supporting localization, SLAM, and autonomous navigation."
}