ASPSuite: Processing multiple flights in an SBF

If the drone pilot leaves the Loki unit on while swapping batteries on the drone when flying larger sites then there will only be a single SBF covering the multiple flights. Each take off and landing of the aircraft is considered a flight. This is not the recommended workflow and can create problems when post-processing.  The following workflow can be used to process data if it were accidentally collected with this method.

1. Use the Project/Flight wizard in ASPSuite to create a project with the single SBF, base station file(s) that cover the entirety of all acquired flights, and the most important part is to add the images from a single flight only. If using the DJI USB Cable workflow, add only the DJI Log (.DAT) files that correspond with the flight you are trying to process.
   1. On the Images page there is a Min Time Between Flights (min) setting. The default is 5 minutes. If it took less than five minutes between the last image taken in one flight, and the first image taken in the subsequent flight you should adjust this setting. This setting is used by the dialog to assign a group number to the images. This is to make it easier to ensure that you only have images from a single flight. It also makes it easier to select the subsequent groups and remove them from the dialog before proceeding.

Min Time Between Flights

Note: Failure to separate the groups can have adverse effects on the ability of ASPSuite to properly align the photocenters resulting in rejected photocenters for latter flights, or bad alignment when taken into PhotoScan or Pix4D.

2. Process through to completion of tagging the images or generating the images text file for the first flight.
3. If you chose not to update the image headers, rename the “YYYYMMDDHHMMSS_images.txt” file to “YYYYMMDDHHMMSS_images_flight1.txt”
4. In ASPSuite, Edit Flight and remove the images from the first flight. Now add the images from only the second flight.
5. Reprocess through to completion of tagging the images or generating the images text file for the second flight.
6. If you chose not to update the image headers, rename the “YYYYMMDDHHMMSS_images.txt” file to “YYYYMMDDHHMMSS_images_flight2.txt”
7. Repeat for subsequent flights recorded in the same SBF file.