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

# 6. Ustvari coneMap

Zadevani diagram prikazuje postopek ustvarjanja zemljevida območij z različnimi podatkovnimi plastmi, kot so satelitski posnetki ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/3.-query-get-satelliteimages.md)), podatkovni nizi tal ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/17.-query-get-soildatasets.md)), podatkovni niz izvedenih opravil ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), podatkovni niz pridelka ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/16.-query-get-yielddatasets.md)) in topografija ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/15.-query-get-topographymap.md)) z uporabo GeoPard.

Ustvarjanje zemljevida območij je asinhrona operacija. Začne se z zahtevo za izvedbo, na katero se kot odgovor vrnejo enolični identifikatorji (UUID-ji) ([zahteva 2 ali R2](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/9.-mutation-generate-zonesmap-asynchronously.md)). Ti UUID-ji povezujejo zahtevo z nadaljnjimi procesi in rezultati.

Nato porabnik API-ja GeoPard počaka na dogodek naročnine GraphQL, ki vsebuje povezane UUID-je ([zahteva 3 ali R3](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/1.-subscription-get-events.md)). Ta dogodek sporoča, da je ustvarjanje zemljevida območij končano in da so podatki pripravljeni za pridobitev.

Nazadnje lahko porabnik API-ja GeoPard pridobi podrobnosti o ustvarjenem zemljevidu območij ([zahteva 4 ali R4](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/6.-query-get-zonesmaps.md)). To vključuje metapodatke, URL-je za upodabljanje, statistično porazdelitev in geometrije ter zagotavlja celovit pregled ustvarjenega zemljevida območij.

**OPOMBA**: ZonesMap je vzdevek za `VectorAnalysisMap` v dogodku naročnine v enumeraciji `TreeNodeEntity` .

<figure><img src="https://29491374-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>Diagram zaporedja: Ustvarjanje zemljevida območij</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/svn/dokumentacija-api/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.
