TixiaoShan/LIO-SAM
LIO-SAM: Tightly-coupled Lidar Inertial Odometry via Smoothing and Mapping observed · 2026-08-28
Health v2 · maintenance only
35/100
- Activity 6
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2254
- days_rel: n/a
- days_push: 565
- n_releases_24m: 0
Adoption not part of the score
4895 stars · 1528 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
LIO-SAM is a real-time tightly-coupled lidar-inertial odometry and mapping package built on factor graph optimization with GTSAM. It fuses lidar and IMU data to produce high-accuracy 3D odometry and mapping, running up to 10x faster than real time.
Use cases
- estimate robot pose from lidar and IMU data
- build 3D maps with a Velodyne or Ouster lidar
- run real-time SLAM on a mobile robot or handheld device
- fuse GPS factors with lidar odometry
- localize a robot in a previously mapped environment
When to choose
- you need accurate real-time lidar-inertial odometry in ROS
- you have a supported lidar (Velodyne, Ouster, Livox) with a 9-axis IMU
- you want a well-cited, widely used SLAM baseline for research or deployment
When to avoid
- you have no IMU or only low-rate IMU data
- you need visual or visual-inertial SLAM with cameras
- you are not using ROS and don't want to adapt the code
Facets
library · maturity stable
robotics simulation computer-vision math robotics autonomous-vehicles cpp slam lidar-odometry lidar-inertial factor-graph-optimization gtsam ros 3d-mapping velodyne ouster algorithms linux
1 source
- readme: https://github.com/TixiaoShan/LIO-SAM · fetched 2026-08-28 · c88902f7658a
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| TixiaoShan/LIO-SAM | main | 35 |
For agents
markdown · JSON · MCP: product_card(name="TixiaoShan/LIO-SAM")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem