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 11 <br /> Road B. As he had stated at the PWETC, the current situation is unsafe, with no <br /> pedestrian refuge, with that road still having a fair amount of traffic; and a lot of <br /> people walking or biking along it. Mr. Larson stated that he really looked forward <br /> to a neighborhood meeting to discuss options as outlined by Mr. Schwartz; opin- <br /> ing that there needed to be a full discussion on the preferences of the neighbors. <br /> Mr. Larson stated that he could be supportive of this short-term solution if the <br /> City was committed to looking at it again in 10 years for a permanent solution; <br /> even though he recognized that interim projects often became permanent. If the <br /> neighborhood could get a 6' paved pathway and 2' buffer, Mr. Larson opined that <br /> a lot of people in the neighborhood would be quite pleased, with the understand- <br /> ing that the road and trail would be separated at some future point. <br /> John Bachhuber; 2223 Marion Road <br /> Mr. Bachhuber thanked the City Council for looking at this issue; one of im- <br /> portance to him and his young family. At the current time, Mr. Bachhuber stated <br /> that it created a challenge and he couldn't allow his children to bike in the neigh- <br /> borhood as there was no safe place for a loop. Mr. Bachhuber stated that he <br /> shared the concerns of Mr. Grefenberg in not wanting a half-way solution that still <br /> created risk; and expressed appreciation for a short- and long-term solution. As <br /> part of the short-term solution, Mr. Bachhuber asked that the City consider rumble <br /> strips as part of the project, as a way to alert vehicles to pedestrians/bicycles, <br /> should they be going off course, given this frequent problem for walkers along the <br /> road. <br /> With no additional audience members coming forward to speak, Mayor Roe end- <br /> ed public comment at this time for further City Council discussion and staff direc- <br /> tion. <br /> Mayor Roe thanked residents for their comments; reiterating the process that <br /> would occur with additional opportunities for staff to meet with residents as a <br /> proposal is refined. Mayor Roe noted that this would be prior to the formalized <br /> process for a project of this type, as a feasibility report or study was authorized, <br /> allowing additional opportunities for public comment and before subsequent ac- <br /> tion approving bids. As always, Mayor Roe noted that staff and the City Council <br /> welcomed public comment throughout the process. <br /> At the request of Councilmember Willmus, Mr. Schwartz advised that, with holi- <br /> days and new engineering staff coming on board after Thanksgiving and the need <br /> to make them part of this discussion and meetings with neighbors, he would antic- <br /> ipate early January for neighborhood meetings; with a report back to the City <br /> Council late in January. <br /> As part of this project, Councilmember Willmus suggested that staff look at all <br /> potential funding sources, including the Park Renewal Program or potential turn- <br /> back monies; as well as other sources of funding that may be appropriate, and <br />
The URL can be used to link to this page
Your browser does not support the video tag.