This article provides an overview of the Aura Merge workflow, including how it works, when to use it, and the three procedures that make up the full workflow.
How it works
Aura's Merge workflow uses a SLAM-based algorithm to non-rigidly align multiple scan datasets, improving accuracy and usability for complex multi-scan projects. Aura processes each scan individually to produce aligned .laz output files. The individual files are then combined in Aura to produce a unified point cloud.
Aura supports merging georeferenced and non-georeferenced scans together.
When to use merge
A single scan does not cover the full project area.
Multiple scans from different positions need to be combined into one point cloud.
A mix of RTK and non-RTK scans need to be aligned to a common reference.
The merge workflow
The merge workflow is split across three articles:
Merge scan data: configure and run the merge in Aura.
Combine merged datasets: inspect, validate, and save the output as a unified point cloud.
View the combined accuracy report (RTK only): generate a combined accuracy report from the merged scan outputs.
Scan compatibility
Aura can merge any combination of scan types. Georeferencing is retained in the merged output only when every scan is an Emesent scanner RTK scan (GX1, ST, STX). If the merge includes any Drone RTK, GCP, or non-georeferenced scan, set Georeferencing to None before merging; the output is not georeferenced.
Processing notes
Scan type | Processing requirement |
|---|---|
Emesent scanner RTK † | Process each scan with the correct device type under Georeferencing mode. Set the base coordinate reference system to match the system used for RTK corrections. Georeferencing must be enabled in Processing Settings. |
Drone RTK and GCP | Set Georeferencing to None before merging. Georeferencing is not retained in the output. |
Non-georeferenced | Set Georeferencing mode to None in Processing Settings. |
Scans from Aura earlier than 1.10 | May default to GPS for non-georeferenced scans. Reprocess in Aura 1.10 or later with Georeferencing set to None. |
† Emesent scanner RTK includes GX1, ST, and STX scanners.
Troubleshooting
Issue | Cause | Solution |
|---|---|---|
Merged RTK scans are not georeferenced | Apply Overrides was not used | Select a georeferencing mode using Apply Overrides before merging. |
RTK scans require manual alignment | Georeferenced scan was not set as the preview file | Select the RTK scan as the Alignment Preview File (satellite icon). |
Aura is not detecting scan files | Wrong folder selected, or scans not processed | Select the offload folder containing |