My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD10800
CWCB
>
Floodplain Documents
>
Backfile
>
11001-12000
>
FLOOD10800
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/23/2009 2:17:47 PM
Creation date
6/12/2007 5:21:15 PM
Metadata
Fields
Template:
Floodplain Documents
Designation Number
592
County
Routt
Community
Routt County and Incorporated Areas
Title
FIS - Routt County and Incorporated Areas
Date
2/4/2005
Prepared For
Routt County
Prepared By
FEMA
Floodplain - Doc Type
Current FEMA Regulatory Floodplain Information
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
123
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 />Dry Creek <br /> <br />To define discharge frequency data for Dry Creek, several methods of analysis were <br />used. A unit hydrograph involving rainfall-runoff relationships yielded the adopted <br />results (Reference 19). Other methods included a regional analysis procedure, as <br />explained in a report by the USGS (Reference 20), and a regional procedure relating <br />peak discharges and drainage area for nearby gaging stations with similar hydrologic <br />characteristics (Reference 19). <br /> <br />Peak discharges for the 10-, 50-, 100-, and 500-year floods of streams in the study area <br />and maximum known peak discharges for nearby streams having similar hydrologic <br />characteristics are shown in Table 1. <br /> <br />The J. C. Temple Reservoir was analyzed by routing the loo-year peak discharge <br />developed from a regional relationship of peak discharges and drainage areas of nearby <br />gaging stations. With this information and information from field inspection by <br />geologists and engineers from the USBR, Grand Junction Office, it appears that the dam <br />is now functionally sound and capable of safely passing a tOO-year flood discharge. <br /> <br />Oak Creek <br /> <br />A hydrologic analysis of flows in Oak Creek was performed for snowmelt and/or <br />rainfall runoff over the basin. There are no active streamflow gage records for Oak <br />Creek. A gage that fonnerly existed on Oak Creek for only 5 years (water years 1953 <br />to 1957) was located 4.5 miles southwest of the Town of Oak Creek. The length of <br />record of this gage was insufficient to be analyzed and provide meaningful results. The <br />SCS unit hydrograph procedure (Reference 21) was then employed to determine the <br />tOO-year peak streamflow. Significant parameters used with this method were a <br />tOO-year, 24-hour rainfall of2.8 inches and an SCS curve number of 70. <br /> <br />A tOO-year peak flow was computed using the assumed basin parameters and compared <br />with the flow values of other streams in the region (Reference 2). Through this <br />comparison, the loo-year peak flow was adjusted to reflect the runoff characteristics of <br />the basin. <br /> <br />The 10-year flood event was assumed to be the result of a snowmelt event. This value <br />was obtained from a regional analysis of streams with acceptable gage records and <br />similar characteristics. <br /> <br />Peak discharge-drainage area relationships for Oak Creek are shown in Table 1. <br /> <br />3.2 Hydraulic Analyses <br /> <br />Analyses of the hydraulic characteristics of flooding from the sources studied were <br />carried out to provide estimates of the elevations of floods of the selected recurrence <br />intervals.. Users should be aware that flood elevations shown on the Flood Insurance <br />Rate Map (FIRM) represent rounded whole-foot elevations and may not exactly reflect <br />the elevations shown on the Flood Profiles or in the Floodway Data Table in the <br />FIS report. Flood elevations shown on the FIRM are primarily intended for flood <br /> <br />30 <br />
The URL can be used to link to this page
Your browser does not support the video tag.