Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • Overview
  • Working with Maps
  • Placing a Map
  • Geolocation Data & Device Location role
  • Adding Data
  • Any tag or All tags
  • Appearance
  • Manual Start Location
  • Show Device Details on Public Dashboard
  • Marker Value
  • Style
  • Full Height Maps
  • Sidebar Dashboards
  • Historical Data
  • High-Resolution Routes

Was this helpful?

  1. Dashboards
  2. Widgets

Map Widget

Quick-Start and Reference to the Datacake Map Widget

Last updated 9 months ago

Was this helpful?

Overview

The Datacake Dashboard Editor features a widget to show one or many positions, including the option to show historical routes and interactivity.

Working with Maps

In order to start with a map widget, you need to add it to a dashboard. The map widget works like mostly all of the widgets on both device and workspace dashboards.

Placing a Map

Bring your dashboard editor into edit mode and add a new widget. This will open up the widget picker and in here you select the "Map" widget type.

This will add the widget to the dashboard and it will open up the widget editor.

Geolocation Data & Device Location role

Map Widgets only support database fields of the type "Geolocation". Most of your devices do have a location field available. If you want to learn more about geolocation data types please head over to the database section of this documentation.

It is necessary that you set the role of that Geolocation field as Device Location. For that, go to your device's configuration. Under fields select Edit Field and set the Role to Device Location.

Adding Data

The location data from your devices that posses a geolocation field will be automatically fed to the map widget. However, if you want to filter which devices get to be shown on a map, you can use tags to select the devices to be shown.

Any tag or All tags

The option "Any tag" represents an OR function, which means that the map widget will display all devices that have any of the selected tags picked from the drop-down-list above.

The option All tags performs an AND function, which means the map will display the devices that have all tags selected on the drop-down-list.

Appearance

The Appearance section allows you to control behaviour and override default settings such as colours or set a different icon.

Manual Start Location

You can setup the initial coordinates shown on the map by enabling this option.

Show Device Details on Public Dashboard

When enabled, allows to show details of devices selected on the sidebar dashboard, described below.

Tint Color

Colorises the widget itself.

Marker Value

You are able to select which information gets to be displayed on the widget. You can select between any of the configured field roles (primary, secondary, device battery, device signal or none). When selecting none, the configured icon of the device will be displayed on the map.

Style

On the Appearance section, you can select the various available map stylings. You can switch between:

  • Light

  • Dark

  • Outdoor

  • Satellite

  • Streets

Full Height Maps

Sometimes you just want to have a single map on a dashboard, and you may want to display it in fullscreen on a wide variety of screen sizes.

However, since our dashboard designer is grid-based, this is not directly possible, as the grids represent an absolute height. Even if you place and scale the widget on the grid in a way that it fully extends to the bottom of your screen, it won't do that on a different screen.

To work around this we have added an option to the map widget that allows you to have the map widget automatically scale to the bottom of the browser window.

In the Appearance section on the map widget settings, you can find an option called "Use full screen height".

After enabling this option and exiting the edit mode of the dashboard editor, the map widget will autoscale to the bottom of the available screen size and/or browser window.

Placing additional Widgets

You just have to make sure that no other widget is below the map widget. They would stay in their position and be overdrawn by the automatically scaling map widget.

Placing Widgets above, left, or right next to the map widget is no problem.

Sidebar Dashboards

When you click on a device on a map, the so-called sidebar menu shows on the right side of the browser window.

Editing Sidebar Dashboards

For the display of the sidebar dashboard, we use the mobile dashboard layout of a device. This means that you can create or customize the Sidebar Dashboard yourself.

To do this, you have to activate the edit mode of the dashboard in your device and activate the mobile layout.

Sidebar Dashboards on Public Dashboard

If you share your global workspace dashboards with others and you want to use the sidebar dashboard feature, you have to enable this first.

To do so, please access the "Appearance" view using the tab bar on the widget editor and enable the option "Show Device Details on Public Dashboard" just as shown in the following screenshot.

Historical Data

Only the map widget on your Device's dashboard allows you to show historical geolocation data in the form of "routes". You can enable this setting in the map widget editor, under Timeframe. This will unfold a time frame picker and you only need to select one of the available time frame presets.

High-Resolution Routes

If you select one of our presets we define the number of data points shown on the map, so for example if you select "Day" as a time frame preset we only show a new data point on the map when 15 minutes have passed to the previous one. This can lead to the fact that we are skipping important route points.

To manually override the resolution parameter please first select a time frame preset and additionally click on "custom". This will open up an editor where you can set the resolution down to as low as 1 minute.