My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Applicant Final Argument
>
OnTrack
>
PDT
>
2015
>
PDT 15-1
>
Applicant Final Argument
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/24/2015 4:00:58 PM
Creation date
11/23/2015 3:51:32 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
15
File Sequence Number
1
Application Name
CHAMOTEE
Document Type
Public Comments
Document_Date
11/23/2015
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
20
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
Eugene Hearing Official <br />November 23, 2015 <br />Page 17 <br />It is most appropriate to apply the "unreasonable cost or delay" clause of the statute in an "as <br />applied" challenge to a code provision, as here. Indeed, in Home Builders LUBA explained that <br />the applicability of this clause (then codified at ORS 197.307(6)) will be most apparent in an as <br />applied context. <br />ORS 197.307(6) prohibits standards, conditions or procedures for approval that, <br />either in themselves or cumulatively, discourage needed housing "through <br />unreasonable cost or delay." The statute does not prohibit reasonable cost or <br />delay. In our view, the question of whether approval standards or procedures <br />discourage needed housing through unreasonable cost or delay cannot, in most <br />cases, be resolved in the abstract, in a challenge to a legislative decision that <br />adopts such standards or procedures. In the absence of actual application of <br />standards or procedures in a particular case, it is difficult to see how any party <br />could demonstrate what the delay or additional cost might be, whether that delay <br />or cost is reasonable or unreasonable, and whether that delay or cost discourages <br />needed housing, either alone or in combination with other standards or <br />procedures. Because different sets of standards and procedures will apply to <br />different applications in different areas of the city, demonstrating in the abstract <br />that standards or procedures cumulatively discourage needed housing is rendered <br />even more difficult. These difficulties are apparent in the present case, because <br />the petitions for review make no attempt to demonstrate why any standards or <br />procedures, alone or cumulatively, result in unreasonable cost or delay, much less <br />what those costs or delays might be. While petitioners argue that certain standards <br />or procedures are likely to increase cost or delay, they make no effort to <br />demonstrate that such increased cost or delay is unreasonable, alone or <br />cumulatively. With the possible exception discussed below, we believe it is highly <br />unlikely that such a demonstration can be made or, if made, reviewed in a <br />meaningful manner, except in the context of an "as-applied" challenge. [Home <br />Builders at 422-423]. <br />In Home Builders LUBA went on to strike down, as contrary to the statute, a code provision that <br />required geotechnical information to be filed with an application when there was no standard <br />relating to that information. That provision was facially contrary to the statute. That provision, <br />while clear and objective, was facially contrary to the needed housing statute. <br />The city's statewide Goal 7 (Areas Subject to Natural Disasters and Hazards) <br />findings discuss the geotechnical analysis requirement at LUCU 9.6710, and <br />suggest that "development must occur in accordance with the analysis' <br />recommendations." Record 496. However, the city does not identify any standard <br />that imposes that requirement, or that relies on the required geotechnical analysis <br />in any way. As far as we can tell, the geotechnical analysis requirement functions <br />only to supply the city with potentially expensive information that has no bearing <br />on any approval standard. Consequently, we agree with petitioners that the <br />requirement violates ORS 197.307(6). [41 Or LUBA at 423-424] <br />
The URL can be used to link to this page
Your browser does not support the video tag.