Structured ingest
LiDAR is required. GNSS and IMU are optional, but the UI makes their presence visible and useful when the data exists.
About LidarFlow
Upload. Validate. Map. Georeference. Download.
LidarFlow exists because there is still a gap between recording robotics data and getting back a mapped output. Visualization tools help inspect the bag. Desktop tools help some teams export frames. This product focuses on the missing SaaS step: rosbag or MCAP in, georeferenced map out.
What the product does
From upload to artifact delivery in one place
Upload. Validate. Map. Georeference. Download. All in your browser.
Production-minded mapping
Runs are tracked, artifacts are downloadable, and every selected setting is visible instead of living in an ad hoc notebook cell.
Clear attribution
LidarFlow builds on serious upstream work and makes that dependence explicit instead of hiding it behind generic platform copy.
Foundations
Built on top of strong mapping and georeferencing projects
GLIM
GLIM
GLIM powers the precision mapping path behind LidarFlow and the canonical map export path.
FlexCloud
FlexCloud
FlexCloud powers the GNSS-backed georeferencing stage that turns SLAM outputs into geographically meaningful deliverables.
Next step