Forum Discussion
Microsoft Employee[PowerBI Dashboard]: Geographic coordinates not being used, instead an aggregate is done
Hi,
data comes from an ASA job which has the following query:
Hub.Payload.BandData.latitude / 10000000.0 AS Band_latitude,
Hub.Payload.BandData.longitude / 10000000.0 AS Band_longitude,
e.g. data is converted from
latitude":527479216,"longitude":128325396,
to 52,7479216,"longitude":12,8325396
which displays correctly when using bing (http://binged.it/1Q0gaVX)
For some reason the stream to powerbi does not show that as a location and will display the following:
When dragging the geo data to the placeholders in the properties of the map, it builds aggregates (in this case here average by default) Anyone knows what the problem is here ?
3 Replies
Try telling Power BI it's a location.
Under the 'Data' tab there's a 'Modelling' ribbon. Select the long and lat columns and change the Data Category to longitude and lattitude respectively. In addition, you should change the "Default summarization" setting for each column to "Do Not Summarize".
Finally, once you have used Long and Lat in the Map visualisation you will still need to drop something in the 'Location' field. This should be some kind of reference field as it will appear in the hover box on the map but you can use anything.
HTH.
Sacha
JensSuessmeyerThere is no such thing in the dashboard that you mentioned (or I was to blind to see it). The data comes out of a ASA job, so maybe this is a difference here. What do you mean by "Data tab" and model ribon ?
-Jens
- Hello,
Sorry, I did notice you mention it was an ASA job then forgot by the time I saw your screenshot.
I was explaining how to do it though Power BI Desktop which is not an option with the output from ASA.
You might struggle. You could try casting the long and lat in your ASA query so it's not a number. You could also try concatenating both fields into a single column (space or comma separator) and dropping that field straight into location but I'm not convinced either will work.
An alternative (but one that would remove the real-time element) would be to land the data in SQL or somewhere and import into Power BI Desktop so you can properly control data types.
Apologies for getting you hopes up.
Sacha
