Sen2cor: Level-2A meteadata error

hm1u16 · April 20, 2020, 2:37pm

Dear all,

I am trying to run Sen2cor (version 2.8.0) on the following scene:
S2A_MSIL1C_20180101T105441_N0206_R051_T30SXJ_20200412T035827.SAFE
and the following error message is occuring:

Schema file: S2-PDGS-TAS-DI-PSD-V14.5_Schema\S2_User_Product_Level-2A_Metadata.xsd
Details: Element ‘Aux_List’, attribute ‘productLevel’: [facet ‘enumeration’] The value ‘Level-2Ap’ is not an element of the set {‘Level-0’, ‘Level-1A’, ‘Level-1B’, ‘Level-1C’, ‘Level-2A’}"

Is this issue occuring because of an issue with the scene (as it is happening for quite a few scenes) or with my version of sen2cor?

ABraun · April 20, 2020, 3:32pm

Level-2Ap is a special (and quite rare) product type which was published only for a short time before the actual operation

Seems like sen2cor does not like such products. Please check if there is another product from the same date which was not processed like this (a ‘real’ L1C).

hm1u16 · April 20, 2020, 4:18pm

So will Sen2cor 2.8 struggle with all products produced before March 2018 over Europe.
Also how can i tell if a product will generate a level-2Ap product from the L1C metadata?

ABraun · April 20, 2020, 6:02pm

depending on where you download the images, you can set the product level as a filter.

hm1u16 · April 21, 2020, 10:05am

Hi ABraun, I tried running the processor on a different scene and it looks like it has generated successfully however the file name has changed from the normal output.

S2A_MSIL1C_20200409T112111_N0209_R037_T30UWB_20200409T132421.SAFE
S2A_MSIL2A_20200409T112111_N9999_R037_T30UWB_20200421T092959.SAFE

As you can see the processing baseline number appears to have changed substantially. Is this an issue i should expect to see?

ABraun · April 21, 2020, 11:27am

puh, I am not sure abut this. Maybe one of the sen2cor specialists can answer.

marujore · April 24, 2020, 5:28pm

@hm1u16
According to: Sen2Cor-02.08.00-Linux64 generates output with different naming convention (*_N9999_*)

“is not a bug, but a way to identify products generated in stand-alone mode”

and according to: Sentinel-2 L2A Processing Baseline number incorrect after running sen2cor
“to keep the actual processing baseline you need to set it manually with the --processing_baseline argument”

Jan · April 25, 2020, 1:29pm

Yes.

99.99 is the default. There is an option in the command line to change it, I believe.

Cheers

Jan