Sentinel-s2 products path


We are generating paths in our catalog system to download the sentinel2 products.
We noticed some discrepancy between l1c and l2a products indexation in the buckets, when the “datatake sensing start” and the “Product Discriminator” dates differs.

For instance, this sentinel-s2-l2a product S2A_MSIL2A_20220508T235741_N0400_R030_T56LRL_20220509T092817 is available at s3://sentinel-s2-l2a/tiles/56/L/RL/2022/5/9/0/ (indexed with its “datatake sensing start” date)

This sentinel-s2-l1c product S2B_MSIL1C_20220508T224529_N0400_R101_T01UFU_20220509T002617 is available at s3://sentinel-s2-l1c/tiles/1/U/FU/2022/5/8/0/ (indexed with its “Product Discriminator” date)

Is this something predictable, and do you know why there is a difference ?

Thank you in advance

Tiles are stored in the folder based on tile sensing time, see metadata for first tile
<SENSING_TIME metadataLevel="Standard">2022-05-09T00:00:14.167691Z</SENSING_TIME>

and for second tile
<SENSING_TIME metadataLevel="Standard">2022-05-08T22:51:21.367747Z</SENSING_TIME>

That said, if you check the corresponding product’s meta-data, for first product, you will see:


It seems there is some consistency as one would expect tile’s sensing time to be within the product start/stop time…
This is unfortunately beyond or knowledge and we recommend to contact Copernicus Support about it.


1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.