My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 04/06/1999
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
1999
>
Agenda - Planning Commission - 04/06/1999
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:16:41 AM
Creation date
9/16/2003 9:33:53 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
04/06/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
191
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
Page 6 -- February 25, 1999 Z.B. <br /> <br /> with the developer's complete application during a public hearing and approved <br /> the request with certain conditions to ensure the project complied with city <br /> codes. <br /> Nine years later, a homeowners association protested the developer's still- <br /> uncompleted development by challenging its special use permit. According to <br /> the association, the city arbitrarily issued the permit without enough evidence. <br /> The association also claimed that even if the permit was properly granted, the <br /> zoning ordinance's sunset clause prohibited the develop6r from completing the <br /> project. In 1997, the city had passed a sunset clause that made a special use <br /> permit null and void if the city council determined that "no significant progress" <br /> had been made in the first 12 months after approval of the permit. <br /> The city claimed it properly issued the permit and argued the sunset clause <br /> didn't apply to previously issued special use permits. <br /> The court concluded the city didn't act arbitrarily in issuing the permit. It also <br /> found the sunset clause didn't apply to the developer's previously issued permit. <br /> The homeowners' association appealed. <br /> DECISION: Affirmed. <br /> The sunset clause didn't apply because it was enacted long after the city <br /> issued the developer a special permit. <br /> There was more than enough evidence that the city properly granted the <br />developer a special permit. According to its zoning ordinance, the city had to <br />consider the planning commission's recommendation, examine the proposed <br />permit's effect on the surrounding area, and determine that the permit wouldn't <br />harm the public. The record showed the'city's planning commission had rec- <br />ommended approving the permit request after reviewing the application and <br />the property. The city council considered the commission's recommendation <br />and the developer's completed application and determined that a special per- <br />mit was appropriate provided the developer abided by certain conditions. <br /> The city's 1997 sunset clause didn't apply to the developer's grocery and <br />gas station. Nothing in the clause indicated it was to apply retroactively, and no <br />law could apply retroactively unless it was clearly meant to do so. Moreover, <br />when the city planning commission recommended enacting the sunset clause, <br />it specifically noted the clause wouldn't affect previously issued permits. <br />see also: Swanson v. City of Bloomington, 421 N. W. 2d 307 (1988). <br />see also: Frank's Nursery Sales lnc. v. City of Roseville, 295N. W.2d 604 (1980). <br /> <br />Lot Size Does public easement area count toward minimum lot size? <br /> <br />Citation: Marshall v. City of Yachats, Court of Appeals of Oregon, <br />No. CA A103508 (1999) <br /> Forrester wanted to build a house on his property in the city of Yachats, Ore. <br />Part of his property was covered by a public easement for an unimproved county <br />road that had been established in 1890. The county had transferred its rights to <br />the state parks department, which used the easement as a public wal 'king trail. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.