Tracking incorrect MD5 Checksum errors from Copernicus Data Ecosystem

[sharkinsspatial]

We have noted large numbers of incorrect MD5 checksums for Sentinel 2 products we are downloading.

As an example we downloaded the following product from the zipper endpoint 5a9eecf4-4114-46d9-a4a5-fcc023d895e4

And obtained its MD5 checksum from the OData endpoint.

The OData MD5 checksum is ba9fced9cf70360be62b5afed48395c5 while the downloaded file's actual MD5 checksum is 82ef414f463d293ab58c77c2e05d5f42

We have encountered this issue for 1000s of products over the past 2 weeks.

@freitagb has reached out directly via email to the ESA representative to try and elevate this issue but note that we will see very reduced Sentinel-2 download throughput and S30 production until this issue is addressed.

ref https://github.com/NASA-IMPACT/hls_development/issues/148