Creating a Processing Task

You can create a processing task while your data is still uploading. Once the upload is complete, the data will be processed.

1. Go to Data Processing > Processing Tasks.

   

2. Click Create processing task.

   

3. Enter a name for the processing task or continue with the assigned default name.

   

4. Select the Dataset(s) you want to process.

   

Crop datasets before processing

Why Crop Before Processing?

• Faster Processing & Lower Resource Use – Smaller datasets reduce feature extraction, registration, and optimization time, as well as RAM/GPU usage.

• Removes Irrelevant & Dynamic Data – Excludes pedestrians, vehicles, outdoor spill-in, and temporary objects that can negatively influence processing.

• More Stable Alignment & Loop Closure – Cropping to a compact, well-connected area increases overlap, reduces false matches, and limits drift.

• Higher Accuracy Where It Matters – Optimization focuses on the area of interest, improving local accuracy and geometric reliability.

• Easier Quality Control – Smaller datasets enable faster visual checks and quicker detection of errors.

• Smaller Deliverables – Produces lighter point clouds, meshes, and floor plans that are easier to share and store.

Perform the following steps to crop datasets before processing:

1. Click the three dots next to the dataset you want to crop.

2. Click Define processing time frame.

   

3. The following screen is displayed. Use the slider to choose the part of the dataset you want to process. Select the time frame that includes the dataset based on the preview map.

   

4. Click Define time frame.

5. Click Next and the following screen is displayed.

6. Configure the point cloud and panorama settings, refer to point cloud and panorama settings.

Configuring Control Point Settings

Control points captured during scanning can be used by Cross-dataset alignment (CDA) to align multiple datasets during processing. Depending on whether these control points were surveyed in the field, there are two possible ways to use them:

1. Under Control Point settings, enable Cross-dataset alignment toggle to use it when datasets share common control points. CDA can use both unmeasured and surveyed control points to automatically align datasets within the same processing task.

2. Upload a surveyed control point file when the captured control points were measured with a total station or another surveying method. With this, you can geo-reference datasets using the surveyed coordinates.

Configuring Cross-dataset Alignment

Cross-Dataset Alignment (CDA) automatically aligns multiple datasets during processing, using surveyed or unmeasured control points, to produce one consistent, drift-free model. Use CDA whenever two or more datasets in the task overlap.

1. Under Control points settings, enable the Cross-dataset alignment toggle.

CDA finds the common control points in the selected datasets and groups them automatically.

2. If CDA is enabled, review CDA groups. The datasets are sorted into:

   • Geo-referenced group: datasets that share at least 2 control points with the uploaded surveyed file. These are aligned to real-world coordinates.

   • Locally-referenced group: datasets that share control points with each other but not with the surveyed file. These are aligned to one another using unmeasured control points.

   • Datasets without link: datasets with no shared control points to any other selected dataset

     Note: The control point names can be edited in case of any manual errors and the link icon denotes that the control point is shared between the other datasets.

For best results when using CDA:

• Ensure that adjacent datasets have some overlapping areas, incorporating a loop closure within the shared region.

• Add at least 2 common control points between each pair of datasets in the X–Y plane (surveyed or unmeasured).

• Place control points 5 m apart with horizontal offset. Don't stack them vertically.

• Use permanent, visible objects so they're recognizable from any direction.

Note: CDA is enabled per processing task and applies only to the datasets you select. There is no extra charge for enabling CDA. Units are charged at the dataset level. CDA works with all NavVis reality capture devices on NavVis IVION Core, Professional and Enterprise, and you can mix datasets captured from different NavVis devices in the same task. A CDA group can hold up to 10 datasets, and a task can contain multiple groups.

Upload surveyed control points

Perform the following steps to upload surveyed control points (from a TLS for eample) in .txt or .csv format:

1. Click Configure settings.
   

3. Click Upload or drop a control points file (.csv, .txt) here to upload a file or drag and drop a file.
   

4. In the dialog box that opens, select Local reference system if your control points file is in a local coordinate system.

   

5. Select Spatial reference system if your control points file is in a global coordinate system. Start typing a name and select the desired spatial reference system from the options that appear.

   

6. Click Upload file.

   The surveyed control points file will be validated. If there are problems with your control points file, this will be indicated and you will need to resolve the problem to ensure the successful processing of your data. Refer to Control point file requirements and formats.

7. Click Save changes to continue.

8. Optionally, add up to five email addresses to receive updates on the completion or failure of your processing task.

9. After finishing configuration for new processing task, you can start processing the task. Click Start Processing.

   

Processing task information

Once you have created a processing task, it will be listed on the Processing Task page with the following information:

• Name

• Status

• Starting date

• Number of datasets included in the processing task.

• Number of datasets that have been successfully processed.

• Number of datasets for which processing has failed.

• Units consumed for all datasets within the processing task.

• Size of all datasets within the processing task.

• Progress of the processing task.

You can expand a processing task to see the following information:

• The datasets included in a processing task.

• The settings chosen for a processing task.

• Whether Cross-dataset alignment is enabled.

• The Status of the individual datasets:

  • Finished (in green): The processing task has completed successfully. The amount shown in the Units Consumed field will be deducted from your processing units balance.

  • Failed (in red): The processing task has failed. This could be caused by data incompleteness or an issue with the processing software. The Units Consumed filed will be empty and no units will be subtracted from your processing units balance.

  • Canceled: You have canceled the processing task. The Units Consumed field will be empty and no units will be subtracted from your processing units balance.

  • Finished (in yellow): The processing task has completed but a large residual in the control points has prevented the task from finishing successfully. Click View control point configuration to see which controls points have large residuals. For more information on this issue go to Knowledge Based Articles.

• Billed area This is displayed after processing is completed, this will be deducted from the Processing Balance.

• Units Consumed:

  • The unit factor of 10 Units/m² processed as Billed Area will be consumed from remaining Processing Balance for datasets captured with NavVis M6 or NavVis VLX 2.

  • The unit factor of 25 Units/m² processed as Billed Area will be consumed from remaining Processing Balance for datasets captured with NavVis VLX 3.

  • The unit factor of 15 Units/m² processed as Billed Area will be consumed from remaining Processing Balance for datasets captured with NavVis MLX.

  • The unit factor of 100 Units/Panorama will be consumed for detection and blurring from remaining Processing Balance.

    Note: Unit consumption applies at dataset level, no additional units will be charged for aligning datasets with CDA.