My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 01/14/2025
Ramsey
>
Public
>
Agendas
>
Council
>
2025
>
Agenda - Council - 01/14/2025
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 9:53:14 AM
Creation date
1/15/2025 8:14:47 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
01/14/2025
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
357
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
i <br /> iE <br /> separation from the roadway and/or adjacent properties. He noted that some communities have no <br /> setback requirement while others have a five foot, or fence requirement. He believed that there <br /> should be some time of setback from the roadway, and perhaps from a sidewalk or trail. <br /> Commissioner Burgess commented that he believes it would be helpful to have some kind of <br /> setback,within the range of 18 inches to three feet,from the street and sidewalks and trails. <br /> Board Member Hagerty stated that he also agrees with a setback, a minimum of 18 inches or two <br /> to three feet on all sides of the lawn unless there is a fence. He stated that he likes the idea of <br /> havinga sign to notify people of what is going on. He also liked the once-a-- ear maintenance <br /> � Yp p g g y <br /> requirement. <br /> Commissioner Houts stated that she does not like requiring a setback outside of the MUSA lines <br /> as that area is rural, but does support a setback for properties within the MUSA. <br /> Commissioner Burgess asked if there would be guidance on what the sign should say, or whether <br /> the City would create the signs for purchase. r <br /> Senior Planner Anderson replied that the City would not provide the signage. He noted that there <br /> are standardized signs that people could obtain. He explained that the language is not as important <br /> because the intention is just to let the public know that what they are seeing is a naturalized <br /> landscape and not a situation where someone just stopped mowing. He noted that some cities only <br /> p J pp g Y <br /> require signage during the transition period when it does not look great. He stated that he could <br /> q �. <br /> send out examples of signs that the City uses on its own property. <br /> Chair erson Fetterle agreed that the hardest period is that transition period. She asked if the <br /> p Y g p p Y <br /> should consider a notice, where a letter would go out to the neighborhood after someone is <br /> approved. <br /> Senior Planner Anderson replied that he has not seen any examples that require notification to r <br /> neighbors and would be hesitant to do that. <br /> Councilmember woestehoff asked if there was a reason this was drafted as part of the nuisance <br /> section rather than the residential landscaping standards. <br /> Senior Planner Anderson replied that the draft was added to that section as that is where the <br /> nuisance language currently exists for yard vegetation over 8 inches. He noted that the language <br /> could be relocated, and a reference could be made to the nuisance section linking those areas. <br /> Councilmember woestehoff commented that makes sense, but if there are going to be different <br /> standards for different areas,perhaps it should be relocated. <br /> Board Member Bernard commented that he would prefer to split the language into different <br /> sections, rural versus MUSA. He commented that he abuts City property and does not believe a <br /> buffer would be needed, whereas a lot in a more developed area would perhaps appreciate the <br /> buffer. <br /> Environmental Policy Board/October 21, 2024 <br /> Page 3 of 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.