Offline environment maps
Inspect captured geometry in the software used for the research workflow.
Robotics & Autonomous Systems
Evaluate spatial datasets for robotics mapping research.
Use captured environments to evaluate offline mapping, spatial representation, and downstream development workflows. Confirm the available data, licensing, and interfaces before treating a scanner as a development platform.
The project challenge
Separate a reusable map from a real-time integration.
A processed point cloud can be useful for environment review and offline research. Live navigation also depends on runtime access, timing, interfaces, software, and system validation that need explicit product-level confirmation.
Useful deliverables
Define the record your team needs.
Development test inputs
Agree how the dataset will be transformed, referenced, and evaluated downstream.
Documented data access
Confirm delivered files, coordinate conventions, licensing, and any source-data availability.
From planning to handover
A workflow for robotics & autonomous systems.
- 01
Specify the research task
Identify offline mapping, simulation input, or a proposed live integration.
- 02
Confirm the data contract
Agree formats, attributes, coordinates, licenses, and required interfaces.
- 03
Evaluate a sample
Inspect the supplied file and test the intended downstream conversion.
- 04
Scope further development
Validate any live access, mounting, synchronization, or SDK needs separately.
Project requirements
Agree these requirements before capture.
- Processed versus source data. A LAS point cloud and a raw sensor recording expose different information.
- Interface availability. Confirm APIs, SDKs, streaming, and version support for the exact configuration.
- Coordinate handling. Agree axes, units, references, and transformations for downstream systems.
- System responsibility. Define the validation and safety responsibilities for any autonomous application.
Relevant systems
Choose around the capture task.
Cobra S & X
Start with the supplied processed LAS sample and discuss any additional data or interface requirements.
Explore Cobra S & X →Pentra
Evaluate portable environment capture where its supported exports match the offline research task.
Explore Pentra →Radix
Assess a 360° capture configuration for mapping geometry, subject to confirmed data access.
Explore Radix →Evaluate the selected hardware and processing configuration using the project’s environment, required detail, and deliverables.
Related reading and resources
Explore the evidence and supporting workflow.
Processed dataset example
Review file format, point count, and coordinate notes.
Explore Processed dataset example →Sensor inputs and processing
Understand how capture inputs differ from delivered outputs.
Explore Sensor inputs and processing →File and interface requirements
Confirm what the chosen workflow can exchange.
Explore File and interface requirements →Robotics & Autonomous Systems questions
Does a BAG or LAS export guarantee ROS integration?
An exported recording or point cloud does not define a supported live ROS interface. Confirm message access, drivers, timing, licensing, and supported versions for the intended integration.
Can the scanner provide autonomous obstacle avoidance?
Any real-time obstacle-avoidance capability, interface, and system validation require explicit confirmation. This page describes spatial dataset evaluation for mapping and development.