# Build a map from standard-camera video

After configuration, 01Spatial turns the standard-camera video into a spatial map for localization, content authoring, and AR delivery. The cloud build continues after you leave the page.

## What happens during a build

The system selects sharp, continuous, well-covered video frames, organizes them into one spatial map, and applies the real-world size, origin, and orientation defined during configuration. It then checks connectivity, target-area coverage, and the completeness of localization assets.

A passing result becomes map assets for Space Studio, the Localization API, and AR clients. If the input or constraints are insufficient, the task fails with an actionable reason instead of publishing a map that only appears complete.

## Start the build

For Map Configurator, complete every required check and select **Build**.

If accepted [01Spatial Reference Boards](/tutorials/mapping/panorama-camera-video/spatial-reference-board) appear in the video and the parse report confirms sufficient observation quality, the map card offers **Build with ChArUco**. Choose either the automatic board route or manually configured GCPs; do not submit two competing coordinate definitions together.

> **GCP** stands for **Ground Control Point**: a fixed point with known site coordinates that can be identified accurately 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 later |
| Building | The system is generating map and localization assets | Do not start another build; you may leave and return |
| Ready | Automated map and asset checks passed | Run field localization tests in Space Studio |
| Failed | An input, coverage, configuration, or output check failed | Read the reason, correct it, and rebuild |

## Validate localization after Ready

**Ready** means automated checks passed; it is not field acceptance. Before release, use [Space Studio localization testing](/tutorials/localization/space-studio-test) to confirm that:

- Localization succeeds near the route start, middle, and end.
- Doors, corners, and cross-room transitions do not jump to the wrong area.
- Normal device height and orientation work.
- Expected lighting conditions remain stable.
- Test content has the correct position, orientation, and distance.

## Respond to failures

### Disconnected area

Check that doors, corners, and corridors were captured continuously from more than one direction. Add a Tie Point only when existing frames genuinely show the same fixed corner. Recapture when no shared view exists.

### Insufficient image quality or coverage

Review the source video for motion blur, low light, prolonged views of blank walls or glass, rapid turns, and moving crowds. Correct the relevant lighting, speed, or route issue and scan again.

### Abnormal GCP or Scale Bar residuals

Verify units, WORLD UP, XYZ values, and the physical location of every observation. Do not add more inaccurate points to average out an error.

### Build succeeds but field localization is unstable

Use Space Studio to record the failing area, device direction, and lighting. A local failure usually needs more viewpoint coverage; incorrect global position or size points first to the GCP coordinates.

## Rebuilds and source changes

You may correct GCPs, Tie Points, or Scale Bars and rebuild. Create a new map to replace or reparse the video so that active map assets are not silently replaced by different input.