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 10 <br />Frohnmayer Bridge and extends eastward in order enable a future extension to Knickerbocker <br />Bridge on the north side of the railroad tracks. The alignment responds to desires for public <br />access along the river, enhanced safety by activating the rivers edge and improving sightlines, <br />and improved ecological function. <br />The southern alignment utilizes the existing culvert crossing within the Millrace Slough. <br />The alignment does not extend east past Frohnmayer Bridge, as constructing a path to the <br />Knickerbocker Bridge on the north side of the railroad tracks may not be feasible due to physical <br />constraints. The alignment instead connects to Riverfront Parkway and Millrace Drive, which is <br />the current eastward travel pattern for pedestrians and bicyclists. The alignment responds to <br />desires to expand the riparian area, improve ecological function, and minimize conflicts between <br />recreation and habitat uses. <br /> Regarding the Alder Street Rail Crossing, the University acknowledges this proposed <br />future crossing by indicating it on the Pedestrian and Bicycle Primary Circulation Plan (Plan <br />Exhibit A Sheet L03) and agrees to design any building near this proposed crossing to avoid <br />interference with the crossing. The University supports the Citys Transportation System Plan <br />and will cooperate to integrate the crossing into the bike path improvements proposed in the Plan <br />at the time of a future project. <br /> G. Duration of the Plan <br /> Opponents arguments: <br />Opponents argue against the Universitys proposed 30-year <br />timeline for the CUP and Greenway permits associated with the Plan. Opponents note that, <br />under EC 9.7340, the Citys default for a CUP is 18 months, and that the maximum extension <br />associated with a modification to a CUP is an additional 18 months. See, e.g., Oct. 3 Cziko letter <br />at Issue 2. <br />Universitys response: <br />EC 9.7340 explicitly allows the City to set a longer timeline for <br />a CUP and a Greenway permit as appropriate. Permits associated with the prior 1988 master site <br />plan for the S-RP zone had a duration of 20 years, and those permits were upheld by LUBA. <br />Moreover, the City granted a three-year extension to those permits, and that extension was also <br />upheld by LUBA. <br /> The University has explained that the 30-year timeline is needed given the vast area <br />covered by the Plan and the uncertain timing of capital needed to complete development <br />contemplated by the Plan. See Plan application narrative at 93. The Citys staff supports the <br />Universitys timeline for the Plan. See Staff Report at 21. The Universitys proposed timeline <br />for the Plan is therefore consistent with EC 9.7340. <br /> The University proposes a new CUP and Greenway permit for the Plan, not a <br />modification of prior, now expired permits. The time limit associated with modification of a <br />CUP under EC 9.7340 therefore is not applicable to the Universitys application. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.