> 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/api-dokumentation/diagrams-with-basic-flows/6.-generate-zonesmap.md).

# 6. Generér ZonesMap

Diagrammet beskriver processen med at generere et ZonesMap ved hjælp af forskellige datalag, såsom satellitbilleder ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/3.-query-get-satelliteimages.md)), jorddatasæt ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/17.-query-get-soildatasets.md)), AsAppliedDataset ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), udbyttedatasæt ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/16.-query-get-yielddatasets.md)), topografi ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/15.-query-get-topographymap.md)) ved hjælp af GeoPard.

Genereringen af ZonesMap er en asynkron handling. Den begynder med en anmodning om udførelse, hvorefter der returneres unikke identifikatorer (UUID'er) i svaret ([Anmodning 2 eller R2](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/9.-mutation-generate-zonesmap-asynchronously.md)). Disse UUID'er forbinder anmodningen med de efterfølgende processer og resultater.

Derefter venter GeoPard API-forbrugeren på at modtage en GraphQL-abonnementsbegivenhed, der indeholder de tilknyttede UUID'er ([Anmodning 3 eller R3](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/1.-subscription-get-events.md)). Denne begivenhed signalerer, at genereringen af ZonesMap er fuldført, og at dataene er klar til at blive hentet.

Til sidst kan GeoPard API-forbrugeren hente oplysninger om det genererede ZonesMap ([Anmodning 4 eller R4](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/6.-query-get-zonesmaps.md)). Dette omfatter metadata, URL'er til gengivelse, statistisk fordeling og geometrier og giver et omfattende overblik over det genererede ZonesMap.

**BEMÆRK**: ZonesMap er aliaset for `VectorAnalysisMap` i abonnementsbegivenheden i `TreeNodeEntity` -enum'en.

<figure><img src="https://1581835146-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FiC8hhOS1b4dhIrarWjL3%2Fimage.png?alt=media&amp;token=1391b1cb-577e-4fc9-af13-836629fd0fd8" alt=""><figcaption><p>Sekvensdiagram: Generér ZonesMap</p></figcaption></figure>


---

# 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/api-dokumentation/diagrams-with-basic-flows/6.-generate-zonesmap.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.
