> 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/nl/producttour-mobiele-app/satellietbeelden-bekijken.md).

# Satellietbeelden bekijken

Bekijk satellietbeelden in de mobiele app om stress, groei en variatie op het perceel te scouten.

Satellietbeelden bekijken

Met de GeoPard mobiele app kunt u satellietbeelden bekijken op uw mobiele apparaat.

Om satellietbeelden te bekijken, moet u eerst het landbouwbedrijf selecteren en vervolgens het perceel waarvan u de satellietbeelden wilt inzien:

Tik vervolgens op SATELLIETMONITORING en tik daarna op het satellietbeeld dat u wilt zien:

U ziet een vergelijkbaar scherm:

<figure><img src="https://lh4.googleusercontent.com/S7EuCt06-Fwicj99mazf8wqUdtYMtQb3-F65tPvlCp8DOZlx3s90f6_C7rVQX2BW0t9DPNKphs3T9bXYgALQsGW66j5fqr9-avhsWjUmI4D6uW3gFUogNexWap_90dXYH_v68zudfQXyYJoseKZpgXTUNNrus3zFCywbJ1EOsWGLRZUPMF6M4rwpx0JD" alt=""><figcaption></figcaption></figure>

Op het scherm hebt u de volgende bedieningen:

1. Index selecteren: RGB, NIR, EVI2, GNDVI, IPVI, LAI, NDVI, SAVI, OSAVI, GCI, NDWI, WDRVI, SBI
2. Inzoomen op het perceel.
3. Inzoomen op uw locatie.
4. De laag verbergen/weergeven.


---

# 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/nl/producttour-mobiele-app/satellietbeelden-bekijken.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.