> 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.md).
# 土壌データを表示
モバイルアプリで土壌データセットを表示し、圃場内の空間的ばらつきを確認します。
土壌データの表示
土壌データを表示するには、まず農場を選択し、次に確認したい圃場の土壌データを選択します:
次に、［SOIL DATA］をタップし、確認したい土壌データマップをタップします:
土壌データマップ画面では、次の操作を確認できます:
1. 土壌データファイル内の異なるデータ層を切り替えることができます。
2. 土壌データの凡例を表示します。
3. 圃場にズームします。
4. 現在地にズームします。
5. レイヤーを非表示/表示します。
6. 圃場にピンを追加します。
土壌データのその他の例:
---
# 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.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.
