My WebLink
|
Help
|
About
|
Sign Out
Home
pm_020710
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
200x
>
2002
>
pm_020710
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/17/2007 3:36:03 PM
Creation date
12/15/2004 8:04:13 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
7/10/2002
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
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 />Gary Wood, 3060 W. Owasso Blvd., said the proposal for protective or safety fencing was a good idea. Small lots or <br />narrow lots may have problems as well as boat houses. For existing buildings, a fence should be allowed ten feet in front <br />of the house. There are some pre-existing fences. <br /> <br />Member Bakeman asked how the fence could be protective (chain link) fence if only on one side. She expressed concern <br />about fenced in shoreland lots as inconsistent with shoreland protection. Property owners could fence in the lot area <br />opposite the lake shore. The height (42") and chain link are objectionable. Leave the 75' setback clear of fences. Privacy <br />can be obtained with landscaping. <br /> <br />Member Mulder noted, as an option, the City could require variances for protective fences. <br /> <br />Chair Duncan felt that property owners should be able to restrict or fence the yards. <br /> <br />Member Peper noted that 3.5 feet is conservative. <br /> <br />There being no comment, Chair Duncan closed the hearing. <br /> <br />Motion: Motion by Member Mulder, second by Member Traynor, to make a recommendation to the City Council <br />that lakes and wetlands 3, 4, 5 should be subject to regulations allowing certain fence types (chain link), heights <br />(42"), and locations (to within 10 feet of the OHWL) for parcels adjacent to shoreland and wetland areas. <br /> <br />Ayes: 3 <br />Nays: 3 <br /> <br />Motion failed. <br /> <br />Member Bakeman felt 20 feet was not enough setback, and any such fence should only be approved by variance or <br />conditional use permit. Member Bakeman recommended natural shoreline. <br /> <br />Member Mulder said fence variances may be arbitrary and/or capricious. <br /> <br />Member Traynor agrees with Member Bakeman on the need for permits or variances. Could a fence be required to have <br />landscaping on the side of the fence facing the body of water? <br /> <br />Chair Duncan stated landscaping which is permitted could be used for privacy, which would destroy a vista. <br /> <br />Member Mulder expressed concern with the issuance of variances - 15 years later the fence cannot be taken down. <br /> <br />Thomas Paschke reminded the Planning Commission that the chain link fence was an option to an opaque fence; a safety <br />vs. a privacy fence. <br /> <br />Member Peper stated lake homes are becoming very expensive; fences on such lots will be appealing. <br /> <br />Motion: Member Mulder moved, seconded by Member Bakeman to forward this matter to the Council without <br />recommendation. <br /> <br />Member Ipsen recommended property owner flexibility. He said he was confused and wished to abstain. <br /> <br />Mayor Kysylyczyn suggested that this is not a critical issue; the Commission could take this up at a later date with a <br />recommendation. <br /> <br />Member Mulder asked for a matrix of what is allowed by the amendment vs. what could be approved under current Code. <br /> <br />Thomas Paschke asked for additional time; table it until next month for more information. <br /> <br />Motion: Member Ipsen moved, seconded by Member Duncan, to reconsider the original motion. <br /> <br />Ayes: 4 <br />Nays: 2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.