> 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-movil/visualizar-datos-de-rendimiento.md).

# Visualizar datos de rendimiento

Visualiza mapas de rendimiento en la aplicación móvil para comparar el desempeño de la cosecha en todo el lote.

Visualización de datos de rendimiento

Para ver los datos de rendimiento, seleccione la finca y luego el lote cuyos datos de rendimiento desea inspeccionar:

A continuación, pulse DATOS DE RENDIMIENTO y después pulse el mapa de datos de rendimiento que desea ver:

En la pantalla de datos de rendimiento puede ver los siguientes controles:

<figure><img src="https://lh4.googleusercontent.com/o2ggl1yXwdTrrE3hd8mY43stEogDaebIH8oTb3ym9AVnlXyJpE-OY3Hq-MbCSsBoDYpxFrhBz_lu5EHLQCrdiGs5MuaSiRWzJGqxiA0WKYpCGrJbMBf29VflGZcokewNeyzXxhmyYBMXHv5O-gDmVzNP-eKXriUes_IzP4u4lYs23fENz9clK2Zdatl2" alt=""><figcaption></figcaption></figure>

1. Le permite cambiar entre diferentes capas de datos del archivo de datos de rendimiento.
2. Muestra la leyenda de los datos de rendimiento.
3. Acerca a la parcela.
4. Acerca a su ubicación actual.
5. Oculta/Muestra la capa.

Algunos ejemplos más de datos de rendimiento:


---

# 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-movil/visualizar-datos-de-rendimiento.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.