productInfo.json -> "footprint" lat and lon flipped since Jan 17 for products in aws bucket s3://sentinel-s1-l1c

Sentinel@AWS
1

Hi,

we are using the s3 hosted sentinel1 data (Sentinel-1 - Registry of Open Data on AWS) and noticed that the information in productInfo.json changed. It looks like the latitude and longitude for “footprint” is flipped. This seems to have changed around the 17th Jan.

Example from before the 17 Jan 2025:
s3://sentinel-s1-l1c/GRD/2025/1/15/IW/DV/S1A_IW_GRDH_1SDV_20250115T062347_20250115T062412_057451_0712C4_E0BE/productInfo.json

Example from after 17 Jan 2025 (similar area):
s3://sentinel-s1-l1c/GRD/2025/1/22/IW/DV/S1A_IW_GRDH_1SDV_20250122T061527_20250122T061552_057553_0716D9_1294//productInfo.json

For the example from 15 Jan 2025 the “footprint” is

“footprint” : {
“type” : “MultiPolygon”,
“coordinates” : [ [ [ [ -0.780311005213395, 50.99433175009266 ], …
}
which is fine but for the example from 22 Jan 2025 the “foortprint” is

“footprint” : {
“type” : “MultiPolygon”,
“coordinates” : [ [ [ [ 51.35694663714535, 1.3993235336160679 ], …
}

which is between Somalia and the Seychelles. When I flip lat and lon the footprint is correct.

Is this a conscious change or a bug somewhere?

Any pointers appreciated!

1 Like
3

Hi @gmilcinski and @matt.ballard,

I wanted to confirm that this issue is still ongoing and is causing significant disruptions to our downstream services.

Can you confirm if the root cause has been identified and whether a fix is planned? Specifically:

  • Will the resolution involve republishing the corrected data with a new SNS notification, or will the metadata be silently corrected?
  • What is the expected timeline for resolving this issue?
  • Can you provide a list of affected assets (the Product IDs should be sufficient)?

This is critical for our operations, so any updates or ETA would be greatly appreciated.

Thank you for your help,
Jona

4

Hi Jona,
as far as I know, there was no proactive change done from our side, so I am guessing this has to do something with the change in the undelying product.

Note that the replication of data to AWS has been taken over by another entity. We have let them know about this thread.

As a general note - we recommend you use Sentinel Hub, and this forum is focused to support of it.

Best,
Grega

5

Hi Grega,
Thanks for the SUPER fast reply!

Just wanted to let you know that on the data details page on the AWS Registry shared above (Sentinel-1 - Registry of Open Data on AWS), Sinergise is still listed as the manager, and this forum is listed as the place to post questions/concerns/issues.

Really appreciate that you’ve let the replication entity know about the issue. If you share who they are, then I can get in contact with them directly (and stop bothering you) to help give them details of the issue, and receive details of the fix.

Cheers,
Jona

6

UPDATE

I followed up with Planet and they found the bug in their code. Here is their most recent reply as of today:

Thank you for your patience. I have been informed that the fix for this issue has been deployed. All newly ingested Sentinel-1 products should now contain correct geometries in productInfo.json. The backlog of products with incorrect geometries is planned to be handled sometime next week. We will keep you updated.

@a2tirb for visibility.

7

Thanks a lot for the update @jona !