> For the complete documentation index, see [llms.txt](https://docs.jakarto.com/asset-viewer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jakarto.com/asset-viewer/en/prise-en-main/filtering.md).

# Filtering

Filtering allows you to display only the assets on the map that match specific criteria.\
This feature is useful for quickly targeting interventions, inspections, or area-based analyses.

### Filter with numeric properties

For quantitative properties (for example area, length, diameter, or height), use the sliders to define a minimum and maximum value range.

In the example below, the first two filters apply to trees:

1. `Projected crown area (m²)`
2. `Trunk diameter (DBH) (cm)`

By narrowing these ranges, only trees matching the selected thresholds remain visible on the map.

### Filter with text properties

For categorical properties (for example `species`, `class`, `type`), select one or more text values.

You can combine multiple text and numeric filters at the same time.\
Each displayed asset must then match all applied criteria.

<figure><img src="/files/NPYeHlDtCWfmaOnPo26J" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/u4GcVAreIgBgAKKa8BzP" alt=""><figcaption></figcaption></figure>

The following three images show an example of text-based filtering using the `p-code` property for traffic signs.

By clicking on the maximum speed 50 sign image (`P-70-2-50`), you can quickly visualize where these signs are located across the territory, and therefore identify zones associated with different speed limits.

<figure><img src="/files/Wjopo7pBhTvBWMMayjwH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/SinKP2VWcdfwHA7GCDad" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/W36vdlYEZ4u7XMqgCuDj" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jakarto.com/asset-viewer/en/prise-en-main/filtering.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
