10. Export options

Opening the dialog window for export options:

• In Project select Export in the secondary sidebar.

OR

• Click on the Export element of the Navigation bar.

10.1. Exporting to Excel

Important

To enable MISSIONPLANNER to export a file to Microsoft Excel, the following are required on your PC:

• Microsoft Excel 2002 (v10.0) or higher.

• In the Microsoft Excel Trust Center (or equivalent location in your version of Microsoft Excel), Trust Access to VBA project object model must be enabled.

It is recommended to export the data to a template that has predefined fields for e.g. line number, coordinates, focal length and overlap.

Exporting to Microsoft Excel using an existing Microsoft Excel report:

1. Open the export dialog.

2. Choose Excel in the left sidebar.

3. Choose a template from the dropdown menu in the main window.

4. Select your sensors in the Sensor selection section.

5. Change the path and file name, if necessary.

6. Click on the Export button.

10.2. Creating a customized Excel template

10.2.1. Basic principle

MISSIONPLANNER uses Excel templates and substitutes the variables found within the template with the corresponding values set in the active project. For the export of flight lines MISSIONPLANNER creates a table that then is copied into the template. The Excel spreadsheet is fully customizable and supports adding images.

Hint

It is recommended to use an existing template and customize it to your specific needs as explained below.

10.2.2. Defined sections

Not all template variables are populated during Excel export. Specify a designated area within the template where these variables can be located. The available areas are listed here:

Two areas can be created:
RangeProject	Area containing all project information
RangeLines	Area containing all information on one flight line. For each flight line new rows are added and a table is created.

Adding a section:

1. Use Excel’s Name Manager to add, delete or edit sections.

2. To open the Name Manager dialog box, on the Formulas tab, in the Defined Names group, click Name Manager.

   

3. Double-click on a variable name to edit the respective section.

   

10.2.3. Variables

The variable names are predefined, see below. Each variable begins with an underscore _ so that it can easily be distinguished from other text in the document. Variables can either exist independently within a cell or be integrated into an equation.

Often, a project is planned using only the main sensor, despite other the availability of other sensors. Here are some examples for this case:

• LiDAR with camera

• additional NIR sensor(s)

These secondary sensors usually do not have the same properties as the main sensor. Key information about the secondary sensors can also be exported into an Excel template.

Adding additional sensors with own keywords:

1. Open the export dialog and choose Excel in the left sidebar.

2. In the sensor selection rubric, select the desired sensor information.

3. Information on the auxiliary sensors will be provided by appending e.g. the suffix _AUX1 to the keyword as shown below for the backward camera.

   

4. Click to add additional sensors of a sensor system.

   Hint

   The main sensor does not require a suffix.

10.2.4. Special cases

In order to compute a sum, mean, minimum or maximum value over all flight lines, the equations must reference the specific sections.

Examples

