Export to KML

Use the Database > Export > KML menu option (geogxnet.dll(Geosoft.GX.UAVSurvey.ExportToKML;Run)*) to export a GDB survey path to a KML file.

The option is also available in the UAV Merge Sorties extension under the UAV Merge Sorties > Plan Survey menu.

Export to KML dialog options

Longitude channel

Select the Longitude channel.

  • If you do not have the X & Y coordinates in units of Longitude and Latitude, exit this tool, use the Coordinates menu to project your data to latitudes and longitudes, and run this tool again.

    • Script Parameter: PLAN_UAV_SURVEY.LONGITUDE_CHANNEL

    Latitude channel

    Select the Latitude channel.

    Script Parameter: PLAN_UAV_SURVEY.LATITUDE_CHANNEL

    Elevation definition

    You can define the elevation either in units of metres Above sea level (Z is +ive up from sea level) or as Terrain clearance (Z is +ive from the drone down).

    Script Parameter: PLAN_UAV_SURVEY. ELEVATION_DEFINITION [0 – Above sea level (default), 1 – Terrain clearance]

    Elevation channel

    Select the channel that contains the elevation in the units/ directions specified above.

    Script Parameter: PLAN_UAV_SURVEY.ELEVATION_CHANNEL

    Output file

    Specify the name of the output KML (.kml) file.

    Script Parameter: PLAN_UAV_SURVEY.OUTPUT_FILE

    Application Notes

    Survey paths generated in the GDB format can be exported to the KML (Keyhole Markup Language) format file. 

    The KML format is an XML- based format for storing, displaying and sharing geographic data and associated content. KML files can be viewed on Google Earth and are also used by many popular survey software and navigation systems. Most drone navigation autopilot systems can directly interpret KML files.

    KML is the most common format for producing UAV navigation files.

    *The GX.NET tools are embedded in the geogxnet.dll file located in the "...\Geosoft\Desktop Applications \bin" folder. If running this GX interactively, bypassing the menu, first change the folder to point to the "bin" directory, then supply the GX.NET tool in the specified format. See the topic Run GX for more details on running a GX.NET interactively.

    See Also: