> 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/product-tour-mobile-app/working-in-the-field-scouting-zones-maps.md).
# Working in the field/Scouting zones maps
Use zone maps in the field to scout variability, record notes, and act faster.
Working in the field/Scouting zones maps
Once in the field, open the application and select the farm you want to explore, and on the next screen select the field that you want to scout.
Next, tap ZONES MAPS and then select the Zones Map you want to scout.
You will see the selected Zones Map with scouting pins on your screen.
By tapping the selected pin, you can view its details and/or add a comment or add/take a picture:
If you edited the zones map or scouting pins, then you will see a notification asking to sync changes with the server. Tap “Send” to synchronize changes on the server.
---
# 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 dynamically 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/product-tour-mobile-app/working-in-the-field-scouting-zones-maps.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
