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

# 6. Ģenerēt ZonesMap

Attiecīgajā diagrammā attēlots ZonesMap ģenerēšanas process, izmantojot dažādus datu slāņus, piemēram, satelītattēlus ([1. pieprasījums jeb R1](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/3.-query-get-satelliteimages.md)), augsnes datu kopas ([1. pieprasījums jeb R1](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/17.-query-get-soildatasets.md)), lietošanas laikā reģistrēto datu kopu (AsAppliedDataset,[1. pieprasījums jeb R1](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), ražības datu kopu (YieldDataset,[1. pieprasījums jeb R1](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/16.-query-get-yielddatasets.md)) un topogrāfiju ([1. pieprasījums jeb R1](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/15.-query-get-topographymap.md)), izmantojot GeoPard.

ZonesMap ģenerēšana ir asinhrona darbība. Tā sākas ar izpildes pieprasījumu, uz kuru atbildē tiek atgriezti unikāli identifikatori (UUID) ([2. pieprasījums jeb R2](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/9.-mutation-generate-zonesmap-asynchronously.md)). Šie UUID sasaista pieprasījumu ar turpmākajiem procesiem un rezultātiem.

Pēc tam GeoPard API klients gaida GraphQL abonementa notikumu, kurā ir iekļauti sasaistītie UUID ([3. pieprasījums jeb R3](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/1.-subscription-get-events.md)). Šis notikums signalizē par ZonesMap ģenerēšanas pabeigšanu un norāda, ka dati ir gatavi izgūšanai.

Visbeidzot, GeoPard API klients var izgūt informāciju par ģenerēto ZonesMap ([4. pieprasījums jeb R4](https://docs.geopard.tech/geopard-tutorials/lva/api-dokumentacija/geopard-api-requests-overview/6.-query-get-zonesmaps.md)). Tajā ietilpst metadati, attēlošanas URL, statistiskais sadalījums un ģeometrijas, sniedzot visaptverošu pārskatu par ģenerēto ZonesMap.

**PIEZĪME**: ZonesMap ir `VectorAnalysisMap` alias abonementa notikumā, kas atrodas `TreeNodeEntity` enum.

<figure><img src="https://1923267647-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>Secības diagramma: ZonesMap ģenerēšana</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/lva/api-dokumentacija/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.
