the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
To what extent does river routing matter in hydrological modeling?
Nicolás Cortés-Salazar
Nicolás Vásquez
Naoki Mizukami
Pablo Mendoza
Ximena Vargas
Abstract. Spatially-distributed hydrology and land surface models are typically applied in combination with river routing schemes that convert instantaneous runoff into streamflow. Nevertheless, the development of such schemes has been somehow disconnected from hydrologic model calibration research, although both seek to achieve more realistic streamflow simulations. In this paper, we seek to bridge this gap to understand the extent to which the configuration of routing schemes affects hydrologic model calibration results in water resources applications. To this end, we configure the Variable Infiltration Capacity (VIC) model, coupled with the mizuRoute routing model in the Cautín River basin (2770 km2), Chile. We use the Latin Hypercube Sampling (LHS) method to generate 3500 different VIC model parameters sets, for which basin-averaged runoff estimates are obtained directly (no routing case), and subsequently compared against outputs from four routing schemes (Unit Hydrograph, Lagrangian Kinematic Wave, Muskingum-Cunge and Diffusive Wave) applied with five different routing time steps (1, 3, 6, 12 and 24 hours). The results show that incorporating routing schemes may alter streamflow simulations at sub-daily, daily and even monthly time scales. The maximum Kling-Gupta Efficiency (KGE) obtained for daily streamflow increases from 0.73 (no routing) to 0.82 (for the best scheme), and such improvements do not depend on the routing time step. Moreover, the optimal parameter sets may differ depending on the routing scheme configuration, affecting the baseflow contribution to total runoff. Including routing models decreases streamflow values in frequency curves and lowers the segment with high discharge values in the flow duration curve (compared to the case without routing). More generally, the results presented here highlight the potential impacts of river routing implementations on water resources applications that involve hydrologic models and, in particular, parameter calibration.
Nicolás Cortés-Salazar et al.
Status: final response (author comments only)
-
RC1: 'Comment on hess-2022-338', Anonymous Referee #1, 02 Nov 2022
The authors conducted a very comprehensive sensitivity analyses of the effects of adding an additional river routing model with various schemes to a hydrological model. The publication shows promise as a great reference work for model experiment setup. In general, the publication is well written and the arguments for conducting the study are clear. The decisions made regarding the methods are well-argued (with the exception of 1) and the results are valuable for the hydrologic community. The limitation of this study are well described. It is understandable given the scope of the study and the data requirements that the authors evaluated a single catchment. For future research, I am eager to discover how the results of this study would be different in a more gentle sloping catchment or for various catchment sizes (e.g using CAMELS-CH Alvarez-Garreton et al., 2018).
That being said, the publications needs some extra work. The main points that need attention are argumentation for hydrological model aggregation, the structure of text and figures, additional reflection on the meaning of study results, and the archiving of code and data.
Major comments:
Temporal aggregation of hydrological model results
In section 3.3 the authors state that for each parameter set the VIC model is run at hourly time-steps and the results are temporally aggregated to various coarser time-steps. In my opinion this is an assumption that there are no non-linear processes in time within the hydrological models. The necessity for this assumption is clear as it results in a clean model experiment. However, the authors should more clearly state this assumption and reflect on this in section 5.1 (last paragraph) and 5.2. I’m curious to read the authors response.
Structure of text
The authors conducted a lot of analyses which to their credit lead to an abundance of methodology steps and results. This makes section 3.5 difficult to read and therefore it needs restructuring. I suggest to use numbering to make the steps more clear even if this disrupts the flow of the text. What might also help the reader is a model run results matrix in the form of a Table that uses the same numbering. This makes it clearer for the reader what results can be expected for each type of model run configuration.
Structure of figures
There are issues with the presentation of the results in the figures. Overall the image quality (dpi) per figure needs to be higher. The colours used to represent the individual routing schemes are inconsistent, please check all figures.
Figure 1: It is difficult to find the catchment on the left panel (1a). Outlining the catchment in red and using a softer tone for the country would help. The colours for elevation bands in 1b are difficult to distinguish, similar issue with the sub-basins in 1c.
Figure 2: Increase image quality.
Figure 3: Highlighting the horizontal axes in red would help find the period of the zoom boxes.
Figure 5: Colours are difficult to distinguish, suggest using the same colors for each scheme as in Figure 3. The vertical axes of each column varies, ticks for KGE are in steps of 0.2 while those of NSE are 0.4. This makes it nearly impossible to assess the relative differences in objective functions. I suggest using the same tick sizes with the exception of NSElog.
Figure 6: There is almost no reference to the different basin areas that are shown using the horizontal axis. It would make the figure a lot clearer if only the 2770 basin area was shown and the individual schemes were plotted next to each other. I suggest placing the results for the other basin areas in the appendix.
Figure 7: Similar to Figure 6 this figure is difficult to read. The total width of the horizontal axis does not add information, therefore I suggest to make the ticks smaller.
Figure 8: Increase the image quality. I suggest to make a separate table for the objective function results.
Reflection on the meaning of study results
The discussion section 5.1 can be extended by reflecting more on the implications of results. For example, we understand what is happening to the hydrological model in the absence of river routing. Compensation through baseflow and no considerable change in precipitation, evapotranspiration and runoff partitioning. What is missing is, what the implication are for users and why it is important to get these parts right in hydrological model setups. This is also the case for the results in 4.4. In addition, the selection of objective-function is discussed but there is no discussion on multi-objective calibration and how these might affect the results. There is reflection needed on the relevance of the differences in objective-function values. What does a difference of xx KGE mean?
Data
The authors state “The codes used in this study are available from the corresponding authors upon reasonable request”. What does reasonable mean?
The Copernicus data policy (https://publications.copernicus.org/services/data_policy.html) states "In addition, data sets, model code, video supplements, video abstracts, International Geo Sample Numbers, and other digital assets should be linked to the article through DOIs in the assets tab."
In the spirit of open-science I strongly encourage the authors to do so. I leave it up to the editor to determine whether this is a requirement for publication.
Minor comments:
Refrain from using acronyms in figure captions. The style of figure captions is inconsistent, e.g. use of “:”, or ”;”, or “,”
Lines 71-72: SWAT model is missing a reference.
Lines 76 -80: Very long sentence, needs restructuring.
Line 93: remove “apparently”
Lines 251 – 254: This is a bold claim that I would remove as it does not add value to speculate.
Line 349: “MC approach”, change to machine learning approach.
Personal dislike of the use of the word “indeed” throughout the publication.
Citation: https://doi.org/10.5194/hess-2022-338-RC1 - AC1: 'Reply on RC1', Pablo Mendoza, 15 Feb 2023
-
RC2: 'Comment on hess-2022-338', Anonymous Referee #2, 16 Dec 2022
I have finished my review of the paper “To what extent does river routing matter in hydrological modeling”, by Cortés-Salazar et al., submitted to HESS. This generally well-written paper attempts to examine the influence of routing algorithm and time step on model performance using subsets of 3500 different runoff regimes generated using the VIC hydrological model. Very mild differences were found between algorithm and time step choices, with one exception: where routing was not simulated, the performance was consistently poor relative to models which simulate routing. Unfortunately, this is not a very compelling result.
While the approach was rigorous in the sense that it compiled data from thousands of model simulations, it suffers from a number of critical methodological issues. I discuss a few of these major issues below:
- Routing is most influential on peak magnitude and timing of large events; both of these are poorly captured by integrated hydrograph metrics such as KGE and NSE. Peak flow differences after calibrating the routing models would be a much more useful metric for evaluating routing model performance. By using integrated measures such as KGE, the critical differences between routing algorithms are not discernable (as seen in nearly all of the reported results).
- Each of the figures in the report are reporting ALL of the output from the simulations, regardless of whether it is important or interpretable or worthy of interpretation. For instance, figure 5 reports KGE, NSE, and NSE of log transformed flows for all 3500 simulations with multiple timesteps, multiple routing schemes. In addition to the only interpretable result from this figure is that no routing is outperformed by routing, there is little utility in comparing NSE values of 0.2-0.3 (the approximate median of these simulations) -differences in NSE below about 0.5 are nearly arbitrary in that a hydrograph with an NSE of 0.2 may not be visibly preferable to an NSE of 0.05. The only feature of this plot referred to in the text was the maximum metric value. Why not simply report that?
- Critically, because the parameters of the VIC model are arbitrary, the comparisons of even the best models are in effect the results of Monte Carlo calibration, the least efficient optimization approach. Comparing the ‘best’ models when these are not rigorously determined to be the actual best for each algorithm (rather than a sampling error) is problematic. For this comparison to be rigorous, I don’t see how to do this without simultaneous calibration of routing and land surface parameters, an issue the authors acknowledge in section 5.2.
- In practice, the routing parameters (such as Manning’s n) would be calibrated in conjunction with VIC model parameters, likely further diminishing any incremental performance differences between the routing models.
- The fundamental results discussed here are obvious without the testing herein. Routing is better than no routing. Low flows are not as impacted by routing differences. Parameter compensation occurs in hydrological models. Routing impacts are not visible when averaged over a monthly time step. Models with instantaneous routing (i.e., no routing) have higher flows. As is, I do not see an additional contribution from this work beyond that which exists in the literature.
It is for the above reasons that I must recommend rejection.
Citation: https://doi.org/10.5194/hess-2022-338-RC2 - AC2: 'Reply on RC2', Pablo Mendoza, 15 Feb 2023
Nicolás Cortés-Salazar et al.
Nicolás Cortés-Salazar et al.
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 623 | 186 | 13 | 822 | 4 | 3 |
- HTML: 623
- PDF: 186
- XML: 13
- Total: 822
- BibTeX: 4
- EndNote: 3
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1