# Page Not Found

The URL `lidarmill-desktop/post-processing/workflow-kk/uploading-files/trajectory` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Trajectories](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/windows/project/trajectories.md)
- [Create New Project](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/project.md)
- [Adding a Trajectory](https://docs.phoenixlidar.com/3rd-party-software-documentation/bathymetric-lidar-processing-in-riprocess/creating-a-project-in-riprocess/adding-a-trajectory.md)
- [Uploading a RECON Mission](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/missions/uploading-a-recon-mission.md)
- [Processing Tools](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/processing-tools.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/windows/project/trajectories.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.

### Option 2 — Browse the documentation index

Full index: https://docs.phoenixlidar.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.phoenixlidar.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/spatialexplorer-8-and-9/user-interface/windows/project/trajectories.md`).

You may also use `Accept: text/markdown` header for content negotiation.