Classification error where tiles are overlapped
Hello,
I am working with this config files (L3A_2018.cfg) with a Sentinel-2 L3A temporal series.
At the end, I get a classification in which the pixels located where the tiles overlap / on the edge of the tiles are misclassified. Rather than being considered as noData, they are classified as "normal" pixels.
The problem must come upstream of the mosaicking step because each separate classified tile is cut according to the boundaries of the shapefiles exported in the "envelope" folder.
Is there a parameter to add to avoid this error?
Thanks
Edited by Elodie-F