My WebLink
|
Help
|
About
|
Sign Out
Home
Minutes - Council - 05/26/2020
Ramsey
>
Public
>
Minutes
>
Council
>
2020
>
Minutes - Council - 05/26/2020
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 11:20:56 AM
Creation date
7/22/2020 1:46:48 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Minutes
Meeting Type
Council
Document Date
05/26/2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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 /> <br />Lonnie Grey, 17530 Nowthen Boulevard NW, stated that he is adjacent to the Hunt property. He <br />echoed the comments from the previous speaker related to traffic and the other concerns expressed. <br />He stated that there is a lot of ATV and snowmobile traffic in the ditches. He asked how the City <br />would deal with the rural activity around a property that would be more of a development. He <br />stated that the roads would not accommodate this increase in density. He stated that he is against <br />the rezoning requests. <br /> <br />Deputy City Administrator Gladhill reviewed written comments into the record. He read aloud <br />th <br />the comments from the resident at 7630 160 Avenue NW in opposition of the requests and the <br />additional pressure that this density would place on wildlife, infrastructure, City budgeting and <br />local businesses. He read another statement from the residents at 17314 Sapphire Street NW, in <br />th <br />opposition of the requests. He read another statement from the resident at 7041 175 Avenue NW, <br />also in opposition of the request noting that 98 percent of those the resident polled were in <br />objection to the 55- and 65-foot lots. <br /> <br />Ben Schmidt, The Excelsior Group, stated that they submitted additional information on why the <br />requested lot sizes were selected. He stated that the City’s plan identifies a density of three units <br />per acre and this plan would have a density of 2.7 lots per acre. He stated that the idea is not to <br />request additional density but to provide choices for the homebuyers and different types of housing <br />with different price points. He stated that he has completed a concept plan with 80-foot lots, that <br />was submitted to the City today, in example and noted that plan includes 327 homes as opposed <br />to the 343 homes shown on this concept plan. He stated that their proposed plan allows different <br />choices and for creativity such as a pond with meandering streets, rather than having straight streets <br />with the highest number of units possible. <br /> <br />Deputy City Administrator Gladhill read a statement received from the resident at 17289 Variolite <br />Street NW, who stated that realtors are looking for one acre lots as they are in demand by buyers. <br /> <br />Deputy City Administrator Gladhill noted that the property is zoned for 80-foot-wide lots and <br />down zoning could have a financial impact to the City. <br /> <br />Acting Mayor Riley stated that the Council has heard the comments expressed at the Planning <br />Commission meeting, read the written comments, and heard the comments tonight. He thanked <br />all of the residents that contributed throughout the process. <br /> <br />Councilmember Kuzma asked if the applicant has a plan for 80-foot-wide lots that would result in <br />327 homes. <br /> <br />Mr. Schmidt replied that they did provide a plan to staff today with 327 lots 80 feet in width. <br /> <br />Councilmember Musgrove asked for details on how the density range is calculated. <br /> <br />Deputy City Administrator Gladhill provided details on the density calculation and how it was <br />determined. <br /> <br />City Council / May 26, 2020 <br />Page 11 of 16 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.