My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 3A: Approval of City Council Minutes
COE
>
City of Eugene
>
Council Agendas 2006
>
CC Agenda - 01/09/06 Mtg
>
Item 3A: Approval of City Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 1:07:56 PM
Creation date
1/6/2006 2:59:39 PM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
1/9/2006
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
79
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
<br /> <br />Mr. Nystrom called attention to the motions before the council. He thought, in general, that staff had <br />worked with the various motions and tried to respond to council concerns or questions that had been raised. <br />He hoped it helped to clarify or alleviate concerns that had been expressed. He said staff was in support of <br />the amendments by and large. He asked the council to consider adoption of the ordinance with the proposed <br />motions before it. <br /> <br />Councilor Poling, seconded by Councilor Solomon, moved that the City Council adopt <br />Council Bill 4910, an ordinance concerning minor land use code amendments. <br /> <br />Councilor Papé said he did not find language on corner lots and fence heights, a concern of his constituents. <br />Mr. Nystrom responded that an amendment regarding this item had initially been considered but enough <br />concerns were expressed about policy issues surrounding it that it had been deferred to the second round of <br />code amendments. <br /> <br />City Attorney Glenn Klein clarified at Councilor Kelly’s request that the Staff Recommended Motions (A) <br />through (E) provided in Attachment A to the Agenda Item Summary (AIS) could be made individually and <br />could be referenced by letter. <br /> <br />Councilor Poling, seconded by Councilor Solomon, moved to amend the motion with Staff <br />Recommended Motion (A) from page 235 of the Agenda Item Summary. Roll call vote; <br />the motion passed unanimously, 8:0. <br /> <br />Councilor Poling, seconded by Councilor Solomon, moved to amend the motion with Staff <br />Recommended Motion (B) from page 235 of the Agenda Item Summary. <br /> <br />Councilor Bettman, seconded by Councilor Ortiz, moved to replace Staff Recommended <br />Motion (B) with a motion to amend Council Bill 4910, Section 13, to remove any proposed <br />revisions to the current code entries for lot area minimum for duplex, triplex, and fourplex <br />lots on Eugene Code (EC) Table 9.2760. <br /> <br />Councilor Bettman averred that policy issues were involved in Section 13 and, as such, she would prefer to <br />have those discussions when the council talked about major land use code amendments. <br /> <br />Councilor Solomon asked Mr. Nystrom for his input on the amendment. Mr. Nystrom responded that the <br />City had on its books for a long time an option for people subdividing land which allowed them to create R- <br />1 lots for alternative housing types such as duplexes, triplexes and fourplexes. He said the question for staff <br />had to do with how to address a larger lot meant for a fourplex that was sold by a developer to someone who <br />wanted to build a single-family home and whether an exception to the lot size limit for such a home could be <br />allowed. He stated that should the amendment not be approved, a lot designated for a duplex and so on <br />would be required to remain so designated. He noted that PDD only saw one or two of such requests per <br />year. <br /> <br />In response to a follow-up question from Councilor Solomon, Mr. Nystrom affirmed that the substitute <br />motion would remove the original amendment’s flexibility. He reiterated that the current language was <br />inflexible and the original amendment had sought to increase the flexibility. He thought, should the code <br />remain the same, staff would have to be more “up front” with developers so that it was understood that a <br />designation could not be changed at a later date. <br /> <br /> <br />MINUTES—Eugene City Council November 28, 2005 Page 4 <br /> Regular Session <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.