> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/mymove-manual/map-explorer.md). # Map Explorer The Map Explorer shows every **device of the project on the map**, with its **status**, the **latest values** of its parameters, and their **alarm thresholds**. From the map, you can open the detail of a sensor, read its alarm events, **compare parameters** of several sensors in one chart, and **save the comparison in Analytics**.
The page includes: * A **map** with one marker per device and a floating **toolbar** (Device list, Device filters, view switches, time range). * A **sensor detail sidebar** with metadata, trend, statistics, last value with alarm thresholds, and recent events. * An **Alarm details** modal for a single alarm event. * **Compare data** mode and **Add to Analytics**. {% hint style="info" %} A device appears on the map only after it has been positioned (Settings → Device visualization → Map). Devices without coordinates are not shown. {% endhint %} {% hint style="info" %} The **time range** selected in the toolbar (24 hr, 2 d, 7 d, 14 d, 30 d, or Custom) applies to every chart, statistic, and event list on the page. {% endhint %} *** ## Prerequisites ### Markers Each marker shows the icon of the **device type** and the **device name** below it. Online devices have a solid marker, while offline devices have a dashed grey marker. Hovering a marker shows a tooltip with device type, EUI, name, status, last transmission, and the trend of the main parameter. Hovering never opens the sidebar. ### Device identification Devices are listed as **device type** and their **EUI** with their **custom name**, using the same naming as the Devices page. *** {% stepper %} {% step %} #### Navigate the map * Zoom and pan the map. The **fit-to-screen** button in the bottom-right corner brings every device back into view. * Click a **marker**, or a row in the **Device list**, to open the sensor detail sidebar. * Press **ESC** or click **X** to close the sidebar. * Use the toolbar to switch between the **Map** view and the **Image** view, which displays the photo of the structure configured in Devices. * Change the map style from the toolbar. ### Device list Click the list icon to open the **Device list**. Devices are grouped by **device type** with a counter per group. Each row shows: * Type * EUI * Custom name * **Online / Offline** status Hovering a row highlights the marker on the map. Clicking it opens the sidebar. ### Device filters Click the filter icon to open **Device filters**: * **Search** by name or EUI. * **Device type** chips: select one or more types to show. * **Offline devices only** toggle. * **Device name** toggle: hides name labels to declutter the map. * **Reset filters** restores the default view. {% endstep %} {% step %} #### Sensor detail sidebar The sidebar opens on the right and keeps its header and action bar visible while you scroll. ### Metadata View the device: * **Status** (Online / Offline) * **Last heartbeat** * **Coordinates** An offline device shows a banner, but its historical data remain available. ### Trend Select a **parameter chip** to plot its trend over the selected time range. The block header provides: * **Parameter preferences**: enable the parameters you want to track, mark favourites to pin them across the platform, and drag them to reorder by priority. * **Expand**: opens the chart in the **Trends** modal, with the same parameter chips and a **download** action. * **Thresholds** toggle: overlays the parameter alarm thresholds as dashed lines. Below the chart are the period statistics: * **Min** * **Max** * **Mean** * **Δ vs period start** ### Last value & alarm thresholds Each parameter has one bar. The bar is divided into the **Alert**, **Warning**, and **Critical** zones defined by the device thresholds, on one or both sides of the baseline. A dot marks the **last value**. Hover the bar to view threshold values. An info icon appears when the parameter baseline is not zero. ### Recent events View the latest device events in the selected time range. Click an **alarm event** to open the **Alarm details** modal. Firmware and connectivity events open a lighter drawer with their details. ### Actions * **Open in Data Explorer**: opens the device in Data Explorer while keeping the current time range. * **Compare with…**: starts Compare data mode. * **View Alarms**: opens the Alarms page filtered for the device. {% endstep %} {% step %} #### Alarm details The modal shows the **Alarmed event graph**: the parameter trend during the 12 hours before and after the event, including threshold zones and the highlighted alarm point. A download action is available. Below the graph, view: * **Alarm details**: alarm level, parameter, value, date, and thresholds. * **Device details**: name, type, EUI, revision, last transmission, and status. {% endstep %} {% step %} #### Compare data Click **Compare with…** in the sidebar or the compare icon in the toolbar. The **Compare mode - click devices to add** banner appears at the top of the map. Click a marker to open a popover listing the device **parameters**. Select the parameters to compare. The **Parameters selected** box maintains the running list. The **Compare data** panel opens on the right with: * **Selected sensors**: one row per device, one chip per parameter, and **Add more** to select other devices. * An **Overlay comparison** chart for the selected time frame. {% hint style="info" %} Only parameters with the **same unit of measure** can be plotted together. Selecting a parameter with a different unit shows an informative toast. {% endhint %} {% endstep %} {% step %} #### Save to Analytics Click **Save to Analytics** in the Compare data panel. The **Add to analytics** modal contains the same tabs as an Analytics profile: * **General info** * **Alarms** * **Axis** * **Customization** Set a **Title**, an optional **Chart description**, and **Select folder**, then click **Save**. The chart is available in Analytics in the chosen folder. {% hint style="warning" %} If saving fails, the toast **Couldn't save to Analytics** appears and your comparison remains active. Retry from the same panel. {% endhint %} {% endstep %} {% endstepper %}
*** ## Troubleshooting
A device is missing from the map The device has no coordinates. Position it from Settings → Device visualization → Map.
A parameter cannot be added to the comparison Its unit of measure differs from the parameters already selected. Start a new comparison for that unit.
The trend chart is empty The device did not transmit in the selected time range. Extend the time range or check the device status in the Devices page.
--- # 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://move-solutions.gitbook.io/untitled/mymove-manual/map-explorer.md?ask=&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.