> 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/dnk/produktguide-webapp/zones-maps-and-analytics/multi-year-zones.md).

# Flerårige zoner

Opret stabile dyrkningszoner ud fra flerårige data for at understøtte langsigtede agronomiske beslutninger.

Historiske (flerårige) managementzoner giver indsigt i hvert eneste område på marken.

<figure><img src="https://lh4.googleusercontent.com/v6-fqjbXEf9i5hsyrzG9L_zhEHzA-ApSUdrMzVJdwfLC24_BbkxY8Q7exFqWg27rz3wWXVI0SmAl-d2hAH_14_pVrAWzHzUC6zrjocY3BMsbPf3PzMwhzbgSsbQajM-F4w_wdw7F" alt=""><figcaption></figcaption></figure>

Historiske (flerårige) managementzoner er baseret på mere end 30 års satellitbilleder fra arkivet. Billeder med den kraftigste vegetation i hver sæson udvælges automatisk til analyserne. Hvert af disse billeder repræsenterer ellers et muligt udbyttelag for det pågældende år.

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

Markens mønster for afgrødeudvikling giver et bedre kendskab til dyrkningsarealet og hjælper med at træffe de rigtige beslutninger om den rette dosering på de rigtige steder. Historiske managementzoner kan bruges som skabelon til tildelingsfiler (Rx) for såning, gødskning og zonestyret jordprøvetagning.


---

# 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/dnk/produktguide-webapp/zones-maps-and-analytics/multi-year-zones.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.
