My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2013_1125
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2013
>
CC_Minutes_2013_1125
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/16/2013 10:36:51 AM
Creation date
12/16/2013 10:36:31 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
11/25/2013
Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
42
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
Regular City Council Meeting <br /> Monday, November 25, 2013 <br /> Page 8 <br /> ing so; with Mr. Schwartz suggesting a Public Hearing could be held at the <br /> PWEC level to hear their feedback at a later date, once under City jurisdiction. <br /> Councilmember Etten also expressed his appreciation to staff for taking time to <br /> research this issue and bring it to the City Council for consideration, as well as for <br /> his time spent negotiating with Ramsey County, opining that it was an important <br /> connection piece, hoping that this could be accomplished. Councilmember Etten <br /> questioned if there was any way to create a separation from the roadway (e.g. <br /> trees or a fence) with this type of scenario to visually affect that it was still an <br /> open roadway. Mr. Schwartz responded that there was little space to do so. Once <br /> the roadway is reconstructed, Mr. Schwartz confirmed for Councilmember Etten <br /> that there was potential to install a pedestrian facility on the north side, and with <br /> wetland issues and embankments on the golf course side, both sides of the road <br /> could be reviewed to further spread the impact. Councilmember Etten opined <br /> that, from his perspective, that would be preferable long-term to avoid crossing a <br /> busy roadway; however, he expressed his full support of moving forward with <br /> speed limit reductions. <br /> At the request of Councilmember McGehee regarding any Minnesota State Aid <br /> (MSA) funding available for construction of this pathway and whether or not this <br /> pedestrian facility needed to be built to the same standards of the roadway since <br /> there would be no truck traffic on it, Mr. Schwartz responded that the City would <br /> experience the same difficulties as Ramsey County in meeting the requirements <br /> for MSA funding now that it was no longer connecting to Highway 280. <br /> Mr. Schwartz advised that City staff had met with MnDOT, with them acknowl- <br /> edging that the City potentially had some undesignated mileage in its state aid ac- <br /> count; making it possible to designate Fulham and back around on the frontage <br /> road for MSA funds. Mr. Schwartz advised that, given the nature of why this <br /> road was disconnected in the first place, MnDOT appeared willing to look at the <br /> potential for state aid designation; however, he noted that it would take time to <br /> build up those MSA funds to any significant level. <br /> Councilmember McGehee opined that, while she was interested in hearing the <br /> perspective of residents, she was not in typically in favor of striped walkways on <br /> the side of streets for bicycling or walking with small children; and preferred a <br /> physical separation. Councilmember McGehee recognized that something was <br /> better than nothing; however, she was in support of including this in long-term <br /> permanent pathway planning. <br /> Councilmember Etten questioned the rationale for not being able to install trees, <br /> or signs to establish a safety zone, and whether this was primarily due to costs. <br /> Councilmember Etten opined that it would at a minimum create a visual barrier <br /> for vehicles, and could prove an effective investment for that 8-10 year period. <br />
The URL can be used to link to this page
Your browser does not support the video tag.