Indices are not in ascending order in MSK_DETFOO

Optical Toolbox
#1

Since November 2018 Indices are not in ascending order with the feature indices in in some of the MSK_DETFOOMSK_DETFOO_B02_.gml.txt (769.6 KB)
Normaly the MSK_DETFOO gml starts in footprint 3 and ends in footprint 8 (3,4,5,6,7,8). In this gml footprint sequence is 3,4,8,5,7,6.
I found the following products with this particularity:
T29SND_20181106
T29SND_20181111
T29SND_20181116
T29SND_20181121
T29SND_20181126
I only found this happening in November 2018.
This particularity returns a error in MACCS Software Version : 5.1.5
Pedro

vns::Plugin::ERROR: Sentinel2L1ImageFileReader(0x1572850): Sentinel2L1ImageFileReaderBase::GetDetFooIndexShift: The detector indices are not in ascending order or do not have a constant shift with the feature indices in the MSK_DETFOO /mnt/archive/demmaccs_tmp/2369/29SND/S2B_MSIL1C_20181111T112309_N0207_R037_T29SND_20181111T132603.SAFE/GRANULE/L1C_T29SND_A008786_20181111T112308/…/…/GRANULE/L1C_T29SND_A008786_20181111T112308/QI_DATA/MSK_DETFOO_B02.gml ! [vnsSentinel2L1ImageFileReaderBase.txx:GetDetFooIndexShift:1394]

1 Like
#2

Did you ever find a solution to this? I’m trying to use the MACCS processor in SNAP and cannot process any imagery newer than October 2018.

#3

The successor to MACCS, MAJA, is able to process these products. Note, however, that it’s not compatible with MACCS, as it uses a different set of processing parameters and output format.