My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 02/23/2010
Ramsey
>
Public
>
Agendas
>
Council
>
2010
>
Agenda - Council - 02/23/2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 2:31:45 PM
Creation date
2/18/2010 4:48:18 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
02/23/2010
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.
/
272
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
plan is submitted to the Met Council. <br />■ Page 6 -12 — 2030 Traffic Forecasts —1 paragraph: The forecasts used are not from the Anoka <br />County Transportation Plan. Text should be reworded to state that the city's consultant used the <br />Anoka County travel forecast model to prepare 2030 travel forecasts. A second sentence should <br />state that the city's consultant modified the Anoka County model by changing socioeconomic <br />data and including additional roadway improvements. This is an error in multiple areas of the <br />plan. It needs to be corrected in all areas. <br />■ Page 6 -12 — 2030 Traffic Forecasts — 2 °a paragraph: The county finds it odd that the Met <br />Council would request 2030 forecasts to be prepared assuming a constructed river crossing as the <br />primary forecasts. The Met Council's Transportation Policy Plan does not include the <br />construction of a new river crossing before 2030. Since it is not an approved regional <br />improvement, it should not be considered a primary forecast, it should be the "reference purposes <br />only" forecast. Additionally, the reference to the Anoka County forecasts is incorrect. The city's <br />consultant used the county's forecasting model to generate future volumes; it did not use actual <br />Anoka County forecasts. Also, the text should clarify whether or not a full access interchange <br />was also assumed at CSAH 83 as part of the scenario with a river crossing and whether or not <br />interchanges at CSAH 56 and CSAH 57 were also assumed as part of the river crossing scenario. <br />Having interchanges at these locations would have a freeway on US 10/169 and could make a <br />significant difference in forecasts. <br />■ Page 6 -13 — Table 12030 Household and Employment Projections by TAZ: Text in the plan <br />notes that the city updated the socioeconomic data in the Anoka County model. The data in the <br />county model is from the Met Council approved system statements and input from the city. Did <br />the city change its socioeconomic data with the approval of the Met Council or is it a new <br />scenario that has not been approved? If it is approved, then nothing needs to be done. If it is <br />different than what has been approved by the Met Council, text should indicate why it is different <br />and what the difference is (e.g, 10 percent additional population by 2030 or 20 percent more <br />employment by 2030). <br />■ Page 6 -14 — Table 6 -2 Existing and Future Traffic Volumes: References to county routes are <br />incorrectly labeled. Additionally, it is difficult to identify travel forecast locations. A map <br />showing the traffic volumes would be easier to follow. For example, CSAH 83 has two numbers <br />listed, one south of CSAH 22 and one north of 153rd. Both numbers are located north of 153rd <br />and south of CSAH 22, but where? Why 153rd for the location, it is not a major roadway facility <br />where you would expect to see a change in volume. Alpine would be a better location and an <br />additional location south of CSAH 116 would also be helpful given that is going to be the more <br />heavily used portion of roadway. <br />■ Page 6 -14 - Table 6 -2 Existing and Future Traffic Volumes: The columns in the table are <br />incorrectly labeled. "Location of Count" should be renamed "Location". "2020 County with <br />future Bridge" should be renamed "2030 Forecasts with River Crossing ". "2020 County without <br />future Bridge" should be renamed "2030 Forecasts without River Crossing ". The year is <br />incorrect for both future scenarios and future volumes are not "counts" they are forecasts. <br />■ Page 6 -14 — Table 6 -2 Existing and Future Traffic Volumes: CR 63 west of CSAH 5 is no <br />
The URL can be used to link to this page
Your browser does not support the video tag.