On to week 3 of the 30 Day Map Challenge. It's day 15 and the theme is "Fire".
Classical Elements ¾: Focus on energy, light, or transformation. Map heat, wildfires, energy consumption, population density at night, or volcanic activity.
I've taken a slightly different angle on this one and used another real-world scenario that should be reusable in many different use cases. In this example we're mapping which properties can be reached within a certain time by fire engines.
I've entered the Addresses for the fire stations for the fire and rescue services in Avon, Dorset and Wiltshire, Gloucestershire, Hereford and Worcestershire, Oxfordshire, South Wales and Warwickshire and used Azure Maps' geocoding API to return the longitude and latitude for each.
Then for each of these I've used the Azure Maps Route Range API to return the drive time in 5 to 30 minute increments, specifying the dimensions of a fire engine. These drive times are then stored in the Power BI dataset, along with rows for each fire station location.
Then in Icon Map Slicer, I display each fire station as a circle, colour coded based on the staffing type. A data label displays the fire station name. Underneath we have the WKT drive time isochrones, colour coded by duration. A range slicer determines the range of isochrones to display.
Then to provide more context, I've used our new vector layer filtering capability arriving in Icon Map Slicer v1.0.0.4 next month, to show 3D buildings and roads from Ordnance Survey's Open Zoomstack layers.
Here's the report in action:
You can download the .pbix file here. Don't forget you'll need to use the 1.0.0.4 version of Icon Map Slicer following the instructions to put Power BI in developer mode.