My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
6.11. SR 06-17-2002
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2002
>
06/17/2002
>
6.11. SR 06-17-2002
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:31:49 AM
Creation date
6/14/2002 9:07:47 PM
Metadata
Fields
Template:
City Government
type
SR
date
6/17/2002
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
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
Ms. Michele McPherson <br />May 23, 2002 <br />Page Two <br /> <br />The drainage calculations have been reviewed, and the following comments are pertaining to them: <br />· The drainage pond needs to be moved out of the drainage and utility easement that is intended <br /> for watermain looping. <br />· The outlet for the pond is shown to have three 3-inch orifices. Elk River standards allow a <br /> minimum orifice 4 inches in diameter. The outlet structure should be revised to include an <br /> orifice at least 4 inches in diameter. <br />· No drainage area map was submitted. <br />· The grading plan shows the top of the berm to be at 925. The High Water Level (HWL) of the <br /> pond is 924.3. Elk River standards require 1 foot of freeboard from the HWL to the top of the <br /> berm. The grading plan should be revised to show the top of the berm at 925.3. Additionally, <br /> the drainage calculations state the Emergency Overflow (EOF) for the pond is at an elevation <br /> of 925. The EOF should be shown on the grading plan and should be detailed to insure it is <br /> constructed properly. <br />· There is an area along the south property line that is hatched on the grading plan, but there is <br /> no indication what this hatched area represents. This hatching should be referenced in the <br /> legend. <br />· The Iow point in the parking area near CBMH 102 appears to overflow onto the property to the <br /> south. An emergency overflow for this Iowpoint should be provided to route this area to the <br /> proposed pond rather than off the property to the south. The EOF for this Iow point should <br /> overflow at an elevation no greater than 1 foot above the elevation of the Iow point. <br />· The ponding calculations show the proposed weighted Cn for the fully developed site with 2.34 <br /> ac. of impervious to be 63. Using 2.34 ac with a Cn of 98 and 3.60 ac. with a Cn of 58, we <br /> calculate the weighted Cn to be 73. The drainage calculations should be revised to show the <br /> correct Cn. <br />· A pair of dashed lines is shown crossing the pond. it is unclear as to whether this is an <br /> easement, and if so, whether a pond can be constructed over it. <br />· The grade of the parking area near the southerly handicapped parking space is 3.13%. 2% is <br /> the maximum grade permitted. <br />· The grades in the area along the north side of the future additions are extremely flat, and the <br /> pavement at the northwest corner of the easterly parking lot is higher than the proposed floor <br /> elevation. <br />· The casting for CB 101 is called out to be a beehive type; Elk River's standard casting in this <br /> case would be a stool type R-4342. <br />· Additional catch basins are needed in the parking lot to collect runoff. <br /> <br />The area for future expansion is very flat and will not drain properly. Even after the addition is built, <br />the area will be too flat. This area should be looked at and reworked. <br /> <br />you have any questions regarding any of these comments, please call. <br /> <br />Sincerely, <br /> <br />Howard R. Green Company <br />Terry J. lVl'a~rer, P.E. <br /> <br />Ltro052302-McPherson.doc <br /> <br />Howard R, Green Company <br /> QQNSULTING ENGINEERS <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.