> 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/analysis-and-dashboards/dashboards.md).
# Dashboards
Turn a map into an interactive dashboard with charts, statistics, and filters in the legend that update as people explore the data.
{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}
A dashboard turns a map into an interactive view of its data, with statistics, charts, and filters in the legend. Each component belongs to a layer and appears beneath it. When people viewing the map filter with one component, the other components update to match.
## Add a component
1. Click **Dashboards** .svg?alt=media\&token=efdf3eba-bee1-42f5-b8a0-e8c05f843423) in the center of the toolbar at the top of the map.
2. Under **Components**, select a type, such as **Bar chart**. A dialog lists the layers that support that component type.
3. Select the layer. The component appears under the layer in the legend, and its settings open.
4. Select the attribute to read and adjust the other settings for that component type. See [Component types](#component-types).
Streamed vector layers and prerendered raster tile layers can't have components.
You can also select a layer, open its **Components** tab, and click **Add component**. Felt AI can add components too: for example, ask "Add a bar chart of parcels by zoning type".
To edit a component, click it in the layer's **Components** tab. Drag components to reorder them. To delete a component, hover over it and click the trash can icon. Deleting a component doesn't change the layer.
## Component types
Each component reads one vector layer attribute or one raster layer band, chosen in its settings. To change how a component's numbers appear, such as the number of decimal places or a suffix, click the dropdown next to **Format**. See [Number formatting](/styling/number-formatting.md).
| Component | Shows | Filter the map by |
| ----------- | ---------------------------------------------------- | ------------------------ |
| Statistic | One number, such as a count, sum, or average | None |
| Bar chart | One bar per category | Clicking bars |
| Histogram | The distribution of numeric values as bars | Dragging across a range |
| Line chart | The distribution of numeric values as a smooth curve | Dragging across a range |
| Filter | A dropdown or slider | Selecting values |
| Time series | Values per year, month, week, day, or hour | Dragging across a period |
### Statistic
A Statistic component shows one number that summarizes a layer, such as total population. In **Stat**, a vector layer offers **Feature count**, **Sum**, **Average**, **Min**, **Max**, **Median**, and **Distinct count**. A raster layer offers **Average**, **Min**, **Max**, and **Std dev** on any band, plus statistics such as **Sum**, **Area**, and **Majority** on bands that support them.
### Bar chart
A Bar chart component shows one bar for each category, such as parcels by zoning type. Under **Vertical axis**, select the attribute in **Group by**; each of its values gets a bar. Under **Horizontal axis**, **Stat** sets the length of each bar: **Feature count**, or a statistic such as **Sum** or **Average** of the numeric attribute you select in **Aggregate**. Click a bar to filter the layer to that category. Click more bars to add categories, or click **Reset** to clear the filter.
### Histogram
A Histogram component shows the distribution of a numeric attribute's values. Under **Horizontal axis**, select the **Attribute** and set the number of bars in **Bins**, up to 50. Under **Vertical axis**, **Stat** sets the height of each bar: **Feature count**, or a statistic such as **Average** of the attribute you select in **Aggregate**. Drag across the chart to filter the layer to a range, and click **Reset** to clear the filter.
### Line chart
A Line chart component shows the distribution of values as a smooth curve instead of a Histogram's bars. Use it for attributes with many distinct values. Under **Horizontal axis**, select the **Attribute**. Under **Vertical axis**, **Stat** measures **Feature count**, or a statistic of the attribute you select in **Aggregate**. Drag across the chart to filter the layer, and click the chart to clear the filter.
### Filter
A Filter component lets people viewing the map narrow a layer by an attribute. For example, they can select a few land use types from a dropdown.
In **Layout**, click **Dropdown** or **Slider**. Numeric attributes can use either; other attributes use a dropdown. In **Behavior**, **Multi-select**, the default, lets people select several values, and **Single-select** allows one.
With **Multi-select**, a text attribute's dropdown shows a searchable checklist. Switch from **is** to **contains** to match part of a value. Click **Reset** to show all features again.
A layer filter, set in the layer's **Filter** tab, is different: it applies to everyone. See [Filter layers](/layers/filter-layers.md).
### Time series
A Time series component uses a date or datetime attribute to group values into intervals, such as incidents per month. It works on vector layers only.
1. Add a Time series to the layer.
2. Under **Horizontal axis**, select the date attribute in **Attribute**.
3. In **Interval**, select **Year**, **Month**, **Week**, **Day**, or **Hour**.
4. Optional: Under **Vertical axis**, change **Stat** from **Feature count** to a statistic, such as **Sum**, and select the attribute in **Aggregate**.
Drag across the chart to filter the map to a period. The axis under the chart shows the start and end of the selected period. Hover over a bar to see its dates. Click **Reset** to clear the filter.
A Time series component doesn't play as an animation. To step through periods, drag across one period at a time, or put one layer per period in a Slider layer group. See [Organize layers](/layers/organize-layers.md).
Dates stored as text, such as in a CSV, must use one of these formats. Time zone offsets, such as `+02:00`, aren't supported.
| Format | Example |
| ------------- | -------------------------------------------------------------------------- |
| Date | `1970-01-01` or `1970/01/01` |
| Date and time | `1970-01-01 00:00:00` or `1970/01/01 00:00:00` |
| ISO 8601 | `1970-01-01T00:00:00`, `1970-01-01T00:00:00.00`, or `1970-01-01T00:00:00Z` |
## Choose what a component counts
A component's **Filtering** settings choose what it counts. Components don't count features hidden by the layer's filters.
* Turn on **Update based on view** to count only what's in the current map view. It's off by default, so the component summarizes the whole layer.
* Turn off **Update based on other filters** to keep the component unchanged when someone filters with another component. It's on by default for charts and statistics, and off for the Filter component.
## Frequently asked questions
Can I add a pie chart or a table to a dashboard?
No. Felt's components are Statistic, Bar chart, Histogram, Line chart, Filter, and Time series. To compare categories, use a Bar chart. To list a layer's features, open the table. See [Table](/tools/table.md).
---
# 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/analysis-and-dashboards/dashboards.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.
