> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/heatmap.md).

# Heatmap

The "Heatmap" widget visualizes values through color areas on a map.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/oaOkE6qF7ycek2PlRKJ3/8C4CAE4F-CB91-4A52-8DC5-617B91C8BE8D.png" alt=""><figcaption><p>The "Heatmap" widget</p></figcaption></figure></div>

## When should this display be used?

This form of representation is well suited to recognizing patterns in complex data and depicting them in an easily understandable way. One possible use case would be, for example, displaying the presence of people in one or more buildings.

## Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/XroM1C7H2Lxa2S21tJsY/3951B30D-3E7C-44A0-8BA9-E028704F26FB.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="115.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Title</td><td>Is affected by the primary asset</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td></td></tr><tr><td><strong>[C]</strong></td><td>Visualizations of asset values</td><td>Each of the three color points represents values from one respective asset</td></tr><tr><td><strong>[D]</strong></td><td>Zoom in</td><td>Enlarges the map display</td></tr><tr><td><strong>[E]</strong></td><td>Zoom out</td><td>Reduces the map display</td></tr><tr><td><strong>[F]</strong></td><td>Home view</td><td>Switches to the home view</td></tr><tr><td><strong>[G]</strong></td><td>Current location</td><td>Switches to the user's current location.<br>Note: Eliona requires permission to access the user's location for this</td></tr><tr><td><strong>[H]</strong></td><td>Center assets</td><td>Displays all assets present in the widget</td></tr></tbody></table>

## Configuration

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/5NStn9Xdz0iswYnFv5sK/9C675EB0-758E-418B-A2B9-90DC4D8F6617.png" alt=""><figcaption></figcaption></figure></div>

1. Make sure you are in the "Dashboard" menu
2. Click "Add widget"
3. Click on "View"
4. click on "Heatmap"
5. Select the primary asset. The name of this asset will appear in the widget title bar **\[A]**.
6. Choose whether the color coding should be static or dynamic **\[B]**\
   Static: The range for values is calculated automatically\
   Dynamic: You can set the range of values manually
7. Select an asset you want to add
8. Select an attribute for the asset **\[C]** \[Note: This field will only appear after you have completed the previous step]
9. (Optional) Give the asset a custom title **\[D]**
10. Choose whether the current value or an aggregated value should be displayed **\[E]**
11. Add further assets if necessary **\[F]**
12. Optional: Choose how much space your new widget should take up on the dashboard **\[H]**
13. Click "Add widget" **\[G]**


---

# 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.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/heatmap.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.
