Would it be correct to say that the products with processing baseline 04.00 should be considered a part of Collection 1? Or will Collection 1 be marked differently somehow?
A presentation at LPS last week said that C1 processing will start in June 2022, but processing baseline 04.00 has already been deployed since earlier this year, so I want to be clear about when exactly C1 starts.
I got this answer from support:
The baseline configuration of the reprocessing leading to Collection-1 will be further enhanced from that of the current PB04.00. PB04.00 should hence not be considered as the final configuration of Collection-1, the final Collection-1 settings will be communicated as soon as settled.
It can as well be assumed that all products generated with PB 04.00 since January, or earlier on with former baselines will all be reprocessed.
Hi Simon,
thanks for sharing this information. That’s good to know.
Collection-1 was mentioned in https://sentinel.esa.int/web/sentinel/-/sentinel-2-processing-baseline-05-deployment-on-06-december-1/1.5?redirect=%2Fweb%2Fsentinel%2Fmissions%2Fsentinel-2.
The new L1C files, starting December 6th, seem to have a processing baseline of N0509 (or 5.09, I think). Although if I read that article correctly, I think the Collection-1 files will have a baseline of 5.00.
Either way, does anyone know what the output baseline is for sen2cor 2.10.1 with these new files? It seems to be output 04.00. It emits a warning, and notes that 04.00 is being used:
Product versions > 14.9 are not implemented yet.
Version 14.9 will be used by default, but warnings during validation might occur.
Sen2Cor. Version: 02.10.01, created: 2021.12.13, supporting Level-1C product version 14.2 - 14.9 started ...
Product version: 14.9
Operation mode: TOOLBOX
Processing baseline: 04.00
The output filenames have the string 0400 and the metadata files reference 04.00:
MTD_MSIL2A.xml
10: <PROCESSING_BASELINE>04.00</PROCESSING_BASELINE>
I’m not sure if that’s “correct”, or whether we should wait for a new sen2cor release to properly process these new files.
Sen2cor 2.11 was released Sen2Cor v2.11 – STEP. It mentions
- Support of the input L1C products generated with the current (14.9) and previous (14.6, 14.5 and 14.2) Products Specification Document
Hello
PB 05.09 was introduced into the nominal (i.e. NRT) processing chain on the 6th of December. It is **not ** Collection 1. Collection 1 (processed with Processing Baseline 05.00) is the reprocessing of the whole data catalogue stretching back to the start of the S2A mission, and is being done by the S2RS service.
Cheers
Jan
Sen2Cor 2.11 still apparently outputs 04.00.
Product versions > 14.9 are not implemented yet.
Version 14.9 will be used by default, but warnings during validation might occur.
Sen2Cor. Version: 02.11.00, created: 2022.10.20, supporting Level-1C product version 14.2 - 14.9 started ...
Product version: 14.9
Operation mode: TOOLBOX
Processing baseline: 04.00
That’s given an input scene that I think is at 05.09: S2B_MSIL1C_20230111T121649_N0509_R066_T27PTS_20230111T140100.SAFE.
But either way, apparently this new 05.09 data (or 04.00?) is not the same as Collection 1.
@bdpg
Can you comment, please? @TomAugspurger notes the 02.11 outputs PB04.00. Is this congfigurable to make it 05.09?
Thanks in advance
Jan
First, processing baseline 5.09 generated by the operational processing starting December 6th is very near to the reprocessing (processing baseline 5.00). Both are based on an identical Sen2Cor version which is also identical to the Sen2Cor provided to the users. Differences exist only in the DEM usage. Operational processing keeps at processing with Copernicus DEM 90m whereas reprocessing is using Copernicus DEM 30m.
There are clear differences between processing baseline 4.00 and 5.0x most of all in evolutions of product format.
I cannot reproduce the output example given above. How it was generated? Which operating system, command line processing was used, …? User processing (toolbox-mode) should always generate processing baseline 99.99 and neither 4.00 or 5.0x. Therefore I don’t see that it can and should be configured.
I checked the same L1C-product and get both on Windows and Linux-Systems (command line processing) the following output:
Product versions > 14.9 are not implemented yet.
Version 14.9 will be used by default, but warnings during validation might occur.
Sen2Cor. Version: 02.11.00, created: 2022.10.20, supporting Level-1C product version 14.2 - 14.9 started …
Product version: 14.9
Operation mode: TOOLBOX
Processing baseline: 99.99
Progress[%]: 0.00 : Generating datastrip metadata
L2A datastrip successfully generated
Differences exist only in the DEM usage. Operational processing keeps at processing with Copernicus DEM 90m whereas reprocessing is using Copernicus DEM 30m.
Makes sense, thanks.
I cannot reproduce the output example given above. How it was generated?
We call sen2cor within a larger process. I’ll try to get a self-contained example of what we’re doing into a dockerfile sometime today or tomorrow.
Actually… I think I just spotted the issue, and of course it’s on my end. We’re explicitly setting --processing_baseline 04.00 when we invoke sen2cor. I’ll read through the user manual and will experiment with some options to see what’s appropriate.
Hi, I have encountered the same problem. I am using a Windows 10 and Sen2.10 ( 2.11 ) to process 2023 S2 products, but there is a warning:
Product versions > 14.9 are not implemented yet.
Version 14.9 will be used by default, but warnings during validation might occur.
Sen2Cor. Version: 02.11.00, created: 2022.10.20, supporting Level-1C product version 14.2 - 14.9 started …
Product version: 14.9
Operation mode: TOOLBOX
Processing baseline: 04.00
How did you handle this issue? How to obtain an effective processor?