Retried today with v. 19096, now Bing loads fine.
Some people still have issues with the Bing imagery. Yesterday on a small mapathon for half of the people it loaded fine and then for other half did not. Today it is not working again for some users.
The day of the suspension of Bing Maps services arrived and my ApiKey died, although apparently Map style URLs still work.
Hello,
We are using Bing Maps API within a Power App, I was getting this error below. I spun up a new api key and that fixed it for 3 days. Now the same error is happening. Anyone know why??
How did you fix?
The creator of the app will likely have been bombarded with messages from Microsoft over the last year or so, about the move from Bing to Azure maps.
Thereâs a discussion (from an OSM imagery perspective) here.
The creator of the bing maps api key would be the one who received this email. They probably never read it since itâs an IT service accountâŚso annoying.
I take advantage of the article about the launch of the new version of ohsome as a reference to how Bing Aerial has been used in openstreetmap.
Absolute and relative number of map edits in OpenStreetMap using Bing Imagery (2020-01-01 â 2025-06-15):
Absolute and relative number of monthly map edits in OpenStreetMap using Bing Imagery:
So what it the current state of the issue?
Somehow Bing Aerial Imagery layer works for me in iD, OsmAnd and Every Door, but not in JOSM. What is going on?
Works for me.
When you run Josm from e.g. a shell prompt or command line, youâll see information about what is happening in the background. When you tick the box for Bing imagery, what happens?
Huh, this is weird. Right now Bing imagery layer in Josm works for me, but it showed âError: Attribution is not loaded yetâ errors when I posted my previous comment. And I am pretty sure it was not working for weeks, that is why I had to learn to use iD.
Is it possible that Josm uses daily rate limited API key and each time when I tried to use this layer daily limited was already depleted?
Unlikely, since iD and JOSM have been using the same Bing API key for some time.
Possibly the bing.attribution.xml file has not been refreshing for a while and then it did. Thatâs the file you can delete (or rename if you like to go save) and then JOSM goes out to fetch a new one. Anyway, I have these red messages when starting up JOSM and loading the imagery⌠few seconds at most and then my snail intertube is able to get fresh tiles.
Iâve been able to use Bing fine recently, with it taking a second to âpop inâ over initial âattribution not loadedâ tiles just as @SekeRob described. @Self-Perfection are you running the latest version of JOSM? Not sure if thatâll fix it but itâs the first thing that comes to mind.
Right now Bing imagery works for for me in JOSM.
I do not remember exactly, but probably I needed to delete ~/.cache/JOSM/bing.attribution.xml once to make it work again, or maybe it just suddenly started to work.
In case anyone still have issues I suggest to stop JOSM, delete ~/.cache/JOSM/bing.attribution.xml and start JOSM again.



