> 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/lidarmill-cloud/workflow/missions/uploading-a-spatialexplorer-mission.md).

# Uploading a SpatialExplorer Mission

## SpatialExplorer V4-V7

This is the most common mission type. This mission type applies to all customer's with a Ranger, miniRanger, or Scout system type. You will need to upload at the minimum a PLP and a NAV file. 

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

Once the PLP file is uploaded, LiDARMill will recommend files to upload (files that are associated with the uploaded PLP) which could include navigation, LiDAR, and/or camera data. If you are only interested in post-processing a trajectory, upload only your NAV (navigation data) and PLP files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.phoenixlidar.com/lidarmill-cloud/workflow/missions/uploading-a-spatialexplorer-mission.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.