> 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/nl/producttour-webapp/export-download/zones-map-export-as-shapefile.md).

# Zoneskaart exporteren als shapefile

Exporteer managementzones als shapefiles voor machines, GIS of partnerplatforms.

Met GeoPard kunt u zonekaarten van uw perceel of percelen exporteren als toepassingen met variabele dosering, die u kunt gebruiken voor precisielandbouw.

Klik op het **Gegevens exporteren** menu-ite&#x6D;**.** Ga naar het **Bestanden downloaden** tabblad om de exportmodus te openen.

Klap de gewenste boerderij en het gewenste perceel uit. Selecteer in de structuur de zonekaarten die u wilt exporteren en klik op de **Downloaden** knop of op de knop **Geselecteerde items downloaden** als u alle geselecteerde items in één keer wilt exporteren.

<figure><img src="https://lh5.googleusercontent.com/MkEOBfg1TVEsDiIn56oSzgPsvPws0glmRg86a_lAt0RyHJM6QHXD8CAo4nH8QJvbdVACQV1AlD2BpM_OAGsfWFFbJ8m_TEpQaS_I5rFAz1hta_IAivxgAztNC801OGu7czVMuD-_" alt=""><figcaption></figcaption></figure>

De geselecteerde zonekaarten worden als shapefiles in een .zip-archief naar uw computer gedownload. U kunt dit archief uploaden naar uw landbouwmachines.


---

# 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/nl/producttour-webapp/export-download/zones-map-export-as-shapefile.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.
