My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD00689
CWCB
>
Floodplain Documents
>
Backfile
>
1-1000
>
FLOOD00689
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/23/2009 1:21:34 PM
Creation date
10/4/2006 9:25:22 PM
Metadata
Fields
Template:
Floodplain Documents
Designation Number
136
County
Arapahoe
Community
Littleton
Stream Name
Slaughterhouse Gulch
Title
Major Drainageway Planning - Slaughterhouse Gulch, Littleton
Date
5/1/1974
Designation Date
5/1/1979
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.
/
99
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 />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 />to repair or replace severely damaged or destroyed struc- <br />tures. This would have a further effect of adversely <br />affecting property values within the zoned district. <br /> <br />This alternate would only alleviate potential flood dam- <br />age below a five-year flood between Prince Street and the <br />South Platte River. Larger floods would overflow Prince <br />Street west of the South Platte River due to the restric- <br />tion of the five-year capacity culvert. <br /> <br />With the adverse effects of the proposed Alternate No.3 for <br />the South Tributary, the Environmental Impact Statement lists <br />as adverse effects of the recommendation: <br /> <br />Again, noise levels during construction would be a short <br />term adverse effect. <br /> <br />It is also felt that implementation of the interim report <br />recommendation would have an adverse effect in view of <br />the more positive flood prevention solutions found in <br />Alternates No.2 and 3. <br /> <br />It is important to keep in mind the fact that the implementa- <br />tion of flood plain zoning and flood plain management regulations <br />is a positive step in minimizing flood damages. Flood plain <br />regulations are not measures which prevent the use of flood <br />prone areas, but do regulate their use to the extent that <br />existing uses will not be perpetuated within the flood plain <br />area over a period of time. If structural measures were to be <br />implemented in a reach to reduce the potential flood damage, it is <br />certain that those improvements would be paid for over a similar <br />period of time to achieve essentially the same objective at the <br />end of that period. For regulatory measures, there are no major <br />public costs. Therefore, the comparison between the two <br />approaches must weigh the chance of flood damages occurring <br />to the private property, at no cost to the City but at some <br />cost to the private property owner, who possibly would acquire <br />flood insurance, against the cost that the City would have to <br />pay to retire bonded indebtedness or to recoup tax monies spent <br />on immediate drainage improvements. Therefore, we should <br />look at both measures as being positive steps in the implementa- <br />tion of a viable flood prevention program, each obtaining the <br />same objective over a period of time, with substantially different <br />cost requirements. <br /> <br />The Environmental Impact Statement indicates that all viable solu- <br />tions presented have both positive and negative aspects. These <br />aspects, however, had to be considered with all other data pre- <br />sented with the alternatives in selecting the more prominent approach. <br /> <br />D. ALTERNATIVE SELECTION <br /> <br />The selection of the alternative for more detail study and design <br />was done in a very thorough and comprehensive manner. The Interim <br /> <br />VI-9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.