Laserfiche WebLink
<br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br /> <br />inference from this oplnlon is that the flows downstream of the confluence are <br />also in question and possibly too high. The primary value of these numbers is, <br />therefore, the consistency they provide on regulatory issues. These values and <br />that of the paleohydrologic evaluation are judged to have the additional value <br />of defining the upper end of the envelope encompassing the field of reasonable <br />flow values. <br /> <br />The streamflow statistical analysis, for all three gaging stations, both with and <br />without approximate values for the 1935 flood, is distinguished by the absence <br />of high flow events. This is believed to be an inaccurate representation of the <br />true distribution of flood events. This is partly indicated by the wide variance <br />in numbers bracketing the 95% confidence interval (i.e. low confidence) of <br />projected la-year and lOa-year flows. The only reliable value developed from the <br />statistical analysis is the mean. The projected flows for the la-year and more <br />infrequent events are judged to be unreliable and probably represent the bottom <br />end of the envelope encompassing the field of reasonable flow values. In <br />addition, paleohydrologic evidence confirms that high intensity, high peak flood <br />events have occurred historically in most individual basins, but not on a basis <br />which is widespread enough to cause major flooding on Fountain Creek. The issue <br />as to whether or not extreme meteorologic events can occur over a large enough <br />area of highly variable topography remains, unfortunately, unresolved. <br /> <br />Regional analyses by Muller (unpublished) and Pitlick (1988) and individual <br />experienced extreme hydrologic events occur within the envelope of values between <br />the current adopted flow values and the statistically generated values plotted <br />on Figures 4.8-1, 4.8-2 and 4.9-1. <br /> <br />Design storm methods in general are used either where gaging information is <br />inadequate and/or where theoretical future flood peaks caused by urbanization are <br />of interest. Typically they are not used, without cal ibration to "real" events, <br />to determine design flow values for major drainageways such as Fountain Creek. <br />Unfortunately, the absence of known frequency flood values places a significant <br />limitation on performing such calibration accurately. Without calibration, <br />design storm methods characteristically produce flows which are on the high side <br />of the true values (in those rare instances where comparisons can confidently be <br />made). This is due to the tendency of hydrologists to estimate (even by a small <br />amount) the values of individual parameters "on the conservative side" to <br />compensate for inadequate i nformat i on or other uncerta i nt i es. Some of these <br />design storm methods even have this conservatism embedded in the methods in order <br />to produce numbers "on the safe side. II There are many opportunities in the <br />choice of variable values and algorithms (storm pattern, rainfall amounts, ground <br />cover interpretation, eN estimation, routing parameters, antecedent moisture <br />assumption, soils interpretation, etc.) for this uncertainty to become compounded <br />with the result that numbers on the high side are produced. Even with these <br />limitations, a design storm method (the ses unit graph procedure in this case), <br />can produce reasonabl e results if parameter val ues are chosen with object ive care <br />(including varying values for varying frequencies), reflecting as accurately as <br />possible the physical realities involved. This was the approach taken herein. <br />Figure 4.9-2 graphically shows the design future peak flows for the study reach <br />by stream distance according to discharge. <br /> <br />4.0-27 <br /> <br />. <br />. <br />. <br />. <br />. <br /> <br />I <br />I <br /> <br />I <br />I <br />I <br />I <br />I <br />I <br /> <br />I <br />I <br />I <br />