> 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/heterogenitetsfaktor.md).
# Heterogenitetsfaktor
Mål variationen inden for marken for at identificere de marker, hvor zoner og variable satser giver mest værdi.
En af de funktioner, GeoPard tilbyder, er heterogenitetsfaktoren for dine marker. For at se den, skal du åbne den ønskede mark, vælge zonekort og klikke på **Info** -ikonet på kortet. Sidepanelet åbnes.
Heterogenitetsfaktoren er det tal, der viser graden af heterogenitet/variabilitet i dine marker. Jo større variation en mark har, desto større er behovet for præcisionslandbrugsteknologier. Det er især nyttigt, når det bruges sammen med GeoPards flersårsanalytik (30 års historik).
Hvis du har mange marker, kan det hjælpe dig med at forstå, hvilke marker du først skal prioritere med [Variabel tildeling](http://test/) (såning, gødskning, sprøjtning).
Ved at kombinere GeoPards heterogenitetsfaktor med flersårsanalytik kan du spare mest på kemi i de mest heterogene marker.
---
# 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/heterogenitetsfaktor.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.
