# Aerial Trajectory Optimization
The aerial trajectory optimization preset uses a 10 second **Trajectory Adjustment Rate** with only the **Up** parameter enabled for optimization:
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.
{% 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.
{% endhint %}
---
# Agent Instructions: 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:
```
GET https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/workflow/lidarsnap-v4/trajectory-optimization/aerial-trajectory-optimization.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.