My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
07-20-2015 Planning Commission Packet
Orono
>
Planning Commission
>
2015
>
07-20-2015 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/11/2020 8:43:11 AM
Creation date
1/12/2016 1:34:15 PM
Metadata
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.
/
373
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).
Show annotations
View images
View plain text
Average Lakeshore Setback <br /> September 21,2011 <br /> Page 2 <br /> 4) Average lakeshore setback is to be measured from the principal structure; attached decks <br /> more than 30"above grade with a guardrail will be considered principal structure. <br /> 5) Pools are considered a structure and must meet average lakeshore setbacks if they have a <br /> fence or not. <br /> The code was revised again in 1992 when the Shoreland �rdinance was adopted, reading as <br /> follows: <br /> 10.56, Subd 16(C)(6). Averase Lakeshore Setbac�k No pr�rtcipal or acce�sory structure <br /> shall be located closer to the lakeshore than the average distance from the shoreline of <br /> existing residence buildings on adjacent lots, except that thrs does not apply to stairways, <br /> lifts, landings, and lockboxes Further, the average lakeshore setback shall apply only ta <br /> classified lakes, and shall not rrpply to tributar�es. The average lakeshore setback line shall <br /> be a straight line connecting the most lakeward prohusions of the residence buildings on <br /> the inunediately adjacent lakeshore lots <br /> The impact af this revision was to codify the practice of defining the `average Iakeshore setback <br /> line' via a line rather than an average of two setback measurements. <br /> In 20U4, Section 10.56 Subd. 16(C)(6) was amended via Ord. No. 11; 3'� Series by addi.ng a <br /> clause that provided staff the ability to administratively approve an average setback <br /> encroachment when the average lakeshore setback can not be met. That amendment reads: <br /> a) In instances where the average lakeshore setback can not be met, administratfve <br /> approval may be granted at the discretion of the Planning Director provided no lake views <br /> oJ an adjacent lakeshore lot are obstructed and adJacent nefghbors p�ovide written <br /> �PProva� <br /> The words "can not be met"were/are critical to this language and were chosen purposely to limit <br /> tl�e administrative approval o�to those situations where the defined average setback line leaves <br /> a property without a functional buildable envelope. An example would be the last lot on a point <br /> such as Bracketts Point, where a line drawn between the two adjacent lakeshore homes would <br /> leave virtually no buildable area within the point lot. The administrative approval is not intended <br /> to give staff the discretion to grant approval merely upon a showing that a proposed <br /> encroachment will not impact a neighbor's views of the lake. <br /> Interpretations and Administration <br /> I believe the original intent of the average setback rule was to protect the lake views a lakeshore <br /> property owner enjoys over their neighbor's lakeshore yard, and avoid the "tunnel" effect of <br /> being set back further from the lake than one's neighbors. As in many of aur codes, the <br /> interpretation and administration of this code has necessarily evolved over time as new or unique <br /> situations arise. It should also be noted that the concept of average setback was not required by <br /> the DNR to be addressed in local5horeland ordinances. <br />
The URL can be used to link to this page
Your browser does not support the video tag.