Minimal TrueView Workflow – LP360

LP360 supports a minimal TrueView Cycle import workflow for certain non-TrueView raw datasets when the data is organized to match the minimum TrueView raw Cycle requirements.

This workflow is useful when a dataset, such as one collected with a Riegl miniVUX, is not a native TrueView dataset but needs to be brought into LP360 through the TrueView / Microdrones / TerraDrone import path instead of the Other import path.

The Minimal TrueView workflow is an alternative import option in LP360 that allows certain LiDAR datasets to be processed through the TrueView processing pipeline even when a complete, standard TrueView dataset is not available.

This workflow is designed to provide flexibility and recoverability in situations where some expected TrueView files are missing or when the data did not originate from a native TrueView system.

Why Would I Use the Minimal TrueView Workflow?

You may consider using the Minimal TrueView workflow in the following situations:

1. Recovering an Incomplete or Damaged TrueView Dataset

In some cases, a TrueView mission may not generate all expected cycle files due to:

Interrupted flights
Power loss or system issues
Incomplete data transfer
Accidental file deletion or renaming

The Minimal TrueView workflow allows LP360 to proceed with processing as long as the minimum required files are available, rather than blocking the import entirely.

2. Processing Non‑TrueView LiDAR Data Using the TrueView Sensor Workflow

Some users have LiDAR data collected with non‑TrueView sensors that still includes:

Raw LiDAR files
A trajectory file
A compatible system configuration

When organized correctly, this data can be imported using the TrueView import path so it can benefit from trajectory‑based processing and TrueView‑style workflows within LP360.

3. Maintaining Consistency with Other TrueView Projects

Organizations that primarily use TrueView systems may want all projects— including edge cases or recovered datasets—processed using a consistent workflow. The Minimal TrueView option allows these datasets to remain aligned with existing TrueView projects and deliverables.

What Makes This Workflow “Minimal”?

LP360 can recognize a folder as a minimal TrueView raw cycle even if standard files such as CycleParams.json or CyclePath.csv are not present.

LP360 only looks for a minimum set of files, which typically includes:

A System configuration file (SCF)
At least one Trajectory file
At least one raw LiDAR file

If some auxiliary files are missing, LP360 may infer certain information during processing.

Minimum Required Files

A minimal TrueView raw cycle must contain the following:

SystemConfiguration.json
At least one trajectory file:
- .T04
- or .UBX
- or .SBF
At least one raw LiDAR file:
- .bin
- .udf
- .rxp
- .raw
- .pck
- .dat
- .ltp

Recommended Folder Layout

The preferred layout is:

System\SystemConfiguration.json
System\*.T04, System\*.UBX, or System\*.SBF
Raw LiDAR files anywhere under the cycle folder

LP360 also supports a special case where all required files are placed directly in the same input folder.

Notes

CycleParams.json is not required for this minimal workflow.
CyclePath.csv is not required for this minimal workflow.
If CycleParams.json is missing, LP360 can use the T04 file to determine the cycle start and end time.
This is a minimal import setup intended to allow the dataset to enter the TrueView Cycle workflow.

Workflow

Organize the raw dataset into a folder that matches the minimum TrueView raw Cycle requirements.
In LP360, open the Import Cycle wizard.
Select TrueView / Microdrones / TerraDrone as the sensor type.
Add the prepared Cycle folder.
Review the detected Cycle information.
Optionally, if the CycleParams.json is missing and you wish to import co-acquired photos, double click the "Camera 1 Path" cell, etc., in the grid and browse to the folder containing the respective photos.
Set the project location if creating a new project.
Finish the import.
Note: If the CyclePath.csv is missing, Trajectory Processing must be completed before a TrajectoryPoints layer is generated to enable the Auto Create Flight Lines or Manual Flight Lines tools to be able to create flight lines for this Cycle.

For a Riegl miniVUX dataset, this means the data can be prepared to enter the Import Cycle workflow without using the Other import path, as long as the folder meets these minimum requirements.

Important Limitations to Be Aware Of

The Minimal TrueView workflow is intended as a fallback or special‑case option, not the default processing path.

Please note:

It may involve less automation than the standard TrueView workflow
Some metadata normally captured during data collection may be unavailable
Additional user review or validation may be required
It is not recommended when a complete, healthy TrueView dataset is available

For best results, the standard TrueView workflow should always be used when possible.

Related to