Sen2cor for S2B

We are doing S2B -quality check but the current version of sen2cor 2.3.1 cannot process S2B_L1C products. It gives next errors:

L1C user product directory must match the following mask: S2A_MSIL1C*.SAFE
but is: S2B_MSIL1C_20170602T095029_N0205_R079_T32QNK_20170602T100342.SAFE


Sentinel-2 Level 2A Processor (Sen2Cor), 2.3.1, created: 2017.02.03 started …
Syntax error in metadata, see report file for details.
Parsing error:
Schema file: L2A_CAL_AC_GIPP.xsd
Details: Element ‘wavelength’, attribute ‘c0’: ‘’ is not a valid value of the local atomic type. (line 0)
Syntax error in metadata, see report file for details.
Parsing error:
Schema file: L2A_GIPP.xsd
Details: Element ‘PSD_Scheme’, attribute ‘PSD_Version’: [facet ‘length’] The value ‘’ has a length of ‘0’; this differs from the allowed length of ‘2’. (line 0)

Sen2Cor 2.4.0 which will have support for L2B Level1C Products is currently under testing and will be published within the next days.

1 Like

For the first error it helped me to simply change the top folder name to S2A_MSI*

1 Like


Access to Sentinel-2B Level-1C products is opened, is there an estimated date for sen2cor 2.4.0 release?



We also only had problems with the first error. By changing the file name to S2A we were able to process S2B with sen2cor 2.3.1. Of course that is not an ideal solution but as a intermediate hotfix it works.

1 Like

Hi all,

Sen2Cor 2.4.0 Supporting S2B is now released.
Berst regards,
Sen2Cor Development Team.

Hi all,

I still get the same error.

Anyone has any idea?

Kind regards.

which version of sen2cor are you using?

I am using 2.4.0.

The aforementioned error still exists when running Sen2cor from SNAP
The trick of changing the B to A in the *.SAFE directory works fine.

Sen2Cor Developers, look at this please:
2A and 2B satellites have different wavelengths, especially Band 8.
Would you like to answer a question, please? How does Sen2Cor work with different satellites? Is it correct to compare images from the different satellites to each other? Should we use any additional coefficients or something for the preparation of the time-series based on both satellites?

According to the link above they also changed band of 2A vehicle. Sen2Cor 2.4.0. was based on the old look up tables.
So, since the tables have changed, when should we expect the updated version of Sen2Cor to work with?