My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD02223
CWCB
>
Board Meetings
>
Backfile
>
2001-3000
>
BOARD02223
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 3:13:35 PM
Creation date
10/4/2006 7:12:40 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
7/23/2001
Description
Draft RICD Rules
Board Meetings - Doc Type
Memo
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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 />. g. <br /> h. <br /> 1. <br /> J. <br /> k. <br /> 1. <br /> <br />. <br /> <br />DRAFT <br /> <br />1. Evidence that the administration and adjudication of the RlCD will <br />not impair the ability of Colorado to fully develop and place to <br />consumptive Beneficial Use its Compact Entitlements; <br />11. Information about the stream reach and the intended use; <br />iii. Information pertaining to the Applicant's legal interest in the lands <br />within and immediately adjacent to the affected stream reach, and <br />in the lands for access to the stream reach; <br />iv. Information about whether the Board has an ISF on the affected <br />stream reach, and whether the RlCD will cause material injury to <br />an ISF on the affected stream reach; <br />v. Evidence that the RICD will not inhibit the maximum utilization of <br />waters of the State; <br />d. Proof that the physical control structures are capable of fully and completely <br />controlling water within the stream channel; <br />e. Documentation describing the reasonable recreation experience sought both in <br />and on the water, including the time of day and season of use sought; <br />f. Information about the reasonableness of the flow amounts claimed, including: <br />i. Proof that the amounts requested in the RICD application are <br />available for appropriation; <br />ii. Information about the frequency of the requested flows, inciuding <br />exceedance calculations and duration curves for the claimed flows; <br />iii. Information showing that the flow amounts ciaimed are required to <br />achieve the reasonable recreation experience described in 5.d <br />herein. <br />Information about whether the exi$ting water quality ciassification is appropriate <br />for the intended use; <br />Information about all necessary permits and the status thereof; <br />List of persons notified by the Applicant about the RlCD; <br />Documentation of the effects that the RlCD and the associated structures will <br />have on current flood elevations; <br />Information about existing or proposed gages on the affected stream necessary to <br />administer the water right being sought; <br />Any and all engineering data, plans, and calculations used to design the faciiities <br />associated with the application for the RlDC or used as a basis for the information <br />submitted as part of this Article 5. This would inciude but not be limited to: <br />engineering plans and specifications; hydraulic calculations; hydrology <br />calculations; plans showing stream cross-sections at X feet intervals and stream <br />gradients throughout the length of the affected reach of stream both before <br />construction of the control structures and following construction of the control <br />structures; channel flow calculations showing water surface profiles for flows of <br />10%, 25%, 50%, 75%, 90%, and 100% of the flow rates sought in the RlCD <br />application by the Applicant; and flow duration and frequency curves for the <br />affected reach of the stream; and, <br />m. Information known to the Applicant concerning pending or envisioned changes of <br />water rights or other water management strategies such as exchanges that may <br /> <br />3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.