My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Applicant Final Argument (6-29-16)
>
OnTrack
>
WG
>
2016
>
WG 16-1
>
Applicant Final Argument (6-29-16)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/26/2017 9:48:43 AM
Creation date
7/1/2016 2:51:04 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
WG
File Year
16
File Sequence Number
1
Application Name
Eugene Towneplace Suites
Document Type
Public Comments
Document_Date
7/1/2016
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
11
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 Hearings Official <br />June 29, 2016 <br />Page 10 <br />Valley River Inn Issue 10: Willakenzie Area Plan Policies <br />Here VRI invokes a refinement plan policy that it says has not been addressed - Willakenzie <br />Area Plan, Commercial Area Design, Policy 10. There are two shortcomings with this <br />complaint. First, Policy 10 is not included in that section of the zoning code that lists the policies <br />from the plan that are to be applied in the Site Review process. EC 9.9500; and EC 9.9700 <br />(Willakenzie Area Plan Policies). The second reason is likely related to the first. Policy 10 is <br />not a mandatory policy because its operative word is "should." Because the policy is limited by <br />the word "should," the Policy is not a mandatory policy that must be complied with. VRI has not <br />shown that Policy 10 needs to be addressed at all in this application. <br />Valley River Inn Issue 11: EC 9.8815 - Willamette Greenway Permit <br />VRI complains that the Applicant has not met the Greenway standard in EC 9.8815(1): <br />"To the greatest possible degree, the intensification, change of use, or <br />development will provide the maximum possible landscaped area, open space, or <br />vegetation between the activity and the river." <br />As background on and a touchstone for how the Hearings Official applies this standard, the post- <br />hearing materials include three Greenway decisions as Exhibits F, G and H. We have also <br />included, as post-hearing Exhibit E1 & E2. These graphics provide two alternate methods of <br />calculating the proportion of development within the Willamette Greenway Boundary depending <br />on whether site landscaping is counted toward "development" or not. <br />Initially, VRI misunderstands the meaning of the standard. It is not focused onwhere to locate <br />the development activity. The proposed development is an independent variable. It is a given. <br />Then the standard looks at that area remaining and asks whether the maximum landscaped <br />area/open space/vegetation has been provided. This reading of the standard is exemplified in <br />post-hearing Exhibit H: WB 10-03 - Goodpasture Partners (2011). That involved a new bridge <br />structure with additional lanes over a channel to the Goodpature Island ponds. The Hearings <br />Official explained, at page 4: <br />"The provision does not ask whether the activity itself would provide maximum <br />landscaped area, open space, or vegetation; rather, the measuring area is the land <br />between the activity and the river, not the activity itself. The staff report <br />accurately states that there would be no change to the landscaped area, open space <br />or vegetation between the activity and the river." (emphasis in original) <br />The Greenway decision in Exhibit G stands for the same proposition. WG 10-01 was for a <br />Greenway Permit for a university parking lot. There the parking lot use encroached into the <br />Greenway. This standard was applied to examine the area between the encroaching parking lot <br />and the river, not to ask whether the parking lot should be moved back out of the Greenway. <br />
The URL can be used to link to this page
Your browser does not support the video tag.