2020
DOI: 10.1016/j.envsoft.2020.104623
|View full text |Cite
|
Sign up to set email alerts
|

HydroDS: Data services in support of physically based, distributed hydrological models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
9
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 22 publications
(9 citation statements)
references
References 35 publications
0
9
0
Order By: Relevance
“…At present, there are two main reverse flow routing methods: One is the hydrological method, which simulates the hydrological cycle process by establishing a lumped or distributed hydrological model (Lewis et al, 2018;Ehlers et al, 2019;Gichamo et al, 2020). The other is the hydrodynamic method, which simulates flood wave routing by building one-dimensional (1D), two-dimensional (2D) and even three-dimensional (3D) hydrodynamic models (Fleischmann et al, 2019;Wing et al, 2019;Haque et al, 2021).…”
Section: Introductionmentioning
confidence: 99%
“…At present, there are two main reverse flow routing methods: One is the hydrological method, which simulates the hydrological cycle process by establishing a lumped or distributed hydrological model (Lewis et al, 2018;Ehlers et al, 2019;Gichamo et al, 2020). The other is the hydrodynamic method, which simulates flood wave routing by building one-dimensional (1D), two-dimensional (2D) and even three-dimensional (3D) hydrodynamic models (Fleischmann et al, 2019;Wing et al, 2019;Haque et al, 2021).…”
Section: Introductionmentioning
confidence: 99%
“…Model-specific steps would be to convert the resulting information (i.e., which pixels/land classes are present per model element) to the specific format a model requires (e.g., storing the most common land class per model element as a value in a netCDF file which the model reads during initialization), and, if necessary, perform some form of data transformation to connect land class data to model parameter values or settings (e.g., by defining a lookup table that contains parameter values for each land cover type). Community-wide efficiency gains are possible if workflows distinguish between model-agnostic and model-specific steps and enable straightforward re-use of the workflow for model-agnostic steps (see also Essawy et al, 2016;Gichamo et al, 2020, who make this argument in the context of webbased model configuration tools).…”
Section: Introductionmentioning
confidence: 99%
“…Model‐specific steps would be to convert the resulting information (i.e., which pixels/land classes are present per model element) to the specific format a model requires (e.g., storing the most common land class per model element as a value in a netCDF file which the model reads during initialization), and, if necessary, perform some form of data transformation to connect land class data to model parameter values or settings (e.g., by defining a lookup table that contains parameter values for each land cover type). Community‐wide efficiency gains are possible if workflows distinguish between model‐agnostic and model‐specific steps and enable straightforward reuse of the workflow for model‐agnostic steps (see also Essawy et al., 2016; Gichamo et al., 2020, who make this argument in the context of web‐based model configuration tools).…”
Section: Introductionmentioning
confidence: 99%