> 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/svn/predstavitev-izdelka-mobilna-aplikacija/filtri-za-mobilni-pregled-polj.md).
# Filtri za mobilni pregled polj
V mobilni aplikaciji filtrirajte karte in podatke o poljih, da se osredotočite na plasti, ki so pomembne.
Filtri za mobilni pregled polja
Za dostop do naprednih možnosti filtriranja tapnite gumb za filtre, da vidite razpoložljive možnosti.
Za **satelitsko** spremljanje imate na voljo naslednje možnosti filtriranja
* **Slike** (brez oblakov, delno oblačno, vse)
* **Datum** (izberete lahko mesec in/ali leto)
V **ZEMLJEVIDIH OBMOČIJ** razdelku lahko filtrirate po:
* Vrsta zemljevidov območij (večslojni, satelitski, tla, presečišča, pridelek in topografija)
* Zatiči – prikaži samo zemljevide z zatiči (Da, Ne in Vse)
* Preneseno – prikaži samo spletne ali brez povezave zemljevide ali vse (brez povezave, spletno in vse)
---
# 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/svn/predstavitev-izdelka-mobilna-aplikacija/filtri-za-mobilni-pregled-polj.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.