Operation	German	English
Count	=ANZAHLA(INDEX(RangeLines;;1)	=COUNTA(INDEX(RangeLines;;1)
Min	=MIN(INDEX(RangeLines;;3)	=MIN(INDEX(RangeLines;;3)
Max	=MAX(INDEX(RangeLines;;4)	=MAX(INDEX(RangeLines;;4)
Average	=MITTELWERT(INDEX(RangeLines;;4)	=AVERAGE(INDEX(RangeLines;;4))
Sum	=SUMME(INDEX(RangeLines;;7)	=SUM(INDEX(RangeLines;;7)

The number at the end of the equation corresponds to the column of the section, e.g. column number 1 = 1 .

10.2.5. Saving the template

The template must be saved in the ProgramData folder:

%ProgramData%\TOPOFLIGHT\{{program version}}\Templates

10.2.6. List of all variables

Range: RangeProject

General
_SensorName	sensor name as displayed in MISSIONPLANNER
_SensorType	display name of the sensor type (Frame, LiDAR, Stepper, Pushbroom, SensorSystem, undefined)
_SenorBrand	brand of the sensor
_SensorModel	model of the sensor
_SensorLabel	sensor’s display name within a sensor system (if it is not part of a system, the configuration name will be shown)
_ProjName	name of the project
_FOVWidth	sensor FOV (field of view) width [degrees]
_FOVHeight	sensor FOV (field of view) height [degrees]
_SpeedKn	aircraft speed [knots]
_SpeedMs	aircraft speed [m/s]
_SpeedKmh	speed [kmh]
_ConfigHAGLFt	flying height above ground level as defined in the sensor configuration [ft]
Frame
_WidthPx	sensor width [px]
_HeightPx	sensor height [px]
_WidthMM	sensor width [mm]
_HeightMM	sensor height [mm]
_PixSize	pixel size [mm]
_FocalMM	focal length [mm]
_MaxFPS	maximum supported frame rate per second
LiDAR
_PRR	pulse repetition rate (Riegl)
_LPS	scan rate (Riegl)
_LaserPower	laser power as defined in the sensor configuration [%]

Range: RangeLines

General
_LineID	line ID
_ParentLineID	flight line number (integer)
_SegmentLineID	segment number of a flight line (integer)
_Sensor	sensor name
_SensorLabel	sensor label
_AMSL_min	minimum absolute altitude
_AMSL_max	maximum absolute altitude
_AMSL_mean	mean absolute altitude
_HAGL_min	minimum height above ground
_HAGL_max	maximum height above ground
_HAGL_mean	mean height above ground
_Start_X	starting point easting
_Start_Y	starting point northing
_End_X	end point easting
_End_Y	end point northing
_Start_Lon	starting point longitude
_Start_Lat	starting point latitude
_End_Lon	end point longitude
_End_Lat	end point latitude
_Length	length [map units]
_SideOverlap_min	minimum side overlap
_SideOverlap_max	maximum side overlap
_SideOverlap_mean	mean side overlap
_Azimuth	azimuth [degrees]
_AzimuthBack	backward azimuth [degreees]
_Azimuth_WGS84	geographic azimuth [degrees]
_AzimuthBack_WGS84	geographic backward azimuth [degreees]
Frame Cameras
_imgCount	number of images
_GSD_min	minimum ground sampling distance
_GSD_max	maximum ground sampling distance
_GSD_mean	mean ground sampling distance
_FWDOverlap_min	minimum forward overlap
_FWDOverlap_max	maximum forward overlap
_FWDOverlap_mean	mean forward overlap
_ImgBase_min	minimum base between image positions
_ImgBase_max	maximum base between image positions
_ImgBase_mean	mean base between image positions
LiDAR
_PTS_min	minimum point density [points / m2]
_PTS_max	maximum point density [points / m2]
_PTS_mean	mean point density [points / m2]

10.3. Exporting as text file

Exporting to a text file:

1. Open the export dialog.

2. Choose Text file in the left sidebar.

3. Check the respective boxes for Flight lines and/or Image positions in the main window.

4. Select you flight line and/ or image position attributes as required in the respective sections.

5. Choose your header options, delimiter and output path and file name.

6. Click on the Export button.

10.4. Exporting as KML

Exporting to a KML file:

1. Open the export dialog .

2. Choose KML in the left sidebar.

3. Select the required attributes by checking the respective boxes for:

   • ProjectArea

   • Footprint

   • ImagePosition

   • ImageFootprint

   • FlightLines

   • Grid

4. Change the path and file name, if necessary.

5. Click on the Export button.

10.5. Exporting as TrackAir

Exporting to a TrackAir file:

1. Open the export dialog.

2. Choose TrackAir in the left sidebar.

3. Choose your project settings, altitude system and units and the output path.

4. Click on the Export button.

Hint

MISSIONPLANNER can open TrackAir MDB projects as TOPOFLIGHT projects.

10.6. Printing flight plan (generating PDFs)

Hint

The templates are compatible with printing on various paper sizes. It is possible to edit the format of PDF templates before printing by clicking Edit in the dialog window that opens upon selecting and Print . These settings, however, are not saved in the file!

Adjusting and saving the template print size:

1. Open the export dialog .

2. Choose Print in the left sidebar.

3. Click Print.

4. On the top left of the newly opened dialog box select the wrench icon.

5. Adjust the page size and orientation according to your needs.

   

10.7. Exporting as Labyrinth

Exporting to a Labyrinth file:

1. Open the export dialog .

2. Choose Labyrinth in the left sidebar.

3. Adjust the path and file name, if necessary.

4. Define the Flight plan number, Icon scale, Label scale and PicRadius as required.

5. Click on the Export button.

10.8. Exporting as Garmin FPL

Exporting to a Garmin FPL file:

1. Open the export dialog .

2. Choose ICAO FPL in the left sidebar.

3. Adjust the path and file name, if necessary.

4. Limit the flight lines per file as required (default 30).

5. Click on the Export button.

10.9. Exporting as ESRI shapefile

Exporting to an ESRI shapefile:

1. Open the export dialog .

2. Choose ESRI Shapefile in the left sidebar.

3. Adjust the path and file name, if necessary.

4. Select the element(s) that are to be exported by checking the corresponding box(es), such as the global extent of the footprints.

5. Click on the Export button.

10.10. Exporting as iX Flight Pro file

Exporting to an iX Flight Pro file:

1. Open the export dialog .

2. Choose iX Flight Pro in the left sidebar.

3. Adjust the path and file name, if necessary.

4. Click on the Export button to export as *.json file.