Forum Discussion
Bing map not plotting points correctly on Firefox?
It appears this is a rate limit issue with either the Virtualearth.net API or Bing Maps itself. There is information on both sites relating to imposed limits, but it's hard to tell which ones would apply to a Power BI report viewed over the web where the integration with Bing Maps is completely out of our hands - this should perhaps be something users are made more aware of?
I solved the problem by using an external tool to get the latitude/longitude for each postcode in my dataset and use those rather than postcodes.
Map plots properly accross all browers, every time, using lat/lng.
Some progress - I tried publishing the file again and now Chrome and Safari seem fine, however Firefox (on three separate computers now, one Windows and two OSX - two of which have never logged in to powerbi.com before and had Firefox installed on them this morning specifically to test this) still shows a blank map.
Using Chrome's Developer tools I can see the following in the console - repeated many times, for the URL below (I have removed the key!) . Is this a rate limit for geocoding postcodes? I know you can only do up to 1000 in Power BI Desktop, but this is only tryng to plot around 440.
https://dev.virtualearth.net/REST/v1/Locations/multigeocode?culture=en-GB&output=json&key=xxxx
- {authenticationResultCode: "ValidCredentials",…}
- authenticationResultCode: "ValidCredentials"
- brandLogoUri: "http://dev.virtualearth.net/Branding/logo_powered_by.png"
- copyright: "Copyright © 2018 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation."
- errorDetails: ["Your request could not be completed because of too many requests."]
- resourceSets: []
- statusCode: 429
- statusDescription: "Too Many Requests"
- traceId: "f0912bd32ebc45e88f4061ce74a3c2ea|DB40210730|7.7.0.0"
It appears this is a rate limit issue with either the Virtualearth.net API or Bing Maps itself. There is information on both sites relating to imposed limits, but it's hard to tell which ones would apply to a Power BI report viewed over the web where the integration with Bing Maps is completely out of our hands - this should perhaps be something users are made more aware of?
I solved the problem by using an external tool to get the latitude/longitude for each postcode in my dataset and use those rather than postcodes.
Map plots properly accross all browers, every time, using lat/lng.