A short path from source imagery to usable outputs.
This guide covers the customer workflow and the assumptions that matter most. It is written for pilots, survey technicians, project managers and specialists reviewing the results.
1. Start a project
Create an account, name the organization and open a project for one site or continuing program. Keep repeated flights of the same area in the same project so later jobs can reference earlier results.
Project managers control access. Editors can upload and submit work; viewers can inspect and download permitted results without changing the project.
- Create or open a project.
- Add the people who need access and choose their project role.
- Confirm the preferred compute pool if your account has more than one.
2. Prepare inputs
A strong reconstruction begins before upload. Use sharp, consistently exposed images with sufficient forward and side overlap. Avoid mixing unrelated flights in one job unless they share a compatible coordinate and capture strategy.
| Aerial images | Primary reconstruction source | RGB JPEG or TIFF imagery with usable metadata |
|---|---|---|
| Ground control | Accuracy and coordinate control | Compatible GCP file with matching image marks |
| Geolocation file | External camera positions | Use when positions are not reliably embedded |
| Existing reconstruction archive | Resume or extend prior work | Useful when a compatible reconstruction already exists |
| Previous Atlassium job | Change analysis | Must belong to the same customer account |
3. Choose processing
Every new job can create the photogrammetric baseline and one or more downstream analyses. Select only the questions supported by the dataset; a roof model, for example, needs sufficient building coverage and geometry.
- Baseline: reconstruction and foundational survey products.
- Terrain: elevation summaries, slope and contours.
- Roof: building reconstruction and roof-plane measurements.
- Stockpile or cut/fill: volume from suitable surfaces and boundaries.
- Change: comparison with a previous compatible point cloud.
- Solar: early-stage PV layout and energy estimates.
- Report: a human-readable summary alongside original artifacts.
4. Follow the job
Jobs move from queued to assigned and running, then to completed, failed or canceled. A renewable lease ties active work to one compute machine. If that machine disappears, the scheduler can return eligible work to the queue rather than losing the record.
The job page shows progress, a safe status message, recorded processing time and every finished artifact. Support can use the job identifier to investigate without asking you to reconstruct the timeline.
5. Review and export
Download the original machine-readable output whenever it will feed another GIS, CAD, reporting or analytical workflow. Use the HTML or PDF report as a concise record—not as a replacement for the underlying data or professional validation.
| Raster | Orthophoto, DSM, DTM and analysis layers | GeoTIFF and preview imagery |
|---|---|---|
| Vector | Boundaries, contours, roofs and layouts | GeoJSON and CityJSONSeq |
| Point cloud / model | Detailed geometry and downstream inspection | LAZ/LAS and textured model artifacts |
| Tabular | Measurements, summaries and exchange | CSV and JSON |
| Report | Review and project record | HTML and PDF |
6. Accuracy and responsible use
Photogrammetric accuracy is not a fixed product specification. It depends on ground sampling distance, camera calibration, image geometry, overlap, motion blur, terrain and vegetation, geolocation quality, ground control and the coordinate reference system.
Inspect quality artifacts and validate checkpoints before relying on measurements. Do not use Atlassium outputs as a cadastral boundary, licensed survey certification, structural assessment, engineering approval, autonomous-navigation input or sole basis for a safety-critical decision.
- Use surveyed control and independent checkpoints where accuracy matters.
- Compare repeat surveys using compatible capture and coordinate methods.
- Record environmental or site conditions that could affect the surface.
- Have qualified professionals approve regulated or high-consequence conclusions.
7. Get support
Email support@atlassium.io with the account name, project name, job identifier, what you expected and what occurred. Do not send passwords, API keys or large source datasets by email.