Dear all,
I’m aware of the current reprocessing campaign and also that an increased sequence number can come from different datatakes as well as reprocessing a scene (e.g., mentioned in this recent thread). However, the following example shows a scene processed with baseline 02.14 (_0_L2A) and two versions reprocessed to baseline 05.00 (_1_L2A, _2_L2A) but with different valid_cloud_cover-flags. As far as I could see this is not an individual case but can be found frequently. I have not found any information about this and hope I’m in the right place to ask. The scenes are from Digital Earth Africa but point a Sentinel-Hub AWS bucket.
properties:
datetime: 2021-02-17T08:07:00Z
eo:cloud_cover: 12.15
sentinel:data_coverage: 100.0
sentinel:product_id: S2A_MSIL2A_20210217T074001_N0214_R092_T36JUT_20210217T101606
sentinel:sequence: 0
sentinel:valid_cloud_cover: True
properties:
datetime: 2021-02-17T08:07:00Z
eo:cloud_cover: 12.44
sentinel:boa_offset_applied: True
sentinel:data_coverage: 100.0
sentinel:processing_baseline: 05.00
sentinel:product_id: S2A_MSIL2A_20210217T074001_N0500_R092_T36JUT_20230521T115503
sentinel:sequence: 1
sentinel:valid_cloud_cover: True
properties:
datetime: 2021-02-17T08:07:00Z
eo:cloud_cover: 0.0
sentinel:boa_offset_applied: True
sentinel:data_coverage: 100.0
sentinel:processing_baseline: 05.00
sentinel:product_id: S2A_MSIL2A_20210217T074001_N0500_R092_T36JUT_20230222T050706
sentinel:sequence: 2
sentinel:valid_cloud_cover: False
