Projects

Projects are where survey work happens. A project belongs to a branch, and the survey you upload and read back on the map lives inside a project.

The lifecycle of a survey

1. Uploaded into the project, in parts, and resumed if the transfer breaks.
2. Scanned, then ingested by a worker off a durable queue.
3. Published — as the last step of that ingest job.
4. Read back on the map in the Workspace.

There is no publish button. Publication is the automatic consequence of the ingest job finishing; a customer has no publish control and the API has no customer publish route. If the result is wrong, the correction is a new release — the published one is immutable.

Processing states stay on the project page in the Console. The Workspace opens a published release.

The projects list

Each row's ⋯ menu offers Rename, Members and Archive.

Archiving asks first, and the question is asked in the row itself: the row expands into a panel showing which project you are about to archive. It is deliberately not a pop-up — it does not trap focus and does not cover what you already had open.

This page is being written.

The create, upload and resume flows are not written up with screenshots yet.