> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/display/map.md).

# Map

Google map plotting bound lat/lng markers with custom icons and labels, auto-centering on them

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-3743dfc34e43ed38ba95a843b8cd08bff7f8d711%2Fwidget-map.png?alt=media" alt="Map of Germany with four acme sites as factory markers in their status colors: Hamburg, Berlin, Düsseldorf and Munich" width="688"><figcaption></figcaption></figure>

A map shows places on a Google map: plants, warehouses, vehicles or machines in the field. Your logic delivers the markers with their coordinates, and each marker can bring its own icon, color and label, for example the status color of a site. The map can center itself on the markers, and users zoom and pan as they know it from Google Maps.

**Good for:** site and fleet overviews, tracking vehicles and containers, service calls in the field.

## Properties

The widget's General tab lists these properties under Receives and Emits. Drop an executor's output, input or trigger onto a row to link it. An example also fills an unlinked widget as demo data in the App Builder.

{% tabs %}
{% tab title="Receives" %}
**`markers`** (from an output, `Array<object>`): The markers to display. The map auto-fits to them when `centerOnMarkers` is enabled.

<details>

<summary>Example</summary>

```json
[
  {
    "lat": 52.52,
    "lng": 13.405,
    "text": "Berlin plant"
  },
  {
    "lat": 48.137,
    "lng": 11.575,
    "text": "Munich plant",
    "iconColor": "#dc2828"
  }
]
```

</details>
{% endtab %}
{% endtabs %}

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs. Settings marked *set per screen* are pinned by nature: every screen keeps its own value.

<details>

<summary>Look &#x26; feel</summary>

* **Default center**: Point the map shows at start as \[latitude, longitude]; markers move it while center on markers is on.
* **Default zoom**: Zoom level at start, from 1 (world) to about 20 (buildings); 10 shows a city, 15 streets. *Set per screen.*
* **Default icon**: Font Awesome class drawn for a marker that names no icon of its own, e.g. fas fa-map-marker-alt.
* **Default icon size**: Size in px of a marker icon that names no size of its own.
* **Default icon color**: Color of a marker icon that names no color of its own; auto keeps the theme's temperate color.
* **Center on markers**: Fits the map to the markers whenever they change; a single marker is centered at the default zoom.
* **Show map type selectors**: Shows the map/satellite switch in the top right corner. *Set per screen.*
* **Show traffic information**: Overlays Google's live traffic on the roads.
* **Show transit information**: Overlays Google's public transport lines and stops.

</details>


---

# 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.heisenware.com/reference/widgets/display/map.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.
