> 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/3.-pridobitev-satelitskih-posnetkov.md).
# 3. Pridobitev satelitskih posnetkov
Spodnji diagram prikazuje, kako pridobiti zgodovinske satelitske posnetke in prejemati novo pridobljene, takoj ko postanejo na voljo v GeoPardu.
GeoPard podpira več ponudnikov, vključno s Sentinel-2, Landsat 4/5/7/8/9 in Planet. Satelitske posnetke lahko pridobite z generičnimi poizvedbami, kot so `getFarms` kot `getFields`, pri čemer se ustrezni podatki nahajajo v entiteti Field ([Request 1 or R1](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/3.-poizvedba-pridobi-satelliteimages.md)). Uporabniki API-ja lahko satelitske posnetke filtrirajo po časovnem razponu, ponudniku, odstotku oblačne pokritosti in vrstah upodobljenih geografskih zemljevidov.
Da bi ostali ažurni z novimi pridobljenimi in obdelanimi satelitskimi posnetki, API GeoPard pošilja naročniške dogodke prek WebSocketa ([Request 2 or R2](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/1.-narocnina-pridobi-dogodke.md)). Ko prejmete `MODIFY` dogodek za satelitski posnetek na ustreznem polju, je ta posnetek pripravljen za prevzem iz API-ja GeoPard po svojem UUID-ju ([Request 3 or R3](/geopard-tutorials/svn/dokumentacija-api/pregled-zahtevkov-api-ja-geopard/4.-poizvedba-pridobi-definirano-satelliteimage.md)).
Ta arhitektura, ki temelji na dogodkih, zagotavlja, da so odjemalci API-ja pravočasno obveščeni in lahko dostopajo do najnovejšega satelitskega posnetka takoj, ko je obdelan in na voljo.
Zaporedni diagram: Pridobivanje zgodovinskih in novo pridobljenih satelitskih posnetkov
---
# 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/3.-pridobitev-satelitskih-posnetkov.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.
