Laserfiche WebLink
Code Review <br />April 19, 2006 <br />Page 3 <br /> <br />Staff contacted and received information from a number of communities (including all <br />adjacent cities) and determined that none of the neighboring communities generally require a <br />fence or retaining wall setback. Only one community for which we had obtained <br />information—Vadnais Heights—required a setback for a fence, and only in the case of the <br />fence being a privacy fence (100% opaque) which it classified as an accessory structure <br />subject to the accessory structure setback of five feet. In addition, the City of Blaine, which <br />does not typically require a setback for a fence, does require a one foot setback for any <br />fence six feet in height. Below is a sampling of fence definitions from other communities: <br /> <br />Arden Hills Undefined <br />Blaine Any partition, structure, wall, or gate erected as a divider marker, barrier or <br />enclosure and located along the boundary, or within the required yard. <br />Circle Pines Any partition, screen, structure, wall or gate erected as a divider, marker, <br />barrier or enclosure. <br />Columbia Heights Any partition, structure, wall or gate erected as a dividing marker, barrier, <br />or enclosure of a permanent nature. <br />Coon Rapids Undefined <br />Cottage Grove Any partition, structure, wall or gate erected as a dividing marker, barrier or <br />enclosure and located along the boundary, or within the required yard. <br />Fridley Undefined <br />Little Canada Any partition, structure, wall or gate erected as a dividing marker, barrier, <br />or enclosure. <br />New Brighton Undefined <br />Shoreview Undefined <br />Vadnais Heights A barrier constructed of materials other than evergreen shrubbery erected <br />for the purpose of protection, confinement, enclosure, or privacy. The term <br />"fence" shall include barriers of at least 25 percent opacity, screening <br />walls, and opaque lines of plantings exceeding thirty inches in height. <br /> <br />Given that there seems to be no confusion regarding what a fence is, despite the absence of <br />a definition in the Code, it would not seem necessary that a definition be added. If the <br />Planning Commission believes a definition would be beneficial, staff would recommend <br />something similar to one of those listed above. More important than a definition, however, is <br />whether the Planning Commission feels the Code should be amended to require a setback <br />for fences in the City. <br /> <br />There are pros and cons relating to the implementation of a fence setback. The benefits of <br />such a setback would include virtually eliminating disputes as to whether a neighbor’s fence <br />was on the property line or over the property line, and would provide sufficient space on <br />one’s own property to maintain both sides of the fence. Another benefit would be the <br />elimination of “back-to-back” fences. Concerns or detriments of a fence setback would also <br />need careful consideration. If property owners have privacy fences set back from each <br />other, this could result in a series of “pedestrian alleys” between the properties, attracting <br />kids or persons with questionable intentions. While fence maintenance would be possible <br />with setbacks, a property owner may be less motivated to maintain the lawn area on the <br />other side of the fence, allowing weeds and tall grass to invade. This would not be a new <br />concern, however, as there will always be residents less concerned about yard appearances, <br />with or without a fence. The other impact of instituting a setback for fences would be to <br />make nearly every fence in the City a non-conforming use.