--- title: "Merge scans in Aura" slug: "merge-workflow" status: "update" updated: 2026-11-12T02:54:14Z published: 2026-11-12T02:54:14Z canonical: "knowledge.emesent.com/merge-workflow" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.emesent.com/articles/llms.txt > Use this file to discover all available pages before exploring further. # Merge scans in Aura [YouTube video player](https://www.youtube.com/embed/OC5Kk6DRTVc?si=cibluX08tiW1xDz_) This article explains how to configure and run the Aura Merge workflow. For an overview of how merge works, scan compatibility, and troubleshooting, see [Merge workflow overview](/v1/docs/merge). ## What you will need - Approximately 20% overlap between scans to support accurate alignment. - Each scan processed individually in Aura before merging, according to its type. - Sufficient available RAM. Avoid merging point cloud files that exceed available RAM, and use subsampled point clouds to reduce computational load. > [!NOTE] > Vehicle RTK, Backpack RTK and non-georeferenced scans can be merged together. Vehicle RTK and Backpack RTK scans improve the alignment of non-georeferenced scans where they overlap. Each scan must be processed in Aura before merging according to its type. For per-type requirements, see [Merge workflow overview](/v1/docs/merge). > [!WARNING] > A merge that includes a Drone RTK, GCP or non-georeferenced scan gives an output that is not georeferenced. Before the merge, set **Georeferencing Mode** to **None** for each of these scans in **Apply Overrides**. For more information, see [Merge workflow overview](/v1/docs/merge) and [Known issues](/v1/docs/known-issues-and-limitations). ## Procedure ### Step 1: Configure the merge job 1. Open Emesent Aura and click **Process Scan** in the top-left corner. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(389).png) 2. Select the **Merge** workflow in the **Configure New Scan Job** panel. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(390).png) > [!WARNING] > Select the offload folder containing the `.bag` files. Do not select the `Output` folder, as Aura will not detect the scan files. 1. Click **Add Datasets**, then click **Add** next to *Add dataset folder*. | 1 | ScanJob123/ | | --- | --- | | 2 | ├── Output/ | ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(391).png) 1. When prompted, select the **Scan Environment** that most closely matches the scan. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(392).png) 1. Wait for Aura to detect and list the available files. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(393).png) 2. Repeat steps 3 to 5 for each additional scan to include in the merge. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(394).png) ### Step 2: Choose an alignment base for preview In the **Alignment Preview File** column, select any scan as the alignment base. It is used for preview only and does not affect the final output. Where available, Aura defaults to a subsampled version. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(395).png) > [!NOTE] > For a merge of Vehicle RTK and Backpack RTK scans only, select one of these scans as the **Alignment Preview File** (satellite icon) to avoid unnecessary manual alignment. ### Step 3: Configure overrides Use **Apply Overrides** to configure scan-specific settings such as **exclusion zones** or **trim data**. For a merge of Vehicle RTK and Backpack RTK scans only, verify that the scans have the correct **georeferencing method** and **GNSS receiver type** assigned. Aura applies these automatically. For each Drone RTK, GCP or non-georeferenced scan, set **Georeferencing Mode** to **None** in **Apply Overrides**. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(396).png) ### Step 4: Select a reference scan (Optional) > [!WARNING] > If a reference scan is **not selected**, Aura performs **pairwise alignment** between all point clouds. This increases computational complexity and may extend processing time. For a merge of non-georeferenced scans, one scan can be set as the reference scan. The reference scan is locked in place, and all other scans align to it. For a merge of Vehicle RTK and Backpack RTK scans only, reference scans are also supported. Proceed to Step 5. ### Step 5: Configure processing settings 1. Define the location and name for the merged output. ![Location and Output fields for the merged output](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/kb-0206-merge-output-location-fix-hs50953672565-merge-drone-rtk-fcedeece.png) 2. Adjust the general merge and output options. See [Merge settings](/v1/docs/processing-settings) for a full reference. ![Merge selected in the Configure New Scan Job panel](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/kb-0206-configure-new-scan-job-merge-fix-hs50953672565-merge-drone-rtk-a606d821.png) For a merge of Vehicle RTK and Backpack RTK scans only, also configure the following: 1. Set the **Base Coordinate Reference System** to match the original horizontal CRS used during scan acquisition (for example, EPSG:4326, WGS 84). 2. To manually enter a full PROJ string, enable **Custom base CRS**. 3. (Optional) Enable **Reprojection** to transform the output into a different coordinate system, then define the **Target Coordinate Reference System** by selecting the desired horizontal and vertical CRS values. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(399).png) ### Step 6: Review and manually align When georeferencing is unavailable or inconsistent across datasets, manual alignment provides an initial position estimate. > [!NOTE] > **Manual alignment is required in the following scenarios:** > > - Merging non-georeferenced scans. > - Merging Vehicle RTK or Backpack RTK scans with non-georeferenced scans. > > For a merge of Vehicle RTK and Backpack RTK scans only, with correct setup, Aura indicates that no manual alignment is required. Skip to Step 7. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(400).png) > [!CAUTION] > Aura attempts to merge scans even if they are misaligned, either horizontally or vertically. This can result in a skewed or inaccurate final output. Always verify alignment before continuing. 1. Click **Load Scans** to load all selected point clouds into the viewer. - Each scan is assigned a unique color to assist with differentiation and alignment. - To add or remove datasets from the current merge job, click **Edit Point Clouds Selected**. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(401).png) Align scans manually using the **Translate** and **Rotate** tools: 1. - Start in **Top View** to position and rotate scans horizontally. - Switch to **Front View** to adjust scans vertically. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(402).png) | ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(403).png) Align all scans horizontally using the Translate and Rotate tools. | ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(404).png) Align all scans vertically using the Translate tool. | | --- | --- | | **Translate** | ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(408).png) | | --- | --- | | **Rotate** | ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(406).png) | > [!NOTE] > Click **Reload Scans** in the **Configure New Scan Job** panel to reset a scan's position. ### Step 7: Start the merge 1. Click **Start** to begin processing. ![](https://cdn.document360.io/c908b593-57d7-4fc8-b409-592fc1051369/Images/Documentation/image(409).png) > [!NOTE] > **Start button not visible** > > If the **Start** button is hidden, click the **Configure New Scan Job** panel at the bottom of the window to reopen the **Processing Scan** panel. ### Step 8: Combine the merged outputs When the merge completes, the outputs are available in the **Merge Complete** panel. To combine and save them as a single point cloud, see [Combine merged datasets](/v1/docs/combine-merged-datasets). For a merge of Vehicle RTK and Backpack RTK scans only, an accuracy report is also generated for each scan. To view a combined report across all outputs, see [View the combined accuracy report](/v1/docs/view-the-combined-accuracy-report). ## Outcome Aura outputs one `.laz` file per scan to the directory specified in Step 1. The outputs are georeferenced only when every scan in the merge is a Vehicle RTK or Backpack RTK scan (GX1, ST, STX). The outputs are grouped in the **Merge Complete** panel and are ready to combine. ## Additional information - [Combine merged datasets](/v1/docs/combine-merged-datasets): next step, inspect, validate, and save the output as a unified point cloud. - [View the combined accuracy report](/v1/docs/view-the-combined-accuracy-report): generate a combined accuracy report (merges of Vehicle RTK and Backpack RTK scans only). - [Merge workflow overview](/v1/docs/merge): compatibility, troubleshooting, and how the workflow is structured. - [Merge settings](/v1/docs/processing-settings): full reference for merge and output options.