Import Cycle
Importing a Cycle is the first step, post flight, of a TrueView 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. Cycles can be imported from a project folder, from a previously set-up archive or from a Guest Flight. If your cycle is from an RTK drone, such as the Phantom 4 RTK, select this method. You can also use this wizard to create an archive without creating a new project.
-
Browse to and select the file location or select a flight from an established archive.
. -
The base station observation files will be pulled from the input information. Any ancillary files can be added using this dialog.
-
Select the location for the output project files. The project name will default to the name of the original input folder but can be changed if needed. Select the spatial reference system.
-
Enter the base station location either by using a previously set-up survey nail or by manually entering the location information.
-
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.