# Corrections

The Corrections window stores computed corrections, and enables users to apply rigid adjustments to the trajectory and pointcloud. The [Align to GCP](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/workflow/ground-control) tool automatically creates vertical corrections in the Corrections window, however corrections can also be created manually from measurements:

## Creating Automated Vertical Corrections

Use the [Align to GCPs ](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/workflow/ground-control)tool to create corrections from vertical residuals between GCPs and the pointcloud:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2FuJxFo583h2UmmYMCJPj6%2Fimage.png?alt=media&#x26;token=92f7e07c-a77e-488b-b6c9-3f73debc5af2" alt=""><figcaption></figcaption></figure>

## Creating Corrections Manually&#x20;

Corrections can also be created manually by selecting points or GCPs in the main view (creating measurements) and then using the **Import from Measurements tool.**

To create corrections manually, select a GCP and the corresponding point in the point cloud which should be co-located with the GCP:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2FGgTqbfDX6RhGvSjx2cvB%2Fimage.png?alt=media&#x26;token=4c8a9891-779c-4021-b962-317d7c3955db" alt=""><figcaption></figcaption></figure>

You should then have two entries in the measurement window, one with source (SRC) PointCloud, and one with source GroundControl:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2FpDdPtjC61vHY4AeXSWCo%2Fimage.png?alt=media&#x26;token=c1f77fce-ce95-432e-93f7-a7e1c373eca4" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Keep the Measurements window clean! A correction must be between two points, either one GCP and one pointcloud point, or two points in the pointcloud. If your measurements window has more than two entries, a correction cannot be created.
{% endhint %}

Use the **Import from Measurements** button to import the measurements as either a Vertical, Horizontal, or Full correction:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2FmZggWMdTWZsZ0SQs6Vsu%2FScreenshot%202024-03-22%20142051.png?alt=media&#x26;token=a0effe57-1c67-4c33-8338-5d480489f305" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you intend to run LiDARSnap with manual corrections enabled, the correction must be a Full (i.e. horizontal and vertical) correction.&#x20;
{% endhint %}

After creating the correction, you should see it as an entry in the **Corrections** window, as well as visualized in the main view:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2F9VZGHBFOcD2MuaF7Oluq%2Fimage.png?alt=media&#x26;token=f2d0b3e1-c3a9-4cb7-b787-631ff2cfe09d" alt=""><figcaption></figcaption></figure>

A correction can also be created from two points in the pointcloud, or between two points in two different pointclouds. To create a correction from two pointcloud points, disable the **GCP-point corrections** option:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2F7jw60Zt5TAjgvhVOopKg%2Fimage.png?alt=media&#x26;token=63661055-4df0-4397-ac4a-bafe068b47f1" alt=""><figcaption></figcaption></figure>

## Applying Corrections

{% hint style="warning" %}
If you are creating corrections to be used with LiDARSnap, do not attempt to apply corrections, as discussed below. For LiDARSnap, Full corrections should be present in the corrections window.&#x20;
{% endhint %}

Corrections can be applied to the active trajectory. This is useful when a single, global shift of the data set is required. Corrections are averaged amongst type, meaning that all vertical corrections are averaged to determine a single vertical adjustment, and all horizontal corrections are averaged to obtain a single horizontal shift:

<figure><img src="https://2222094320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdEevfLZRIk38LUPwDa4V%2Fuploads%2FM3KPI1thMhcgAvNOruVt%2Fimage.png?alt=media&#x26;token=1dde5262-cd40-4099-aefc-c368082b46f7" alt=""><figcaption></figcaption></figure>

Applying a correction to the active trajectory will create a new trajectory with the applied shift.&#x20;
