HTTP 403 for images from services.digitalglobe.com

[cschotte]

URL

https://services.digitalglobe.com/earthservice/tmsaccess/tms/1.0.0/DigitalGlobe:ImageryTileService@EPSG:3857@jpg/18/155211/132645.jpg?connectId=ca613e76-811f-46e7-9e1d-84f6795441c2

How to reproduce the issue?

Open project https://tasks.hotosm.org/projects/11966 and start mapping. You will see a black map without any images. HTTP 403 error for all images from services.digitalglobe.com

Screenshot(s) or anything else?

No response

Which deployed environments do you see the issue in?

Released version at openstreetmap.org/edit

What version numbers does this issue effect?

2.2.1.1

Which browsers are you seeing this problem on?

Microsoft Edge

[arch0345]

Unfortunately we no longer have access to Maxar imagery, see #9710

[nickrsan]

Yes, you'll want to contact the manager of that HOT project to have them update the imagery source in use, unfortunately. They've configured a custom imagery source, so it's not an issue with iD, but with the task configuration. I submitted a report of bad imagery on a task within the broader task there already, but if you have any relation with them, you might communicate that directly.

Closing as duplicate.

[cschotte]

[like] Clemens Schotte reacted to your message:

…

________________________________ From: Nick Santos ***@***.***> Sent: Tuesday, October 24, 2023 6:19:05 PM To: openstreetmap/iD ***@***.***> Cc: Author ***@***.***> Subject: Re: [openstreetmap/iD] HTTP 403 for images from services.digitalglobe.com (Issue #9947) Yes, you'll want to contact the manager of that HOT project to have them update the imagery source in use, unfortunately. They've configured a custom imagery source, so it's not an issue with iD, but with the task configuration. I submitted a report of bad imagery on a task within the broader task there already, but if you have any relation with them, you might communicate that directly. Closing as duplicate. — Reply to this email directly, view it on GitHub<#9947 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACDMVFATZ6XQERF3YORVMYDYBABBVBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIYTKOBQGI4DMMBVGKSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRTGUZDQOJXHE3DEMVENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWTTIOJYHEZDGNMCUR2HS4DFUVUXG43VMWSXMYLMOVS2UMJZGUZDCNZUHAZDFAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDCNJYGAZDQNRQGUZIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTKMRYHE3TSNRSGKTXI4TJM5TWK4VGMNZGKYLUMU>. You are receiving this email because you authored the thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.