My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 5.3
ElkRiver
>
City Government
>
Boards and Commissions
>
Planning Commission
>
Planning Packets
>
2000-2005
>
2002
>
02-26-2002
>
Item 5.3
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/16/2018 2:16:08 PM
Creation date
7/16/2018 2:16:06 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
30
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
• Mr. Scott Harlicker <br /> February 20, 2002 <br /> Page Two <br /> • The proposed improvements require some filling of the wetland area. These are <br /> noted on the plan with identified mitigation areas. Obviously, this project will need to <br /> go through a Technical Evaluation Panel for the wetland issues. <br /> B. STORM DRAINAGE <br /> Detailed storm drainage calculations were provided. These have been reviewed. In <br /> general, the storm drainage concept is fine. However, there are a number of questions <br /> and modifications that need to be answered or made. These include the following: <br /> • The report does not clearly show a comparison of the total of pre and post total site <br /> discharge rates. It appears as though the post-development rate is less than the <br /> pre-development rate for the 100-year event. <br /> • The 100-year peak pond elevations are summarized in the drainage report. The <br /> 100-year high water elevations (100-year HWL) are shown on the preliminary <br /> grading plan for ponds 40, 42, 43, and 44. The grading plan should show the 100- <br /> year HWL for all ponds in the development. <br /> • The 100-year HWL for pond 66 is shown in the report as 945.4; the calculations <br /> submitted show this elevation to be 945.0. This should be corrected in the report. <br /> • The calculations should be revised to show the normal water level to be at the outlet <br /> • elevation at the beginning of the 100-year event. This will affect the calculated 100- <br /> year HWL for most of the ponds. <br /> • Pond 8 along Ranch Road is shown to have no outlet other than overflowing the curb <br /> onto 215th Avenue. Storm sewer is shown in the area. An inlet should be added <br /> behind the curb to drain this area. <br /> • The trail crossing the ditch between Ranch Road and 215th Avenue will require a <br /> culvert within the ROW of Ranch Road. <br /> • The EOF between Lots 10 and 11, Block 1, is shown at an elevation of 947.0. The <br /> low point at the intersection of 214th Avenue and Queen Street is 945.0, leaving a <br /> potential pond depth of 2.0 feet in the road should the storm sewer become <br /> obstructed. The low point should be raised or the EOF should be lowered to allow a <br /> maximum ponding depth of 1.0 foot. <br /> • The EOF between Lots 19 and 20, Block 1, should be moved to the lot line between <br /> Lots 18 and 19. <br /> • Details of the pond outlets should be provided in the drainage report. Many of the <br /> ponds in this development have a weir outlet. Are these constructed with rip-rap, <br /> treated timbers, or some other materials? <br /> • No water quality calculations have been provided to determine if adequate dead <br /> storage has been provided. <br /> • No analysis of the 1-year or 10-year events has been provided. <br /> • The calculations show a curve number of 39 for lawn (good) soil type A in the <br /> developed condition in the yard area of the lots. Typically, residential developments <br /> import topsoil for lawn and the soil type in the yards is more characteristic of type B <br /> soils. The curve number for this case would be 61. The calculations should be <br /> • revised to show a curve number of 61 for yard areas. <br /> Howard R. Green Company <br /> Ltr 2-20-02 Harlicker.rev CONSULTING ENGINEERS <br />
The URL can be used to link to this page
Your browser does not support the video tag.