My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 05/07/2009
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2009
>
Agenda - Planning Commission - 05/07/2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:00:07 AM
Creation date
5/1/2009 12:33:35 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
05/07/2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
110
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 />{~) <br /> <br />Zoning Bulletin <br /> <br />March 25, 2009j Volume 31 No.6 <br /> <br />!{) <br /> <br />Staff ofthe city's planning department analyzed the Hectors' requests. <br />Ultimately they determined that the requested zone change "was too in- <br />tense and not in. keeping with the [c Jity's plans." The staff recommended <br />the Hectors' proposed amendments be denied. The city commission (the <br />"Commission") later accepted that recommendation and denied the Hec- <br />tors' application. <br />The Hectors appealed the Commission's decision to distriCt court. <br />Among other things, they agued that the city "cornniitted a series of con- <br />stitutional violations, [and] failed to identify and articulate reasons for <br />. denying the Hector's zoning requests." The district court found for the <br />city. <br />The Hectors appealed. On appeal, the Hectors argued that: (1) the <br />Commission acted in an arbitrary, capricious and unreasonable manner <br />when it considered the Hectors' application; (2) since the city's policy <br />plap. cQntaining goals, objectives, and standards pertainmg to zoning <br />regulations was not "passed under the required statutory procedures" <br />(it was adopted as a resolution rather than an ordinance), the city did <br />not have a comprehensive plan and was therefore in violation of state <br />statutes; and (3) meetings between city officials and the Hectors' legal <br />counsel regarding city concerns about the .Hectors' proposal amoUnted <br />to illegal contract zoning. - <br /> <br />() <br /> <br />DECISION: Affirmed. <br /> <br />The Supreme Co\lrt of North Dakota first held that the city did not <br />act arbitrarily, capriciously, or unreasonably in denying the Hectors' pro- <br />posed amendments. In so holding, the court first explained that it would <br />have to affirm the city's decision if it found it was the "product of a ra- <br />tional mental process" under which the city relied on both facts and law <br />in reaching its decision on the Hectors' proposals. The court conclud- <br />ed that the city's decision was the product of such a process because in <br />"moving through the steps, analysis and hearings" required by the city's <br />Land Development Code (the "Code"), the city strictly followed the <br />. form and procedu,re required. Moreover, the planning department's deci- <br />sion, upon which the denial was based, was formed by a "reasoned and <br />rational analysis." <br />The court next held that the city complied with statutes requiring it to <br />have a comprehensive plan for its zoning regulations. Disagreeing with <br />the Hectors' contentions, the court found that the policy statements em- <br />bodied in the city's policy plan had later been codified in the Code, and <br />the Code contained standards the city was required to follow when mak- <br />ing zoning decisions. <br />Finally, the court held that the city had not engaged in contract zon- <br />ing with the Hectors. The court explained that contract zoning occurred <br />"when a local government contracts away the exercise of its zoning <br /> <br />@ 2009 Thomson Reuters <br /> <br />7 <br /> <br />I <br />I <br />I <br />.__ ____J <br /> <br />37 <br />
The URL can be used to link to this page
Your browser does not support the video tag.