My WebLink
|
Help
|
About
|
Sign Out
Home
2017_07-25_PWETCpacket
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Agendas and Packets
>
201x
>
2017
>
2017_07-25_PWETCpacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/8/2017 11:34:25 AM
Creation date
12/8/2017 11:33:03 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Agenda/Packet
Commission/Committee - Meeting Date
7/25/2017
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
45
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
263 Metropolitan Council and the regional growth plan for the Twin Cities area. If a <br />264 number looks unreasonable, they can communicate that with the Metropolitan <br />265 Council. <br />266 <br />267 Mr. Culver commented the Metropolitan Council model is not going to put 5,000 <br />268 cars on a roadway that cannot handle it. There may be 5,000 additional cars that <br />269 want to go somewhere, but they cannot because the roadway cannot handle it, and <br />270 then they end up on a larger road. They also have to look at the larger picture to <br />271 see how growth in other cities affects Roseville's traffic patterns. Mr. Culver stated <br />272 there is a plan to add a lane to Highway 36. <br />273 <br />274 Member Seigler stated that is why he is concerned when the focus on transit and <br />275 bicycles. As other Cities grow and Highway 36 continues to get worse, everything <br />276 will continue to flood onto Roseville's streets. <br />277 <br />278 Chair Cihacek commented the methodology does not have a predictive value for <br />279 them. They can agree the numbers are conservative and congestion will continue to <br />280 increase, and they need to use that information to find a solution. They also need to <br />281 understand what the assumptions are regarding volume of traffic. Mr. Culver <br />282 suggested they discuss these issues further outside of this meeting. <br />283 <br />284 Mr. Mareck stated this is a capacity constraint model that restricts the traffic flow <br />285 to what the capacity is to the existing roadway lanes or to what is known to be added <br />286 in the future. It is done this way so that they understand how a road will function if <br />287 no additional funding is available. The City can then find solutions with the County <br />288 and Mn/DOT with any available funding. <br />289 Member Seigler inquired why they do not just have the road show it will not <br />290 function instead of changing the number to reflect what the road can handle. That <br />291 way they can focus on Highway 36. <br />292 Member Misra suggested they broaden their explorations of assumptions. Not all <br />293 young people are buying cars and baby boomers will not be driving in 2040. Mr. <br />294 Culver pointed out understanding the assumptions will be part of their response to <br />295 the Transportation Plan. <br />296 In response to Mr. Culver, Mr. Mareck stated the model does not directly consider <br />297 self -driving cars or any other technology that is not fully integrated at this time. It <br />298 is hard to know what impact it will have, but it is important to acknowledge through <br />299 a narrative in the plan. <br />300 Member Wozniak stated some reports show that self -driving cars are only 10 years <br />301 away and insurance rates will be too high for regular drivers that it will push them <br />302 into self -driving cars. <br />303 The Commission directed Mr. Mareck to include a narrative regarding self -driving <br />304 cars in to the Transportation Plan. <br />Page 7 of 11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.