Maxar (Premium) is not Maxar's Premium layer

[rivermont]

The layer in iD listed as 'Maxar Premium Imagery' seems to be using the layer that JOSM calls Maxar Standard Imagery, which has older imagery than a different layer that JOSM has as 'Maxar Premium Imagery'.

The following vintage layers seem to match JOSM's 'Premium' and 'Standard' layers respectively, and the second also seems to match iD's Premium.

[tordans]

Offtopic @rivermont: What is the URLs to those date visualizations?

[mvexel]

@tordans (copying from Slack)

https://discover.digitalglobe.com: filter by Type-Mosaic and Line-Vivid Standard, the two results seem to be what JOSM has, at least for the area I checked

[Mahabarata]

see also #1217 and my next comment on 6 Nov 2021.

[maGIScian]

I stopped eating my sausages and mash and drinking my beer to add to this. That's how serious it is. Validators are validating tasks mapped in standard, practically remapping everything. This is happening in our projects in Mozambique and some areas of DRC...

[Jorieke]

Yes, despite the beer and sausages of @maGIScian he is right, we are encountering the same issue with for example some of our mapping projects in Mozambique. In JOSM there is no issue, you have like usually the Maxar Standard layer and the Maxar Premium layer. It is only in ID that this is an problem. In ID you have listed Maxar Premium in the background layers, but it is thus actually Maxar Standard imagery.

It looks thus that it is an issue with ID, because JOSM can do it, so I guess ID must be able to do it too?

[maGIScian]

See some background information on how this affects us at https://hotosm.slack.com/archives/C4GLC45PY/p1642582282025900

[tyrasd]

Hey all. I'm really sorry that resolving this takes longer than anticipated.

The problem is that Maxar communicated to us (@mbrzakovic) that the "Maxar Premium" layer in iD actually corresponds to the "Maxar Premium" product. I didn't want to change the layers without confirmation from Maxar, that there was indeed a mixup of the two products. Unfortunately, we didn't hear back from them when we asked for clarification shortly after this issue was raised here.

In ID you have listed Maxar Premium in the background layers, but it is thus actually Maxar Standard imagery.

Can you please tell me how you came this this conclusion? I didn't find a way to definitely rule out the (unlikely) possibility that the layer is correct in iD and just reversed on JOSM's side.

[maGIScian]

Hi Martin, I'd be happy to have a call with you to demonstrate how we came to this conclusion and how it affects us. Please email me: andries.heyns@london.msf.org and we can set up a call, even today. It's a serious issue and definitely not Premium everywhere as they say.

[Jorieke]

@tyrasd many thanks for looking into this!!

[tyrasd]

This was now fixed by Maxar. 🎉 The iD profile should now return the most recent Maxar imagery (like in JOSM). PS: I noticed that in some locations the servers still have a few of the old tiles cached, but that should resolve itself relatively soon.

[rivermont]

Can confirm that the area I had compared seems to have the newer stuff now!

[maGIScian]

Yassssssssss thank you!!! Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Will Bennett ***@***.***> Sent: Tuesday, February 8, 2022 7:05:41 PM To: openstreetmap/iD ***@***.***> Cc: Andries Heyns ***@***.***>; Mention ***@***.***> Subject: Re: [openstreetmap/iD] Maxar (Premium) is not Maxar's Premium layer (Issue #8852) CAUTION: This email originated from outside MSF. Do not click links, open attachments or provide information unless you recognise the sender and know that the content is safe..

________________________________ Can confirm that the area I had compared seems to have the newer stuff now! — Reply to this email directly, view it on GitHub<#8852 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVXHSNQZD2Y7DCZAFUQJ5NDU2FSQLANCNFSM5J635AQA>. 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>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Jorieke]

Yesss, it seems to work fine now!!
Many thanks Martin and Maxar!!

[pedrito1414]

Echoing thanks on resolving this!