01Spatial Documentation

Machine-readable: manifest · index · English Markdown

For robotics developers

Reliable positioning comes first

Robotics projects usually focus on localization and monitoring rather than AR rendering. A robot needs to know where it is, which way it faces, and where it has already travelled across a large environment. 01Spatial provides visual positioning in one persistent Spatial Map and retains localization and movement records for navigation, task execution, monitoring, and review.

A robot can use an onboard camera or an externally mounted camera. With camera intrinsics that correspond to the submitted pixels, 01Spatial returns a 6-DoF position and orientation in the Spatial Map coordinate frame. Wheel odometry, an IMU, local SLAM, or the navigation stack can continue to estimate high-frequency motion. VPS supplies global initialization, area recognition, and accumulated-drift correction.

One map connects robots and operations

The robot client primarily consumes:

  • Global poses returned by the localization API.
  • The Map Origin and axes used to align navigation, task points, and other systems.
  • A sequence of localization results used to correct local SLAM or navigation state.

Space Owners primarily use:

  • Localization records, timestamps, and device trajectories in Analytics.
  • Historical playback of inspection, delivery, or operating routes.
  • Analysis of failed areas, repeated detours, unusual dwell, and operational hot spots.

For example, a factory operator can verify whether an inspection robot covered its assigned areas, identify places where localization repeatedly failed, and compare route duration over time. The robot is a Space User; the organization operating the factory or campus is the Space Owner.

Private deployment and industrial security

Industrial spatial data can reveal facility layout, production lines, equipment positions, access routes, inspection schedules, and operating patterns. 01Spatial supports private deployment so mapping, localization, map assets, and trajectory records can remain in a customer-controlled environment.

Customers can bring the deployment into their existing IT / OT security program and control:

  • Data location, backup, and retention.
  • Network boundaries, service entry points, and isolation.
  • Accounts, device credentials, roles, and least privilege.
  • Logging, auditing, monitoring, and incident response.
  • Software upgrades, model updates, and maintenance windows.

Private deployment does not replace security governance. It keeps data control, access policy, and the runtime environment inside that governance so production-space data does not have to leave a controlled network.

  1. Choose LiDAR or another appropriate capture method and build the Spatial Map.
  2. Align a custom Origin with the facility, CAD / BIM, or navigation coordinate frame.
  3. Validate localization with the production robot camera and its real intrinsics.
  4. Integrate returned poses into SLAM, navigation, or task execution.
  5. Configure device identity, access, trajectory history, and alerts.
  6. Run long-duration tests at production speed and under representative light, occlusion, and network conditions.