> 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/geopard-api-parskats.md).
# GeoPard API pārskats
Pēdējais atjauninājums: 2023. gada 10. jūlijs
GeoPard ir precīzās lauksaimniecības platforma ar visām funkcijām, kas pieejamas caur API
GeoPard API piedāvā gan GraphQL, gan REST galapunktus vienkāršai mijiedarbībai. Darbojoties gan kā pasīvs, gan aktīvs interfeiss, tas ļauj citām lietotnēm programmatiski pieprasīt analītisko atvasinājumu izveidi un saņemt atjauninājumus, kas saistīti ar sarežģītu datu apstrādi.
Izmantojot GeoPard API, nekavējoties ir pieejami visi izejas datu kopumi — tostarp ražas novākšanas dati, tehnika, augsnes paraugu ņemšana un skeneri, satelītattēli un reljefs — kā arī analītiskie atvasinājumi, piemēram, pārvaldības zonas, vienādojumu kartes, rekomendācijas un rastra virsmas.
GeoPard API atbalsta dažādas ģeotelpisko datu atveides iespējas, nodrošinot gan Raster (`jpg`, `png`, `geotiff`) un Vector (`shp`, `geojson`, `isoxml`) formātus. Lai iegūtu visaptverošu pārskatu par API, skatiet mūsu [emuāra ierakstu](https://geopard.tech/blog/upkdhsnyk1-precision-agriculture-api/).
---
# 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/geopard-api-parskats.md?ask=&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.
