My WebLink
|
Help
|
About
|
Sign Out
Home
05/06/98 Special Meeting
Ramsey
>
Public
>
Dissolved Boards/Commissions/Committees
>
Road and Bridge Committee
>
Agendas
>
1998
>
05/06/98 Special Meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/19/2025 11:58:30 AM
Creation date
6/9/2003 1:57:41 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Document Title
Road & Bridge Committee - Special
Document Date
05/06/1998
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
CASE #1 <br /> <br /> LEAD LINK CLOSURE OF 158TH AVENUE <br />IN CONJUNCTION WITH THE APPLE RIDGE DEVELOPMENT <br />By: Steve Jankowski, City Engineer <br /> <br />Background: <br /> <br />The proposed Apple Ridge subdivision, when fully developed, can be expected to generate about <br />1,350 trips on a daily basis. The proposed street layout encourages the majority of these trips to <br />utilize only Apple Ridge streets and T.H. #47. A traffic engineering analysis was prepared by <br />Bolton & Menk, Inc. and is attached to this case. That analysis estimated that 182 daily trips <br />would be generated from the subdivision to C.S.A.H. #5 using 157th-Lane. <br /> <br />During the course of the approval process, a number of public meetings were held at which <br />concern was expressed from the adjacent existing subdivision that traffic from the Apple Ridge <br />development would exceed the levels identified in the study and adversely impact their quality of <br />life. At various times, these citizens had requested a "lead link" closure of 158th Avenue, <br />between Osmium and Potassium Streets in the new subdivision, which would allow only <br />emergency vehicles to pass through. This plan would limit only 17 Apple Ridge homes to the <br />use of neighboring, existing subdivision street, or approximately 170 daily trips. <br /> <br />It is anticipated that final plat approval of the last four phases of the Apple Ridge subdivision <br />will be on the May 12 Council agenda, and the issue of whether or not this type of street closure <br />should be required of the developer has not been resolved. If the Council desires this type of <br />street closure, it should be clearly stated in the development agreement, and the area residents <br />should be informed of the decision. <br /> <br />Observations: <br /> <br />The type of street closure requested will be problematic for several reasons. Any type of closure <br />that will allow emergency vehicles to pass through without damage, will also allow non- <br />emergency vehicles to pass through undamaged. It could be anticipated that such a closure will <br />require frequent maintenance. Secondly, a conversation with the City of Coon Rapids <br />engineering department indicated that a "sawed" chain link type of street closure, attempted <br />several years ago, did result in minor damage to emergency vehicles. In one instance, the chain <br />was mistakenly replaced without the sawed link, and major damage resulted to a fire department <br />vehicle. The temporary closure was removed after that incident. The City of Coon Rapids also <br />has an emergency street closure which has been in place for approximately two years with only <br />one incidence of a drive-through. This is a gate-type of closure which is required to be <br />physically opened by getting out of the emergency vehicle. An automatic type of gate facility <br />was over $4,000 and was deemed to be too expensive to install and maintain. The non-automatic <br />gate, used by the City of Coon Rapids, costs less than $1,000 and the most vulnerable piece is a <br />two by six piece of lumber with $100 of reflective warning tape. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.