> 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/mobairurebyfirut.md).

# モバイル圃場レビュー用フィルター

モバイルアプリでマップと圃場データを絞り込み、重要なレイヤーに集中できます。

モバイル圃場確認用のフィルター

詳細な絞り込みオプションにアクセスするには、フィルターボタンをタップして利用可能なオプションを表示します。

の **衛星** モニタリングでは、次の絞り込みオプションがあります

* **画像** （雲なし、部分的な雲、すべて）
* **日付** （月および／または年を選択できます）

<figure><img src="https://lh3.googleusercontent.com/BaVqUgBlWsZ6vIeIUBoRIjXgf9KJ2PXbs3aHbvPqfvWDdMw_TphitamZXy6SxhcyA4LJPDNnBSFkIpWdJqwlZmrDxwSHenMa2Yr4fcExuZtMI13lObNiqwUu0fgQME02x3sSu6hxe834l7_Rq49-6Q" alt=""><figcaption></figcaption></figure>

の **ゾーンマップ** セクションでは、次の条件で絞り込めます：

* ゾーンマップの種類（マルチレイヤー、衛星、土壌、交差、収量、地形）
* ピン – ピン付きのマップのみを表示（はい、いいえ、すべて）
* ダウンロード済み – オンラインまたはオフラインのマップのみ、またはすべてを表示（オフライン、オンライン、すべて）

<figure><img src="https://lh3.googleusercontent.com/16ZBKps4RoXQNARx-oB59VPfifsHuXEXALWMnQnfmtgMYrwRmHYFg8GRLV_Z85NpHqXtXZl4nt6kLq_dMk0_rx11_sCbyI1kqEQC5dXqRBESmSKQf11PnCH3eYV79MKbgjSnp9zUcdZOGqq3GQbQbA" alt=""><figcaption></figcaption></figure>


---

# 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/mobairurebyfirut.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.
