> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/fieldagent-mobile-ios/data-schemas/flight-plans.md).

# Flight Plans

The app can [import](/home/fieldagent-mobile-ios/60-second-guides/flight-plan-import.md) and [export](/home/fieldagent-mobile-ios/60-second-guides/flight-plan-export.md) multiple data types for a flight plan.

***

<table><thead><tr><th>File Type</th><th data-type="checkbox">Import</th><th data-type="checkbox">Export</th></tr></thead><tbody><tr><td>.csv</td><td>true</td><td>false</td></tr><tr><td>.json</td><td>true</td><td>true</td></tr><tr><td>.kmz</td><td>false</td><td>true</td></tr></tbody></table>

***

## Imported Types

The app can read .csv and .json files to produce a flight plan.&#x20;

### CSV

A CSV file can populate a flight boundary in the app. Flight parameters cannot be included in the CSV file; only boundary coordinates can be imported with this file format.

#### Requirements

* The boundary points should be ordered correctly from a clockwise or counter-clockwise direction.
* There must be exactly two fields per row. &#x20;

#### lat-lon

If the .csv column labels are `lat,lon` or absent, the subsequent rows must contain precisely two fields, ordered latitude and longitude.

There is an example CSV file below.

{% file src="/files/BexckeQNz6KroFiFJs9o" %}
Example CSV file with lat,lon coordinates
{% endfile %}

#### lon-lat

If the .csv column labels are `lon,lat` the subsequent rows must contain precisely two fields ordered longitude and latitude.

***

### JSON

A .json file can provide both flight boundary (geometry) and flight parameters to the app.

#### Requirements

The file must follow the [JSON Schema](https://json-schema.org) below.

{% file src="/files/xmOcIufthbnHmjKrddbu" %}
JSON Schema for a Flight Plan
{% endfile %}

Below is an example JSON file that conforms to the schema above.

{% file src="/files/cwG3LZciRkv3F4rHJiHl" %}
Example Flight Plan JSON File
{% endfile %}

***

## Exported Types

The app can export .kmz files representing flight plans with flight parameters and coordinates.

### KMZ

The app can export a flight plan for use in DJI Pilot 2.

#### Requirements

The format of the KMZ file is documented on [DJI's Developer Page](https://developer.dji.com/doc/cloud-api-tutorial/en/api-reference/dji-wpml/overview.html).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.senterasensors.com/home/fieldagent-mobile-ios/data-schemas/flight-plans.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.