Hi all,
I’ve been using sen2three recently via command line and it’s having troubles in processing recent 2018 images. It seems to be a simple parsing error out of different PSD version. I also confirmed the schemas in rep_info folder is different to 2017 images after being processed by sen2cor 2.5.5. The 2017 images shows PSD 12 for the Datastrip schema while the 2018 images shows PSD 14. I can smoothly process 2017 images.
The error says:
Any thoughts on this?
Thanks!
-Nando
Hello,
we are facing the same error when we try to process 2018 images with sen2three 1.1.0. Changing the MAX_TIME Value didn’t help. Processing 2017 images work perfectly fine.
is it possible that sen2three cannot process 2018 Images at all?
Or maybe there is just something wrong with my schema-file?
Thank you.
-Marius
I have had the same issue. Has anyone identified a fix for this?
Same issue here. Using all 2018 imagery.
I recall on another thread that using imagery post 2016 does not work I think due to the file naming change. Too bad. I wanted to use this in my project.
I do get a L3 file but obviously no product
Using this date range:
<L3_Synthesis>
<Min_Time>2018-01-01T00:00:00Z</Min_Time>
<Max_Time>2018-12-31T23:59:59Z</Max_Time>
Or this one (thought I’d experiment in my limited way) :
<L3_Synthesis>
<Min_Time>2017-01-01T00:00:00Z</Min_Time>
<Max_Time>2018-12-31T23:59:59Z</Max_Time>
If I don’t delete the L3 folder I then receive this error on a subsequent run:
AttributeError: ‘bool’ object has no attribute ‘getchildren’
Full L3_GIPP settings:
<?xml version="1.0" encoding="UTF-8"?><Common_Section>
<Log_Level>INFO</Log_Level>
<Display_Data>true</Display_Data>
<Target_Directory>DEFAULT</Target_Directory>
<PSD_Scheme PSD_Version=“13” PSD_Reference=“S2-PDGS-TAS-DI-PSD-V13.1_Schema”>
<UP_Scheme_2A>S2_User_Product_Level-2A_Metadata.xsd</UP_Scheme_2A>
<UP_Scheme_3>S2_User_Product_Level-3_Metadata.xsd</UP_Scheme_3>
<Tile_Scheme_2A>S2_PDI_Level-2A_Tile_Metadata.xsd</Tile_Scheme_2A>
<Tile_Scheme_3>S2_PDI_Level-3_Tile_Metadata.xsd</Tile_Scheme_3>
<DS_Scheme_2A>S2_PDI_Level-2A_Datastrip_Metadata.xsd</DS_Scheme_2A>
<DS_Scheme_3>S2_PDI_Level-3_Datastrip_Metadata.xsd</DS_Scheme_3>
</PSD_Scheme>
<PSD_Scheme PSD_Version=“14” PSD_Reference=“S2-PDGS-TAS-DI-PSD-V14.2_Schema”>
<UP_Scheme_2A>S2_User_Product_Level-2A_Metadata.xsd</UP_Scheme_2A>
<UP_Scheme_3>S2_User_Product_Level-3_Metadata.xsd</UP_Scheme_3>
<Tile_Scheme_2A>S2_PDI_Level-2A_Tile_Metadata.xsd</Tile_Scheme_2A>
<Tile_Scheme_3>S2_PDI_Level-3_Tile_Metadata.xsd</Tile_Scheme_3>
<DS_Scheme_2A>S2_PDI_Level-2A_Datastrip_Metadata.xsd</DS_Scheme_2A>
<DS_Scheme_3>S2_PDI_Level-3_Datastrip_Metadata.xsd</DS_Scheme_3>
</PSD_Scheme>
<GIPP_Scheme>L3_GIPP.xsd</GIPP_Scheme>
</Common_Section>
<L3_Synthesis>
<Min_Time>2017-01-01T00:00:00Z</Min_Time>
<Max_Time>2018-12-31T23:59:59Z</Max_Time>
<Tile_Filter>*</Tile_Filter>
RADIOMETRIC_QUALITY
<Radiometric_Preference> AEROSOL_OPTICAL_THICKNESS</Radiometric_Preference>
<Cirrus_Removal>true</Cirrus_Removal>
<Shadow_Removal>true</Shadow_Removal>
<Snow_Removal>false</Snow_Removal>
<Max_Cloud_Probability>0.0</Max_Cloud_Probability>
<Max_Invalid_Pixels_Percentage>0.0</Max_Invalid_Pixels_Percentage>
<Max_Aerosol_Optical_Thickness>0.0</Max_Aerosol_Optical_Thickness>
<Max_Solar_Zenith_Angle>0.0</Max_Solar_Zenith_Angle>
<Median_Filter>3</Median_Filter>
</L3_Synthesis>
<NO_DATA>0</NO_DATA>
<SATURATED_DEFECTIVE>1</SATURATED_DEFECTIVE>
<DARK_FEATURES>2</DARK_FEATURES>
<CLOUD_SHADOWS>3</CLOUD_SHADOWS>
4
<NOT_VEGETATED>5</NOT_VEGETATED>
6
7
<MEDIUM_PROBA_CLOUDS>8</MEDIUM_PROBA_CLOUDS>
<HIGH_PROBA_CLOUDS>9</HIGH_PROBA_CLOUDS>
<THIN_CIRRUS>10</THIN_CIRRUS>
<SNOW_ICE>11</SNOW_ICE>
<URBAN_AREAS>12</URBAN_AREAS>
</Level-03_Ground_Image_Processing_Parameter>
I am having the same problem.
Has there been any solution proposed?
Or alternatively is there an official bug/error reporting portal we can log this issue with?
Considering it is now 2019 it would be nice to have the tool working on recent imagery.
