---
title: Exploring Your Data
slug: kronpam-how-to-guides/exploring-your-data
description: This step-by-step guide explores data using the Reporting module, covering topics such as accessing tables, applying filters, and counting records. Learn how to group data by type and find the top 10 temperature recordings in 2015. Discover formatting opt
docTags: 
createdAt: 2022-08-18T14:06:15.000Z
---

This is the third step of creating your own report with the Reporting module.

In this section, we will explore data using example cases.

### Start exploring your data.

Click on the table name you just created in the list of available tables.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/sDv002p2ypso0jijlpSRT_image.png" size="64" width="788" height="101" position="center" showCaption="false"}

By default, you’ll be presented with a Table View.


::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/Z1hzbhTob9igE84qEnutk_image.png" size="40" width="591" height="208" position="center" showCaption="false"}

### Find how many records there are in the table.

Let’s walk through a basic query to get the count of all records in our table.

First, we’ll need to change the **Since** filter to capture the range of our data. You can use simple phrases to apply these filters, like “3 years ago”:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/ZKUSxHgzT6b2ut448iUM-_image.png" size="38" width="305" height="188" position="center" showCaption="false"}

The upper limit for time, the **Until** filter, defaults to **now**, which may or may not be what you want. Look for the **Metrics** section under the **GROUP BY** header, and start typing *Count* - you’ll see a list of metrics matching what you type:

Select the COUNT(\*) metric, then click the green **Query** button near the top of the explore:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/aH1serRvejWYRkDTpxqNv_image.png" size="34" width="693" height="220" position="center" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/KN92XJ7-ItcSiBVE6CUQ__image.png" size="26" width="254" height="97" position="center" showCaption="false"}

You’ll see your results in the table:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/kwCdgZc-jAG4UHdco9WHn_image.png" size="38" width="198" height="79" position="center" showCaption="false"}

### Count the number of records by type.

Let’s group this by the *weather\_description* field to get the count of records by the type of weather recorded by adding it to the **Group by** section:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/9jYSz8VOfb0Z8RRQ7S-PH_image.png" size="38" width="248" height="88" position="center" showCaption="false"}

And run the query:

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/ukpNeGWldsc8qmpKvb0eW_image.png)

### Find the top 10 times and places that recorded the highest temperature in 2015.

We replace *weather\_description *with* latitude, longitude,* and *measurement\_date* in the *Group by* section:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/z4T0oreC2VcMvHhRmDFwR_image.png" size="34" width="458" height="99" position="center" showCaption="false"}

And replace *COUNT(\*) with max\_\_measurement\_flag*:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/Sm90oeFfavACqwmb3k9x6_image.png" size="44" width="311" height="99" position="center" showCaption="false"}

The *max\_\_measurement\_flag* metric was created when we checked the box under **Max** and next to the *measurement\_flag* field, indicating that this field was numeric and that we wanted to find its maximum value when grouped by specific fields.

In our case, *measurement\_flag* is the value of the measurement taken, which clearly depends on the type of measurement (the researchers recorded different values for precipitation and temperature). Therefore, we must filter our query only on records where the weather\_description is equal to “Maximum temperature,” which we do in the **Filters** section at the bottom of the explore:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/EtTtIkk1BlWnp5CC4gizG_image.png" size="44" width="671" height="196" position="center" showCaption="false"}

Finally, since we only care about the top 10 measurements, we limit our results to 10 records using the **Row limit** option under the **Options** header:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/13RMGtNkgkHxwyD9x9_Op_image.png" size="42" width="224" height="89" position="center" showCaption="false"}

We click **Query** and get the following results:

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/k8ie7zw7FHxqreWHhcy6s_image.png)

In this dataset, the maximum temperature is recorded in tenths of a degree Celsius. The top value of 1370, measured in the middle of Nevada, is equal to 137 C, or roughly 278 degrees F. It’s unlikely this value was correctly recorded. We’ve already investigated some outliers with Superset, but this just scratches the surface of what we can do.

 You may want to do a couple more things with this measure:

- The default formatting shows values like 1.37k, which may be difficult for some users to read. You may likely want to see the full, comma-separated value. You can change the formatting of any measure by editing its config *(***Edit Table Config** > **List Sql Metric** > **Edit Metric **> **D3Format**)
- Moreover, you may want to see the temperature measurements in plain degrees C, not tenths of a degree. Or you may want to convert the temperature to degrees Fahrenheit. You can change the SQL that gets executed against the database, baking the logic into the measure itself (**Edit Table Config** > **List Sql Metric** > **Edit Metric** > **SQL Expression**)

### Change the visualization of the data.

Let’s create a better visualization of this data and add it to a dashboard. We change the Chart Type to **Distribution - Bar Chart**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/cUPWsUVwVlG30Ai5ljo9V_image.png" size="38" width="493" height="178" position="center" showCaption="false"}

Our filter on Maximum temperature measurements was retained, but the query and formatting options are dependent on the chart type, so you’ll have to set the values again:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/uZPq9rmc6n36XBqPKnCr-_image.png" size="70" width="511" height="340" position="center" showCaption="false"}

You should note the extensive formatting options for this chart: the ability to set axis labels, margins, ticks, etc. To make the data presentable to a broad audience, you’ll want to apply many of these to slices that end up in dashboards. For now, though, we run our query and get the following chart:


![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/Z4M7_iUFQDzv2A9S-9GbL_image.png)