My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
6.1. - 6.5. SR 08-27-2001
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2001
>
08/27/2001
>
6.1. - 6.5. SR 08-27-2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:32:37 AM
Creation date
5/14/2003 6:49:50 PM
Metadata
Fields
Template:
City Government
type
SR
date
8/27/2001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
80
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 />August 9, 2001 <br />Page Three <br /> <br />No traffic information has been provided relative to the proposed widths of the <br />roadways and the narrower rights-of-way contained within the development. In <br />fact, none of the submittal documents even indicate the proposed width of the <br />internal roadways. By scale from the preliminary plat, it appears that most of the <br />roadways are proposed at 28 feet wide with the roadway around the park/pond in <br />Lot 6 being 20 feet wide in a 50-foot right-of-way. Clearly, this width is not wide <br />enough for two-way traffic; however, the submittal does not indicate that one-way <br />traffic is anticipated around Lot 6. <br /> <br />This most recent submittal appears to change the first north-south street in the <br />development from a proposed public street to a private street. It appears that <br />there is a lot line through the middle of the street, and no right-of-way is provided. <br />This change is perfectly acceptable to City staff. The Street Department had a <br />concern with the original submittal regarding maintenance of a street that would <br />act more as a parking lot, given the amount of head-in parking provided. <br /> <br />B. Drainage Issues <br /> <br />A detailed design summary of the internal storm sewer has been provided with <br />the most recent submittal. There are a couple areas where the storm sewer <br />design calculations do not match the grading plan. These areas should be <br />revisited, and the storm drainage calculations resubmitted or the grading plan <br />revised. <br /> <br />There are several drainage areas where areas sized from 0.50-1.86 acres drain <br />to a single catchbasin. From our experience, it is difficult to get more than 0.5 <br />acres of drainage area into a single catchbasin. Any area with more than 0.5 <br />acres should be revisited and additional inlet capacity provided. <br /> <br />Aisc, there still are a couple of areas where additional catchbasins need to be <br />provided to pick up drainage before it sheets onto the internal public roadway <br />system. An example of this would be by Buildings 104-112 and, likewise on the <br />west side of the street, the parking area for Buildings 16, 18, 20, 22, and 24. <br /> <br />The grading plan has been revised around the two major pond areas to eliminate <br />the retaining wall from the north side of each of these ponds. The' north side is <br />now a 3:1 slope with a ten-foot bench at the normal high water level. Both of <br />these ponds would still need some type of fencing around the three sides that <br />have retaining walls due to the fact that there is sidewalk immediately adjacent to <br />the retaining wall. However, the fence could be more of a decorative nature just <br />to eliminate accidental falls off of the sidewalk over the retaining wall. <br /> <br />The secondary smaller ponding area south of the east pond/park area still has a <br />double six-foot high retaining wall around its entire perimeter. We still question <br />whether or not this type of installation should be allowed, and if so, we would <br />recommend a five- to six-foot high cyclone fence around the entire perimeter to <br /> <br />Howard R, Green Company <br /> CONSULTING ENGINEERS <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.