Format Reference
Reference current delivery families, output caveats, and interoperability expectations.
Working examples
Each guide gets a technical evaluator from zero to a successful call quickly.
Clear boundaries
Docs distinguish public demo routes from customer-specific production commitments.
Copy-paste examples
Examples, schemas, errors, and caveats are meant to be usable as written.
Docs index
Developer Docs 1
Point clouds and geometry
Roam references LAS/LAZ, COPC, E57, PLY, OBJ, glTF/GLB, and OpenUSD for sample and production discussions. Sample endpoints return metadata and preview subsets rather than full production payloads.
- COPC and LAZ are treated as cloud-native/default point-cloud delivery references.
- PLY remains the preview/archive fallback for neural and research workflows.
- OpenUSD is positioned as the simulation-oriented scene container.
Developer Docs 2
Semantic and autonomy outputs
Use semantic layers, MCAP, Lanelet2, and OpenDRIVE references when validating downstream compatibility and contract requirements.
- MCAP appears in readiness and format references only.
- Autonomy sample outputs are manifest-level today, not full certified HD maps.
- Program-specific output contracts are set during scoping.
Developer Docs 3
Delivery semantics
Sample routes expose manifests, checksums, preview statistics, and artifact descriptors. Production delivery methods remain program-specific and are not self-serve platform guarantees.
Developer Docs 4
Boundaries and caveats
A format listed here means Roam can discuss or scope around it. It does not mean every format is always available on every program or exposed through the public sandbox.
- Accuracy thresholds remain engagement-specific.
- CRS, semantic schemas, and authoritative-use assumptions are agreed in writing before capture starts.
From evaluation to scoping
Need a live test surface?
The docs map the contract. The sandbox proves it with a real demo key, sample-data listing, and readiness response.
Raise NDA, security, privacy, and delivery constraints in the first conversation instead of after procurement restarts the process.
Need immediate scheduling? Use the programs inbox.