My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Public Works Committee - 02/20/2018
Ramsey
>
Public
>
Agendas
>
Public Works Committee
>
2010 - 2019
>
2018
>
Agenda - Public Works Committee - 02/20/2018
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2025 11:16:28 AM
Creation date
2/16/2018 9:45:06 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Public Works Committee
Document Date
02/20/2018
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
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
Councilmember Kuzma asked how this would interact with the efforts of Mr. Tinklenberg. <br />Community Development Director Gladhill stated that Mr. Tinklenberg believes that this is a <br />necessary step and will help with the City's momentum. He noted that once there is more <br />certainty in the planning, it will increase the priority ranking of the project. <br />Chairperson Riley asked for additional details on the planning that has been done for the rail <br />crossings. <br />City Engineer Westby replied that the previous funding applications for the Ramsey rail <br />applications used the cost estimate that was obtained from Anoka County. He stated that the <br />City has not expended funds to do any additional design work on that. He stated that the more <br />information, the better. He noted that the better the estimate and design work is, the higher <br />ranking and more opportunity you will have. He stated that the City will no longer be competing <br />with Anoka once their funding is completed. He explained that the additional design work will <br />solve some of the unknowns including property acquisition costs and whether the crossings <br />should be underpasses or overpasses. <br />Chairperson Riley asked if the coalition partners have looked at this design proposal. <br />Community Development Director Gladhill stated that staff first wanted to obtain support from <br />the City Council prior to sharing that proposal. He noted that the partners are aware of the desire <br />to complete the design work. He stated that the recommendation could be to move this forward, <br />contingent on sharing the information with the design partners. <br />Councilmember Johns stated that perhaps the proposal could be shared with the partners prior to <br />this moving forward to City Council. <br />Chairperson Riley noted that there are five public meetings scheduled and stated that seems like <br />a lot of meetings. <br />Community Development Director Gladhill noted that the temperature of the public could be <br />gauged as the process moves along and if that number of meetings is not needed, the schedule <br />can be scaled down. He noted that some business owners and stakeholders like more one on one <br />interaction while others like an open house meeting style. He noted that staff can scale back if <br />that seems appropriate as this moves forward. He stated that all of these options are still within <br />the overall vision. He stated that this would provide flexibility in that smaller pieces can be <br />constructed individually, or they could also be partnered together. He noted that the details will <br />provide a lot of information, and used the example of the cost for property acquisition. He stated <br />that in some instances, a few feet make the difference between partial acquisition and whole <br />parcel acquisition which have major cost differences. <br />Chairperson Riley stated that he would want to ensure that this is in line with the coalition and <br />wants to prevent the perception that Ramsey is going rogue and working on their own project. <br />Public Works Committee / January 16, 2018 <br />Page 6 of 14 <br />
The URL can be used to link to this page
Your browser does not support the video tag.