My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 10/06/2005
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2005
>
Agenda - Planning Commission - 10/06/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:38:02 AM
Creation date
9/30/2005 11:48:25 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
10/06/2005
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
314
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
/\s the area grows in population tu~d traffic volume, the need ]tbr roadway improvements <br />becomes necessary. With the continued tra£fic growth on TH 10, it is proposed that TH <br />10 will be improved to a i'bur-lane freeway facility through the City of Ramsey by 2017. <br />It is also proposed that Armstrong Boulevard will be re-aligned to the west o£ its cra'rent <br />location through the Pulte Site. This will allow for eat interchange to be constructed at <br />the intersection of TH 10,. either with a signalized intersection on Armsla'ong with ramp <br />access to and fi'om TH I0 or a system-to-system interchange. <br /> <br />By 2030, a river crossing to the south over the Mississippi River is proposed that will <br />connect with the interchm~e at TH 10 and Armstrong Boulevard. Assuming that these <br />improvements will be ~mde to the roadway network, the t~'affic/Yom the developments <br />will access the roadway network differently and traffic patterns will change. The results <br />of the 2017 and 2030 Full Build analyses are located in Table 8. These resuRs take into <br />account the realignment of Azmstrong Boulevard and the two new study intersections <br />created by the realignment. It is assumed that the existing intersectior/of Armstrong <br />I~tmlevard (Old Armstxong) and Industry Avenue will be redesigned be~bre 2007 to <br />handle thc 2007 traffic without the realignment of Armstrong. This design will provide <br />sufficient geometry a~ the intersection for the traffic in 2017 and 2030. Also a sh~gle- <br />point intersection is anticipated at TH 10 and Armstrong Boulevard for analysis purposes. <br />The intersection lanes and traffic control Chat is required for LOS D or better operations <br />each year is noted in Figure 10. <br /> <br />hie 8:21117 and 2030 Fall Buihl 5'litigated Oper:ationa! A~!a!ysis ...... <br />er-Tseetion & Traffic COntrol i$cenario i Peak Hour Intersection Maximum Deia¢2 <br />! Delav*-LOS LOS-v/c** <br />~stro,m~ Blvd & TH 10/169 j 2(117 AM ~i 16~6-B 35.4-D-0.g6 <br /> <br /> PlVl [ 14.7-B 41.0-D-0.87 <br /> Signaliz~..d 20.30 AM i t 8.1 -B 51.7-D-0.94 <br /> PM .. ).I 48.2-D.. I t6.6-F-l,13 <br />m~t-'ong I3 Ivd & Industry Ave N W 2017 AM ~ 21.0-C 4~,0-D-0.94 <br /> PM 32.9-C $4.8-D-O,gg <br /> <br /> ,S'iRnalized 2030t1 ! AM ,~'~ 1.8-C 47.0-D-0.92 <br /> <br /> , J PM 27.6-C 47.[-D-0.98 <br />'Xrmstrong ~ Int~usn3, ,,&~,~ h~ 2017' i AM tg.0-B 36.0-D4hS4 <br /> ! PM .9..~-C 46.5-D-0.99 <br /> ,S'ignt tized 2030 i AM '~ 4o.4-D~0,94 <br /> [ PM 31.6-C 48.2-D-0.99 <br />mm)ag I}lvd & ~<lpine Drive N W 20 [ 7 AM 8.4-A 13,3-B-0.60 <br /> PM 8,4A 18.5-B-0.6 I <br />S(g,alized 2030 AM t2.1 - B 2'i .4-C-0.51 <br /> PM i 3.0-B. 25.1-C-0.54 <br />ne Drive NW & TH I 0/[69 201'7 "AM 12. I-B ] 27.%C-0.8'8 <br /> PtVI' 15,4-B i 56.2~E-0,95 <br /> 3'[g~nalizqd 2030 AMI 48.8-D I 85.6-Fq .11 <br /> PM I 86,3- FI~ 1.48.6:F-1.28 <br /> <br />(.)Id <br /> <br />iai, <br /> <br />Pi;Ire Homes Development EA PI/ <br />Ti'q/tic/mi?ac/Sludy <br />( 'il); 0/' ]?al~*,S'<y. ,4 ;*okL1 COZ/t*ly, Minnesota <br /> <br /> Page 20 of 24 <br />Prepared by: <br />Bo/ton &. Menk, hw <br /> <br />125 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.