My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 7: Action: Ordinance on Infill Compatibility Standards Code Amendments
COE
>
City of Eugene
>
Council Agendas 2009
>
CC Agenda - 12/14/09 - City Council Meeting and Meeting of the Eugene Urban Renewal Agency
>
Item 7: Action: Ordinance on Infill Compatibility Standards Code Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:55:10 PM
Creation date
12/11/2009 10:55:42 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
12/14/2009
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.
/
439
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
Mayor and City Council <br />November 10, 2008 <br />Page 2 <br />The MiCAP history provides a recent and relevant example. City Council adopted twoMiCAP <br />ordinances in August, 2008. The Home Builders Association(HBA) appealed both ordinances. <br />The larger of the two ordinances (20417) had the “acknowledgement” language, so allsixteen <br />amendments in this ordinance were delayed until June 2009 when LUBA deniedthe appeal of <br />this ordinance. In other words, an entire set of important protections for Eugene neighborhoods <br />was delayed for ten months because of an appeal that LUBA found had no merit at all. <br />In the MiCAP appeal, it wasn’t until seven monthsafter the ordinances were adopted that LUBA <br />got around to denying the HBA’s objection to the record and moving ahead with the appeal <br />briefs and arguments. While the HBA appeal was a serious effort to have both ordinances <br />remanded, and therefore involved significant legal expenses, a party just wanting to delay an <br />ordinance long enough to file an application under existing code would not have to incur <br />significant legal costs. Using an objection to the record, the party could – for minimaleffort and <br />cost – get a delay long enough to submit theirapplication. The party could then drop the appeal <br />and not have to even produce a brief explaining the basis of their appeal. <br />To sum up: Including the “acknowledgement” language encourages any party who wants to <br />delay an ordinance long enough to avoid having to comply with new regulations to file aLUBA <br />appeal,regardless of the merits of the appeal.This makes all land use ordinances with the <br />“acknowledgement” language vulnerable to the delay-by-appealtactic, regardless of how well <br />the ordinance is crafted or how strong Council support is for the ordinance or how urgent the <br />need is for the ordinance. <br />The appropriate strategy <br />The ACA worries that an ordinance that goes into effect thirty days after adoption may be <br />remanded orreversedthereby creating an “on-again/off-again” situation. There is a very direct <br />and appropriate way to minimize this risk: Planning staff and the ACA should do a thorough job <br />of crafting the substantive ordinance provisions and providing adequate findings. <br />Again, the MiCAP experience shows where the problem lies. LUBA did notfind that the City <br />had made any error in the code amendments themselves. Instead, LUBA remanded one <br />ordinance because Planning staff had simply failed to provide obviously required findings. If <br />staff had done their job properly, LUBA would not have remanded the ordinance. <br />Neither Portland nor Corvallis use anything like the “acknowledgement” clause for two very <br />good reasons: a) Their staff told me they’ve never had a serious problem of the sort the ACA <br />worries about; and b) such language is an admission the City lacks confidence that it has acted <br />properly. <br />The City Charter provision and dealing with exceptional situations <br />The City Charter provides what Council should consider the standard provision for ordinance <br />effective dates –i.e., thirty days after adoption, irrespective of an appeal. There are situations in <br />which the effective date may need to be sooner, and the Charter provides for a 2/3 Council vote <br />to adopt an “emergency” ordinance. There may also be situations in which Council decides <br />longer than thirty days is necessaryfor affectedparties to adapt to significant changes in the <br />code. <br />
The URL can be used to link to this page
Your browser does not support the video tag.