# Build a map from 360° video

After scan data and spatial constraints are configured, 01Spatial turns the 360° video into a spatial map for localization, content authoring, and AR delivery. The process runs in the cloud and continues even after you leave the page.

## What happens during a build

The system organizes valid spatial observations into one continuous map and applies the scale, origin, and coordinate orientation defined during configuration. 01Spatial then checks the result for consistency, coverage quality, and release completeness.

A result that passes these checks is packaged as production-ready map assets for Space Studio, the Localization API, and AR clients. If the input or constraints cannot support a reliable result, the task fails explicitly with an actionable reason instead of publishing a map that only appears complete.

## Start the build

For the manual method in this guide, complete every required check in Map Configurator and select **Build**. Portal changes the map to a queued or building state.

If [01Spatial Reference Boards](/tutorials/mapping/panorama-camera-video/spatial-reference-board) are present and the parse report confirms sufficient observation quality, the map card offers **Build with ChArUco**. This is the automatic reference route. Choose either the board route or manually configured GCPs; do not submit two competing world-coordinate definitions together. GCP stands for **Ground Control Point**, a fixed point with known site coordinates that can be identified in several frames.

## Understand map states

| State | Meaning | What to do |
| --- | --- | --- |
| Pending | The job is waiting for mapping capacity | Keep the map and source unchanged, then check progress later |
| Building | The system is generating the map and preparing localization assets | Do not start another build; you may leave and return later |
| Ready | The map and localization assets passed publication gates | Run real localization tests in Space Studio |
| Failed | An input, geometry, constraint, or asset gate failed | Read the failure reason, correct the configuration or recapture, and rebuild |

Completion time depends on video length, extracted frame count, space size, and the server queue. The task does not depend on keeping the page open; its status is stored by the server.

## Validate localization after Ready

**Ready** means automated health checks passed; it does not mean every real use case has been accepted. Before publishing AR content, [run a localization test in Space Studio](/tutorials/localization/space-studio-test) with the target device or representative images and verify that:

- Localization succeeds near the route start, end, and middle.
- Doors, corners, and cross-room transitions do not jump to the wrong area.
- Normal device height and orientation work, not only the mapping-camera height.
- Expected daylight, evening, or artificial-light conditions meet the project requirement.
- The localized origin, axes, and scale agree with content in Space Studio.

If one area is unstable, first distinguish insufficient coverage, blur, weak connectivity, and incorrect coordinate constraints. Correct the cause instead of repeatedly submitting the same input.

## Respond to failures

### Disconnected area

Check whether doors, corners, and long corridors have repeated bidirectional coverage. Add a high-confidence tie point only when existing frames genuinely see the same static point. If there is no shared view, recapture; a tie point cannot create missing visual evidence.

### Insufficient image quality or coverage

Common causes are motion blur, low light, blank walls or glass, and moving crowds. Review the exported video, improve lighting, walk more slowly, or change the route and recapture.

### Abnormal GCP or scale residuals

Confirm that units are meters, the up axis is correct, XYZ values were entered accurately, and every observation lands on the same physical point. Do not add incorrect GCPs in an attempt to average out the error.

### Build succeeds but field localization is unstable

Use Space Studio to test the failing area and record device, direction, lighting, and image evidence. A localized failure usually needs better viewpoint coverage in that region. Global offset or scale errors point first to the GCP coordinate frame.

## Rebuilds and source-video changes

The parsed data version behind a Ready map is immutable. You can correct constraints and rebuild safely on that version. To replace the video or reparse the scan data, create a new map. This prevents active localization assets from being silently replaced by new input.