> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/next-lab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/next-lab/3d-scanning/guides/vlx/processing-the-scans.md).

# Processing the Scans

## NavVis IVION

NavVis IVION is a cloud-based digital twin platform that allows users to present curated 3D-scanned sites with metadata like points of interest, waypointing and room information.

**For most purposes, IVION will only be used for processing point cloud data for your further use cases in CAD or rendering.** \
\
If you wish to use IVION for its presentation capabilities; check out this **demo** to see if suitable for your use-case; for setup, refer to the [NavVis Knowledge Base](https://knowledge.navvis.com/docs/overview-of-navvis-ivion) or with [NavVis Academy (free, sign-up with your own credentials).](https://academy.navvis.com/)

***

## Processing Workflow

1. Remove the SSD from the socket located below the screen 
2. Use the provided USB cables to connect the SSD with a computer 

{% embed url="<https://next-lab.iv.navvis.com/>" %}

4. Logon to NavVis IVION, the scanner's cloud processing companion. and navigate to the **upload data** page\
   NExT Lab will provide you with credentials and details. &#x20;
5. You should automatically be in your dedicated cloud instance.
6. Press Data Processing

<figure><img src="/files/8JPfovE7Hhc1PHtkLoJm" alt=""><figcaption></figcaption></figure>

6. In file explorer, access the SSD > Data > datasets\_rec
7. Drag and drop the entire folder with the corresponding date and time of your scan into the 'upload recorded data' box

<figure><img src="/files/JpPgF5fsAwfn26TZRKBE" alt=""><figcaption></figcaption></figure>

7. Once uploaded, navigate to **processing tasks** on the left&#x20;
8. Click 'create a new processing task" and select your uploaded scan

<figure><img src="/files/DcnIMSR7tzMu7jCz7PkA" alt=""><figcaption></figcaption></figure>

9. Configure settings depending on the nature of your scan and click **start processing**

<figure><img src="/files/A4UAtpTNS5KbC9YHtxDK" alt=""><figcaption></figcaption></figure>

10. You will need to make the following changes to the point-cloud configuration&#x20;

* Point cloud resolution to 5mm: This is the highest quality possible. Always do 5mm and downsample afterwards if a lower resolution is required.
* The **high confidence** **setting** has a range of 10m, and will be a smaller, but more complete scan.&#x20;
* The **standard setting** has a range of 30m and is good for interior or built up spaces.
* The **outdoor setting** has a range of 50m. The point cloud density may be sparce on the edges for this reason, however, this setting is good for larger spaces.&#x20;

10. The scan will now be sent to the NavVis server for processing. This may take several hours.
11. Once the processing status has changed to 'complete' navigate to **processed data** on the left.&#x20;
12. Here you can select and downolad your preferred files.&#x20;

<figure><img src="/files/5fGWykaKZQrnvtocNpfP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/PsTGhUuLT3LfRefjxqta" alt=""><figcaption></figcaption></figure>

For more information, you can visit the NavVis knowledge base linked below.&#x20;

{% embed url="<https://knowledge.navvis.com/docs/uploading-data>" %}

***

## Next Steps

VLX point cloud outputs, as SLAM datasets, look different to stationary terrestrial scanning outputs - they tend to be noisier.

**Meshing**

You will find that you cannot run the [recommended type ](/next-lab/3d-scanning/guides/working-with-3d-scan-data/point-clouds-to-meshes.md#inside-or-outside)of algorithms.\
Meshing them is harder as they lack a cloud structure that guarantees successful meshing.

**Combining Datasets**

Use [point-to-point techniques](/next-lab/3d-scanning/guides/working-with-3d-scan-data.md#aligning) to combine clouds together.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ms-kb.msd.unimelb.edu.au/next-lab/3d-scanning/guides/vlx/processing-the-scans.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.