My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
05-14-2025 Council Packet
>
City Council Packets
>
2020-2029
>
2025
>
05-14-2025 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/22/2025 5:16:07 PM
Creation date
6/18/2025 9:52:33 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
131
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
2 <br /> <br />none. Staff additionally conducted a survey of residents who live on Gervais and Twin Lakes for their <br />input on the matter. Most current property owners do not have fences running along the lakeshore <br />despite having the right to install them. Out of 37 survey responses, results showed a 50/50 split <br />between those that would like to see formal regulations and those who would like the code to remain <br />as-is. Because of the lack of clear direction from residents and the lack of a basis beyond aesthetics, the <br />Planning Commission recommended that the code not create new regulations for lakeshore properties. <br />The Commission acknowledged that nothing would prohibit residents from instigating a change to the <br />Code at a later date should they determine it has become an issue. <br /> <br />Third, the Planning Commission recommended multiple minor adjustments to tighten the standards <br />such as providing a clear definition/explanation of temporary fencing, clarifying how berm height <br />would be measured, and verifying requirements related to swimming pool fences. <br /> <br />KEY CHANGES <br />1. Code Reorganization <br />The city’s existing regulations intermix residential and non-residential requirements. The proposed <br />code is restructured to clearly differentiate between general standards, residential and non- <br />residential standards, and special-purpose fences. Staff believe that this makes the code easier to <br />read, interpret, and enforce. <br /> <br />2. Clarified Application Process <br />New language has been added at the request of the City Attorney that outlines basic permit <br />submittal requirements including a fence depiction, confirmation of property line compliance, and <br />a survey if requested. The proposed code reinforces that property owners are solely responsible for <br />verifying fence placement. <br /> <br />3. Height Standards <br />The maximum height for fences remains unchanged: 6.5 feet in residential rear/side yards and 8 <br />feet in non-residential side/rear yards. The code would cap front yard fences at 4 feet across all <br />districts, a standard currently implied in the code but that is less than clear. Staff ensured that clear <br />exceptions exist for corner lots, through lots, and security fences. Lastly, the proposed ordinance <br />adds a clarifying provision which addresses fence height when placed on created berms, a common <br />practice among residents seeking greater fence height. The provision allows berms to add a <br />maximum of 1 additional foot in height. <br /> <br />4. Stormwater and Visibility <br />Clarifies that fences within five feet of property lines must not obstruct or divert stormwater flow <br />onto their neighbor’s property. The Code retains the 30-foot visibility triangle for corner lots which <br />exists as its own section in City Code already (called a “Clear Vision” standard). <br /> <br />5. Fence Maintenance and Condition <br />The proposed code beefs up the City’s maintenance standards and provides more specificity. It <br />defines failure conditions, including when a fence leans more than 10% out of vertical. The code <br />clarifies required maintenance based on material type (e.g., replacement of rotten boards or broken <br />slats). <br /> <br />6. Special-Purpose Fences
The URL can be used to link to this page
Your browser does not support the video tag.