> 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/spatialexplorer-8-and-9/post-processing/data-processing-workflows/backpack-and-pedestrian-lidar-processing.md).

# Backpack and Pedestrian Lidar Processing

This workflow covers processing raw, pedestrian-acquired lidar data from a native-Phoenix system. Typically pedestrian lidar acquisition is performed using a backpack mount. This workflow covers the conventional lidar production workflow, where a processed trajectory is created via inertial processing and used to build a point cloud. SLAM processing can also be used to process backpack-acquired data sets, and may produce more accurate results when GNSS availability is limited - [see the SLAM workflow here](/spatialexplorer-8-and-9/post-processing/data-processing-workflows/slam-workflow-beta.md). 

1. If using a RECON system, open one of the DATA files. SpatialExplorer will detect the other associated DATA files, and then will proceed to extract lidar, imagery, and navigation data.
2. Open the PLP file. After opening the PLP file, [select a CRS](/spatialexplorer-8-and-9/user-interface/windows/project-setup.md) for the project.
3. If working with data from a Riegl lidar scanner, [convert the RXP files to SDCX files](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/lidar.md).
4. Import a processed trajectory (CTS, CLS, SBET, POF). If you do not yet have a processed trajectory, produce one using either [InertialExplorer](/3rd-party-software-documentation/inertialexplorer-desktop-8.70-8.90-processing.md), [NavLab embedded](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/navlab-embedded.md), or [NavLab via LiDARMill](/lidarmill-cloud/workflow/processing-tools/navlab-pipeline.md). 
   1. When processing data acquired via a pedestrian platform, it is recommended to use the Pedestrian dynamics profile in NavLab or InertialExplorer. 
5. Configure [processing settings](/spatialexplorer-8-and-9/user-interface/windows/project/rover/lidars/lidar-processing-settings.md) for the lidar. Consider a 360 degree field of view, and a minimum range of 0.5 meters. 
6. [Create processing intervals](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/create-intervals.md) (these intervals will also apply to imagery).
7. [Create a point cloud](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/create-cloud.md). If using a Riegl lidar scanner, consider the [MTA Uncertainty](/spatialexplorer-8-and-9/user-interface/windows/project/pointclouds.md#example-mta-uncertainty) attribute.
8. [Import ground control points](/spatialexplorer-8-and-9/user-interface/windows/project/ground-control-points-gcps.md) (if available).
9. Visually check lidar relative accuracy and determine what degree and type of optimization needs to be performed. Consider reviewing trajectory accuracy reports to determine what trajectory parameters (X,Y,Z, yaw, pitch, roll) require optimization. It's not uncommon to solve for all parameters with pedestrian data sets. 
10. Run [LiDARSnap](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/lidarsnap-v4.md) and optimize for necessary parameters. Typically, the LiDARSnap Mobile Trajectory Optimization preset works well with Pedestrian data sets. Consider whether ground control points should be enabled with LiDARSnap, to act as a vertical constraint.
11. If ground control is available, [compute residuals](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/ground-control.md) from point cloud to control points to determine what rigid adjustment, if any, is needed to match lidar elevations to ground control elevations.
12. Perform any additional classification necessary.  Users can make use of the [Classify on Selection ](/spatialexplorer-8-and-9/user-interface/windows/classify-on-selection.md)window, as well as some [automated classification](/spatialexplorer-8-and-9/user-interface/toolbars/analytics/classify.md) routines. 
13. Generate accuracy [reports](/spatialexplorer-8-and-9/user-interface/toolbars/workflow/reports.md).
14. Generate deliverables such as [rasters](/spatialexplorer-8-and-9/user-interface/toolbars/analytics/create/create-maps.md) (RGB raster, DTM, DEM) and [vector deliverables ](/spatialexplorer-8-and-9/user-interface/toolbars/analytics/create/create-contours.md)(contours and meshes).


---

# 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/spatialexplorer-8-and-9/post-processing/data-processing-workflows/backpack-and-pedestrian-lidar-processing.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.