My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council - 02/22/2022
Ramsey
>
Public
>
Minutes
>
Council
>
2022
>
Minutes - Council - 02/22/2022
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 10:25:43 AM
Creation date
3/10/2022 9:01:49 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council
Document Date
02/22/2022
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
34
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
<br />a Comprehensive Plan Amendment adopted by Resolution #22-009. He stated because this was <br />already passed once and should this new resolution be adopted, it would revert back to the version <br />that was approved on January 11, 2022. <br /> <br />Councilmember Musgrove asked for an explanation of the difference between the two statements. <br /> <br />Deputy City Administrator/Community Dev. Director Hagen replied the version included in the <br />resolution on January 11, 2022 had six criteria for consideration that a developer would have to <br />meet in order for the new district to be utilized. There were two criteria, the first for in-fill type <br />developments, characteristics of the surrounding neighborhood would not support development at <br />the minimum density. A separate criteria was the property is adjacent to existing rural residential <br />large lot development and development at three plus units per acre would not meet the character <br />of the neighborhood. A developer when using this new tool would have to meet two of the six. <br />When the Planning Commission reviewed this and held the public hearing they opted to combine <br />those two statements into one with the reasoning that if the developer could meet one of the two, <br />they arguable could meet both. <br /> <br />Brian Walker, 17289 Variolite Street, stated the Council are representative of the residents. He <br />stated that there has been opposition to this development but they are not listening to the residents. <br />He didn’t understand why there is a Comp Plan when it can be changed. He didn’t feel the City <br />did their due diligence because they didn’t see if that property would support the density planned <br />for the 80-foot lot sizes. He stated at the Planning Commission meeting, he asked City Staff to <br />make sure this problem doesn’t happen with other developments. <br /> <br />Councilmember Heineman thanked Mr. Walker for his comments, passion, and work around this <br />issue. He noted that Mr. Walker’s statements that no one supports this and no one listens to the <br />residents, are broad statements. <br /> <br />Mr. Walker stated when this started with public meetings, there were 200 people on line with 100 <br />speaking or writing letters on it. He explained that somehow he has become the spokesperson to <br />speak for the residents on this. He stated because of how he has been treated, they don’t want to <br />come. <br /> <br />Councilmember Heineman stated the 2040 Comprehensive Plan, with 18 years, is not realistic to <br />think it won’t be changed. He explained the adjustments are being made because of organizations <br />like the Met Council that get involved with Ramsey business. He noted what they are doing is <br />realigning this so it works to not oppose the Met Council. He stated this is a procedural issue <br />because it has already been voted on. <br /> <br />Jeff Johnson, 4540 Bowers Drive, stated that the Councilmember Heineman stated he wants to be <br />in alignment with the Met Council and asked why. <br /> <br />Councilmember Heineman replied he didn’t want to be in alignment. This is a procedural issue <br />because of the Met Council. <br /> <br />City Council / February 22, 2022 <br />Page 11 of 34 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.