The TrueView Sensor Tab processes data collected from GeoCue TrueView platforms and various other sensors.

There are three positioning modes available for processing TrueView 3D Imaging Sensor (3DIS) data.  These modes are:

• Single Base – a single base station has been set up at or near the project.  Alternatively, a single remote base station (such as a member of a Continuously Operating Reference System, CORS) will be employed.
• Smart Base – a virtual base station from the Applanix SmartBase service will be employed
• PP-RTX – Precise Point Positioning from the Trimble PP-RTX service will be used

There are three collection modes available with a TrueView 3DIS:

• LIDAR and Cameras (3DIS mode) the default data capture mode, LIDAR only, and Cameras only.

  Best Practice:

• Set a local base station near the takeoff location of the drone. You must observe for at least 5 minutes prior to startup of the TrueView system to at least 5 minutes after shutdown. If practical, an observation session over two hours is preferred since it allows for a more accurate position estimate. Rely on Smart Base and PP-RTX as backups for project recovery in the event something happens with your local base station.  

Figure 1: Sensor Tab in the LP360 Ribbon

Import

Import Cycle

Cycle Processing

Auto Create Flight Lines

Sensor Processing

Trajectory Processing

Geocoding

EXIF Tags/EO

Colorize

Export Photo Package

Trajectory Report

Trajectory Plot

Pilot Log File

Processing

Post Processing

Strip Align

Ortho Mapping

Agisoft Ortho Mapping

Feature Edit

Manual Flight Lines

Select/Edit Features

Save Feature Edits

Delete Selected Features

Discard Feature Edits

Undo / Redo Feature Edits

Archive

Archive Manager

Utilities

Survey Nail Manager

LiDAR Calibration

Camera Calibration

Live Stream

DJI PPK Utility

TV540 Data Copy

Job

Job Manager

User Tips:

• Cycle Import: Use the multi-cycle import feature to handle large flight datasets efficiently.
• EXIF Tagging: Ensure EXIF tags are updated post-processing to maintain compatibility with photogrammetric software.
• Cloud Monitoring: If a cloud job fails, users can now view execution logs and retry processing directly from Job Manager
• We also have workflows for processing with DJI and Wingtra LiDAR sensors and their specific LP360 tabs.

Prior to starting data processing, you should verify the following:

• The source data collected in the field is available either (a) on the USM memory stick from the sensor now attached to the processing computer or (b) has been copied to a folder on the processing computer or local network.
• The base station observation file, if using a local base station, has been downloaded in RINEX format and either (a) copied to a local folder on the processing machine or (b) copied to the “Cycle_xxxxxx_yyyyyy\System” folder of the flight, either on the USM or in the local folder.  Copying the observation file to the Cycle\System folder of a flight will automatically associate that file with that flight and include it in any processing. The observation file must be in RINEX 2.11 format or later.
• The base station details; latitude/longitude/elevation (in ellipsoid meters) of the reference point, the manufacturer make/model of the hardware and the input frame of reference (including epoch) to be used in processing the trajectory.
• The spatial reference system (coordinate system) to be used for the project.  This should be the output SRS you want for your deliverable data set.