Quickfix to inconsistent input in SafetyFactorGeoTechnic

SafetyFactorGeoTechnic implements a method for fixing on the fly inconsistent inputs such as zero values in input maps (line 140).

Maps such as Slope may have zero values as natural outputs from DEM processing: such values are phisically acceptable but are not acceptable for computational reasons.

This is why actual - Slope maps must have zero values replaced by 0.009 [==tan(0.5°)] - Soil thickness must have zero values replaced by 0.1 meters

This must be implements in a sound input check policy.. ..while now the SafetyFactorGeoTechnic.checkInputQuickfix(double[] args) has been implemented.

Suggestion is: - ask user for DEM [required] - compute Flow, Slope, Soil Thickness and Ab from it so that they satisfy: - computationally acceptable values - fixed borders (derrived maps are one cell smaller that source DEMs)

Comments (1)