Some ideas for how to map data in Power BI Desktop
Part two of a five-part series of blogs

Anyone who has tried to get a meaningful non-US map out of Power BI Desktop will know that it's often not straightforward! This blog shows you how to overcome some of the issues, including geocoding data, getting latitude and longitude settings and changing cross filter settings in relationships.

  1. Techniques for creating maps in Power BI Desktop
  2. Starting the map (this blog)
  3. Geocoding (setting the correct localisation for data)
  4. Obtaining latitude and longitude data
  5. Using latitude and longitude data to create a map

Posted by Andy Brown on 08 June 2017

You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

Starting the map

A reasonable first step would be to create a map ...

The map tool

Use this tool to turn your visualisation into a map.

 

... with the following field settings:

Fields for map

The map is showing total sales quantity by region location, broken down by animal type - which is exactly what we want to do.

 

Unfortunately our regions are a bit imprecise:

List of regions

Regions 1, 3 and 9 should be easy to pin down to the UK, but most of the others could be anywhere.

 

To say the least, Bing (the Microsoft mapping tool used by Power BI Desktop) doesn't make a very good guess:

World map

Our UK sales have just gone global!

As a first step, we could try geocoding the data, to persuade the software that (for example) North mean the North of England - which is what we'll do in the next part of this blog.

This blog has 0 threads Add post