My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Open Record 3 final rebuttal by applicant (10-17-18)
>
OnTrack
>
CU
>
2018
>
CU 18-1
>
Open Record 3 final rebuttal by applicant (10-17-18)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/17/2018 3:35:50 PM
Creation date
10/17/2018 3:35:48 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
CU
File Year
18
File Sequence Number
1
Application Name
U of O North Campus
Document Type
Public Testimony
Document_Date
10/17/2018
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
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
Virginia Gustafson Lucker, Hearings Official <br />October 17, 2018 <br />Page 4 <br />II. Rebuttal to Opponents Evidence and Arguments <br />This part of the Universitys final rebuttal describes issues raised by opponents that relate <br />to the applicable approval criteria and provides the Universitys response to those issues. For <br />each group of relevant issues, the University identifies the applicable approval criteria, <br />summarizes the opponents arguments, and provides the Universitys response. <br />A. Nature of the Universitys Plan <br /> Opponents arguments: <br />Opponents argue that the Universitys Plan is not sufficiently <br />detailed. See, e.g., Oct. 3, 2018 Letter from Paul Cziko at Issue 2; September 29, 2018 <br />Additional Testimony letter from UO Riverfront Restoration and Education Group et al. <br />(RREG) at Inadequacy of the Universitys CUP application. <br /> Opponents also advocate for multiple separate CUP applications and master site plans for <br />different areas of the S-RP zone. See, e.g., Sept. 29 RREG letter. <br />Universitys response: <br />EC 9.3725 requires a CUP for \[t\]he master site plan for <br />developments proposed in the S-S-RP zone. Although neither master plan nor master site <br />plan are defined in the Eugene Code, a master plan/master site plan is commonly understood in <br />Oregon land use law as a conceptual document that identifies proposed uses and the general <br />locations of those uses within the master plan area. The uses and facilities proposed in a master <br />plan are distinct from the design details of any specific facility contemplated in the master plan. <br />Design details are generally determined through subsequent permit processes. See, e.g., Bauer v. <br />City of Portland, 44 Or LUBA 210, 255 (2003) (affirming the citys findings that \[b\]ecause of <br />the large scale of the \[Powell Butte master plan\] and relatively long term for implementation, it <br />is not possible to accurately determine full design details and impacts at this time.) <br /> The Universitys current Plan provides greater detail than the 1988 master site plan that <br />was approved by the City and upheld by LUBA. This is made clear by comparing the narrative <br />3 <br />and site plans in the 2018 Plan with the narrative and site plans in the 1988 application. The <br />overview section of the 1988 application specifically states that the application provides only <br />broad planning guidelines and not detailed design information for specific facilities: <br />The purpose of the Master Plan and Design Guidelines is to provide <br />broadplanning and development guidelines for the implementation <br />of the Riverfront Research Park. The Master Plan, by its very <br />nature, does not provide detailed design information for every <br />building or improvement which ultimately will be constructed. <br />Instead, the Plan delineates general areas in which buildings can be <br />built, defines the overall scale of development, and outlines open <br />3 The 1988 application is in the record beginning at page 3851 of the Cziko File pdf. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.