-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Maxar Imagery #9710
Comments
This only happens when OSM's token for Maxar expires, they are usually pretty quick to release an update to rotate the token, so no point removing it. Though it seems they are taking their time to rotate the token this time. |
Part of osmlab/editor-layer-index#1889 . |
More information on what's going on is available here: https://community.openstreetmap.org/t/maxar-imagery-not-working-was-maxar-is-blurred-in-id-and-other-similar-topics/100524/28 Removal may make sense (Maxar says this is "permanent"), but probably worth keeping as a temporary removal on iD's end. |
Sadly, our attempts to restore the service have not been successful yet. There is still an ongoing joint effort of the OSMF and HOT on this, but from what I can tell it's probably not going to be a quick process, unfortunately. 😒 I have, for now, removed the Maxar Premium layer from the background selection list. |
Maxar aerial imagery has been dead for a while now, see openstreetmap/iD#9710 for more.
Maxar aerial imagery has been dead for a while now, see openstreetmap/iD#9710 for more.
Maxar aerial imagery has been dead for a while now, see openstreetmap/iD#9710 for more.
URL
No response
How to reproduce the issue?
Maxar imagery is now only useful for mapping outlines of continents.
Any closer and it is just a blur, worldwide.
So if it cannot be fixed, might as well remove it.
It has seen better days, #7787 .
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
No response
What version numbers does this issue effect?
No response
Which browsers are you seeing this problem on?
No response
The text was updated successfully, but these errors were encountered: