My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 07/27/2010
Ramsey
>
Public
>
Agendas
>
Council
>
2010
>
Agenda - Council - 07/27/2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 2:42:23 PM
Creation date
7/22/2010 3:18:06 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
07/27/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
200
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
Case # , , py <br />CONSIDER MEMORANDUM OF UNDERSTANDING BETWEEN CITY OF RAMSEY AND <br />ANOKA COUNTY IN REGARDS TO RUM RIVER `IN-HOLDING PARCEL' AT 18055 <br />ROANOKE ST NW <br />By: Tim Gladhill, Associate Planner <br />Background: <br />On April 13, 2010, the City Council denied a request by the Metropolitan Council to include the parcel at <br />18055 Roanoke St NW with a designation as `Pazk' on the Future Land Use Map in order to be consistent <br />with Anoka County Park plans. The request indicated that the zoning would remain residential and would <br />only be amended to `Park' if Anoka County Parks were to acquire the parcel. Following that decision, <br />Staff began working with the Metropolitan Council and Anoka County Parks regarding options moving <br />forward in order to complete the 2030 Comprehensive Plan. A suggested alternative included the City <br />entering into a Memorandum of Understanding (MOU) with Anoka County to clazify adopted and future <br />plans for the Subject Property. <br />Findings: <br />Only the Anoka County Parks' Comprehensive Plan (2006), which is the guiding document for future <br />park planning, currently includes this in-holding parcel as future acquisition. The City had the <br />opportunity to comment on that plan (including future acquisitions) prior to that plan being adopted. <br />Anoka County Parks was not required to directly notify the Subject Property of the proposed future <br />acquisition at this stage and in order to move forwazd, would need to be included in the Anoka County <br />Parks Master Plan. The Anoka County Parks Master Plan has yet to be completed and would require <br />Public Hearings, including direct notification to the Subject Property. The City should be advised that it <br />has the opportunity to comment on that plan during this phase as well and is anticipated to be completed <br />in the near future. <br />Anoka County Parks Staff is supportive of the request since Master Plan has not been completed. The <br />MOU states that if, and only if, Anoka County Parks acquires the in-holding parcel, the City would <br />consider supporting a change of Future Land Use designation as `Park'. The MOU would specify that <br />the County would not be utilizing eminent domain and that the owner could sell to any party it chooses, <br />while still stating that the City opposes the change in land use. From a Metropolitan Council perspective, <br />the MOU documents that the City and County are working towards consistent plans that will include <br />proper public processes. From a Property Owner perspective, it documents that Anoka County is only <br />interested in willing sellers and is not seeking to use eminent domain. However, the Property Owner is <br />still concerned of any plans reference the Subject Property as future park, and is opposed to the MOU. <br />The outcome of the master plan process could include the inclusion or removal of the Subject Property as <br />a future pazk/acquisition. Only the County process will determine that outcome. <br />The MOU would need to be referenced in the text of the Comprehensive Plan, but would not need to be <br />shown on the Future Land Use Map. Anoka County Parks Staff has agreed to draft MOU for review by <br />
The URL can be used to link to this page
Your browser does not support the video tag.