Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Description | |
| Checkout URI | https://github.com/MOLAorg/mola_mapper.git |
| VCS Type | git |
| VCS Version | develop |
| Last Updated | 2026-11-17 |
| Dev Status | DEVELOPED |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mola_mapper | 0.1.0 |
README
:world_map: mola_mapper :arrows_counterclockwise:
Global back end of MOLA: keyframe map, loop closure and geo-referencing
LiDAR-inertial odometry with loop closure and a global pose graph (GNSS, gravity, gyroscope), for MOLA, in C++ and ROS 2.
Documentation | MOLA | Solutions | Plans & Pricing
The live mola_mapper GUI building the map of the Colosseum
(VBR dataset, colosseo_train0), sped up 10-80x.
Points are colored by height, and after each loop closure the corrected keyframes glide into place.
🤖 What is mola_mapper?
mola::mapper::Mapper is a MOLA module that runs next to a front end (LiDAR
odometry) and its state estimator. It keeps a central map of keyframes, looks
for loop closures, and optimizes a global pose graph with GNSS, gravity and
gyroscope factors, which also yields the geo-reference. It does little
estimation of its own and is not a mola::NavStateFilter.
🗺️ Features
- 🔁 Loop closure detection in a background thread (
mola_sm_loop_closure), with global registration of bird’s-eye-view descriptors and ICP refinement - 📈 Global pose graph (GTSAM): odometry chain, loop closures, GNSS, gravity, gyroscope and wheel odometry factors
- 🌍 Geo-referencing:
T_enu_to_mapis estimated with its covariance and published live - 🔄 Loop closure corrections are sent back to the LiDAR odometry, which rebuilds its local map from the corrected keyframes
- 🖥️ Live GUI: keyframe map at the optimized poses, colored by height, with corrections gliding into place and an optional scripted camera (overviews, close-ups, loop closure shots)
- 🧰 Offline tools: re-optimize a saved graph (
mola-mapper-reoptimize), or replay a recorded mapper input to tune it deterministically (mola-mapper-cli) - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Lyrical, Rolling), and usable from pure C++ with
mola-cli
🚀 Quick start
Install MOLA following the installation guide.
For the datasets with a profile in mola_lidar_odometry (the ones of its
mola-lo-gui-<name> launchers), mola-mapper-gui-<name> runs LIO, the state
estimator and the mapper live, with the GUI:
mola-mapper-gui-vbr /path/to/vbr/colosseo_train0/
mola-mapper-gui-kitti 00
# Any profile, e.g. TIERS with its sensor:
TIERS_SENSOR=ouster-os0 mola-mapper-gui-dataset tiers /path/to/sequence.bag
Launchers exist for conslam, fomo, geode, grandtour, hilti2022, kitti,
newer-college, ntu-viral, rosbag1, rosbag2 and vbr. Variables set by the
caller win, e.g. MOLA_WITH_GUI=false MOLA_QUIT_ON_DATASET_END=true for a headless run.
🧩 Module topology
-
mola::LidarOdometry(LIO) uses the state estimator (mola::state_estimation_smoother::StateEstimationSmoother) as its onlyNavStateFilter, and pushes sparse keyframes to the mapper throughmola::SharedKeyframeMap. -
mola::mapper::Mapperreceives those keyframes, and GNSS and IMU readings from the raw data source as amola::RawDataConsumer. It also implementsmola::MapSourceBase(geo-reference),mola::DiagnosticsProviderandmola::ExecutableBase. - After loop closures, it tells the front ends (
mola::LocalMapCorrectionSource), which can then rebuild their local maps from the corrected keyframes around them, including those of earlier visits.
File truncated at 100 lines see the full file