> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/farm-user-and-access-setup/edit-a-boundary.md).

# Edit a boundary

Adjust field boundaries to fix geometry and keep analytics aligned with the real field.

You can edit the boundaries of your field(s) using the same ‘drawing’ tool, in cases when you want to edit some inaccuracies of the drawn or uploaded field.

1. To start editing, first, select the field you want to edit from the fields list. Then open the ‘Field Operations’ menu and select the ‘Edit Field Boundary’ item.

<figure><img src="https://lh4.googleusercontent.com/5BNDejR9jtcYJQcm-Xot6kJOtSrAg9X6A_9LSNX_NchF_yitQ6odTo1niIKIpZnVTBgjRHtjzzMZ0ztKj47hBVD0wBscA27KJQPxNOKI0vmpgwgl0_1GJqrkqN5a09F4p9VNEAoY" alt=""><figcaption></figcaption></figure>

2. Double-click the boundaries, to activate the editing tool. The moving points will be activated and you can change the boundary by moving it or adding additional points for drawing a more detailed boundary of the field.

<figure><img src="https://lh6.googleusercontent.com/xTKmJgcghewey9oIyQT7ttPKhHRqLJLsscnoz3Mgc4HOL5Rzp3dhPd2wF69SJhTC5xSyeSCO1g0QKMdOEd-gucRrGhGYp41_Jlrwu0W9HpkesFXYKBQEL-XUFNIF0YZ0lMoR3Fwd" alt=""><figcaption></figcaption></figure>

3. To draw an additional polygon click the **Draw** button.
4. To exclude some area (a pond, slope, etc) from the field, click the **Make hole** button. Then select the area you want to exclude from the field in the same way as you were drawing a field. The highlighted area is excluded from the field when you click anywhere outside the highlighted area. You can also fine-tune the excluded area as in editing boundaries by activating the points and moving/deleting them.
5. To delete the selected point, select it and click the **Delete** button.
6. It is possible to use any data layer as a background base map.

<figure><img src="https://i0.wp.com/help.geopard.tech/wp-content/uploads/2022/10/image.png?resize=1024%2C553&#x26;ssl=1" alt=""><figcaption></figcaption></figure>

7\. To save the changes, click the **Save\&Finish** button. You will see a confirmation message that the changes were saved.

<figure><img src="https://lh5.googleusercontent.com/bamn6oJKfYwsLJHPv6hnMrzRoISLY8dPtuPoul4FFwVRVeqGKlQ_MukkkYae24T0uVL_xA0xwh-g-rz5CRj2cT7kMilkvfI7Oun7aNpt81TOCIbjd4TKIx1HhXyUnqAvGfYtzp9m" alt=""><figcaption></figcaption></figure>

**Note:** After you have edited the boundaries of your field, we advise you to run the Zones Creator tool to generate a new analysis because old zone maps were built based on old boundaries and won’t be regenerated. You can use the ‘Clone an existing Zones Map’ option to get new results quickly.


---

# 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://docs.geopard.tech/geopard-tutorials/product-tour-web-app/farm-user-and-access-setup/edit-a-boundary.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.
