> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/workflow/lidarsnap-v4/trajectory-optimization/aerial-trajectory-optimization.md).

# Aerial Trajectory Optimization

The aerial trajectory optimization preset uses a 10 second **Trajectory Adjustment Rate** with only the **Up** parameter enabled for optimization:

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

This will result in a single vertical adjustment for each 10 second section of the trajectory. This works well to correct for vertical drift between different flight lines in an aerial dataset. Using a relatively slow **Trajectory Adjustment Rate** restricts the optimizer from applying sudden adjustments along the trajectory, and ensures that ample observations are used when computing each adjustment.&#x20;

{% hint style="info" %}
Aerial data sets may require optimization of **Yaw**, in addition to **Up**. Determination of heading (or yaw) with most lidar systems utilizes the system's course-over-ground as determined by GNSS (kinematic alignment). This process can sometimes result in a poor heading determination, and thus, yaw should possibly be considered for optimization.&#x20;
{% endhint %}