My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 12/03/2009
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2009
>
Agenda - Planning Commission - 12/03/2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:01:23 AM
Creation date
11/30/2009 9:32:33 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
12/03/2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
138
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 />/n..... <br />r <br />'''::__./ <br /> <br />(() <br /> <br />i( i. <br />\\>:::/! <br /> <br />Zoning Bulletin <br /> <br />September 10, 20091 Volume 31 No. 17 <br /> <br />nature of the vegetation, or building(s) provides screening that is equal <br />in protection to the required width of buffers." <br />To comply with the'condition in his business permit, Poliquin applied <br />to the Board, seeking a lesser buffer than the 100 foot buffer required <br />by S 1.6. <br />The Board approved the lesser buffer of 65 feet from Wyman's prop- <br />erty. It did so after finding that with the vegetative screening proposed by <br />Poliquin, the 65 feet of buffer was equal in protection to the 100 feet of <br />buffer without the vegetation. <br />Wyman challenged the Board's decision to approve the lesser buffer. <br />Wyman argued that the lesser. buffer permit issued by the Board consti- <br />tuted an "improperly granted variance." He argued that S 1.6 imposed <br />a binding setback requirement that could only be altered by obtaining <br />a variance from the town's Board of Appeals (the "BOA"). Further, he <br />contended that because S 1.6 "[did] not require any particular type of <br />buffering, such as landscaping, it impose[d] a straight distance require- <br />ment that [was] identical in form and purpose to a setback." <br />The BOA affirmed the Board's approval ~f Poliquin's lesser buffer <br />permit. <br />Wyman again appealed, and the superior court affirmed the BOA's <br />decision. <br />Wyman again appealed. <br /> <br />DECISION: Affirmed. <br /> <br />"'-", <br /> <br />The Supreme Judicial Court of Maine held that S 1.6-the "'buffer <br />zone' provision"-did not impose a mandatory setback requirement re- <br />quiring a variance from the town's BOA. <br />The court noted that, as defined by the Ordinance, a "variance" was a <br />"relaxation of the terms of [the] Ordinance." Here, the lesser buffer per- <br />mit did not relax or reduce the Ordinance's buffer requirements. Rather, <br />reading the two "buffer" provisions (i.e., S 1.6 and S 1.7 of the Ordi- <br />nance) together, the Ordinance authorized a developer to comply with <br />the buffer requirements by more than one acceptable means. A developer <br />could either: (1) under S 1.6, create a straight distance of 100 feet; or (2) <br />under S 1.7, demonstrate that the vegetation or topography or nature <br />of the buildings created a buffer "sufficient to afford the same level of <br />screening that the straight distance of [100] feet would afford." <br />Moreover, the court rejected Wyman's argument that S 1.6 imposed <br />a straight distance requirement that was identical in form' and purpose <br />to a setback, which required a variance. Setbacks and buffers differ, ex- <br />plained the court. Setbacks impose straight distance requirements in all <br />circumstances, whereas buffers can be satisfied with reduced distances, <br />provided there is adequate screening through some other means. Further, <br />the purpose of a setback is to prevent the construction of buildings too <br />close together, whereas the purpose of a buffer is to reduce noise and <br /> <br />@ 2009 Thomson Reuters <br /> <br />5 <br /> <br />63 <br />
The URL can be used to link to this page
Your browser does not support the video tag.