> For the complete documentation index, see [llms.txt](https://docs-7.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-7.phoenixlidar.com/lidarmill-desktop/workflow-kk/trajectory-processing.md).

# Trajectory Processing

## Summary 

During acquisition, the Rover collects quality GNSS and IMU data for both real time visualization of the trajectory and for use in Post Processing of the navigation data.  

The user has the ability to access [NavLab](https://docs.phoenixlidar.com/lidarmill-desktop/post-processing/workflow-kk/trajectory-processing/navlab-trajectory-processing-and-upload/navlab-processing) directly from the SpatialExplorer program.  

Navlab cloud-based trajectory post processing software uses data from a reference station (either private or public) to extend corrections to the rover GPS that are received at the base as the mission is collected.  

This refined GNSS observation data on the rover is then coupled with the IMU accelerometer and gyroscopic data to create a highly detailed and accurate trajectory.  

The original navigation data is processed, smoothed, and filtered to create a post processed trajectory that is a critical first step for creating quality remote sensing data from your platform.  

## Details 

The user can import a post processed trajectory from:

1. [LiDARMill's Navlab ](https://docs.phoenixlidar.com/lidarmill-desktop/post-processing/workflow-kk/trajectory-processing/navlab-trajectory-processing-and-upload)
2. [Novatel's Inertial Explorer software](https://docs.phoenixlidar.com/lidarmill-desktop/post-processing/workflow-kk/trajectory-processing/inertial-explorer-trajectory-upload)