You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since three/four weeks ago the Maxar Premium layer has stopped working in multiple editors- i.e. the endpoint has simply come down and is nonresponsive. Trying to investigate the cause.
Update:
There are several other reports of same. It looks like this started happening at or around June 1st 2023.
After looking around this seems to be a larger time break that previous times when the Maxar keys have been rotated. Suspect that this endpoint is gone for good. Others have filed issues with Maxar and not heard back.
“The message we received is that Maxar had to discontinue the service due to security issues. Maxar leadership have said the decision is permanent for now "until security concerns can be resolved"
Description
Since three/four weeks ago the Maxar Premium layer has stopped working in multiple editors- i.e. the endpoint has simply come down and is nonresponsive. Trying to investigate the cause.
Update:
There are several other reports of same. It looks like this started happening at or around June 1st 2023.
https://community.openstreetmap.org/t/maxar-imagery-not-working-was-maxar-is-blurred-in-id-and-other-similar-topics/100524/14
hotosm/tasking-manager#4846
Here's the original blog post announcing the sat imagery launch for OSM six years ago in May of 2017:
https://blog.maxar.com/earth-intelligence/2017/digitalglobe-satellite-imagery-launch-for-openstreetmap
Version
any/all (iD, JOSM seeing it too)
What browser are you seeing the problem on? What version are you running?
all
The OS you're using
n/a
Steps to reproduce
Simply use Maxar Premium and observe the lack of imagery. :)
The browser URL at the time you encountered the bug
n/a
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response
The text was updated successfully, but these errors were encountered: