Abstract
Water depths and velocities predicted inside urban areas during severe storms are traditionally the final result of a chain of hydrologic and hydraulic models. The use of a single model embedding all the components of the rainfall–runoff transformation, including the flux concentration in the river network, can reduce the subjectivity and, as a consequence, the final uncertainty of the computed water depths and velocities. In the model construction, a crucial issue is the management of the topographic data. The information given by a Digital Elevation Model (DEM) available on a regular grid, as well as all the other elevation data provided by single points or contour lines, allow the creation of a Triangulated Irregular Network (TIN) based unstructured digital terrain model, which provides the spatial discretization for both the hydraulic and the hydrologic models. The procedure is split into four steps: (1) correction of the elevation z* measured in the nodes of a preliminary network connecting the edges with all the DEM cell centers; (2) the selection of a suitable hydrographic network where at least one edge of each node has a strictly descending elevation, (3) the generation of the computational mesh, whose edges include all the edges of the hydrographic network and also other lines following internal boundaries provided by roads or other infrastructures, and (4) the estimation of the elevation of the nodes of the computational mesh. A suitable rainfall–runoff transformation model is finally applied to each cell of the identified computational mesh. The proposed methodology is applied to the Sovara stream basin, in central Italy, for two flood events—one is used for parameter calibration and the other one for validation purpose. The comparison between the simulated and the observed flooded areas for the validation flood event shows a good reconstruction of the urban flooding.
Highlights
The design of hydraulic infrastructures, like sewers or culverts, and the flood hazard maps delineation are based on the prediction of the rainfall–runoff process occurring inside a catchment basin for a given return time period
The traditional approach splits the process into three different steps: (1) the rainfall–runoff transformation, differentiating the total rain into net rain plus infiltration and evaporation, (2) the concentration of the net rain in the hydrographic network and its propagation up to the boundary of the flooded area, (3) the propagation of the fluxes entering the domain of the flooded area
Section 2.1) that, starting from Digital Elevation Model (DEM), make a correction to the topographical data by removing sinks and peaks, identifying a hydrographic network through which the runoff is formed and routed, and include singularities given by infrastructures
Summary
The design of hydraulic infrastructures, like sewers or culverts, and the flood hazard maps delineation are based on the prediction of the rainfall–runoff process occurring inside a catchment basin for a given return time period. The traditional approach splits the process into three different steps: (1) the rainfall–runoff transformation, differentiating the total rain into net rain plus infiltration and evaporation, (2) the concentration of the net rain in the hydrographic network and its propagation up to the boundary of the flooded area, (3) the propagation of the fluxes entering the domain of the flooded area
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
