Errors Sen2Cor 2.4 via snappy: metadata does not exist & java property is not recognized

Optical Toolbox sen2cor
#1

Hi all,
I am running Sen2Cor 2.4 through python using:
…
input_image = snappy.ProductIO.readProduct(file)
L2A_image = snappy.GPF.createProduct(‘Sen2Cor’, parameters, input_image)
…

Here are the error logs that I get:
…
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.s2.ortho.S2OrthoProductReaderPlugIn: Building product reader - EPSG:32632
WARNING: org.esa.s2tbx.dataio.metadata.GenericXmlMetadata: Metadata: the path to element [metadata_level] does not exist
WARNING: org.esa.s2tbx.dataio.metadata.GenericXmlMetadata: Metadata: the path to element [granuleidentifier] does not exist
WARNING: org.esa.s2tbx.dataio.metadata.GenericXmlMetadata: Metadata: the path to element [bandid] does not exist
INFO: org.hsqldb.persist.Logger: dataFileCache open start
Warning: org.apache.xerces.parsers.SAXParser: Property ‘http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit’ is not recognized.
Compiler warnings:Compiler warnings:

WARNING: ‘org.apache.xerces.jaxp.SAXParserImpl: Property ‘http://javax.xml.XMLConstants/property/accessExternalDTD’ is not recognized.’ WARNING: ‘org.apache.xerces.jaxp.SAXParserImpl: Property ‘http://javax.xml.XMLConstants/property/accessExternalDTD’ is not recognized.’

INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterOp: Executing tool ‘Sen2Cor’ with command line: ‘C:\Users\user.snap\auxdata\Sen2Cor-2.4.0-win64\L2A_Process.bat --resolution 10 C:\t\S2A_MSIL1C_20170127T102301_N0204_R065_T32TNS_20170127T102258.SAFE --GIP_L2A C:\Users\user\documents\sen2cor\L2A-GIPP-custom.xml’
INFO: org.esa.snap.core.gpf.operators.tooladapter.DefaultOutputConsumer: Sentinel-2 Level 2A Processor (Sen2Cor), 2.4.0, created: 2017.06.05 started …
INFO: org.esa.snap.core.gpf.operators.tooladapter.DefaultOutputConsumer: selected resolution is 10 m.
…
Then the process seems to proceed alright but not always. Any idea where these might be coming from and why they seem to not affect the result?

#2

any reason why you don’t use sen2cor version 2.5.5?

#3

For consistency. I have already produced a lot of work based on the 2.4 conversions. At least going from 2.3 to 2.4 the results were not 1 to 1 with the same settings. Is changing to 2.5.5 going to solve the problem?

#4

I don’t know. But you could test for one scene to see if the error persists. Generally, working with the latest version should avoid most of the issues.