Skip to main content
Field mapping is what makes one widget work for every vertical. You tell the Fleet widget which key in your payload means latitude, which means speed, and so on — once, in the config panel. No code, no redeploy.

​
Dot-notation paths

Reach into nested objects with dots and into arrays with numeric indices:
PayloadPathResolves to
{ "gps": { "lat": 18.9 } }gps.lat18.9
{ "location": [23.1, 79.9] }location.023.1
{ "telemetry": { "position": { "lat": 28.6 } } }telemetry.position.lat28.6

​
Core fields

The Map view needs a device ID and coordinates; everything else is optional.
​
Device ID field
path
required
Unique identifier — e.g. deviceId, id, node, machine_id.
​
Latitude / Longitude
path
e.g. gps.lat / gps.lng, or location.0 / location.1.
​
Heading
path
Rotates the marker — e.g. heading, telemetry.yaw.
​
Speed
path
Shown in the marker popup.
​
Status
path
Drives marker/row color (green / amber / red).

​
Extra display fields

Any payload key can surface in the marker popup and detail panel — add an extra field with a label and a path (Passengers → meta.passengers, Battery → telemetry.battery).

​
Same widget, four payloads

{ "deviceId": "bus-07", "gps": { "lat": 18.92, "lng": 72.83 }, "speed": 42 }

{ "id": "drone-01", "telemetry": { "position": { "lat": 28.61, "lng": 77.20 } }, "battery": 82 }

{ "node": "field-A3", "location": [23.18, 79.94], "moisture": 0.42 }

{ "machine_id": "CNC-7", "coords": { "x": 12.5, "y": 44.1 }, "rpm": 2400 }
The same Fleet widget reads all of them — only the mapping differs.

Back to Fleet overview

The six views and the data contract.