CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken from a pre-release build, so a supplier's trial watermark is visible over the table.
What this does, and what you get back
Upload a set of aerial photos and CupixWorks processes them into a georeferenced aerial dataset you can open in SiteView. You choose which outputs to generate; processing happens in the cloud after the upload finishes.
The flow is a seven-step wizard and every step is listed down the left so you can see where you are: Image Selection, Capture Info, CRS, GCP, Processing Options, Resolution, Summary.
1. Image Selection
Drag the photos onto the drop zone or browse for them. A minimum of six images is required, and the panel says why more is better: high overlap between photos improves accuracy.
Once loaded, the images appear as a table with each file name and size, a total count, and a delete control per row.
2. Capture Info — and the geocoordinates precondition
Set the Capture Date and a Name, then choose the workspace and project.
Only projects with geocoordinates enabled appear in the project list. The panel says so, and it is the single most likely reason a project you expect is missing. Drone data is georeferenced by nature, so a project with no coordinate system has nowhere to put it.
The upload goes to the project's Site by default.
If your project is not listed, set its origin coordinates first — see Use Project Origin Coordinates.
3. CRS — the output coordinate reference system
Two coordinate systems, set separately.
| Field | What was observed |
|---|---|
| Horizontal | An EPSG code, for example EPSG:32652 — WGS 84 / UTM zone 52N. |
| Vertical | A height system, for example EPSG:3855 — EGM2008 height. The list also offered EPSG:5773 — EGM96 height and Ellipsoidal height (WGS 84). |
| Geoid model and Geoid height | Appear once a geoid-based vertical system is chosen. |
Outputs are generated in whatever you set here, so this is the field to check with whoever will consume the data.
4. GCP — ground control points
Ground control points make the result measurably accurate rather than approximately placed. CupixWorks detects targets in the photos automatically, and you supply the surveyed coordinates.
CRS for GCP is either Same as Project CRS or Different from Project CRS, with its own EPSG picker when they differ.
The GCP list comes from a CSV. Choose the column order first — PENZ, PNEZ, FEN, PNE — then Upload CSV. Once loaded, the points appear as a table of Point / Easting / Northing / Elevation, the button becomes Replace CSV, and the detected targets appear as numbered markers on an aerial preview.
If the column order does not match the file the panel rejects it and says which line failed: “Line 2 has coordinates that are not numbers. Check the Column Format above matches the file.” Change the Column Format and upload again — the file is fine, the reading of it was wrong.
GCPs are optional. Without them the panel says the photos are georeferenced from their EXIF geotags alone, which is less accurate. That is a usable result for a visual record and not one for measurement.
5. Processing Options — acquisition method and outputs
| Acquisition method | When to choose it |
|---|---|
| Nadir images | Photos taken with the camera pointing straight down, perpendicular to the ground. |
| Oblique | Photos taken at an angle, not directly down. |
Then choose the outputs. Four checkboxes: Orthomosaic, Raster DSM, Mesh, Point Cloud. Each one you tick is more processing time, so tick what will be used.
6. Resolution — quality against speed
| Choice | What it trades |
|---|---|
| High-Res, Slow Processing | Maximum detail and clarity. Takes longer and produces larger files. For projects needing accurate measurement. |
| Low-Res, Fast Processing | Smaller outputs, faster processing. For a quick assessment or visual inspection. |
This is the one choice that cannot be softened later — a low-resolution run has to be re-run to get detail back.
7. Summary — and what to check before you commit
The last step is titled Ready to Upload and restates everything: name, uploader, capture date, the full destination, the chosen outputs, the resolution, the image count, the GCP count, the GCP CRS and the output CRS.
Check three of them: the destination, the outputs, and the resolution. The others are recoverable by re-running a step; those three decide what you get and how long you wait.
Press Upload & Process. The upload starts and processing follows it in the cloud.