Wave 1 segment

Route, corridor, and environment capture for autonomy teams that need grounded refresh data without vague mapping claims.

Roam helps autonomy, mapping, and validation teams review route and environment delivery structure before live corridor or site-refresh programs begin.

Review route and corridor proof Start program scoping

Likely buyer teams

Autonomy and mapping leadsSimulation and validation teamsRoute expansion teams

What teams usually need to confirm

Open-format outputs and explicit caveats around HD-map-adjacent deliverables
Manifest and acceptance criteria examples for route refresh programs
Clear line between demo proof and production review

First pains to address

Changed infrastructure and new geographies create evaluation risk.

Teams need open-format route and scene data without confusing it with certified HD-map products.

Procurement cares about provenance, refresh cadence, and delivery structure.

Example program shapes

Urban corridor refresh for new-market validation

Yard, dock, and interchange environment capture

Route change-detection and validation support

Deliverable fit

Output families that fit this workflow.

Open full deliverables matrix

Point clouds

Structured geometry for measurement, mapping, simulation prep, and change review.

Authoritative for: Measurement-adjacent review, geometry QA, GIS intake, and reconstruction baselines.
Preview use: Subset exploration, coverage checks, and visual inspection.

LAZ / LASCOPCE57PLY

GIS layers

Vector and raster exports for infrastructure, corridor, and geospatial modernization workflows.

Authoritative for: Spatial analysis, corridor review, site documentation, and digital-infrastructure intake.
Preview use: Map previews, feature review, and QA walkthroughs.

GeoJSONGeoPackageCOGShapefile / KML

HD map objects

Route and roadway object references for autonomy evaluation programs where object layers are in scope.

Authoritative for: Autonomy evaluation, route refresh review, and roadway object reasoning where the engagement explicitly calls for it.
Preview use: Manifest-level compatibility checks and object-layer inspection.

Lanelet2OpenDRIVEGeoJSON feature layers

Raw sensor data

Camera, LiDAR, calibration, pose, and trajectory data for teams that need first-order inputs rather than post-processed visuals alone.

Authoritative for: Training corpora, reprojection, calibration review, and downstream reconstruction pipelines.
Preview use: Subset validation, pose sanity checks, and pipeline bring-up.

Image/video framesPCAP / raw LiDAR exportsTrajectory / pose filesCalibration bundles

Materials you can review now

public exampleOpen asset

Sample manifest

Example manifest structure showing delivery versioning, formats, checksums, and CRS metadata.

Why review it: Roam can describe delivery structure in a machine-readable way before a live program starts.

Boundary: This is an illustrative public example, not a customer-specific delivery commitment.

public exampleOpen asset

Acceptance criteria outline

Example definition-of-done checklist for coverage, metadata, and artifact integrity.

Why review it: Roam can frame output acceptance criteria in operational terms.

Boundary: Thresholds are illustrative and must be set in the actual engagement.

demo-onlyOpen asset

Sample dataset catalog

Live demo datasets, manifests, and gated artifact downloads.

Why review it: The public demo routes are real and runnable today.

Boundary: Demo subsets are not equivalent to a production program or customer packet.

public exampleOpen asset

Sample delivery packet

Public outline of a delivery packet with manifests, QA, artifact references, and caveats.

Why review it: Roam thinks in terms of delivery packets rather than isolated media files.

Boundary: Commercial terms, sensitive handling rules, and customer-specific destinations stay under NDA.

Likely objections

Is this a mapping vendor pitch in disguise?

No. Roam supports route and environment capture with explicit caveats. It does not present itself as a public HD-map platform.

We need validation and refresh, not abstract AI branding.

The offer is route refresh, evaluation corpora, and delivery discipline, not generic AI positioning.

Ways to engage

Technical evaluation

Start with docs, sample data, format references, and the sandbox before opening a live program.

Audience: ML engineers, simulation leads, GIS analysts, platform teams

Available now: Public and available now through developer docs, sandbox APIs, and sample-data examples.

Validate technical fit

Live program scoping

Scope environments, outputs, review constraints, and timeline through an intent-first intake path.

Audience: Founders, VPs, robotics PMs, autonomy leads, operations buyers

Available now: Public intake is available now; commercial and operational specifics are finalized in the engagement.

Start program scoping

Security, privacy, and legal diligence

Bring data handling, deletion, privacy-sensitive capture, and diligence questions in early.

Audience: Security reviewers, privacy counsel, legal, procurement

Available now: Public diligence materials are available now; customer-specific review expands under NDA when needed.

Start diligence review

From evaluation to scoping

Review route and corridor proof

Inspect route-facing formats, metadata, and caveats.

Raise NDA, security, privacy, and delivery constraints in the first conversation instead of after procurement restarts the process.

Review route and corridor proof Start program scoping

Need immediate scheduling? Use the programs inbox.