> 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/zonekort-og-analyser/rediger-zonekort-flet-og-split.md).
# Redigér zonekort: flet og split
Flet og del zonepolygoner for at rydde kortene op og passe til driftsbehovene.
Ved at bruge funktionerne til at flette og opdele zoner kan du flette og opdele polygon(er) eller forvaltningszoner (eller et hvilket som helst andet datalag) og tildele en polygon eller en hel zone til en anden klasse. Det hjælper med at finjustere zonekort til præcise operationer som såning, gødskning eller sprøjtning.
1. Åbn det ønskede markfelt, gå til sektionen Zonekort, vælg derefter et kort, åbn handlingsmenuen, og klik på пунктet ‘Gå til zonekort-siden’:
2. Klik på "Rediger zoner" og vælg derefter "Flet zoner"
3. Fletningsforløbet for zoner indeholder 2 trin:
a. vælg den zone (farve), som du vil flette polygoner ind i,
b. vælg en eller flere polygoner på kortet
Afkrydsningsfeltet "Tilføj hele zonen" aktiverer en fuld fletning af en zone ind i en valgt zone.
4. Klik på "Afslut"
---
# 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/zonekort-og-analyser/rediger-zonekort-flet-og-split.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.
