For autonomous vehicle teams
When road-test data keeps ending in one-off scripts, LidarFlow gives you one browser path from rosbag or MCAP to a mapped point cloud you can review across the team.
Use cases
If you record LiDAR or camera data and still write glue scripts to turn it into 3D, this page is for you.
LidarFlow replaces the pile of bag-conversion commands, topic checks, mapping scripts, and handoffs that grows around a repeated rosbag or MCAP workflow — whether you reconstruct from LiDAR or a single camera.
For robotics field validation
Use one workflow for upload, topic validation, run status, and artifact delivery instead of rebuilding the post-processing chain every time a new recording lands.
For site capture and reconstruction
If your team records LiDAR — or just a forward camera — and then spends days cleaning up the path from capture to a delivered point cloud, LidarFlow replaces that glue. With only a camera, the monocular metric-depth path still gets you metric 3D.
Best fit
Who this platform is for
- Teams already recording LiDAR and tired of stitching together post-processing scripts
- Operators who need visible QA around mapping and georeferencing runs
- Leads who want a repeatable workflow without standing up a full internal SLAM platform first
Delivery
Why teams use it
The value is not only map creation. It is also the audit trail: what topics were selected, what settings were used, what worker processed the run, and which artifacts came back out.
Invite-only beta