Hi Oleg,

there is no out-of-the-box solution. But several workarounds are possible (listed below in order of human effort).

1. Re-run L2 processing, but use DO_ATMO = FALSE. Delete all TOA files afterwards

2. Calculate the distance from QAI

• extract cloud, cloud shadow and snow from the QAI files (force-qai-inflate might help)
• compute the distance (gdal_proximity seems to implement this). -distunits GEO and -maxdist 32767 seems to be compatible with the DST computed internally in FORCE. Note that I did not test this solution.

3. You will end up with artefacts across tile boundaries when using approach 2. You should evaluate whether this is a problem. A solution might be to compute mosaics of the QAI files first (force-mosaic), use approach 2 on the mosaic, then re-cube the files afterwards (force-cube). This would even be more exact than the original FORCE solution because it would get rid of artefacts between MGRS tiles, too.

Cheers,
David