Laserfiche WebLink
Requires City Council approval of extra-territorial extensions rather than the Planning <br />? <br /> <br />Director <br />Requires public hearings for all annexation requests <br />? <br /> <br />Increases public notification consistent with the Planning Commission’s recommendation <br />? <br /> <br /> <br />Although the City Council did not specifically direct these policy changes, staff is providing this <br />alternate draft of the ordinance to facilitate any intended motions on December 10, 2007. <br />Further discussion of these revisions is included below. <br /> <br />Extra-Territorial Extensions <br />Staff and the Planning Commission have recommended a Type II process for the review of extra- <br />territorial extensions. This remains unchanged in the draft ordinance in Attachment A. <br />However, Councilor Bettman questioned whether the Type II process (Planning Director <br />approval) was appropriate for extra-territorial extension applications. She indicated a preference <br />to consider a Type IV or V process, or other option that requires City Council approval, rather <br />than the proposed Type II process. In response, the alternative draft ordinance in Attachment B <br />is crafted to require City Council approval as an alternative to the proposed Type II process. <br />This alternative approach would be similar to the annexation review process, whereby <br />applications would go directly to the City Council for a public hearing. <br /> <br />Given the unique nature of these requests, staff believes that, if the council wishes to be the <br />decision-maker with respect to extra-territorial extensions, the council review process set out in <br />the alternative draft in Attachment B is more appropriate than the standard Type IV process. The <br />Type IV process is typically used for site specific Metro Plan or Refinement Plan Amendment <br />requests and also involves a two-step process with the Planning Commission and City Council. <br />The Type V procedures would not be an appropriate tool as that process is limited to legislative <br />actions. <br />Councilor Bettman also requested that we ensure that the ordinance would generally prohibit the <br />City from extending water or sewer service to areas outside the Urban Growth Boundary (UGB). <br />This is ensured through the approval criterion at EC 9.8121(1) which only allows approval of an <br />extension where the property proposed to be served is located within the City’s UGB, the airport, <br />or Lane Community College. Two exceptions to this general prohibition are specified under <br />9.8121(8), which would allow the council to approve such an extension in the case of a <br />communicable disease hazard for which the extension is the only practical remedy or where, <br />consistent with existing council policy, EWEB has entered into an agreement to provide water <br />services to properties within a now dissolved water district. Apart from the land use approval <br />process included in the draft ordinance, due to the City Charter relationship between the City of <br />Eugene and EWEB, the City Council must also approve of any proposals by which EWEB <br />would enable another entity (by its provision of water or services) to expand service areas. To <br />the extent necessary, this is addressed in Section 1 of the Ordinance, amending EC 2.212. <br />Councilor Bettman also suggested that the code provisions be more clearly tied to the detailed <br />policy direction in Eugene Resolution 2643, concerning extra-territorial extensions. In both of <br />the attached draft ordinances, we have provided such clarification by inserting several references <br />to, and consistency requirements with; “adopted resolutions” (See proposed revisions to EC <br />2.212, 9.8115, 9.8121 and to Ordinance Section 8). The City rarely includes in its code a <br />reference to a specific resolution, as such a reference would need to be amended if the resolution <br />Page 2 of 4 <br /> <br />