My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packet
>
OnTrack
>
CA
>
2022
>
CA 22-1
>
Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/1/2022 2:53:43 PM
Creation date
6/8/2022 4:14:28 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
CA
File Year
22
File Sequence Number
1
Application Name
Willamette River Greenway Code Amendments
Document Type
Staff Report
Document_Date
6/14/2022
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
91
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
DRAFT WILLAMETTE RIVER GREENWAY DESIGN PLAN <br />3.0 SETBACK DETERMINATION <br />3.1 OVERVIEW <br />This section discusses the setback component of Goal 15, previously established setbacks, prior approved <br />Willamette Greenway permits, and the recommended approach for establishing a Willamette River <br />Greenway setback as a component of the Design Plan. <br />3.2 GOAL 15 WRG SETBACK PROVISIONS <br />OAR 660-015-0005 Goal 15: Willamette River Greenway, and Eugene Code (EC) 9.8815 Willamette Greenway <br />Permit Approval Criteria and Standards, provide standards for the establishment of setback lines to keep <br />structures separated from the river. Section C.3 of Goal 15 provides use management considerations <br />and requirements for local plans and implementing measures. Subsection (k) provides for the Greenway <br />setback. Other relevant considerations include providing adequate public access to the river, protection of <br />significant fish and wildlife habitat, and enhancing and protecting the natural vegetative fringe along the <br />river. EC 9.8815(5)(a), nested within the approval criteria for Willamette Greenway Permits, provides that <br />intensification, changes of use, or development shall require the establishment of a setback line to keep <br />structures separated from the river. <br />OAR 660-015-0005, C.31. Greenway Setback. <br />A setback line will be established to keep structures separated from the river in order to protect, maintain <br />preserve and enhance the natural, scenic, historic and recreational qualities of the Willamette River <br />Greenway, as identified in the Greenway Inventories. The setback line shall not apply to water-related or <br />water-dependent uses. <br />EC 9.8815(5)(a). <br />[I]ntensification, change of use, or development shall conform with the following applicable standards: (a) <br />Establishment of adequate setback lines to keep structures separated from the Willamette River to protect, <br />maintain, preserve, and enhance the natural, scenic, historic, and recreational qualities of the Willamette <br />Greenway. Setback lines need not apply to water related or water dependent activities as defined in the <br />Oregon Statewide Planning Goals and Guidelines (OAR 660-15-000 et seq.). <br />Both the OAR and Eugene Code exclude water-related and water-dependent uses from the setback, <br />however neither one includes a definition for the uses. OAR 632-005-0020 provides definitions for the <br />terms: <br />Water-related uses are defined as: <br />"Uses which are not directly dependent upon access to a water body, but which provide goods or services <br />that are directly associated with water-dependent land or waterway use, and which, if not located adjacent <br />to water, would result in a public loss of quality in the goods or services offered. Except as necessary for <br />water-dependent or water-related uses or facilities, residences, parking lots, spoil and dump sites, roads and <br />highways, restaurants, businesses, factories, and trailer parks are not generally considered dependent on or <br />related to water location needs." <br /> - Page 61 of 91 <br />WILLAMETTE RIVER GREENWAY CODE AMENDMENTS 26 <br />
The URL can be used to link to this page
Your browser does not support the video tag.