# 5. Post Acquisition Checks

After data acquisition, it is important to review the collected data to prevent any mishaps, and correct mistakes as early as possible. The idea is to do a quick postprocessing workflow with reduced accuracy/density to ensure everything is in order:

{% hint style="danger" %}
Please follow instructions below after every acquisition. To give some examples, they will save your day when

* you lose the MicroSD card on the way to the office
* you didn't safely remove the MicroSD card when downloading data earlier, and are now using a card with a corrupted filesystem
* rover's storage filled up and you didn't see the warnings on the status LED or in SpatialExplorer
* you forgot to remove the lens cap on the camera and didn't observe the realtime photo stream in SpatialExplorer
* a camera stored photos to a memory card that filled up during acquisition and you didn't see the warnings on the status LED or in SpatialExplorer
* you misconfigured the trigger interval of the camera
* you forgot to remove the LiDAR sensor cap and don't observe the realtime stream in SpatialExplorer
* you copied the wrong folder (from a previous acquisition) off of rover's storage and then deleted all folders in the source
* a reference station didn't log raw observations, or logged observations with no measurements because it's antenna was disconnected, or had no memory card installed, or ran out of power
* you loaded the wrong flightplan and flew one area twice, and didn't cover the other one at all
* you mistakenly created a flightplan with incorrect altitude, or flew too fast
* you accidentally constrained the LiDAR's field of view, but your altitude and flightline spacing requires a larger FOV
* you selected the wrong measurement program for your Riegl LiDAR, resulting in reduced range or reduced point density
  {% endhint %}

## Quick Workflow

1. Copy the data from rover (SD card or SSD) to a folder in your field laptop
2. Assemble the data from all involved reference stations into a subfolder
3. Copy camera data from any cameras that store photos to their internal memory cards into the cam0/ or cam1/ folder
4. Take photos of your setup showing sensor offsets and orientations. This is especially important if you operate multiple systems or the same system on multiple different platforms. We have had customers mount the system in creative ways and ending up with the configuration upside-down, reverse, with swapped dual-GNSS antenna cables or simply with varying antenna offsets. All of these mistakes can cause problems in postprocessing, and photos help us quickly diagnose these issues, and fix those problems in postprocessing.
5. If possible, run trajectory postprocessing, either using Inertial Explorer or using SpatialExplorer's NavLab plugin. If not possible, just skip this step to use the realtime trajectory in the .nav file.
6. Open the PLP file in SpatialExplorer. Wait for the data to be parsed. Watch for yellow warning messages in the bottom panel.
7. Once the project has loaded, visually check for complete photo coverage in the 3D view. Then disable the camera layer and ensure the trajectoy is continuous and starts and ends where intended. You can enable the OpenStreetMap layer to reference the trajectory.
8. Fuse the data into a cloud. To speed things up, you can configure the LiDAR sensors to process only a fraction of the data by reducing the downward FoV and the density in the sensor settings dialog


---

# 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/rover/theory-and-workflow/post-acquisition-checks.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.