# Mobile Trajectory Optimization

The mobile trajectory optimization preset optimizes for all parameters (**south, east, up, roll, pitch, yaw**) using a 2 second **Trajectory Adjustment Rate**. 

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

Generally speaking, this is a more aggressive optimization routine than the Aerial preset. Mobile datasets commonly suffer from low-quality GNSS data and unideal vehicle dynamics, so a more aggressive trajectory optimization routine is preferred.&#x20;

Users can modify the **Trajectory Adjustment Rate** parameter to control the frequency that adjustment is performed. Increasing this parameter to about 5 seconds may be ideal when the processed trajectory quality is high and frequent adjustment is not necessary.

{% hint style="info" %}
If your processed trajectory quality is high (as determined by attitude and position separation plots, satellite observation plots, and estimated accuracy plots), it is recommended that you disable optimizing the **East** and **South** parameters, as the horizontal component of your position is likely not in need of optimization.&#x20;
{% endhint %}

If significant adjustment is required, consider disabling **Preserve Local Trajectory Shape**, as this parameter will restrict the optimizer from performing sudden adjustments, which may be required.&#x20;


---

# 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/mobile-trajectory-optimization.md?ask=<question>
```

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.