My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD01644
CWCB
>
Floodplain Documents
>
Backfile
>
1001-2000
>
FLOOD01644
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/23/2009 12:58:13 PM
Creation date
10/4/2006 10:13:51 PM
Metadata
Fields
Template:
Floodplain Documents
Designation Number
46
County
Denver
Community
Denver
Title
Flood Hazard Boundary Map - Supplementary Report, Sanderson Gulch & Weir Gulch, Denver, Colorado
Date
3/1/1975
Designation Date
7/1/1975
Floodplain - Doc Type
Floodplain Report/Masterplan
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
49
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />I <br />I <br /> <br />I <br />I <br /> <br />I <br /> <br />I <br /> <br />I <br /> <br />I <br /> <br />I <br /> <br />I <br />I <br /> <br />I <br /> <br />I <br />I <br /> <br />I <br />I <br />I <br />I <br />I <br /> <br />All computer work was completed on the company IBM 1130 Computer. <br />The computer has an 8K storage capacity which can be increased <br />to 12K with the use of disc storage units. This added capacity <br />made operation of the total model quite simple. The program <br />offers an optional amount of computer output. All hydrographs <br />were available in storage at all times and could be recalled for <br />any operation. <br /> <br />All storm hydrographs were computed on a two minute time increment. <br />This had a number of advantages. First of all, it provided for <br />a more accurate determination of the peak flow rate and time to <br />peak, as well as the computation of the total hydro graph volume. <br />Also, it provided for greater accuracy in the routing program <br />where the determination of required storage is quite important. <br />Thirdly, the two minute increment provided the ability to lag <br />hydrographs to the nearest two minutes of flow time. In urban <br />drainage, where normal storm hydrographs characteristically <br />have steep narrow peaks, the flow time increment becomes very <br />important. For most conditions, the flow time varied from 0 <br />to 16 minutes. <br /> <br />Lagging and adding the total hydrograph in the downstream direc- <br />tion provides a fairly realistic representation of the actual <br />flow condition. Ideally, the hydro graph should be attenuated <br />by recognizing channel storage. In the case of Sanderson and <br />Weir Gulches, it was felt that the existing reservoirs provide <br />storage detention to a much larger degree than channel storage <br />and the effect of channel storage wou~d be negligible in <br />comparison. The lagging effect, however, keeps the time frame <br />of the hydrograph in the proper perspective. <br /> <br />Overall, utilization of the computer model as an analytical <br />tool permitted the calculation of nearly 1,300 hydrographs, <br />as required by the contract, in a comparatively short period <br />of time. Also, the computer model offered a much greater <br />degree of flexibility. <br /> <br />HYDRO DESCRIPTION <br /> <br />As mentioned earlier, the HYDRO model directly follows the <br />Colorado Urban Hydrograph (CUHP) Procedure as outlined in Part <br />4 of the Runoff Section of the Urban Storm Drainage Criteria <br />Manual. A quick review of the CUHP indicates that this pro- <br />cedure is based on the derivation of a synthetic unit hydro- <br />graph and statistically determined rainfall information. <br />The unit hydrograph approach to storm runoff determination, <br />when historical recorded information is not available, was <br />originally developed by Sherman in 1932 and expanded upon by <br />Snyder in 1938. The unit hydrograph reflects the integrated <br />effects of basin characteristics such as area, shape, slope <br /> <br />-21- <br />
The URL can be used to link to this page
Your browser does not support the video tag.