Estimated delay time in providing L2A data on AWS-S3


#1

Hi, I’m need to how much delay is being added on average in processing of L1C data and to final L2A data available in S3 bucket (which will be available starting this july 2018).

Also, I’ve estimated an average delay of 12-48 hours in processing of L1C data after it is captured.

Thanks,
Gurman


#2

The major part of a “delay” is a matter of processing at ESA ground stations so you should revert this question to them (support@copernicus.eu). If you get a response, we would certainly appreciate a follow up info.

Based on our non-scientific observations cca. 50% L1C products are available on SciHub 6-12 hours after acquisition , cca 25% up to 24 hours and the rest later.
For L2A I think that ESA is waiting for most of the orbit to be processed (to L1C), before it starts with Sen2Cor. I read somewhere that delay is about 2 days after L1C.

After data is available on SciHub, it takes on average 1 hour to copy it to AWS (in/after the periods of SciHub problems this time may be prolonged)


#3

I took some time and analysed cca. 26.000 L1C products ingested in last 2 days. The results are unfortunately far from what we were hoping for:

(cca)
12.000 products have been ingested in under 12 hours
-1.600 in 12-24 hours
-5.100 in 1-2 days
-3.600 in 2-3 days
-700 in 3-4 days
-2.200 more than 4 days (these are probably related to https://scihub.copernicus.eu/news/News00320)


#4

Thank you for the reply, I can’t open the link somehow (system is not allowing me). Would you know how these product scales (xx.00 formats) is aligned with level 1C to 2A transfer process.


#5

Not sure I understand your question. The chart above is for L1C products only and it shows, how long it takes from when satellite acquires the image to when the image is available in SciHub.