> 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/60-second-guides/create-a-field-and-flight-plan-with-a-csv-file.md).

# Create a field and flight plan with a CSV file

CSV Files can be imported into FieldAgent Mobile by choosing to open the file with “FieldAgent” on you iPad. These CSV Files of GPS points can be used to create a Flight Plan and or even a new Field.

## CSV File Format <a href="#csv_file_format" id="csv_file_format"></a>

* GPS points must be written in decimal degrees format.&#x20;
* Your CSV file must include two columns. Latitude values go into column A, and Longitude values go into column B.

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FeJO8wEUyReqGIxvr652a%2Fcsv.jpg?alt=media&amp;token=603ea650-2410-4057-b2d3-52f55f61aa1f" alt=""><figcaption></figcaption></figure></div>

* Each row is a pair of latitude longitude points. The order of these pairs dictates how your field boundary is drawn. This Image shows the field boundary created from the CSV file above. Each numbered point on the field corresponds to the same numbered row in the CSV file.&#x20;

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FsntON8QZ2GQJLFc6BIr5%2Fimage.png?alt=media&amp;token=c820cc1a-6ede-408d-8bc2-abc790d37f7f" alt=""><figcaption></figcaption></figure></div>

* List your GPS points in a clockwise or counterclockwise pattern around your field. Going out of order can create strange field shapes such as the field shown below. This field boundary was created by swapping rows 4 and 7 in the original CSV file shown above.

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FjOzrOoYeNcC3UfktnVL8%2Fimage.png?alt=media&amp;token=fb31a546-84ae-4534-a68a-3d20c16abf08" alt=""><figcaption></figcaption></figure></div>

### Importing a CSV <a href="#importing_a_csv" id="importing_a_csv"></a>

1\. Select the .CSV file on your mobile device

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2F175HzHTHcWTv5LeOGRGC%2Fimage.png?alt=media&amp;token=2dd4ec48-281f-493a-a40a-3469720bbc5b" alt=""><figcaption></figcaption></figure></div>

2\. Choose to open the file with FieldAgent

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FMWfofPsLB3bCLgVySwhh%2Fimage.png?alt=media&amp;token=134bf4f1-948d-4cda-98aa-f28020f5922a" alt=""><figcaption></figcaption></figure></div>

3\. The CSV will open up as a flight plan over a new field.

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FOaXbcjMjVZeEN07jSHOY%2Fimage.png?alt=media&amp;token=05387223-0093-4006-9f3c-639fc87a1880" alt=""><figcaption></figcaption></figure></div>

## Creating a Field <a href="#creating_a_field" id="creating_a_field"></a>

1\. To save the field click the settings wheel in the top right corner.

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FrhVvtUE0U1Ztd3sxxTE3%2Fimage.png?alt=media&amp;token=1db8b3f6-8c67-4235-bc95-77304583ddb4" alt=""><figcaption></figcaption></figure></div>

<img src="https://static.zohocdn.com/zoho-desk-editor/static/images/file.png" alt="" data-size="line"> <mark style="background-color:yellow;">Note: Only the field boundary will be saved. Flight parameters will need to be reentered for future flights.</mark>

\
2\. Click Create a Field

<div align="left"><figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2F5x7frO69oaPwekXaSvyd%2Fimage.png?alt=media&amp;token=c6e499f1-5a81-43f2-a6a3-7b94cc31e481" alt=""><figcaption></figcaption></figure></div>

3\. Name your field and click OK.

<figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2Fv1Z5J8wvWuqMzgFqzMvV%2Fimage.png?alt=media&amp;token=ea62082b-cbd0-4596-b924-23237340f577" alt=""><figcaption></figcaption></figure>

4\. Click Upload. The field will be saved and uploaded to FieldAgent. This Field will be visible in all FieldAgent clients.


---

# 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/60-second-guides/create-a-field-and-flight-plan-with-a-csv-file.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.
