My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 1: Ordinance on Oregon West Management
COE
>
City of Eugene
>
Council Agendas 2008
>
CC Agenda - 02/19/08 Public Hearing
>
Item 1: Ordinance on Oregon West Management
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:18:00 PM
Creation date
2/15/2008 11:03:25 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
2/19/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.
/
459
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 />requirements of Goal 5, and therefore, with regard to OAR 660-023-250(3)(a), the proposed <br />PAPA does not aftect a GoalS resource and the City is not required to apply Goal 5. <br /> <br />Furthermore, in Larson v. Wallowa County, 23 Or LUBA 527 (1992), the Land Use Board of <br />Appeals ruled that if property is not included in the Goal 5 inventory of the acknowledged <br />comprehensive plan, and a proposed zone change does not affect that inventory, a local <br />goverriment is not required to consider whether the property should be included on that <br />inventory. The same logic is rightly applied here. <br /> <br />Secondly, addressing OAR 660-023-250(3)(b): The changes sought by this application will not <br />allow new uses that could conflict with a signiticant Goal 5 resource site. There are no Goal 5 <br />resources on the site itself. None of the various studies, inventories, refinement plans, and <br />facilities plans has listed this specif1c site in an adopted inventory, declared it a significant <br />resource, applied a Goal 5 resource overlay, or otherwise regulated or limited the redevelopment <br />of the site as a Goal 5 resource. <br /> <br />Natural Resources are addressed in the City of Eugene Goal 5: Inventory and Water Resources <br />Conservation Plan, 2005 which fulfins the State of Oregon's GoalS requirement for local <br />governments to protect significant riparian corridors, upland wildlife habitat and wetlands. The <br />subject site is not included in any of the plan's inventory maps or tables, nor has it been <br />designated with a Waterside Protection (/WP) or Water Resources Conservation (/WR) Overlay <br />Zone. <br /> <br />Because the changes proposed by the application do not create or amend any portion of an <br />acknowledged plan, or any code provision adopted in order to protect a significant Goal 5 <br />resource or to address specific requirements of GoalS, all of these safeguards will remain in <br />effect. <br /> <br />Lastly, addressing OAR 660-023-250(3)(c): The changes sought by this application do not <br />amend the acknowledged Urban Growth Boundary. <br /> <br />Conclusion: <br />Oregon Administrative Rule 660-023-0250 "Applicability" stipulates that local governments are <br />required to apply Goal 5 when considering Post Acknowledgment Plan Amendments if the <br />amendment affects a Goal S resource. For the purposes of that rule, the section lists three <br />circumstances (OAR 660-023-0250(3){a), (b), and (c) quoted above) under which, and only <br />under which, a Post Acknowledgment Plan Amendment would affect a Goal 5 resource. As <br />evidenced above, none of the three circumstances are raised by the proposed anlcndments, and <br />therefore the amendments will not affect a Goal 5 resource. The City of Eugene is not required <br />to apply Goal 5 when considering the consistency of the proposal. The City of Eugene can find <br />that the action requested by this application is consistent with Statewide Planning GoalS. <br /> <br />Santa Clara ~ Zone Change Application <br />Written Statement - August 2,2007 <br /> <br />Page 30 of 41 <br />
The URL can be used to link to this page
Your browser does not support the video tag.