Forum Discussion
I dont see bubble in the map
Hi, today I don´t see the bubble in the map of my dashboard, plesase help, thanks.
8 Replies
- cfosund
Helper I
Hi
I was able to fix it by changing the data type for the long/lat columns from Data type: Text to:
Data type: Decimal Number
Format: General
I re-uploaded the PBIX file and the Bing maps are now working 👍- asavadiansFrequent Visitor
I tried this but it's still not loading. I am even getting this error in Desktop.
- juliobn7Regular Visitor
New warning message: one or more latitude longitude values are not valid, the latitude values must be between -90 and 90 and the longitude values between -180 and 180, however all my lat and long values are fine. please help
- juliobn7Regular Visitor
The bubbles if they appear in the power bi desktop map but not in the service, I hope it is solved soon.
- v-yulgu-msft
Microsoft Employee
Hi juliobn7,
In my test, the map bubbles displayed well in service.
Have you re-published the report to service for a test?
Which type of map visual did you use? Did all bubbles disappear on service or just some certain points? Besides, please test to create map visual directly on service to see whether issue persists.
Regards,
Yuliana Gu
- cfosund
Helper I
Same issue here, maps with coordinates works perfectly in the Power BI Desktop.
But today in the Power BI service, none of the maps works.
I have tried to republish the report, but the error persists."latitude values should be between -90 and 90, and longitude values should be between -180 and 180."
- zulkifilNew Member
I was able to fix it by changing the data type for the long/lat columns from Data type: Text to:
Data type: Decimal Number
Format: Decimal Number
I re-uploaded the PBIX file and the Bing maps are now working.you can check on below link. it is working now.
https://www.seerab.com/visualization-of-honour-crimes-in-punjab-pakistan/
- asavadiansFrequent Visitor
I tried this, along with multiple different settings, and I'm still getting the error message saying my lat/long values are not valid. I saw on another post someone saying this is a bug with Power BI service, although I've been getting this error in the Desktop version as well.