# Quick Start Guide

The following general instructions explain the major functions of the LiDARMill platform. For more in depth instructions and details, see the [Post Processing Workflow](https://docs.phoenixlidar.com/lidarmill-cloud/workflow).

## Create a new project

To "[Create Project](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/project)", click the red plus button in the bottom corner of the Projects section.

## Upload Files

[Upload your navigation (.nav) and LiDAR (.ldr, .rxp and .plp) data](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/missions#navigation-lidar-camera-files), along with your [reference station data](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/reference-station) (\*.hcn or RINEX format).

## Create Pipelines

Create a pipeline in the Pipelines tab inside your project. LiDARMill will request certain input files, and you can indicate these files among the ones you just uploaded.

### The NavLab Pipeline

Use a [Navlab pipeline](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/processing-tools/navlab-pipeline) to post-processes your trajectory data in forward and reverse directions using Tightly Coupled and Loosely Coupled solutions.

### The Spatial Fuser Pipeline

Use [Spatial Fuser Pipeline](https://docs.phoenixlidar.com/lidarmill-cloud/workflow/processing-tools/spatial-fuser-pipeline) to fuse your NavLab Trajectory data and your LiDAR data into a point cloud that you can view and analyze in a Point Cloud viewer right in your browser window. From here, you can download and deliver (in industry standard *.las or* .laz formats), or run other LiDARMill Pipelines


---

# 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-6.phoenixlidar.com/lidarmill-cloud/quick-start-guide.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.