> 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/esp/tour-del-producto-aplicacion-web/satellite-monitoring/crop-development-index-graph.md).

# Gráfico del índice de desarrollo del cultivo

Sigue el desarrollo del cultivo a lo largo del tiempo con un gráfico que compara los valores de las imágenes entre fechas y lotes.

GeoPard ofrece gráficos del desarrollo de los cultivos desde 1988. Se generan automáticamente para cada parcela y utilizan únicamente datos de **zonas sin nubes ni sombras** . Pasa el cursor sobre los puntos para ver los valores medios del NDVI. Puedes alternar entre las vistas **anual y mensual** para obtener información detallada.

Estos gráficos ayudan a los agricultores a **detectar el momento óptimo para la cosecha**, supervisar los cultivos a mayor escala y mejorar la productividad y la sostenibilidad.

<figure><img src="https://2708050521-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>El gráfico del desarrollo de los cultivos está disponible para datos desde 1988. Se genera automáticamente para cualquier parcela</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/esp/tour-del-producto-aplicacion-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.
