01Spatial Documentation

Machine-readable: manifest · index · English Markdown

Scan with FJD

An FJD input uses panoramas plus pano-pose-info.csv, with an optional E57 point cloud. E57 is a common reality-capture exchange format; in this workflow it supplies optional 3D geometry. 01Spatial validates and normalizes the files as one map input.

FJD data requires neither 01Spatial Reference Boards nor Map Configurator; upload it and start the build.

Prepare the export package

The ZIP must contain:

  • .jpg, .jpeg, or .png panoramas.
  • A pose file named exactly pano-pose-info.csv.
  • Optionally, one E57 point cloud.

Images may be stored in a ZIP subdirectory. Image names in the CSV must match the panorama filenames exactly. If you rename an image, update the CSV before upload.

site-fjd.zip
├── panoramas/
│   ├── pano_00001.jpg
│   └── pano_00002.jpg
├── pano-pose-info.csv
└── scan.e57              # optional

Capture and upload

Keep effective mobile spacing within about 2 m and add overlap at doors, turns, and occluded areas. Finish with a closed route.

Select FJD in Spatial Maps and choose:

  • Local: select the complete ZIP from this computer and keep the page open until upload completes.
  • Cloud, recommended for large files: upload the ZIP to a drive supported by the current Portal interface, then provide a direct file link for server-side download.

The FJD input submits these related files together in one ZIP so the panorama, pose-table, and point-cloud versions cannot diverge. Select Build after upload.

Portal reports the panorama count, pose-file status, and E57 availability. When Ready, compare the camera path, Points, and available LiDAR data before localization tests.