BLOGS BY TOPIC▼
BLOGS BY AUTHOR▼
BLOGS BY YEAR▼
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.
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 ...
Use this tool to turn your visualisation into a map.
... with the following field settings:
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:
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:
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.