Mission file formats

The Plan tab reads and writes several mission formats so you can move plans between ground stations, GIS tools and backups. Boundaries, map overlays and parameter files use their own import paths.

Mission formats

Format	Import	Export	Carries
`.altmission`	Yes	Yes	The native, lossless format: waypoints with attached actions, fence, rally points, points of interest and plan metadata
`.waypoints`	Yes	Yes	ArduPilot waypoint text file (`QGC WPL 110`)
`.plan`	Yes	Yes	QGroundControl JSON: mission, fence geometry and rally points
KML	Yes	Yes	Waypoints as placemarks and a path
KMZ	Yes	Yes	Zipped KML
CSV	Yes	Yes	One mission item per row

Export from the Plan tab footer menu: Export (.altmission, lossless), Export .waypoints, Export .plan (QGC), Export KML, Export (.kmz) and Export CSV. Import a plan with Import in the FLIGHT PLANS library.

.altmission

A JSON file with a version number, so older files migrate on load. Use it to back up or share a plan without losing anything. A .plan import keeps the fence geometry but not the fence settings, so it is merged into the current fence; an .altmission import restores the fence as saved.

.waypoints

The ArduPilot text format, one mission item per line.

QGC WPL 110
1	0	16	0	0	0	0	-35.363262	149.165237	584.000000	1
0	3	16	0.00000000	0.00000000	0.00000000	0.00000000	-35.361540	149.164475	100.000000	1
0	3	16	0.00000000	0.00000000	0.00000000	0.00000000	-35.360068	149.168137	100.000000	1

Fields: sequence, current, frame, command, param1 to param4, latitude, longitude, altitude, autocontinue.

.plan

The QGroundControl JSON format.

{
  "fileType": "Plan",
  "geoFence": { },
  "groundStation": "ADOS Mission Control",
  "mission": {
    "items": [ ],
    "plannedHomePosition": [ ]
  },
  "rallyPoints": { },
  "version": 1
}

KML and KMZ

Import: points become waypoints and line strings become a connected path. Waypoints without an altitude take the plan’s default altitude. Export: waypoints are written as placemarks and a line string. The altitude mode is absolute for waypoints in the Absolute (MSL) frame and relativeToGround otherwise. The frame is also written into the placemark data so a re-import restores it. KMZ is zipped KML. Mission Control packs and unpacks it for you.

KML stores coordinates as lon,lat,alt. Mission Control converts them, but keep the order in mind if you edit a KML file by hand.

CSV

The export header is:

seq,lat,lon,alt,command,frame,speed,holdTime,param1,param2,param3,param4,param5,param6,param7,rawCommand

Attached actions are written as their own rows. On import, the header row decides the column layout. lat and lon columns are required (latitude, lng and longitude are accepted too). A row with no altitude is skipped, and an unknown command becomes a plain waypoint. Each skipped or changed row is reported with its line number.

Boundary and overlay imports

These files add reference shapes to the map. They do not add waypoints.

Import	Files	Where	Result
Boundary	KML, KMZ, a zipped shapefile (`.zip`) or a bare `.shp`	Footer menu → Import boundary (KML/SHP)	Polygons become survey boundaries; holes inside them become survey keep-out areas
Vector overlay	`.kml`, `.kmz`	Map overlays (`L`)	Shapes drawn on the map for reference
Raster overlay	GeoTIFF (`.tif`, `.tiff`)	Map overlays (`L`)	An image draped on the map

A shapefile must be in latitude and longitude. If it uses a projected coordinate system, import the zipped bundle that includes its .prj file.

Parameter files

The Parameters tab reads and writes flight controller parameter files.

Format	Layout	Written by
`.param`	`NAME,VALUE` (or `NAME VALUE`) per line	Export (Mission Planner style)
`.params`	`VEHICLE_ID COMPONENT_ID NAME VALUE TYPE` per line	Export QGC

Load either format with Compare to diff it against the flight controller before writing.

Flight log exports

Recorded flights export from Flight logs, including GPX tracks and telemetry as CSV, KML or KMZ. The Plan tab does not export GPX.

Plan library

The FLIGHT PLANS library stores plans in your browser’s IndexedDB. You can make folders, search, sort by Name, Date or WPs, rename, duplicate, move, export and delete plans, and load the mission from a connected drone with From Drone.

Browser storage can be cleared. Export important plans as .altmission files.

Next steps

Mission planning

Edit and upload an imported plan.

Flight logs

Review and export recorded flights.

Get started

Fly

Plan and review

Firmware support

Configure the flight controller

Nodes

Test without hardware

Cloud, AI and settings

Android GCS

Mission formats

.altmission

.waypoints

.plan

KML and KMZ

CSV

Boundary and overlay imports

Parameter files

Flight log exports

Plan library

Next steps

Mission planning

Flight logs

​Mission formats

​.altmission

​.waypoints

​.plan

​KML and KMZ

​CSV

​Boundary and overlay imports

​Parameter files

​Flight log exports

​Plan library

​Next steps

Mission planning

Flight logs

Mission formats

.altmission

.waypoints

.plan

KML and KMZ

CSV

Boundary and overlay imports

Parameter files

Flight log exports

Plan library

Next steps