> 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/jpn/tsu-mobairuapuri/dtawo-1.md).
# 収量データを表示
モバイルアプリで収量マップを表示し、圃場ごとの収穫成績を比較します。
収量データの表示
収量データを表示するには、まず農場を選び、次に確認したい圃場とその収量データを選択します:
次に、［収量データ］をタップし、表示したい収量データマップをタップします:
収量データ画面では、次の操作ができます:
1. 収量データファイルのさまざまなデータレイヤーを切り替えられます。
2. 収量データの凡例を表示します。
3. 圃場にズームします。
4. 現在地にズームします。
5. レイヤーを非表示/表示します。
収量データの追加例:
---
# 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/jpn/tsu-mobairuapuri/dtawo-1.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 `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.
