> 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/diagrami-osnovnih-tokov/5.-izvedi-enacbe.md).

# 5. Izvedi enačbe

Diagram poteka Execute Equations prikazuje postopek izvajanja enačb znotraj rešitve GeoPard.

Običajno je priporočljivo uporabljati vnaprej shranjene enačbe na ravni računa ali organizacije. Enačba vsebuje povezave do drugih podatkovnih nizov, kot so SoilDataset, AsAppliedDataset, YieldDataset, SatelliteImage itd. Atributi iz teh povezanih podatkovnih nizov služijo kot spremenljivke v enačbi, kar pomeni, da so podrobnosti o podatkovnih nizih zbrane vnaprej. Najpogosteje uporabljeni podatkovni nizi so SoilDatasets ([Zahteva 1 ali R1](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/17.-poizvedba-pridobi-soildatasets.md)), AsAppliedDataset ([Zahteva 1 ali R1](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/59.-poizvedba-pridobi-asapplieddatasets.md)), and YieldDataset ([Zahteva 1 ali R1](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/16.-poizvedba-pridobi-yielddatasets.md)).

Izvajanje enačbe se sproži asinhrono. Prvi zahtevek sproži izvajanje enačbe in vrne UUID-je, ki identificirajo ustrezni EquationMap ([Zahteva 2 ali R2](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/75.-mutacija-asinhrono-ustvari-equationmap.md)). Povzetek tega izvajanja se dostavi prek GraphQL naročniških dogodkov preko WebSocket ([Zahteva 3 ali R3](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/1.-narocnina-pridobi-dogodke.md)). Po dostavi dogodka lahko uporabnik GeoPard API pridobi informacije, kot so metapodatki, statistika in geometrije ([Zahteva 4 ali R4](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/76.-poizvedba-pridobi-equationmap.md)).

Dogodkovno usmerjena arhitektura GeoPard zagotavlja robusten, učinkovit in odziven sistem za izvajanje enačb in pridobivanje njihovih rezultatov.

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2F9JqRQu208BIu74IPw0BX%2Fimage.png?alt=media&amp;token=f503851e-f67a-4bac-bb32-a2bf8cbbe136" alt=""><figcaption><p>Diagram poteka: Execute Equation</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/diagrami-osnovnih-tokov/5.-izvedi-enacbe.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.