Last updated:
Map
The Map control visualizes geographic locations on a map, showing one or multiple pins based on data from a dataclip. Each pin represents a location and can be used for interaction, navigation, or drill-through.
| Setting | Required | Description |
|---|---|---|
| Navigation | No | When enabled, clicking a pin opens the device’s default navigation app, routed to that location. |
Data mappings
Section titled “Data mappings”| Mapping | Required | Description |
|---|---|---|
| Pin | Yes | The dataclip header containing the location values used to position pins. |
| Locations | Yes | The dataset (rows) used to generate pins: each row becomes a separate pin. |
Location format
Section titled “Location format”Location values must follow latitude;longitude;precision;altitude;altitudePrecision, matching the Location field’s format: latitude and longitude are required, the rest optional. An incorrect format may prevent pins from rendering correctly.
Events
Section titled “Events”| Event | Description |
|---|---|
| On click | Triggered when a user clicks a pin: a drill-through mechanism using that pin’s unique identifier. With Navigation enabled, this opens navigation instead. |
| On update | Triggered whenever the control updates its data or values. |
- Make sure location data strictly follows the required format to avoid rendering issues.
- Keep the Locations dataset focused, to control how many pins are shown.
- Enable Navigation only when users actually need direct routing.
- Combine with drill-through actions for deeper insight into location-specific data.