Change L2CoarseResolution on the fly
Following the issue 81 on GitHub (https://github.com/CNES/MAJA/issues/81) and ensuing investigations on the quality of the cloud mask with L2CoarseResolution set to 120m vs 240m, I ended-up with a few questions (all the following refer to Maja 4.2.x).
If no DTM is found by startmaja
for a given tile, it creates one at 120m resolution, while dtmcreation
defaults to 240m. Both tools create a DTM DBL.DIR without mention of its resolution (that I could find, besides file size). Is there any other way to switch from 120m to 240m than to overwrite this DBL.DIR sub-directory ?
I could find in install/maja/4.2.3/etc/conf/user/MAJAUserConfig_SENTINEL2.xml
a line setting <L2CoarseResolution>
to 240. Is this UserConfig bypassed by startmaja, and if so, is it the expected behavior ?
There are some good reasons for end-users to keep using L2CoarseResolution at 240 meters, at least until we at CESBIO better tune the L2COMM settings to overcome some scaling effects that, for some cases, degrade the S2 cloud mask quality @120m. But what would be the best practice to do this ?
- prepare 240m resolution DTMs using dtmcreation tool, then call startmaja ?
- have startmaja to comply with the L2CoarseResolution setting in the UserConf file ?
- or add a
--L2CoarseResolution
option to startmaja that would check for preexisting DTM at the requested resolution, and if not found prepare it (besides a preexisting DTM @120m) ?
I guess this will lead to a DM.
Thanks,
Jerome