> 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/swe/produktvandring-webbapp/zonkartor-och-analyser/flerariga-zoner.md).
# Fleråriga zoner
Skapa stabila skötselzoner från flerårsdata för att stödja långsiktiga agronomiska beslut.
Historiska (fleråriga) skötselzoner ger insikter om varje plats i fältet.
Historiska (fleråriga) skötselzoner byggs utifrån mer än 30 år av arkiverade satellitbilder. Bilder med topp i växtligheten under varje säsong väljs automatiskt som indata till analyserna. Annars representerar varje sådan bild en möjlig avkastningsfil för det aktuella året.
Mönstret för grödans utveckling i fältet hjälper till att lära känna odlingsområdet bättre och att fatta rätt beslut med rätt insatsnivåer på rätt platser. Historiska skötselzoner kan användas som underlag för receptfiler (Rx) för sådd, gödsling och zonbaserad jordprovtagning.
---
# 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/swe/produktvandring-webbapp/zonkartor-och-analyser/flerariga-zoner.md?ask=&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.
