My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD07007
CWCB
>
Floodplain Documents
>
Backfile
>
6001-7000
>
FLOOD07007
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2010 7:10:34 PM
Creation date
10/5/2006 2:41:19 AM
Metadata
Fields
Template:
Floodplain Documents
County
Statewide
Community
State of Colorado
Basin
Statewide
Title
Expected Annual Flood Damage Computation - Users Manual
Date
6/1/1977
Prepared For
State of Colorado
Floodplain - Doc Type
Flood Mitigation/Flood Warning/Watershed Restoration
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
93
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 />~ <br /> <br />variables for the entire reach. In the case of damage, several relation- <br />ships are usually used, each representative of a particular damage <br />category. <br /> <br />The principal reason for computing flood damage is to determine the <br />effectiveness of different flood plain management plans in reducing <br />damage. This reduction is commonly referred to as an inundation reduction <br />benefit and is measured as the difference in equivalent annual flood <br />damage with and without a plan. Different management plans alter the stage, <br />flow, frequency, and damage relationships in different ways (see Exhibit 1 <br />for a detailed discussion). With a different relationship the damage is <br />different--usua11y 10wer--than without the plan. Thus, for any plan which <br />causes a change which can be quantified, damage with the plan can be <br />computed. Without a plan, damage is still likely to change. Increases in <br />damageable property in existing structures, residual damage to new <br />structures, increases in stage from greater or more rapid runoff all can <br />cause a change in future damage., <br /> <br />6. REACH SELECTION <br /> <br />Frequency, flow, stage and damage data are used for each reach; thus, <br />these data must be representative of the actual frequency of flood events, <br />flow regime, and flood damage for that reach. Reach lengths should be <br />selected to allow segregation of output as required for specific study <br />needs. For example, for plan formulation output may be needed in sufficient <br />detail that changes in stream and development characteristics are identified. <br />Generally, hydraulic and hydrologic factors govern the selection of the <br />index location. Frequency data input for one reach will be used for subse- <br />quent reaches until another data set is input (FR cards). This does not hold <br />for stage, flow or damage data (QF, SF, SQ, QS, SD, QD or DG cards). These <br />data must be input for each reach. <br /> <br />7. FLOOD PLAIN MANAGEMENT PLANS <br /> <br />The expected annual flood damage with any structural or nonstructura1 <br />flood plain management plan can be computed provided the effect of such a <br />plan can be expressed in terms of the stage, flow, frequency or damage data <br />used by the program. Such plans can include nonstructura1 measures such as <br />relocation, flood proofing, e1evation-on-fi11 or such structural measures <br />as reservoirs, channelization and levees. A discussion of the effect of <br />various measures on the stage, flow, frequency and damage relationships is <br />presented in Exhibit 1. <br /> <br />Up to nine flood plain management plans can be evaluated. Each plan's <br />name and number are input (PN card) and the corresponding stage, flow and <br /> <br />5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.