Requires an LP360 Drone license.
Introduction
This article includes a step-by-step guide on how to process DJI L1, L2, and L3 processed data in LP360. This workflow requires the user to first pre-process the data using DJI Terra desktop and later continue the processing in LP360.
The main difference between the DJI Raw L1/L2 and the DJI Processed L1/L2/L3 workflow, is that the raw workflow only uses LP360, while the processed workflow uses DJI Terra desktop app and LP360.
Pre-Requisites
- Before starting with the workflow, the user will need to have LP360 v2026.1 or newer.
- DJI Terra desktop 5.2 or newer.
DJI L1/L2/L3 Processed Workflow
DJI Terra Pre-processing
Project creation and data import
Import Advanced Settings
Generate flight lines
Post Processing
Other recommended steps:
Strip Align
Smoothing
Control Points
AI Ground Classification
Advanced AI Classification – Ground+, Forestry, and Utilities
How to process DJI L1/L2/L3 Processed workflow
0. PPK processing - DJI PPK Utility
If using PPK as your positioning solution, we recommend using the DJI PPK Utility to properly add the base station file in RINEX format to your raw data before processing in DJI Terra. This utility will convert the file to a format used by DJI Terra.
1. Pre-process the flight in DJI Terra
The first step is to perform the sensor trajectory processing and initial point cloud generation from the raw data is performed in DJI Terra as a pre-processing step before beginning the workflow in LP360 Drone.
2. Project creation and raw data import
1. Select "Import Raw Missions into New Project" on the Startup dialog or select Cycle Import on the Sensor Tab.
2. Under the Sensor Type, select "L1/L2/L3 (Processed)", then press Next
3. Press "Add DJI Terra Mission Folder"
4. Select the desired cycle folder.
Note: If the DJI Terra folder has been moved to a new location, it is also required to select the raw data location
5. LP360 will select by default the closest CRS read from the DJI Terra files. Usually, these do not always include the vertical datum. Therefore, the user will need to manually select it (in the example, we can see in red the CRS that requires our attention).
|
Note: - LAS CRS if you selected in DJI Terra "Geoid: default", then the vertical CRS is "Ellipsoidal" height. - SBET CRS is the same horizontal datum as the LAS, but without projection and in meters. In the example, the SBET CRS is NAD83(2011) + Ellipsoidal in meters. We do not select the projection here, also the SBET is always in meters, do not select USft or ft. |
6. Define the Projects Root Folder, TrueView Output Project Name and Project Coordinate Reference System and click Finish.
| Note: If the DJI Terra CRS does not match with the LP360 project CRS, LP360 will show a dialog about different CRS selection. If the user intention is to let LP360 to do the reprojection instead of DJI Terra, press Yes and continue. In the example the user processed in DJI Terra in CRS: WGS84 UTM and selected in LP360 the CRS: NAD83(2011) State Plane. Since the user wants to perform the reprojection in LP360, select "Yes" to continue. |
7. Selecting the processed flights to be imported will automatically submit a Reproject (RPJ) Job to the Job Manager for each Cycle/Flight to ensure the LAS and SBET matches the project CRS.
8. Upon completion of the RPJ job by the Job Manager :
a) Job Manager will indicate completion by the green flag
flashing on the Job Manager icon
b) The job will need to be completed to view the resulting point cloud.
9. If desired, or for troubleshooting, in Job Manager , select the applicable RPJ job, then select View Log to review the RPJ processing log.
10. In Job Manager , select the applicable RPJ job, then select Open Project to open the applicable project for the job, if not currently open.
11. Then, select Complete Job to add the LAS and TrueView Trajectory file(s) to the project.
3. Flight lines generation
The Auto Create Flight Lines tool, found on the Sensor Tab of the ribbon, is the automated tool used in conjunction with the Manual Flight Lines
tool, also found on the Sensor Tab of the ribbon, in the step of the workflow where one takes each real-time trajectory of the flights and segments them into only those sections you need for data generation. There are 2 ways to generate flight lines:
After the flight lines are generated, the flight will look like this:
4. Post-Processing
The Post Processing tool in the LP360 Sensor Tab is designed to prepare datasets for downstream tools by creating trajectory files for each flight line from the sensor trajectory files and cutting the LAS data into files corresponding to those flight lines.
5. Next Steps
Strip Align
To use this functionality, users must have the Strip Align Add-On License Product.
This step is optional. The Strip Align tool is intended to identify and correct the alignment between the flight lines in a single cycle, and/or between multiple cycles. For information on identifying when and how to use Strip Align, see the Strip Align page.
Control Points
If interested in 3D accuracy assessments using Accuracy Stars, Checkerboards, and/or Concentric Circles , users must have the 3D Accuracy Add-On License Product.
If you are only interested in estimating the accuracy of Z (elevations), check the Delta-Z Only option in the top left-hand corner of the Control Points Report Dialog and no additional licensing is required.
The intention of this step is to add check points and compare them to our point cloud to estimate the accuracy and review for any bias (constant offset in all the point cloud). If there is, we can remove it it and create a final QC accuracy report.
Smoothing
This step is optional. The Smoothing PCT will help reduce the point cloud noise envelope or the thickness of the point cloud. This algorithm works well for manmade structures, flat areas or regular surfaces. For information on how this tool works, please visit the Data Smoothing in LP360 page.
Classification
LP360 offers a variety of classification options. The most common in LP360 is Ground Classification. The How to Classify Ground using LP360 page discusses the options available for ground classification.
Point Cloud Tasks (PCTs) can also be used to perform other processes on the data for classification or modification purposes.
AI Classification
To use this functionality, users must have the Auto AI Ground Classification Cloud add-on license or advanced AI cloud licenses - AI Ground+. AI Forestry, or AI Utilities.
An alternative route to the point cloud segmentation is to use AI tools, AI Ground Only and Advance AI Classification tools.
LP360 supports four AI models.
- AI Ground Only - AI model optimized to extract only the Ground model. It does not include any other feature.
- Ground+ – Optimized for ground and terrain‑related classification, including classifying common above ground features.
- Forestry – Advanced tree segmentation designed for vegetation, canopy, and tree‑level analysis.
- Utilities – Tower and wire extraction designed for power line workflows, where identifying wires, towers, and related infrastructure is required.
Exporting or Extracting Final Products/Deliverables
Using the Export Wizard, a variety of deliverables can be exported from LP360.
- For users interested in extracting (or clipping) a section of a raster or LAS layer, see the links below:
Comments
0 comments
Please sign in to leave a comment.