Map

MAP

Live position widget with device points, tracks and board-originated GPS updates.

At a glance

Default8 x 5

Minimum4 x 3

Resizeboth

Pinrequired

Interactiveno

Behavior

Can track latest point or keep a trail depending on config.
Useful for mobile assets, field rigs and outdoor sensing.
Pairs with Image and Table for geospatial dashboards.

Firmware contract

Publish latitude and longitude values through the expected pin format.

On the app side this widget snaps to the 8-column square grid and uses both resizing. Its raw type is MAP and the matching icon token in the app is map.fill.

Pin support: Virtual pins or stream-backed location data consumed as map coordinates.

Transmission: Location updates are regular telemetry writes interpreted as geographic points, usually latitude/longitude pairs with optional label or radius metadata.

Canvas preview

docs.widget.preview

41.9028°N 12.4964°E

Map

inside

GEOFENCE

Widget contract

Property	Value
Raw type	MAP
Default size	8 x 5
Minimum size	4 x 3
Resize mode	both
Pin requirement	required
Pin support	Virtual pins or stream-backed location data consumed as map coordinates.
Interactive	read-only / service
Transmission	Location updates are regular telemetry writes interpreted as geographic points, usually latitude/longitude pairs with optional label or radius metadata.

Allowed pin families

Virtual pins or stream-backed location data consumed as map coordinates.

Transport path

Location updates are regular telemetry writes interpreted as geographic points, usually latitude/longitude pairs with optional label or radius metadata.

Operational limits

Meaningful UX depends on valid coordinate cadence

Configuration surface

isPinToLatestPoint keeps the viewport pinned
isMyLocationSupported overlays the viewer location
isSatelliteMode flips the map style
radius and labelFormat tune context
trail depth should stay bounded when devices publish GPS frequently

Limits and caveats

Meaningful UX depends on valid coordinate cadence
It is a large widget and is not useful below its minimum 4x3 footprint
Mixed coordinate payload formats quickly create phantom jumps or broken tracks

Protocol and implementation notes

Map payloads should document whether they are latitude/longitude only or also carry radius, labels or trail metadata.
High-frequency GPS updates need bounded trail depth and viewport policy or the dashboard becomes noisy faster than the board becomes useful.

Layout notes

Canvas footprint

8 x 5

Default footprint in the Plynx canvas before user resizing.

Resize floor

4 x 3

The minimum size accepted by the app during drag-resize.

Interaction model

Display

Whether the user edits state directly or only reads it.

Related widgets

SuperChart

Historical and live chart surface with multiple streams, periods and annotations.

Terminal

Bidirectional terminal for commands, logs and line-oriented interaction.

Table

Dynamic multi-row table fed by firmware commands and row updates.

Eventor

Automation rules widget for conditions, actions, mail and notification flows.