Wrong cloud_cover metadata for granules

[piyushrpt]

We are noticing that some of the metadata.json files have eo:cloud_cover value set to 0.0 when the original granule_metadata.xml files indicate that CLOUDY_PIXEL_PERCENTAGE is nearly 100. Probably due to a possible truncation issue?

An example:

s3://sentinel-cogs/sentinel-s2-l2a-cogs/17/T/NM/2023/7/S2B_17TNM_20230715_0_L2A/S2B_17TNM_20230715_0_L2A.json

The corresponding properties in the xml file from scihub are:

{
'CLOUDY_PIXEL_OVER_LAND_PERCENTAGE': 99.998772, 
'CLOUDY_PIXEL_PERCENTAGE': 99.997038, 
'CLOUD_SHADOW_PERCENTAGE': 0.001284, 
'HIGH_PROBA_CLOUDS_PERCENTAGE': 98.281348, 
'MEDIUM_PROBA_CLOUDS_PERCENTAGE': 1.691321, 
'NODATA_PIXEL_PERCENTAGE': 34.623703, 
 'aws_stac_id': 'S2B_17TNM_20230715_0_L2A'
}

[piyushrpt]

A quick check over the last 2 days shows that there are over 11000 images published in the last 2 days alone where the eo:cloud_cover is 0.0 and CLOUDY_PIXEL_PERCENTAGE is greater than 10. A large number of these have cloud pixel percentage greater than 90 but the range seems to be all over the place.

[gadomski]

This should be fixed by the ongoing reprocessing. After reprocessing is complete, we will check to ensure this is resolved.