> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/layers/filter-layers.md).
# Filter layers
Show only the features in a layer that match a condition, such as Status is Open. A filter hides features without changing the layer's data.
A layer filter shows the features that match a condition, such as "Status is Open", and hides the rest. It applies to the whole layer: on the map, in the [table](/tools/table.md), and in [spatial analysis](/analysis-and-dashboards/spatial-analysis.md). Filtering doesn't change or delete the layer's data, so you can edit or remove a filter at any time.
Everyone viewing the map sees the filtered result, and people viewing the map can't remove a layer's filters. To let them choose what to show, add a [Filter component](/analysis-and-dashboards/dashboards.md#filter), which appears in the legend.
## Add a filter
1. Click **Edit map** in the toolbar at the top right of the map.
2. Select the layer in the legend.
3. In the detail panel, click the **Filter** tab.
4. Click **Add filter** and select an attribute.
5. Select a comparison, such as **is** or **greater than**, and enter or select a value. Features that don't match disappear from the map.
To match a list of values, select **is**, then select each value. Number attributes with fewer than 100 distinct values also offer a checklist when you select **equals**.
Combine several filters with **and** to match all of them, or with **or** to match any of them. To turn off or delete a filter, use its card in the **Filter** tab.
## Comparisons by attribute type
| Attribute type | Comparisons |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Text | is, is not, contains, doesn't contain, exists, doesn't exist |
| Number | equals, doesn't equal, greater than, less than, between, greater than or equal to, less than or equal to, exists, doesn't exist |
| Boolean | is true, is false |
| Date | is, before, after, between, exists, doesn't exist |
## Save the filtered features as a new layer
1. In the **Filter** tab, click the feature count next to **Add filter**, such as **631 features**.
2. Click **Update in new layer**. Felt adds a layer containing only the matching features.
To split a layer by category, repeat this with a filter for each category.
## Filter by location
Layer filters work on attributes, not location. To keep only the features inside an area, [clip](/analysis-and-dashboards/spatial-analysis.md#clip-a-layer-to-a-boundary) the layer with a polygon of that area. Clipping creates a new layer. To let people viewing the map draw an area and filter by it, add the [Spatial filter](/tools/spatial-filter.md) extension.
To list only the features in the current map view, open the layer's **ยทยทยท** menu in the legend and click **Open table**, or press **T**. Then select **Visible** at the top of the table.
---
# 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://help.felt.com/layers/filter-layers.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.
