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

# 6. Generuoti zonų žemėlapį

Diagramoje pavaizduotas „ZonesMap“ generavimo procesas naudojant įvairius duomenų sluoksnius, tokius kaip palydoviniai vaizdai ([1 užklausa arba R1](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/3.-query-get-satelliteimages.md)), dirvožemio duomenų rinkiniai ([1 užklausa arba R1](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/17.-query-get-soildatasets.md)), atliktų darbų duomenų rinkinys ([1 užklausa arba R1](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), derliaus duomenų rinkinys ([1 užklausa arba R1](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/16.-query-get-yielddatasets.md)) ir reljefas ([1 užklausa arba R1](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/15.-query-get-topographymap.md)) naudojant „GeoPard“.

„ZonesMap“ generavimas yra asinchroninė operacija. Ji pradedama pateikus vykdymo užklausą, į kurią atsakant grąžinami unikalūs identifikatoriai (UUID) ([2 užklausa arba R2](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/9.-mutation-generate-zonesmap-asynchronously.md)). Šie UUID susieja užklausą su tolesniais procesais ir rezultatais.

Tada „GeoPard“ API naudotojas laukia GraphQL prenumeratos įvykio, kuriame pateikiami susieti UUID ([3 užklausa arba R3](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/1.-subscription-get-events.md)). Šis įvykis praneša, kad „ZonesMap“ generavimas baigtas ir duomenis jau galima gauti.

Galiausiai „GeoPard“ API naudotojas gali gauti sugeneruoto „ZonesMap“ informaciją ([4 užklausa arba R4](https://docs.geopard.tech/geopard-tutorials/ltu/api-dokumentacija/geopard-api-requests-overview/6.-query-get-zonesmaps.md)). Tai apima metaduomenis, atvaizdavimo URL, statistinį pasiskirstymą ir geometrijas, todėl pateikiama išsami sugeneruoto „ZonesMap“ apžvalga.

**PASTABA**: „ZonesMap“ yra `VectorAnalysisMap` pseudonimas prenumeratos įvykyje `TreeNodeEntity` išvardijimo tipe.

<figure><img src="https://570611445-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>Sekų diagrama: „ZonesMap“ generavimas</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/ltu/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.
