> 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/data-explorer.md).

# Data Explorer

The Data Explorer page provides **full access to the historical data** collected from all system devices. This tool allows you to examine trends and data collected from each sensor in detail, making it easier to identify patterns or significant changes in the monitored parameters.

{% hint style="info" %}
Each type of sensor displays distinct graphs, varying based on the type of data it collects.
{% endhint %}

## Data visualization

In Data Explorer, each graph displays a specific parameter detected by the sensor. Where possible, traces corresponding to different monitoring axes are overlaid to facilitate data interpretation. The standard configuration of each graph is as follows:

* **Top Legend**, which includes:
  * Name of the trace or reference axis.
  * The color corresponding to the trace on the graph.
  * The maximum value recorded within the selected time range (this value is aggregated from the data).
* **Navigable Data Preview**, use the slider to zoom into the selected time range.
* **Graph**, displays multiple overlaid traces.

<figure><img src="/files/7LeoBsmfXmv7SkuFVJOg" alt=""><figcaption><p>Chart detail - Acceleration amplitudes</p></figcaption></figure>

***

## Structure of the Data Explorer Page

For each available sensor, you can view the trend of the collected data through the **Trends** feature. For certain types of sensors, additional details on each measurement are provided in the **Acquisitions** section. Consequently, the Data Explorer interface is divided into two main areas:&#x20;

* **Trends**
* **Acquisitions**

### Trends

The "Trends" section in Data Explorer provides a collection of graphs that highlight the progression of all the data collected for each parameter measured by the sensors. Each type and version of sensor is associated with distinct graphs, which vary based on the type of data acquired. Each individual graph reflects each parameter measured by the sensor individually. Additionally, the graphs show a subset of the data, filtered by the selected time range, providing a customizable view of the sensor's performance over time.

{% hint style="info" %}
**Data aggregation** is applied based on the selected time range, and this aggregation method varies depending on the specific sensor in use.
{% endhint %}

For dynamic sensors (as the Accelerometer and the DDS - Dynamic Displacement Sensor), when data is not aggregated, each data point (called Acquisitions) shown in the Trends graphs corresponds to a value derived from a sampling period that can last several minutes. These acquisitions could be the maximum value recorded during the sampling period, or the average value or the peak-to-peak (pk-pk) value, depending on the sensor type.

{% hint style="info" %}
For more information on the differences between Static and Dynamic monitoring sensors, refer to the section [**Monitoring Types**](/untitled/references/devices.md#monitoring-types).
{% endhint %}

<figure><img src="/files/9DnzJ1vNq9bHVMrlwVfA" alt=""><figcaption><p>Data Explorer - Trends</p></figcaption></figure>

### Acquisitions

The "Acquisitions" section provides detailed information about each measurement taken by the sensors. It is important to note that this section is only available for dynamic sensors, such as the accelerometer and the DDS - Dynamic Displacement Sensor.

Dynamic monitoring data has a unique nature, where each event called "acquisitions" corresponds to a sampling that can vary from 30 seconds to 2 minutes. The insight graphs provided for each acquisition are the waveforms and frequency responses collected during a single sampling session by a dynamic sensor.

<figure><img src="/files/X564n6p7qydm05GyiD3i" alt=""><figcaption><p>Data Explorer - Acquisitions</p></figcaption></figure>

***

## Find and select devices

The default display format is "List," which shows a list of available sensors in the menu on the left. Alternatively, you can switch to a different display mode, "Image," by expanding the selection menu using the "Expand view" button.

{% hint style="info" %}
In Data Explorer, you can view data from only one sensor at a time.
{% endhint %}

### List view selection

To view data for a specific sensor, select it from the list on the left. You can filter by device type or search using the device's custom name or EUI.

<figure><img src="/files/Clm8J9bkSIHkATYwn185" alt=""><figcaption><p>Data Explorer - collapsed sensor view</p></figcaption></figure>

### Image view selection

To switch to the "Image" mode, which provides a spatial representation of the sensors for a more intuitive visual context, click the "Expand view" button located above the sensor list. This mode can make sensor selection easier and more immediate, especially for certain types of projects.

<figure><img src="/files/RzKxr6dPuIkPI0Kuee6C" alt=""><figcaption><p>Data Explorer - expanded sensor view</p></figcaption></figure>

***

## Data Export Feature – Historical Dataset Retrieval

The Export Data functionality in Data Explorer enables users to retrieve the entire historical dataset collected by a sensor since its activation, directly from the MyMove cloud servers.

To initiate a data export, the user can click the “Export Data” button located in the top-right corner of the Data Explorer interface. This action opens a configuration sidebar on the right, where the following export options are available:

* Filename Customization: The user can define a custom name for the exported dataset.
* Time Interval Selection: Users can specify the exact start and end timestamps for the data to be included in the export.
* Parameter Selection: All available data parameters for the selected sensor are listed. Users can select one or more parameters to include in the export. Each selected parameter corresponds to a separate column in the resulting CSV file.
* Column Ordering: Parameters can be reordered via drag and drop to define the desired column sequence in the exported CSV file.

Due to the potentially large volume of data associated with long-term monitoring, the system automatically optimizes the export by partitioning the dataset into multiple CSV files, each representing a distinct time segment (“data slots”). This ensures robust and scalable data retrieval without limitations on the requested time range.

The Export Data tool is designed for high-performance data analysis workflows and supports complete historical access for all sensor types available in Data Explorer.

<figure><img src="/files/Mcl8nep2JxdBS7Ng01dH" alt=""><figcaption><p>Export Data sidebar</p></figcaption></figure>

***

## Learn more about sensor data

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Accelerometer</strong></td><td><a href="/pages/dd510neHELziSgVBgghW">/pages/dd510neHELziSgVBgghW</a></td><td><a href="/files/ahIcvJF6gJuOLMat21aI">/files/ahIcvJF6gJuOLMat21aI</a></td></tr><tr><td><strong>Dynamic Displacement Sensor</strong></td><td><a href="/pages/y2TmqZkLlSqQykthIFmt">/pages/y2TmqZkLlSqQykthIFmt</a></td><td><a href="/files/RDi8TokBeJjBk5KR7Eic">/files/RDi8TokBeJjBk5KR7Eic</a></td></tr><tr><td><strong>Vibrometer</strong></td><td><a href="/pages/igML1YvfrVD8kXAyB4pE">/pages/igML1YvfrVD8kXAyB4pE</a></td><td><a href="/files/TkLapACYv0sJzkwgTFZw">/files/TkLapACYv0sJzkwgTFZw</a></td></tr><tr><td><strong>Tiltmeter</strong></td><td><a href="/pages/HiSO8ocXRyyIQjKluSPi">/pages/HiSO8ocXRyyIQjKluSPi</a></td><td><a href="/files/5T4o77ei6lOS33N6ozme">/files/5T4o77ei6lOS33N6ozme</a></td></tr><tr><td><strong>Environmental sensor</strong></td><td><a href="/pages/lbtjd6XlYyLAzhDmR3Jj">/pages/lbtjd6XlYyLAzhDmR3Jj</a></td><td><a href="/files/iwfQXXVY3YHMEWWfnnxX">/files/iwfQXXVY3YHMEWWfnnxX</a></td></tr><tr><td><strong>Communication node</strong></td><td><a href="/pages/0SE2jGQj9E10o1IRwc3I">/pages/0SE2jGQj9E10o1IRwc3I</a></td><td><a href="/files/sxF5IrLGG4Jv4yHWbjms">/files/sxF5IrLGG4Jv4yHWbjms</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://move-solutions.gitbook.io/untitled/mymove-manual/data-explorer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.