Machine-readable: manifest · index · English Markdown
Errors and troubleshooting
First isolate the failing layer: upload, build, viewing, localization request, or AR alignment. Avoid changing scan data, intrinsics, and coordinate conversion at the same time.
Upload and build
| Symptom | Check first |
|---|---|
| ZIP is not recognized | Confirm that the file is a valid ZIP and contains everything required by the selected input type. |
| Device type mismatch | Select the correct LiDAR brand and confirm that its E57 retains the expected device metadata. |
| Images and poses do not match | Match filenames, extensions, and letter case exactly between the images and pose table. |
| Capture density is too low | Keep mobile capture spacing within about 2 m and fixed stations within about 5 m; add coverage at entrances and turns. |
| Parsing fails | Confirm that the whole video plays, that its format is currently accepted by the interface, and that a cloud-drive link points directly to one downloadable file. |
| Building fails | Keep the Map ID, failure time, Input, and Pipeline version. Retry once as prompted; contact support if the same error repeats. |
HTTP status
| Status | Action |
|---|---|
400 | Fix missing or invalid image, fields, or intrinsics. |
401 | Replace a missing, expired, or malformed API Key. |
403 | Correct resource ownership or the API/Map/Project Key combination. |
422 | Capture a clearer view with more mapped fixed detail. |
429 | Back off according to the response; do not retry concurrently. |
5xx | Keep the current AR alignment and retry later. |
The result looks wrong
- Content is mirrored or rotated 180°: the CV-to-graphics axis conversion is missing or has been applied twice.
- Content jumps when a response arrives: the client used the current AR camera transform instead of the transform captured with the uploaded image.
- There is a constant offset: Content, the map Origin, and the localization pose are not expressed in the same map coordinate frame.
- Only some devices fail: inspect the actual image resolution, rotation, crop, and intrinsics submitted by those devices.
- One area consistently fails: inspect mapping cameras and Points in Space Studio. Rescan and rebuild if that area lacks coverage.
When contacting support, provide the Portal environment, Map ID, timestamp and timezone, input type, Pipeline version, HTTP status, and a key-redacted minimal request. Do not send credentials or complete customer source data outside an approved secure channel.