> 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.md).

# Create New Mission

With the project created, the next step is to upload mission data. A mission is essentially a data set. The data set type will determine what files you are required to upload. 

## Video Tutorial 

{% embed url="<https://www.youtube.com/watch?t=320s&v=bgIK0jfE5Tc>" %}

## Creating a new mission <a href="#navigation-lidar-camera-files" id="navigation-lidar-camera-files"></a>

In the **Missions** tab, click the red plus button to "Create new mission".&#x20;

![Missions Tab](/files/-McArRFks7Iq8eGjODH0)

![Create New Mission Button](/files/-MT5DQ8YCJxHbgq-UbTr)

It is possible to upload your project files from Dropbox or from a local drive. You will need to specify the mission type. The mission type will determine which files you will be required to upload:

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

## Mission types:

### [SpatialExplorer ](/lidarmill-cloud/workflow/missions/uploading-a-spatialexplorer-mission.md)

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.&#x20;

### [RECON](/lidarmill-cloud/workflow/missions/uploading-a-recon-mission.md)

This mission type applies to customers with a RECON or RESEPIsystem. You will need to upload all of the DATA files associated with your project.&#x20;

### [Pointcloud  Processing](/lidarmill-cloud/workflow/missions/uploading-a-pointcloud-processing-mission.md)

This mission type is used for post processing LAS files and trajectories. With this mission type you will need to upload a LAS or LAZ file - you also have the option of uploading a trajectory file (CTS, CLS, POF, SBET, etc). See more info here.&#x20;