My WebLink
|
Help
|
About
|
Sign Out
Home
2006-06-27_PWETC_AgendaPacket
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Agendas and Packets
>
200x
>
2006
>
2006-06-27_PWETC_AgendaPacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/22/2010 4:13:55 PM
Creation date
9/11/2006 11:01:12 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Agenda/Packet
Commission/Committee - Meeting Date
6/27/2006
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
61
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).
View images
View plain text
<br /> Table 2 - Summary of Rulemakinl! Studv Phase II, June 2005 <br />Site Name Stormwater Estimated Stormwater Stormwater Increased Percent of Total <br /> Practices Total Practice (s) Practice (s) Cost of Development <br /> fit within Development Cost from Cost from Stormwater Cost for <br /> existing, Cost City City BMP's to Stormwater <br /> City Approved Approved meetCRWD BMP's to meet <br /> approved Plan Plan AND Criteria CRWD Criteria <br /> site plan? CRWD <br /> Planl <br />CVS Yes $4,000,000 $73,215 $100,459 $27,245 0.68% <br />Pharmacy <br />The Metro Yes $15,500,000 $75,977 $96,584 $20,607 0.13% <br />The Yes $22,000,000 $99,232 $139,372 $40,140 0.18 % <br />Heritage <br /> <br />I - Average Cost based on three consultants data <br /> <br />On July 12, 2005, the District, in conjunction with RWMWD held a joint meeting with their member <br />Cities to solicit input on the draft technical standards for Rules. As the result of previous <br />collaboration, the District and RWMWD had the same standards for all criteria except wetland <br />management. The CRWD criterion for wetlands is more restrictive than the RWMWD because the <br />CRWD only has 1.4% of its wetlands remaining. The RWMWD has over 8% of its land area as <br />wetlands. <br /> <br />Based on comments received at that meeting and additional rule development efforts, the District <br />completed the drafting of the proposed Rule during August and September 2005. <br /> <br />On October 5,2005, the District adopted the SONAR and authorized the distribution of the draft Rules <br />to interested stakeholders for review and comment. (See Appendix K) The District accepted <br />comments for a 45-day period ending on November 25,2005, and held a public hearing on November <br />16,2005. During the 45-day review period, the District held a meeting with its member Cities to <br />review the draft Rules. At the public hearing an extension of the comment period to December 15, <br />2005 was requested and granted by the Managers. Many of the comments received pertained to the <br />volume control rule and its implementation on road projects. (See Appendix L) Additionally, there <br />was a request for a Technical Advisroy Committee (T AC) to address the concerns raised during the <br />comment period. <br /> <br />On January 4,2006 the Manager's established a joint TAC with Ramsey-Washington Metro <br />Watershed District and adopted a workplan and timeline for the Committee. (See Appendix M) The <br />workplan directed the committee to discuss and make recommendations on 5 main topics: <br /> <br />. 1" Infiltration Standard <br />. Roads/Linear Projects <br />. StandardINon-Linear Projects <br />. Alternative Compliance (Off-site Compliance, Variances) <br />. Maintenance/Longevity <br />. Definitions, Ambiguities, Misc. <br /> <br />CRWD - Statement of Need and Reasonableness (SONAR) for Watershed District Rules June 7, 2006 Page 4 of6 <br /> <br />"Our mission is to protect, manage, and improve the water resources of the Capitol Region Watershed District. " <br />
The URL can be used to link to this page
Your browser does not support the video tag.