Requires an LP360 Drone, LP360 Land Basic or LP360 Land Standard license.
Importing a Cycle is the first step, post flight, of a sensor workflow. A Cycle can be imported into LP360 to form a new Project or, if a Project already exists, to add a Cycle to that project.
All TrueView sensors write their various data streams to a standard file folder structure called a “Cycle.” The original meaning of cycle was an on/off cycle of the sensor. It is possible to have multiple collections (flights, in the case of a drone) in a single Cycle so it is not necessarily correct to think of cycle as being synonymous with a flight.
The source data from a TrueView flight will consist of a folder with at least one cycle folder named Cycle_dddddd_tttttt showing the date and time of the data collection. Each cycle folder will contain one or more flight sub-folders with the same naming convention Flight_dddddd_tttttt to segregate the source data if there were multiple take-offs and landings during the cycle. Each cycle folder will also contain a System sub-folder with the associated configuration files and logs for that cycle.
How to Import a Cycle File
- The first step is to select how the cycle will be imported. There are three Import Mode options on the Import Settings page:
-
-
-
Import Flights into NEW/CURRENT Project (Not Recommended for TrueView sensors!) – this option imports a Cycle into an existing or new project. We recommend against this because you will not have a backup of the Cycle in the native “Cycle Format.”
-
Import and Archive Flights into NEW/CURRENT Project – this option adds the Cycle to an Archive and creates/adds to an LP360 project (Recommended for TrueView sensors).
-
Archive Flights – this option imports a Cycle from a USB/File and adds it to an Archive. This option does not run the same checks on the data as the previous step would do. We recommend against using this option because you will not have performed any checks on the data being put into the archive.
-
-
Raw Mission Import Wizard - Import Settings page
- On the Import Settings page, select the desired Sensor type for import.
-
-
- LP360 Drone has the capability to import data from TrueView sensors, as well as systems such as the DJI Zenmuse L1 or L2, Wingtra LiDAR, DJI Phantom 4 RTK, M210 RTK, DJI Zenmuse P1 (M300 RTK), and DJI Mavic 3 Enterprise (M3E) for both real-time kinematic (RTK) and post processing kinematic (PPK) workflows, and image processing to an orthomosaic and generated point cloud.
-
- Additional sensors may be added upon request. Other supports any point cloud with a sensor trajectory file.
-
- LP360 Land has the capability to import data from TrueView Go sensors.
- LP360 Drone has the capability to import data from TrueView sensors, as well as systems such as the DJI Zenmuse L1 or L2, Wingtra LiDAR, DJI Phantom 4 RTK, M210 RTK, DJI Zenmuse P1 (M300 RTK), and DJI Mavic 3 Enterprise (M3E) for both real-time kinematic (RTK) and post processing kinematic (PPK) workflows, and image processing to an orthomosaic and generated point cloud.
-
Once the Import Mode and Sensor Type are set, click the Next button.
On the Input Flights page, browse to and select the file location or select a flight from an established archive.
-
-
Folder – Add one or more TrueView Cycle/Flight by selecting the Cycle folder(s) found on the USB. Select this option and browse for the desired Cycle folder(s).
-
Archive Zip File – If you or a pilot in the field has previously archived TrueView Cycles/Flights to an LP360 Cloud Cycle-Archive and shared that archived Cycle for download, use this button to add archived Cycles to the queue for import into the project without them needing to reside in a configured TrueView Archive.
-
Archive Manager – If you or a pilot in the field has previously archived TrueView Cycles/Flights to an Archive, use this button to add archived Cycles to the queue for import into the project.
-
-
NOTE: The archive folder location must be set up in the Archive Manager prior to using this option.
-
-
-
While on the Input Flights page, certain columns can be edited by a user. These fields are indicated by a pencil icon , see editable fields below:
-
Area (Site) name – This is an optional label that can be added when you are segregating a
Project (e.g., “Peabody Mine 77”) into multiple areas such as “Pit Area” and “Stockpile Yard.” -
Ancillary Files – This section of the dialog allows you to add any files you would like that are
relevant to this project. For example, you could add a Check Point file, pdf description files,
project reports and so forth. Note that these ancillary files will be associated with the Cycle, not
the Project (that is, added to the Cycle file structure). If you are simultaneously archiving this
project, these ancillary files will be included in the compressed archive. -
Archive Description – An optional description that can be viewed when viewing the archived
Cycle in the TrueView Archive Manager. Only visible when one of the import options that
archives is selected.
Raw Mission Import Wizard - Input Flights page (TrueView Sensor)
Once the flights are selected and visible in the Cycles section of the Input Flights page, click the Next button. Visit these links for information on the DJI L1/L2 Raw Import and the Wingtra Import.
If working with TrueView Go, visit this link for information about TVGO Processing.
The Base Observation Files page allows for the optional input of Base Station Observation files. Note: If you are not using a Single Base strategy (i.e., RTK, SmartBase or PP-RTX) or wish to add the base observation files later during trajectory processing, you can skip this page.
Raw Mission Import Wizard - Base Observation Files page
Once satisfied with the Base Observation Files page, click the Next button.
On the Output Project page, select the output folder location for the project files (this will default to the Default Project Root Folder if previously set in the Project Settings Dialog). The Project Name will default to the name of the input cycle folder but can be changed if needed. Additionally, select the desired Coordinate Reference System.
- If the CRS has not been used previously in LP360, click the Select... button to browse available horizontal and vertical coordinate systems. Once a CRS is used, it is saved in the Recent Coordinate Reference Systems drop-down.
Raw Mission Import Wizard - Output Project page
Once all options (Project Root Folder, Project Name, and CRS) are set on the Output Project page, click the Next button.
On the Flight/Base Positioning page, users may enter the Reference Mark (base station location) either by using a previously set-up survey nail or by manually entering the location information. If desired, the Reference Mark can be entered later in processing.
Raw Mission Import Wizard - Flight/Base Positioning page
Click Finish when ready to begin.
Layers Created Upon Completion of Import
Layer Type |
Data |
Notes |
xxx_Stations |
Contains the camera station calculated from the photocenter of each camera. Essentially a dual photocenter that contains both the left and right oblique images. |
Can be used to view the oblique image pairs using Feature Analyst. |
xxx_Photos |
Contains the photocenters for each camera. |
Can be used to view the oblique images for each camera using Feature Analyst. |
xxx_Trajectory Points |
Contains the 1 PPS GNSS “heartbeat” real-time positions of the sensor. |
Provides visual representation of flight path; not used for processing. |
xxx_LogPoints |
Used to view system log file entries. |
Primarily used for trouble-shooting and debug. |
xxx_TrajectoryLine |
Vector representation of the trajectory points. |
|
Xxx_GoogleHybrid |
WMS layer added for visual reference. |
|
Comments
0 comments
Please sign in to leave a comment.