My WebLink
|
Help
|
About
|
Sign Out
Home
06/03/86
Ramsey
>
Public
>
Dissolved Boards/Commissions/Committees
>
Planning and Zoning
>
Agendas
>
1980's
>
1986
>
06/03/86
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/21/2025 4:12:07 PM
Creation date
7/18/2006 2:00:18 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Document Title
Planning and Zoning Commission
Document Date
06/03/1986
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
112
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
<br />Responsibility for any new. bridge oapacity needs to be Ihared among leveral <br />unitl of government. Affected agencies must agree on an equitible way to <br />Ihare study costs, th1s il also l1kely to be true of improvement costa. <br /> <br />Short Range Actions: (W1thin the next 10 years) <br /> <br />ADoka and Hn/DOT need to reach agreement on improvements to intersections <br />and Ferry street or to traffic operations to handle short range demand. <br />The long t1me period for design and approval of additional capacUy in a <br />new or widened bridge makes a short range solution critical. It would be <br />desirable to have sufficient capacity to carry about 2400 vehicles per hour <br />in each direction. <br /> <br />The next step in an acceptable bridge development process usable by the <br />state and USDOT ill a detailed environmental impact analys1s of alternatives <br />in the priority corridor to tie down more accurate cost implications. The <br />alternatives analysis should further test the finding that Ferry st. is the <br />critical link. <br /> <br />Long Range Actions: (Beyond 1996-97) <br /> <br />Action is needed to provide more bridge and approach road capacity in the <br />priority corridor. Due to its location, the TH 169 crossing will <br />experience demand in excess of its capacity even with the avail1bility of <br />new river crossing capac1ty at TH 610 to the south. Providing for such an <br />imProvement will require a long term inter-governmental approach to <br />planning, design and fUnding. <br /> <br />The second priority corridor segment would include bridge locations 8 through <br />12. This segment is that part of the corridor which runs from 109th Ave-Hanson <br />Blvd. north of the new TH 610 crossing south to 1-694. This segment is between <br />Brooklyn Park and Brooklyn Center on the wst of the river and Coon Rapids imd <br />Fridley on the east. The long term increase in traffic demand across the <br />second priority segment ill greater than the other two segments and current <br />congestion on 1-694 ill and has been of concern to travelers and officialS. <br /> <br />The technical committee has made the following findings regarding the second <br />priority segment and identified short and long range actions appropriate to the <br />findings. <br /> <br />Findings: <br /> <br />The analysis of future development shows a long tel'lll increase in east west <br />travel demand in this corridor. The largest increase in the study area <br />will be generated in Brooklyn Park. AlSO, total travel demand on 1-694 is <br />and will continue to be the greatest ot all crossings in the study area. <br />Provision of an additional crossing in this corridor would probably raise <br />demand further, especially if the crossing wre near to 1-694. <br /> <br />The year 2000 de:Bl1d (185,000 trips) will exceed the combined capacity of <br />TH 610 _ 1-694. In the short run there is a capacity restraint on TH 610 <br />at the west end <;erDlinus w1th TH252. This constraint is based on the <br />assumption in the study that TH 610 will not be constructed west of this <br />point before 2000. If 610 were complete then the bridge would be at <br /> <br />35 <br /> <br />52 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.