> 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-conjuntos-de-datos-aplicados.md).

# Visualizar conjuntos de datos aplicados

Visualiza conjuntos de datos aplicados en la aplicación móvil para comparar las operaciones con los planes.

Ver conjuntos de datos aplicados.

Seleccione la explotación y, luego, el lote donde desea ver los conjuntos de datos aplicados.

A continuación, toque **CONJUNTOS DE DATOS APLICADOS**, y luego toque el conjunto de datos que desea abrir.

Puede usar estos controles en la pantalla:

<figure><img src="https://lh4.googleusercontent.com/w4mpvgR3rAVoDuICj67FA4PYuCsfswOILXxXaXQeyy9IAC032lDJBM2pV0cLdzLSeQSj9w2OP67kdQ9mImJJQLq1ZWZngU-B2bGEbcmH5KaKePpmDjVHF3AxXM60yCRCDQNWkjQyVUsX73qJdu1SDijkJEHtXQjHYwf7mUKk2j_cyZ8huN3Ef_TYJ9ey" alt=""><figcaption></figcaption></figure>

1. Cambie entre diferentes capas del conjunto de datos aplicados.
2. Muestra u oculta la leyenda.
3. Acerca el zoom al lote.
4. Acerca el zoom a su ubicación actual.
5. Oculta o muestra la capa.

Aquí hay más ejemplos de conjuntos de datos aplicados:


---

# 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-conjuntos-de-datos-aplicados.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.