> 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/karte.md).

# map

The "Map" widget shows a map section with the assets placed on it.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/wNWHFiQD6Mreka7AOB3K/DDFDB14B-121F-46CB-B42D-79B42ACFA54B.png" alt=""><figcaption><p>The map with several assets.</p></figcaption></figure>

The status of the displayed assets can be checked.

{% hint style="warning" %}
Attention!\
For this widget to work, the [-> location of the assets](/collection/english-v14/documentation/assets/assets-auf-einer-karte-platzieren.md) must be set correctly.
{% endhint %}

## Configure widget

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/FdnBAMTMY64ct6A4EuQL/43A787EC-B055-496F-9EE3-085FFCDCA7C2.png" alt=""><figcaption><p>The configuration window for the "Map" widget</p></figcaption></figure>

1. Make sure you are in the "Dashboard" menu
2. Click "Add widget"
3. Click on "View"
4. click on "Map"
5. Select the primary asset. The name of this asset will appear in the widget title bar **\[A]**.
6. Select an asset you want to add **\[B]**
7. Select an attribute for the asset **\[C]** \[Note: This field will only appear after you have completed the previous step]
8. Add further assets if necessary **\[D]**
9. Choose how the assets should be displayed. **\[F]**\
   Type: Only that an asset is present at the corresponding location is displayed.\
   Status: The status of the asset is displayed.
10. Optional: Choose how much space your new widget should take up on the dashboard **\[E]**
11. Click "Save" **\[G]**
12. The widget is displayed on the dashboard

## Using the widget

### Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/NU0Z4KhYAneK3M2m70B0/C87F5EE2-78F2-497A-AF7F-A137FD6955C3.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 selection of the "Primary Asset"</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[C]</strong></td><td>Assets</td><td>The assets at their geographical location</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>

### Navigate in the map

#### Move map

When the mouse pointer is over the "Map" widget: Hold down the left mouse button and move the mouse to move the map.

#### Tilt map

When the mouse pointer is over the "Map" widget: Hold down the right mouse button and move the mouse to tilt the map. Alternatively, you can also hold down the Ctrl key (Windows & Mac) and use the left mouse button.


---

# 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/karte.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.