> 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/pt-br/tour-do-produto-aplicativo-web/satellite-monitoring/crop-development-index-graph.md).

# Gráfico do Índice de Desenvolvimento da Cultura

Acompanhe o desenvolvimento da cultura ao longo do tempo com um gráfico que compara os valores das imagens entre datas e talhões.

A GeoPard oferece gráficos de desenvolvimento das culturas desde 1988. Eles são gerados automaticamente para cada talhão, usando apenas dados de **áreas sem nuvens e sombras**  . Passe o cursor sobre os pontos para ver os valores médios de NDVI. Você pode alternar entre as visualizações **anuais e mensais** para obter informações detalhadas.

Esses gráficos ajudam os agricultores a **identificar o momento ideal da colheita**, monitorar as culturas em uma escala maior e aumentar a produtividade e a sustentabilidade.

<figure><img src="https://1397135423-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>O gráfico de desenvolvimento das culturas está disponível para dados desde 1988. Ele é criado automaticamente para qualquer talhão</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/pt-br/tour-do-produto-aplicativo-web/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.
