My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 04/03/2008
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2008
>
Agenda - Planning Commission - 04/03/2008
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:44:58 AM
Creation date
3/28/2008 12:54:09 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
04/03/2008
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.
/
211
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 />.p"'"", <br />) <br /> <br />.i <br /> <br />March 25, 2008/ Volume 21 No.6 <br /> <br />found that there was no evidence that the state legislature intended <br />that the construction of a place of worship would be religious exer- <br />cise. The court found that, in the absence of discrimination against a <br />particular religious use, land use regulations intended to protect pub- <br />lichealth and safety were not subject to a strict scrutiny review un- <br />der S 52-571b. Accordingly, S 52-571b did not provide broader pro- <br />tection than RLUIPA, and thus did not apply to the Society's claim <br />for the same reasons the court found RLUIPA did not apply. <br />The court also found that the town's denial of the Society's special <br />exception application to build the temple in the residential zone was <br />supported by substantial evidence. However, the court found that <br />only three of the town's conclusions were supported by evidence. <br />The town's conclusion that the temple's design was not in har- <br />mony with the design of other buildings in the vicinity was not a <br />valid reason for denial, the court found. Strict enforcement of ar- <br />chitectural harmony restrictions would prevent any nontraditional <br />non-Judeo/Christian religion from building its temple in the town, <br />the court said. The court found that although the temple design <br />was not typical of buildings found in a rural New England setting, <br />the proposed temple was generally attractive, relatively modest <br />and not entirely out of character for a place of religious worship in <br />such a neighborhood. <br />Substantial evidence in the record did not support the town's con- <br />clusion that the proposed use would create additional traffic con- <br />gestion and hazards, the court found. The court noted that special <br />exceptions by their nature generate different and more intense traf- <br />fic than residences. Accordingly, a special exception application can <br />only be denied if it would have a significantly greater impact on traf- <br />fic congestion in the area than uses permitted as of right. The court <br />found that the town, in reaching its conclusion, wrongly determined <br />that a traffic erigineer did not rely on a traffic survey at the site. The <br />court also found that the town failed to determine that the increase <br />of traffic congestion on festival days at the temple would be signifi- <br />cantly more than a permitted use of the property would produce. <br />The town's conclusion that the Society's intention to use the prop- <br />erty as a "tele-medicine treatment site" was inconsistent with the in- <br />tent and purpose of the zoning regulations was not a valid ground <br />for denial, the court found. If the proposed use as a temple otherwise <br />complied with zoning regulations, the mere possibility that it would <br />be used for an impermissible purpose was not a legitimate ground <br />for denial, the court said. <br />However, there was evidence to support the town's conclusion <br />that the proposed use was not in harmony with the general character <br /> <br />.5 <br /> <br />141 <br />
The URL can be used to link to this page
Your browser does not support the video tag.