[X] I have checked that this issue has not already been reported.
[X] I have checked that this bug exists on the latest version of HydroMT-Wflow.
Reproducible Example
For example, some stations in the GRDC database have very small values for uparea (<30 km2). Using the snap_uparea method, these gauges will be snapped to the pixel with the closest value for uparea, but that does not mean that it is a river pixel
Current behaviour
Gauges with small upareas are correctly snapped, but this will give an error when running wflow when you request river discharge as output.
Desired behaviour
As this feature is mostly relevant for discharge stations (I think), it would better if only the river cells are considered to snap towards. Alternatively, gauges with an uparea smaller than the uparea used in setup_rivers could also be ignored. But I think the first option is better.
HydroMT-Wflow version checks
Reproducible Example
For example, some stations in the GRDC database have very small values for uparea (<30 km2). Using the snap_uparea method, these gauges will be snapped to the pixel with the closest value for uparea, but that does not mean that it is a river pixel
Current behaviour
Gauges with small upareas are correctly snapped, but this will give an error when running wflow when you request river discharge as output.
Desired behaviour
As this feature is mostly relevant for discharge stations (I think), it would better if only the river cells are considered to snap towards. Alternatively, gauges with an uparea smaller than the uparea used in
setup_riverscould also be ignored. But I think the first option is better.Additional context
No response