In Dashboard Week Day 2, the challenge is to visualise dataset from London Fire Brigade. The dataset comes from In this challenge, the main activities include data understanding and creating dashboard.

Data Understanding

Generally, the provided dataset for Dashboard Week Day 2 is clean. Furthermore, the data in every row appears to be consistent.

Creating dashboard

The objective of the created dashboard is to explore the occurrence of fire-related incidents in London. Metrics which are used to evaluate occurrence of fire-related incidents and their impact include number of incidents, total calls and total notional cost.

Map chart

Map chart was created to determine the part(s) of London that have/has high incident numbers or fire brigade calls or cost. The dashboard creation mainly involved map charts and dashboard actions (set and filter actions). In this dashboard, there are 2 types of map charts, that include Automatic Map and Density Map which are shown in figures 1 and 2, respectively.

Figure 1. Automatic map chart to show total incidents by boroughs

Figure 2. Density map chart to show total incidents by wards

In terms of usage, automatic map chart is used to single out specific region(s), while density map chart is applied to see cluster or region with specific density.

An additional tip when creating map chart is to put the relevant fields to the details to ensure that the viewers can look at their desired details from the map.

Set Action

In this dashboard, set action is used to show highlights and trends of incident numbers based on specific incident group(s). Furthermore, the set action will enable separation of incident group(s) across different year which can be drilled down to the 12 months in the corresponding year. Figure 3 and 4 show how set action in this dashboard was configured and works, respectively.

Figure 3. Set action configuration

Figure 4. Set action for different incident group(s) and drilldown to different months in a year

Filter Action

The last part of the dashboard involves filter action. Filter action was used to filter property type(s) based on selected property category(s). Configuration and application of filter action are shown in figure 5 and 6, respectively.

Figure 5. Filter action configuration

Figure 6. Filter action application

As an additional note, ‘Exclude all values’ was selected in Clearing the selection tab in figure 5 as viewers may want the chart about property type to not show when no property category(s) is(are) selected.

Kristiadi Uisan
Author: Kristiadi Uisan