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 />4.0 DESIGN PLAN FINDINGS <br />4.1 OVERVIEW <br />Goal 15 allows for adoption of an administrative review procedure and design plan as an alternative to the <br />subjective approval criteria and public hearings specified in subsections 3(a) through (e) of the goal. If a <br />city chooses to prepare and adopt a design plan and administrative review procedure for a development <br />within the Greenway, the design plan must provide findings showing compliance the following criteria, set <br />out in 3(b)(1) and (2) of paragraph F of Goal 15: <br />To the greatest possible degree: <br />The intensification, change of use or development will provide the maximum possible landscaped area, <br />open space or vegetation between the activity and the river. <br />Necessary public access will be provided to and along the river by appropriate legal means. <br />4.2 FINDINGS <br />Following are findings of compliance with the aforementioned criteria for the preparation and adoption of <br />the Design Plan. <br />OAR 660-015-0005 F.3(b)(1) <br />To the greatest possible degree, the intensification, change of use or development will provide <br />the maximum possible landscaped area, open space or vegetation between the activity and the <br />river. <br />The Design Plan and associated land use code amendments establish a Greenway Setback to keep <br />structures separated from the Willamette River and to protect, maintain, preserve, and enhance the <br />natural, scenic, historic, and recreational qualities of the Willamette Greenway. The Greenway Setback is <br />shown on Map 3.1 and will apply when an applicant to develop housing on a property within the Greenway <br />chooses to proceed under the clear and objective standards established by the land use code amendments <br />associated with this Design Plan. The Greenway Setback applicable to properties subject to the Willakenzie <br />Area Plan is 35 feet from the top of bank of the Willamette River, in accordance with the language of <br />that plan. The setback applicable to properties zoned S-DR Downtown Riverfront Special Area Zone is <br />in accordance with the requirements of EC 9.3147 and Figure 9.3135 S-DR Zone Regulating Plan. The <br />Greenway Setback applicable to properties zoned S-RP Riverfront Park Special Area Zone is 35 feet from top <br />of bank, as established in EC 9.3715. For all other properties within the Greenway Boundary and subject <br />to the setback, the land use code amendments associated with this Design Plan provide for a setback of <br />100 feet from the top of bank of the Willamette River. These setbacks are collectively referred to in these <br />findings as the Greenway Setback. <br />In concert with the administrative review procedure and clear and objective standards included in the <br />land use code amendments associated with this Design Plan, the Greenway Setback will, to the greatest <br />possible degree, provide the maximum possible landscaped area, open space or vegetation between the <br />housing development and the Willamette River. <br /> - Page 68 of 91 <br />WILLAMETTE RIVER GREENWAY CODE AMENDMENTS 33 <br />
The URL can be used to link to this page
Your browser does not support the video tag.