> 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/api-docs/diagrams-with-basic-flows/3.-get-satellite-imagery.md).
# 3. Get Satellite Imagery
The diagram below shows how to fetch historical Satellite Images and receive newly acquired ones as they become available in GeoPard.
GeoPard supports several providers, including Sentinel-2, Landsat 4/5/7/8/9, and Planet. You can fetch Satellite Images with generic queries such as `getFarms` and `getFields`, with the relevant data located in the Field entity ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/3.-query-get-satelliteimages.md)). API consumers can filter Satellite Images by date range, provider, cloud coverage percentage, and rendered geo map types.
To stay updated on newly acquired and processed Satellite Images, the GeoPard API sends subscription events through WebSocket ([Request 2 or R2](/geopard-tutorials/api-docs/geopard-api-requests-overview/1.-subscription-get-events.md)). When you receive a `MODIFY` event for a Satellite Image on the relevant field, that image is ready for collection from the GeoPard API by its UUID ([Request 3 or R3](/geopard-tutorials/api-docs/geopard-api-requests-overview/4.-query-get-defined-satelliteimage.md)).
This event-driven architecture ensures API customers are notified promptly and can access the latest Satellite Image as soon as it is processed and available.
Sequence diagram: Get historical and newly acquired Satellite Images
---
# 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/api-docs/diagrams-with-basic-flows/3.-get-satellite-imagery.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.
