> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/basics/map.md).

# Map

**Category:** Control

**Version:** 1.0

**Last Updated:** April 14, 2026

**Author:** Any2Info

***

### Description

The Map control allows visualization of geographic locations on a map-based interface. It displays one or multiple location pins based on data provided through mappings.

Each pin represents a location derived from a dataclip and can be used for interaction, navigation, or drill-through scenarios.

### Configuration Options

| Setting    | Required | Description                                                                                                                                              |
| ---------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Navigation | No       | Enables navigation functionality. When enabled, clicking a pin will start navigation to the selected location using the device’s default navigation app. |

***

### Data Mappings

| Mapping   | Required | Description                                                                                                  |
| --------- | -------- | ------------------------------------------------------------------------------------------------------------ |
| Pin       | Yes      | Determines which dataclip header contains the location values used for positioning pins on the map.          |
| Locations | Yes      | Determines the dataset (rows) used to generate location pins. Each row results in a separate pin on the map. |

***

### Location Format

The location values must follow a specific pattern to be correctly interpreted: latitude;longitude;precision;altitude;altitudePrecision

* **latitude** (required)
* **longitude** (required)
* **precision** (optional)
* **altitude** (optional)
* **altitudePrecision** (optional)

This format must match the specification as defined in the dataclip designer. If the format is incorrect, locations may not be rendered properly.

***

### Behavior

* Each row from the **Locations** mapping results in a separate pin on the map.
* The **Pin** mapping defines which column contains the location data.
* The control is visually rendered on the dashboard.
* Supports multiple location pins simultaneously.

***

### Events

| Event     | Description                                                                                                                        |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| On Click  | Triggered when a user clicks on a map pin. This acts as a drill-through mechanism using the unique identifier of the selected pin. |
| On Update | Triggered whenever the control updates its data or values.                                                                         |

***

### Interactions

* **Pin Click (Navigation enabled):** Opens navigation to the selected location.
* **Pin Click (Default):** Triggers the On Click event for drill-through scenarios.
* The control supports standard map interactions such as viewing multiple pins and interacting with them.

***

### Usage

Use the Map control when geographic visualization of data is required.

Typical use cases include:

* Displaying asset or device locations
* Visualizing customer or user distribution
* Location-based dashboards
* Enabling navigation to physical locations
* Drill-through based on geographic data

***

### Tips & Best Practices

* Ensure location data strictly follows the required format to avoid rendering issues.
* Use meaningful datasets in **Locations** to control the number of displayed pins.
* Enable **Navigation** only when users need direct routing functionality.
* Combine with drill-through actions for deeper insights into location-specific data.

***

### Changelog

| Version | Date           | Change                               |
| ------- | -------------- | ------------------------------------ |
| 1.0     | April 14, 2026 | Initial documentation version added. |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/dashboard/controls-toolbox/basics/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.