My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 5 - PH on Laurel Hill Plan
COE
>
City of Eugene
>
Council Agendas 2004
>
CCAgenda-11/08/04Mtg
>
Item 5 - PH on Laurel Hill Plan
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:47:57 PM
Creation date
11/4/2004 8:59:35 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
11/8/2004
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
474
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
Comments submitted to the City of Eugene Planning I~!°~0~-, :i!;OE~/E <br /> regarding the Zone Change Application for the parcel identified' <br /> on the County Assessor's Map 18-03-03-2-3 as Tax Lots 199, <br /> <br /> Submitted by the Laurel Hill Valley Citizens neighborh~l~~V ~ D <br /> August 5, 2004. <br /> <br /> Since this application has been submitted concurrently with a refmement plan <br />application, I may repeat some of the arguments which have already been submitted to <br />you by the Laurel Hill Valley Citizens in opposition of the Refinement Plan Change <br />Application. The two applications are linked because the same arguments have b¢on <br />submitted in support of both plan change and zone change. <br /> <br />Criteria #2 The proposed zone change is consistent with applicable refinement <br />plans. In the event of inconsistencies between these plans and the Metro Plan the <br />Metro Plan controls. <br /> <br /> The map included in the Laurel Hill Valley Refinement Plan, clearly shows that <br />the subject property is not within the area designated for commercial development. The <br />Applicant's argument that the subject property is adjacent to the commercial node does <br />not change the fact that the subject property is not included in that node. We refer you to <br />Exhibit E in the application, "Findings of Hearing Official", page 3, Paragraph 4 where it <br />is the finding of the Hearings Official that: <br /> "The subject property is not with this commercial area of the development node. <br /> This specific map [referred to above] should prevail over the more general Laurel <br /> Hill Refinement Plan Land Use Map above referenced". <br /> The Applicant argues that "this proposal will allow development that will provide <br />for the future neighborhood commercial needs of Laurel Hill residents". We refer you to <br />again to Exhibit E of the application, "Zone Change Staff Report", page 4, last paragraph <br />where the Staff evaluation states that: <br />"Since no portion of the development node has been developed to date, there <br />appears to be no public need to designate additional land as commercial". <br />Nothing substantive has changed since these Staff findings, there has been no further <br />development since that date, other than the realignment of Moon Mountain Drive, and we <br />argue that Staff's reasoning remains correct. <br /> Further more, in Policy 5 of the East Laurel Hill Plan, as noted by the Applicant <br />(P.8), states that: <br /> "no additional sector of East Laurel Hill shall be designated for commercial <br />purposes until a public need has been demonstrated". <br />The Applicant has failed to demonstrate any such need at this time, referring instead to "a <br />public need for effective land use planning". Clearly, this amounts to a conflation of <br />needs because a need for more commercial development in the Laurel Hill development <br />is not the same thing as the general need for intelligent land use planning, a need that will <br />always exist even if all of Laurel Hill Valley was developed as commercial property. <br /> <br /> I-A-1 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.