> 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/monitoreo-satelital/grafico-del-indice-de-desarrollo-del-cultivo.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 proporciona gráficos de desarrollo de cultivos que se remontan a 1988. Se generan automáticamente para cada lote, utilizando solo datos de **zonas libres de nubes y sin sombras** . Pase el cursor sobre los puntos para ver los valores medios de NDVI. Puede alternar entre **vistas anuales y mensuales** para obtener información detallada.

Estos gráficos ayudan a los agricultores a **detectar el momento óptimo de cosecha**y supervisar los cultivos a mayor escala, además de 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%2FCPTPgYcnX5R6t8cY5NFW%2FGeoPard%20-%20Biomass%20development%20index%20as%20a%20graph.png?alt=media&amp;token=36d87266-093f-43b3-a14c-85f0a0cad58a" alt=""><figcaption><p>El gráfico de desarrollo del cultivo está disponible para los datos desde 1988. El gráfico se crea automáticamente para cualquier lote</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/monitoreo-satelital/grafico-del-indice-de-desarrollo-del-cultivo.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.