Laserfiche WebLink
Western Dam Engineering <br /> Technical Note <br /> <br /> <br /> May 2017 <br /> <br /> <br />13 <br />classification and can be defined with <br />return periods ranging from a 50-year <br />event to extreme events with return <br />periods less frequent than a 1,000-year <br />event (like the probable maximum flood <br />[PMF]). <br />Step 2: Develop the IDF storm hyetograph <br /> Estimate a depth-duration-frequency <br />relationship (from local precipitation <br />gages, gage-adjusted radar rainfall data, <br />NOAA Atlases, Hydrometeorological <br />Reports [HMRs], Site-Specific or Statewide <br />Probable Maximum Precipitation [PMP] <br />studies, etc.) <br /> Estimate areal reductions (if applicable). <br /> Estimate elevation reductions (if <br />applicable). <br /> Estimate spatial and temporal <br />distributions. <br />Step 3: Estimate watershed loss parameters and <br />excess precipitation <br /> The most pertinent watershed loss <br />parameters (as they relate to dam safety) <br />are surface retention (initial losses) and <br />infiltration. <br /> Some common methodologies to estimate <br />these loss parameters include: Green and <br />Ampt, Natural Resources Conservation <br />Service (NRCS) Curve Number, and Initial <br />and Constant Loss. <br />Step 4: Transform watershed excess precipitation to <br />discharge hydrographs <br /> Excess precipitation (i.e., runoff) is <br />translated to discharge hydrographs using <br />a translation methodology—the unit <br />hydrograph is generally the most preferred <br />and is based on physical watershed <br />properties and associated flood travel <br />times. <br /> Some common methodologies to estimate <br />unit hydrographs include: <br />o Watershed-Specific Unit Hydrographs <br />– Use watershed precipitation and <br />stream discharge data. <br />o Synthetic Unit Hydrographs – Where <br />insufficient watershed data is <br />available, common methodologies <br />include those of the U.S. Bureau of <br />Reclamation, NRCS, Clark, and the U. S. <br />Geological Survey (USGS). <br />Step 5: Estimate watershed runoff volumes and <br />hydrographs <br /> Use a hydrologic model, like HEC-HMS, and <br />the data estimated in the previous steps to <br />estimate peak runoff rates and volumes. <br /> If applicable, combine and route sub- <br />watershed hydrographs through the <br />watershed drainage network <br />watercourses. Some common watercourse <br />routing methodologies include: Kinematic <br />Wave, Muskingum-Cunge, Lag, and <br />Modified Puls. <br />So that’s runoff in a nutshell—the reader is <br />encouraged to reference the WDETN runoff article [3] <br />for a more detailed discussion. But how do we know if <br />the flood modeling runoff results are reasonable and <br />reliable? This is where a variety of calibration and <br />validation techniques and methodologies can be <br />applied to justify and refine results and the input <br />parameters that contribute to them. <br />Watershed Model Calibrations <br />General Discussion and Overview <br />Model calibrations comprise adjustments to model <br />input watershed parameters such that model results <br />closely approximate observed or predicted data. <br />Watershed parameters are initially estimated and <br />adopted based on the methodologies and techniques <br />discussed in the previous runoff review section (as well <br />as in the WDETN runoff article [3]). Although these <br />methodologies are reflective of industry standards and <br />state of the practice, they typically require <br />adjustments to produce reasonably accurate results. <br /> <br />Figure 2 presents an example in which the modeled <br />runoff volume, time to peak discharge, and the peak <br />discharge do not reasonably replicate measured <br />discharge data, which could indicate that the model <br />results are inaccurate and/or questionable. To justify <br />selection of adopted hydrologic model input <br />parameters and verify associated model runoff results, <br />model calibrations and validations are necessary.