stuart.middleton on 21 Oct 2015 15:03:38
From our own experiences and comments we've found generally on the web, it appears that Power BI does now work correctly with longitude and latitude.
Power BI should be able to take longitude, latitude, and a value as the only required inputs for a map. However, it requires a location and (as far as we can tell) completely ignores anything in the longitude and latitude fields. Indeed, if we enter both a longitude and latitude to a map already using locations, a working map stops working.
Note that we have validated the accuracy of the longitude and latitude values, and we’ve set them to the appropriate data types.
- Comments (3)
RE: Better use of longitude and latitude in maps
Possibly this fix has led to a weird error message. “To display latitude and longitude pairs, set the aggregate for Latitude and Longitude to Don’t summarize. See details”. Hard to imagine what to do in this case.
RE: Better use of longitude and latitude in maps
The issue that you are describing is due to PowerBI automatically trying to SUM the Latitude & Longitudes. This is why values show up in Antartica as mentioned by Ben.
There is a quick and simple workaround. Create a new column and concatenate Lat & Long with a ',' between the 2 values. Hence, it should look like "-27.523456,153.576647".
Put this concatenated value in Location when you design your PowerBI map. It will now work perfectly.
RE: Better use of longitude and latitude in maps
We are facing a similar issue. We have validated lat/long values and have set them correctly, but the map does not populate correctly with some values showing up in Antarctica!