My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD00608
CWCB
>
Floodplain Documents
>
Backfile
>
1-1000
>
FLOOD00608
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/23/2009 1:21:39 PM
Creation date
10/4/2006 9:23:39 PM
Metadata
Fields
Template:
Floodplain Documents
Designation Number
516
County
Denver
Community
Denver
Title
Flood Insurance Study - Denver, CO, Volume I
Date
3/1/1996
Designation Date
5/1/2000
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.
/
73
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 />Peak discharges for Cherry Creek were previously determined as part <br />of the July 1976 UDFCD Flood Hazard Area Delineation report for <br />Cherry Creek (Reference 10), Those discharges were computed using <br />the EPA Storm Water Management Model (Reference 37). The Cherry <br />Creek basin was assumed to be fully developed, <br /> <br />" <br /> <br />Peak discharges for Lakewood Gulch and Lakewood Gulch Overflow were <br />previously determined as part of the 1976 UDFCD major drainageway <br />planning report (Reference 39), Those discharges were computed <br />using the Colorado Urban Hydrograph Procedure as outlined in the <br />Urban Storm Drainage Criteria Manual (Reference 40), Split flows <br />were calculated along Lakewood Gulch in the reach between Decatur <br />Street and the South Platte River, The divergence of flows from <br />Lakewood Gulch at Decatur Street is referred to in this study as <br />Lakewood Gulch Overflow, <br /> <br />Peak discharges for Dry Gulch (Lakewood Gulch Tributary) were <br />previously determined as part of the 1977 UDFCD Flood Hazard Area <br />Delineation report (Reference 12), The Colorado Urban Hydrograph <br />Procedure (Reference 40) was used to compute the 10-, 50-, and <br />lOa-year events under fully developed basin condi tions. The 500- <br />year flood peak was obtained by extrapolation from the frequency- <br />discharge curve, <br /> <br />Peak discharges along Harvard Gulch, Harvard Gulch Overflow, Dry <br />Gulch (Harvard Gulch Tributary), and West Harvard Gulch were <br />determined as part of the 1979 UDFCD Flood Hazard Area Delineation <br />report (Reference 14), Those discharges were computed using the <br />Colorado Urban Hydrograph Procedure (Reference 40). <br /> <br />Split flows were calculated along Harvard Gulch between South <br />Downing Street and South Logan Street, Due to the limited capacity <br />of the box culvert between South Downing and South Ogden Streets to <br />carry the lOa-year flood, flooding occurs overland to an old <br />channel, through a detention pond, and reJolns Harvard Gulch. <br />These flows through Logan Park are referred to in this study as <br />Harvard Gulch Overflow. <br /> <br />Dry Gulch (Harvard Gulch Tributary) consists of two 43- by 68-inch <br />reinforced-concrete pipe culverts along the entire study reach. <br />These culverts carry only 250 cfs of the 1,330 cfs lOa-year flood <br />event. The remaining floodwaters flow overland through a park area <br />and continue down Pearl Street to the confluence with Harvard <br />Gulch. <br /> <br />Peak discharges for Goldsmith Gulch and Southmoor Park Tributary <br />were determined as part of the 1976 UDFCD Flood Hazard Area <br />Delineation report (Reference 15), The 10- and lOa-year discharges <br />were computed using the Colorado Urban Hydrograph Procedure <br />(Reference 40), The 50- and SOO-year discharges were obtained by <br />interpolation and extrapolation of the frequency-discharge curve. <br /> <br />Southmoor Park serves as a detention pond to reduce flows along <br />Southmoor Park Tributary, Reduced flows are released through an <br /> <br />17 <br />
The URL can be used to link to this page
Your browser does not support the video tag.