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.
Geocoding (setting the correct localisation for data)
To convince Power BI Desktop that regions are in the UK, add a calculated column to the region table:
Create a calculated column adding the letters UK onto each region (I'm assuming a similar tactic would work for any other country).
You could then use the new UkRegion column as a Location field:
We're using the UkRegion to identify where sales took place.
This gives better results - but they're still wrong:
At least all sales are taking place in the UK, but the North-West region should be centred over Manchester (as one example).
What's happening is that we're relying on Power BI Desktop to decide where the North-West is. It would be a better idea to position data exactly, and to do that we'll use the fact that we know the postcode of each shopping centre in which a transaction took place, and from this can derive the latitude and longitude setting.