> 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-webapp/satellite-monitoring/crop-development-index-graph.md).

# Grafiek van de gewasontwikkelingsindex

Volg de gewasontwikkeling in de tijd met een grafiek die beeldwaarden vergelijkt over verschillende datums en percelen.

GeoPard biedt grafieken van de gewasontwikkeling vanaf 1988. Deze worden automatisch voor elk perceel gegenereerd en gebruiken alleen gegevens uit **gebieden zonder bewolking en schaduw** . Beweeg de cursor over de punten om de gemiddelde NDVI-waarden te bekijken. Je kunt schakelen tussen **jaarlijkse en maandelijkse** weergaven voor gedetailleerde inzichten.

Met deze grafieken kunnen landbouwers **het optimale oogstmoment bepalen**, gewassen op grotere schaal monitoren en de productiviteit en duurzaamheid verbeteren.

<figure><img src="https://3615228694-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FYaHvUsBE2yeW4h67fFMG%2FGeoPard%20-%20Biomass%20development%20index%20as%20a%20graph.png?alt=media&amp;token=950aee4d-9e84-40a9-a85a-ecbd80266e87" alt=""><figcaption><p>De grafiek van de gewasontwikkeling is beschikbaar voor gegevens vanaf 1988. De grafiek wordt automatisch voor elk perceel aangemaakt.</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/nl/producttour-webapp/satellite-monitoring/crop-development-index-graph.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.
