Zoneomics Logo
search icon

Eugene City Zoning Code

APPLICATION REQUIREMENTS

AND CRITERIA

9.8000 Introduction.

Sections 9.8000 through 9.8865 of this land use code establish comprehensive requirements and approval criteria for each land use application. These provisions serve as the basis for evaluating whether a specific land use application fulfills the particular application requirements and approval criteria.

(Section 9.8000, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8005 Applicability and Effect of Application Requirements, Criteria, and Concurrent Review.

(1) Additional provisions addressing the applicability of sections 9.8000 through 9.8865 are found in EC 9.2000 through 9.3980, which identify various uses that require approval of a particular land use application. Land use applications referred to in EC 9.8000 through 9.8865 are subject to the procedural requirements in EC 9.7000 through 9.7925, Application Procedures, and any additional requirements of EC 9.8000 through 9.8865. To the extent there is a conflict, the provisions in EC 9.8000 through 9.8865 control.

(2) If an initial proposal also requires an application be submitted for one or more of the following:

(a) Adjustment review;

(b) Site review;

(c) Conditional use permit;

(d) Planned unit development;

(e) Zone change;

(f) Willamette River Greenway permit; or

(g) Standards review,

the applicant may elect to have the applications reviewed concurrently according to the highest application type. All other provisions of this code would continue to apply to each application, including, but not limited to, the approval criteria.

(3) If the city’s final decision for any land use application reviewed and approved in accordance with the provisions of this land use code includes a finding of compliance with specific land use development standards, those standards shall not be considered at the time of a development permit application.

(Section 9.8005, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8007 Notice.

Where EC 9.7100-9.7685, or administrative rules referenced in those code sections, require an applicant to mail, post or publish notice, the city shall not approve the subject application(s) if the applicant has not submitted a signed affidavit of notice affirming that the applicant has provided notice as required.

(Section 9.8007 added by Ordinance 20433, enacted June 8, 2009, effective July 10, 2009.)

9.8010 List of Adopted Plans.

The documents listed in the following Table 9.8010, including any adopted amendments, are the currently effective adopted plans that may be applicable to a particular land use application. The plans and adopted policies are more particularly set forth beginning at EC 9.9500, and the boundaries for each are depicted on Map 9.8010, Adopted Plans.

Table 9.8010 List of Adopted Plans

Bethel-Danebo Refinement Plan (Phase II)

River Road-Santa Clara Neighborhood Plan

Bethel-Danebo Refinement Plan

Riverfront Park Study

Comprehensive Stormwater Management Plan

South Hills Study

Envision Eugene Comprehensive Plan

South Willamette Subarea Study

Eugene Downtown Plan

TransPlan (Metro Area Transportation Plan)

Eugene-Springfield Metropolitan Area General Plan (Metro Plan)

Walnut Station Specific Area Plan

Eugene 2035 Transportation System Plan

West University Refinement Plan

Fairmount/U of O Special Area Study

Westside Neighborhood Plan

Jefferson/Far West Refinement Plan

Whiteaker Plan

Laurel Hill Neighborhood Plan

Willakenzie Area Plan

19th and Agate Special Area Study

Willow Creek Special Area Study

River Road-Santa Clara Urban Facilities Plan

(Section 9.8010, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20362, enacted February 13, 2006, effective March 17, 2006; Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20528, enacted May 14, 2014, effective June 23, 2014; Ordinance No. 20582 enacted June 26, 2017, effective July 31, 2017; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20619, enacted July 22, 2019, effective August 25, 2019; Ordinance No. 20708, enacted April 22, 2024, effective May 30, 2024.)

9.8015 Adjustment Review – Purpose.

The adjustment review process is intended to:

(1) Encourage design proposals that respond to the intent of the code and creatively meet or exceed the specific development standards.

(2) Allow adjustment to the development standards in an efficient and effective manner.

(Section 9.8015, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8020 Adjustment Review – Applicability.

Adjustment review is available only where this land use code provides that a specific standard may be adjusted. Applications for adjustments review to standards in this land use code shall be considered under a Type II application process, unless the applicant requests that the adjustment review be considered concurrently with a related Type III application. Appeals of “minor” adjustment review decisions shall be considered by the Hearings Official using the process at EC 9.7650 – 9.7685. Appeals of “major” adjustment review decisions shall be considered by the Planning Commission using the process at EC 9.7600 – 9.7635.

(Section 9.8020, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.

9.8025 Adjustment Review – General Requirements.

(1) Except as provided in subsections (2) and (3), the adjustment review application shall be prepared by one or more of the following professionals unless waived by the planning director::

(a) Oregon licensed architect.

(b) Oregon licensed civil engineer.

(c) Oregon licensed landscape architect.

(d) Oregon licensed land surveyor.

(2) An application for adjustment review under EC 9.8030(21) shall comply with the following:

(a) Unless waived by the planning director, the application shall be prepared by one or more of the following professionals:

1. Oregon licensed architect.

2. Oregon licensed civil engineer.

3. Oregon licensed landscape architect.

4. A professionally trained botanist or biologist, with sufficient training and experience in planning and design to evaluate consistency of the application with all applicable standards.

(b) Unless waived by the planning director, if the application is not prepared by a professionally trained botanist or biologist, one or more of the professionals preparing the application shall have sufficient professional expertise and training in field botany or related biological sciences to evaluate consistency of the application with application standards.

(c) The application shall include a site plan that shows sufficient detail and supporting information to demonstrate compliance with applicable standards. Unless waived by the planning director, the site plan shall be prepared by an Oregon licensed civil engineer or an Oregon licensed surveyor.

(d) The site plan and application shall be signed by each of the professionals preparing the application, certifying that the application is true and correct to the best of his or her professional ability, and that, if applicable, the professional standards of his or her profession have been met therein.

(3) Unless waived by the planning director:

(a) An application for adjustment review under EC 9.8030(25)(a) and (b) shall be prepared by one or more of the following professionals:

1. Oregon licensed architect;

2. Oregon licensed civil engineer;

3. Oregon licensed landscape architect; or

4. Oregon licensed land surveyor.

(b) An application for adjustment review under EC 9.8030(25)(c) shall be prepared by one or more of the following professionals:

1. Oregon licensed architect;

2. Oregon licensed civil or geotechnical engineer;

3. Oregon licensed landscape architect;

4. Oregon licensed geologist;

5. A professionally trained botanist, biologist, ecologist or geomorphologist; or

6. A creek restoration specialist with a bachelor’s degree in the subject field and at least 5 years of applied experience in botany, biology, ecology, geomorphology or a closely related field.

(Section 9.8025, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009.)

9.8030 Adjustment Review – Approval Criteria.

The planning director shall approve, conditionally approve, or deny an adjustment review application. Approval or conditional approval shall be based on compliance with the following applicable criteria:

(1) Lot Standards Adjustment. Where this land use code provides that the lot standards may be adjusted, the standards may be adjusted upon finding that the proposed lot dimensions are consistent with the purpose of the applicable zone and suitable for the area.

(2) Setback Standards Adjustment. Where this land use code provides that the setback standards applicable to specific zones may be adjusted, the standards may be adjusted upon finding that the proposed setback is consistent with the following applicable criteria:

(a) Minimum and Maximum Front Yard Setback Adjustment. The minimum or maximum required front yard setback may be adjusted if the proposal achieves all of the following:

1. Contributes to the continuity of building facades along the street.

2. Creates an attractive pedestrian environment along all adjacent streets

3. Is compatible with adjacent development.

Maximum front yard setbacks may be adjusted without any requirement for pedestrian amenities if the location of the front yard is unsafe or intrinsically unsuitable for pedestrians or to protect disruption to significant natural resources.

(b) Minimum Setbacks for Park Improvements in PRO Zone. The minimum required special setbacks for park improvements may be adjusted upon a finding that the proposal achieves all of the following:

1. Consistent with EC 9.2600 Purpose of PRO Park, Recreation and Open Space Zone.

2. Is compatible with adjacent development.

(c) Minimum Setbacks for Drive-Through Facility Service Areas and Stacking Lanes. Standards establishing a minimum setback for service areas and stacking lanes may be adjusted upon a finding that the proposal achieves all of the following:

1. Is compatible with adjacent development.

2. Creates an attractive pedestrian environment along all adjacent streets.

3. Where necessary, provides visual separation between adjacent development.

(d) Outdoor Merchandise Display in C-2. The limitation on outdoor merchandise display in EC 9.2170(8)(b)(2) may be adjusted upon a finding that the proposed adjustment is consistent with the intent set out in EC 9.2170(1).

(3) Landscape Standards Adjustment. Where this land use code provides that the landscape standards may be adjusted, the standards may be adjusted upon finding that the proposed landscape is consistent with the following applicable criteria:

(a) General Landscape Standards. Standards establishing a minimum percent of landscape area on the development site, may be adjusted upon a finding that the proposal achieves all of the following:

1. Where necessary, provides visual separation between adjacent development.

2. Provides clearly defined entries and pedestrian pathways.

3. Enhances and softens structural elements.

4. Breaks up large expanses of parking.

5. Protects and enhances the value of adjacent or on-site natural areas.

6. In the case of multiple-unit developments, buffers dwellings from views that are unattractive and creates areas for outdoor privacy for residents.

(b) Basic Landscape Standard (L-1). The standards of EC 9.6210(1) may be adjusted if the proposal enhances a development site by providing attractive, open landscaped areas where distance is the primary means of separating different uses or developments.

(c) Low Screen Landscape Standard (L-2). The standards of EC 9.6210(2) may be adjusted if the proposal achieves at least one of the following:

1. A landscape treatment that uses a combination of distance and low-level screening (minimum 30 inches, maximum of 42 inches) to separate uses or development and the screening is adequate to soften the impact of the use or development.

2. In those instances where visibility between areas is more important than a total visual screen, the alternative landscape treatment is appropriate for the site.

(d) High Screen Landscape Standard (L-3). The standards of EC 9.6210(3) may be adjusted if the proposal uses landscape screening to provide a physical and visual separation between uses or development.

(e) High Wall Landscape Standard (L-4). The standards of EC 9.6210(4) may be adjusted if the proposal continues to provide extensive screening of both visual and noise impacts to protect adjacent users.

(f) Partial Screen Fence Landscape Standard (L-5). The standards of EC 9.6210(5) may be adjusted where the proposal achieves at least one of the following:

1. A moderate level of screening, adequate to soften the impact of the use or development.

2. In those instances where visibility between areas is more important than a total visual screen, the alternate landscape treatment is appropriate for the site.

(g) Full Screen Fence Landscape Standard (L-6). The standards of EC 9.6210(6) may be adjusted if both of the following are achieved:

1. The proposal provides a tall, complete visual separation to protect abutting uses.

2. Living plant landscaping is not practical for the site.

(h) Massed Landscape Standard (L-7). Adjustments may be made to the standards of EC 9.6210(7) if the proposal provides a landscape treatment appropriate for interior yards of large development sites adjacent to arterial and collector streets or to non-residential uses adjacent to residential development as the case may be.

(4) Building Orientation and Entrance Standards Adjustment. Where this land use code provides that building orientation and entrance standards may be adjusted, the standards may be adjusted upon finding that the proposal complies with one of the following:

(a) Promotes compatibility with adjacent property.

(b) Creates building orientations and entrances that achieve all of the following:

1. Support and augment the building setback, massing and architectural details.

2. Achieve an attractive streetscape with a strong building presence on existing and future streets.

3. In the case of multiple-unit developments, provides socialization benefits to residents.

(5) Underground Utilities Standard Adjustment. Where this land use code provides that the underground utility standard may be adjusted, the standards may be adjusted upon finding that one or more of the following exist:

(a) Underground utility placement would be unreasonably onerous to the applicant.

(b) Underground utility placement would be disruptive to significant natural resources.

(6) Large Commercial Facilities Standards Adjustment. Where this land use code provides that the large commercial facilities standards may be adjusted, the standards may be adjusted upon finding that the design contributes to one or more of the following:

(a) Improving the appearance and function of large commercial facilities.

(b) Encouraging efficient use of land resources and urban services.

(c) Encouraging mixed use.

(d) Supporting transportation options.

(e) Promoting detailed, human-scale site and building design.

(7) Large Multi-tenant Commercial Facilities Standards Adjustment. Where this land use code provides that the large multi-tenant commercial facilities standards may be adjusted, the standards may be adjusted upon finding that the design achieves all of the following:

(a) Provides for pedestrian safety, comfort and convenience.

(b) Produces visual clarity of circulation paths and building entrances for the pedestrian.

(8) Multiple-Unit Standards Adjustment. Where this land use code provides that the multiple-unit standards may be adjusted, the standards may be adjusted upon finding that the design achieves all of the following:

(a) Maximum Building Dimension. The requirements set forth in EC 9.5500(6)(a) may be adjusted if the proposal creates building massing and/or facades that:

1. Create a vibrant street facade with visual detail.

2. Provide multiple entrances to building or yards.

(b) Building Articulation. The requirements set forth in EC 9.5500(7) may be adjusted if the proposed building design:

1. Utilizes architectural masses, features or details to distinguish elements of the building.

2. Defines entryways in appropriate scales.

(c) Open Space. The requirements set forth in EC 9.5500(9), except for the amount of open space required per Table 9.5500(9) Open Space Requirements, may be adjusted if the applicant demonstrates consistency with all of the following:

1. The requested adjustment will allow the project to achieve an equivalent or higher quality design of open space than would result from strict adherence to the standards through:

a. Enhanced public and private spaces that contribute positively to the site, streetscape, and adjoining properties. Design elements for this purpose may include high quality materials, outdoor seating, enhanced pedestrian space, pedestrian-scaled lighting, canopy trees and other landscape materials and other user amenities; and

b. An overall site design that promotes safety, security and privacy, and reduces visual, noise, and lighting impacts of development on adjacent properties.

2. When abutting property is zoned R-1 Low-Density Residential, the design provides an appropriate combination of setbacks, landscaping and screening to buffer between the multiple-unit development and the adjacent Low-Density Residential zone.

(d) Block Requirement. The requirements set forth in EC 9.5500(10) may be adjusted if the proposal achieves at least one of the following:

1. Provides an equivalent or greater degree of vehicular and pedestrian circulation.

2. Traditional block patterns that reduce the apparent scale of large developments by breaking the site up into smaller land units. (See also EC 9.6810 Block Length.)

(e) Site Access and Internal Circulation. The requirements set forth in EC 9.5500(11) may be adjusted in accordance with the criteria in this subsection. In the case of an adjustment, all of the following standards apply:

1. Sidewalks may be designed as curbside walks only along those portions of the private streets providing parallel on-street parking.

2. Street trees may be placed in tree wells or adjacent to the sidewalk.

(f) Vehicle Parking. The requirements set forth in EC 9.5500(12) may be adjusted if the proposal achieves to the same degree as would strict compliance with the standards all of the following:

1. Limitations on the use of continuous parking drives in large-scale multiple-unit developments.

2. Limitations on the size of individual parking lots in multiple-unit development.

3. Minimal negative aspects of parking uses in multiple-unit developments.

Where cost considerations preclude parking beneath or within residential buildings, combinations of partial and interrupted parking drives; on-street parking; and small, dispersed parking courts are an acceptable alternative.

(9) Bicycle Parking Standards Adjustment. Where this land use code provides that the bicycle parking standards may be adjusted, the standards may be adjusted upon finding that the design achieves all of the following:

(a) Consistency with EC 9.6100 Purpose of Bicycle Parking Standards; and

(b) Shared bicycle parking remains convenient and clearly visible for users.

In cases where the standard for required bicycle parking for a development site would require in excess of over 1,500 bicycle spaces, the applicant may also seek an adjustment by submitting for city review a Bicycle Management Program. The Bicycle Management Program shall address how the applicant will encourage bicycle use and the rationale for requesting an adjustment. City approval of the Bicycle Management Program shall constitute the granting of an adjustment.

(10) Motor Vehicle Parking and Loading Standards Adjustment. Where this land use code provides that the motor vehicle parking standards may be adjusted, the standards may be adjusted upon finding the applicable corresponding criteria are met.

(a) Maximum Number of Off-Street Parking Spaces. Except within a /TD Overlay Zone, an adjustment that approves installation up to 120 percent of the maximum spaces permitted by EC 9.6410(2), Maximum Number of Off-Street Motor Vehicle Parking Spaces, may be allowed, if all of the following criteria are met:

1. Additional parking is necessary to meet the parking demand for a specific use as demonstrated by a parking- traffic study prepared by a traffic engineer.

2. At least 60 percent of the parking lot is allocated and striped for compact cars; or the tree canopy coverage of all surface area parking, as calculated at EC 9.6420(4)(d)3. is equal to or greater than 50% and meets the requirements of EC 9.6420(4)(d)3.

3. A proposed Transportation Demand Management (TDM) Program has been approved by the city that contains strategies for reducing vehicle use and parking demand generated by the development and establishes benchmarks by which the program’s effectiveness will be measured annually.

(b) Loading and Drive-Through Design Standards. Adjustments may be made to the standards of EC 9.6415 based on the following.

1. The minimum depth required in EC 9.6415(1) for a specially designed area may be adjusted upon a determination that a lesser minimum is adequate to prevent the extension of the line-up of automobiles into the public right-of-way.

2. An adjustment may be granted to the loading and service drive off-street maneuvering space requirement of EC 9.6415(3) for property located on a local street where existing or projected traffic volumes do not exceed daily traffic counts of 750 vehicles.

(c) Parking Area Standards. Adjustments may be made to the landscape standards of EC 9.6420(3) upon finding that the proposed landscape is consistent with the following applicable criteria:

1. Provides visual separation, as needed, between adjacent development.

2. Provides clearly defined parking area entrances and on-site pedestrian circulation.

3. Enhances and softens the appearance of parking structures.

4. Breaks up large expanses of parking.

5. Protects or mitigates the loss of significant trees or other natural features on or adjacent to the development.

(d) Special Event Permanent Parking Facilities. The standards of EC 9.6435 for permanent parking facilities for special events may be adjusted provided the proposal results in the development of attractive, safe, and efficient special event parking areas.

(11) Vision Clearance Area – Approval Criteria for Adjustment Review. The vision clearance standards of EC 9.6780 may be adjusted if it is determined that no feasible alternative to the intersection to address vision clearance is available, and any of the following conditions exist:

(a) Traffic can safely approach and enter the intersection or street given existing traffic control devices or other physical conditions of the area.

(b) Topographic conditions are so extreme or structures exist such that it is not practical to provide required vision clearance.

(c) Additional traffic control structures or facilities may be required to provide for adequate public safety.

(12) Intersections of Streets and Alleys Standards Adjustment. The minimum offset intersection requirements set forth in EC 9.6830 may be adjusted if the proposed adjustment is necessary and is designed so that no offset dangerous to the traveling public is created as a result of staggering of intersections. An offset necessary to assure safety and efficiency based on traffic engineering principles shall be required. Upon submittal by a traffic engineer and approval by the city of a study that demonstrates the safety and efficiency of an intersection offset of a lesser distance, the minimum intersection offsets of 100 feet on a local street, 200 feet on a collector street, and 400 feet on an arterial street may be adjusted. Offsets shall be measured from the center lines of the two intersecting streets.

(13) Tree Preservation and Removal Standards Adjustment. The minimum tree preservation requirement and maximum mitigation allowance of EC 9.6885(2) may be adjusted if one of the conditions listed in subparagraph (a) below applies and the proposed design complies with the criteria in subparagraph (b):

(a) Conditions. To qualify for an adjustment, one of the following conditions must apply:

1. Strict compliance with tree preservation and removal standards is not feasible due to other requirements of this code or existing site constraints such as topography or other natural features; or

2. An adjustment to the minimum tree preservation and/or mitigation requirement is necessary in order to achieve a net density greater than 75 percent of the maximum net density for the applicable zone; or

3. The existing trees required to meet the minimum preservation requirement are unlikely to survive the level and type of anticipated development due to susceptibility to windthrow or other natural causes of failure.

(b) Criteria. To qualify for an adjustment, the proposed design must meet the following criteria:

1. The proposed reduction in the minimum tree preservation requirement or increase in mitigation allowance is necessary to accommodate a reasonable level of development.

2. In no case shall the minimum tree preservation requirement be reduced below 30% for areas at or above 900 feet elevation and areas within the Willamette River Greenway Tree Preservation Zone 1, as depicted in Exhibit B-1 to Ordinance No. 20693.

3. Except for areas at or above 900 feet elevation and areas within Willamette River Greenway Tree Preservation Zone 1 as depicted in Exhibit B-1 to Ordinance No. 20693, proposals may mitigate up to 100% of the minimum tree preservation requirement if the following requirements are met:

a. For proposed subdivisions, new trees must be planted so that lots up to 7,000 square feet in area will contain a minimum of two trees and lots 7,000 square feet or more will contain a minimum of three trees.

b. For all other developments, the proposed design must provide one tree per dwelling unit.

4. For areas at or above 900 feet elevation, and areas within Willamette River Greenway Tree Preservation Zone 1 as depicted in Exhibit B-1 to Ordinance No. 20693, mitigation is limited to 10% of the minimum preservation requirement.

5. For areas within Willamette River Greenway Tree Preservation Zone 2 as depicted in Exhibit B-1 to Ordinance No. 20693, mitigation is limited to 20% of the minimum preservation requirement.

6. New trees planted to meet mitigation requirements are subject to the requirements at EC 9.6885(2)(e)2.d. Installation and Maintenance.

7. Trees planted to meet applicable landscape standards may be counted toward mitigation requirements.

8. Except as provided in EC 9.8030(13)(b)(9), existing trees that are located on the development site may be designated for preservation and counted toward mitigation requirements in lieu of planting new trees if:

a. The tree measures under 8-inches Diameter Breast Height (d.b.h.); and

b. The tree is listed in Table 9.6885(2)(e)2. Approved Species List.

9. The provisions of EC 9.8030(13)(b)(8) do not apply to portions of a development site located within the Willamette River Greenway. On portions of a development site located within the Willamette River Greenway, existing trees may be designated for preservation and counted toward mitigation requirements in lieu of planting new trees if:

a. The tree measures under 8-inches Diameter Breast Height (d.b.h.);

b. The tree is a species included on the City’s adopted list of plant species for sites at or below 500 feet in elevation, attached as Exhibit F to Ordinance No. 20351; and

c. The tree is located on the development site and within the Willamette River Greenway Boundary but outside of the Willamette River Greenway Setback. No existing trees located within the Willamette River Greenway Setback may count toward mitigation requirements.

(c) For purposes of EC 9.8030(13):

1. “Willamette River Greenway” means all lands within the adopted Willamette River Greenway Boundary established by Resolution No. 2592.

2. “Willamette River Greenway Setback” is that area identified on the Willamette River Greenway Setback Map adopted as Exhibit A-1 to Ordinance No. 20693.

(14) Overlay Zone Development Standards Adjustment. Unless a subsection of EC 9.8030 sets out adjustment review criteria for a specific overlay zone, where this land use code provides that overlay zone standards may be adjusted, the standards may be adjusted upon a finding that the adjustment of the standards will result in a development that is consistent with the purpose of the overlay.

(15) S-H Historic Zone Standards Adjustment. In addition to the allowed adjustments to standards provided elsewhere in this land use code, any standard applicable to an S-H Historic Zone may be adjusted upon finding that the proposal is consistent with the purpose of the applicable zone and is suitable for the area.

(16) Downtown Plan Area. Where this land use code provides that a development standard applicable within the Downtown Plan Area as shown on Map 9.2161(6), Downtown Plan Map, may be adjusted, approval of the request shall be given if the applicant demonstrates consistency with all of the following:

(a) The requested adjustment will allow the project to achieve an equivalent or higher quality design than would result from strict adherence to the standards through:

1. A building orientation, massing, articulation and façade that contribute positively to the surrounding urban environment; and

2. An overall site and building design that creates a safe and attractive pedestrian environment. Design elements for this purpose may include special architectural design features, high quality materials, outdoor seating, pedestrian-scaled lighting, prominent entries facing the street, multiple openings or windows, and a significant use of clear, untinted glass.

(b) Impacts to any adjacent residentially-zoned property are minimized. Design elements for this purpose may include treatment of building massing, setbacks, screening and landscaping.

(c) For adjustments pursuant to EC 9.2170(10) only, placing utilities underground would be unreasonably onerous to the applicant.

(17) S-RN Royal Node Special Area Zone Standards Adjustment. A standard applicable within the S-RN Royal Node Subarea LDR, MDR, RMU, CMU or MSC may be adjusted upon a finding that the proposed adjustment:

(a) Is consistent with the purposes of the S-RN Royal Node Special Area Zone as set forth at EC 9.3800; and

(b) Meets the applicable adjustment criteria in another subsection of EC 9.8030, if any.

If there is no EC 9.8030 subsection that pertains to the type of standard being considered, adjustment may be permitted based solely on compliance with EC 9.8030(17)(a).

(18) S-CN Chase Node Special Area Zone Standards Adjustment. A standard applicable within the S-CN Chase Node Special Area Zone Subarea C, HDR/MU or HDR may be adjusted upon a finding that the proposed adjustment:

(a) Is consistent with the purposes of the S-CN Chase Node Special Area Zone as set forth at EC 9.3100; and

(b) Meets the applicable adjustment criteria in another subsection of EC 9.8030, if any.

If there is no EC 9.8030 subsection that pertains to the type of standard being considered, adjustment may be permitted based solely on compliance with EC 9.8030(18)(a).

(19) Improvements, Streets and Alleys.

(a) The requirement in EC 9.6505(3)(b) that all paving improvements to streets and alleys adjacent to the development include drainage, curbs and gutters, sidewalks, street trees and street lights may be adjusted to allow the site developer to improve the streets and alleys adjacent to the development site with a temporary surface, designed and constructed in accordance with the City’s adopted temporary surface permit procedures. A temporary surface may be allowed when the site developer can demonstrate that a temporary surface is adequate to serve the development site and that a temporary surface will not impede the public’s use of the right-of-way.

(b) The paving requirement at EC 9.6505(3)(b) may be adjusted if the site developer has shown that a street or alley adjacent to the development will not be impacted by the development.

(20) Public Accessways. The public accessway standards of 9.6835(1) may be adjusted if the developer has shown that pedestrian and bicyclists traveling to and from nearby residential areas, transit stops, neighborhood activity centers, and other commercial and employment and industrial areas are already being provided safe, convenient and direct access. “Nearby” means within 1/4 mile that can reasonably be expected to be used by pedestrians, and within 2 miles that can reasonably be expected to be used by bicyclists.

(21) /WR Water Resources Conservation Overlay Zone Adjustment. Where this land use code provides that a provision of the /WR Water Resources Conservation Overlay Zone may be adjusted, approval may be given only upon a finding that the proposed adjustment meets criterion (a), (b), (c) or (d) below:

(a) For any property containing a /WR conservation area due to a resource identified as a wetland, upland wildlife habitat or riparian site in the Goal 5 Water Resources Conservation Plan, an adjustment to the provisions of EC 9.4920 may be made if no previous adjustment under this section has been approved for the specific portion of the conservation area and all of the following are met:

1. More than 33 percent of the development site is occupied by the combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback;

2. The proposed reduction in the /WR conservation area will result in the combined area described above constituting at least 33 percent of the development site;

3. The parcel is not already developed with a building suitable for occupancy;

4. The area of the subject parcel is 10,000 square feet or less;

5. The portion of the development site removed from the /WR conservation area complies with EC 9.4980(2)(a)(4), (4)(b), (5)(a), (8), and (10);

6. The portion of the development site outside the /WR conservation area, including the area removed, complies with EC 9.4980(7);

7. The portion of the development site that remains in a /WR conservation setback area complies with EC 9.4980(1) through (5);

8. The reduction occurs first by reducing the area of any portion of the resource site that extends landward beyond the conservation setback. If additional reduction in the /WR conservation area is needed to reduce the combined area to 33% of the development site area, the conservation setback area described in EC 9.4920(1)(b) may be reduced the minimum necessary to meet the standard in subsection 2.; and

9. The proposed adjustment is consistent with EC 9.8030(21)(e).

(b) For property containing a /WR conservation area due to a resource identified in the Goal 5 Water Resources Conservation Plan as a Category A, B or C stream or as a Category A wetland, an adjustment to the provisions of EC 9.4920 may be made if no previous adjustment under this section has been approved for the specific portion of the conservation area and all of the following are met:

1. The proposed reduction in the conservation setback distance is no more than 20%;

2. The portion of the development site removed from the /WR conservation area complies with EC 9.4980(2)(a)(4), (4)(b), (5)(a), (8), and (10);

3. The portion of the development site outside the /WR conservation area, including the area removed, complies with EC 9.4980(7);

4. The remaining /WR conservation setback area complies with EC 9.4980(1) through (5);

5. For Category A wetland sites, reduction in the width of the /WR conservation area shall occur first in areas where the adjacent wetland is of lower quality or is more disturbed by human activities and expansion of the width of the /WR conservation area shall occur first in areas where the adjacent wetland is of higher quality or is less disturbed by human activities;

6. For riparian or upland wildlife habitat sites where a reduction in the width of the /WR conservation area is allowed, the conservation setback area may be reduced, to the extent practicable, according to the following priority order: a. Where the reduction area does not include a mapped Goal 5 resource site designated for protection in the Goal 5 Water Resources Conservation Plan, b. Where the adjacent habitat quality is lower; and

7. The proposed adjustment is consistent with EC 9.8030(21)(e).

(c) For property containing a /WR conservation area due to a resource identified in the Goal 5 Water Resources Conservation Plan as a Category A or B stream or as a Category A wetland, an adjustment to the provisions of EC 9.4920 may be made if no previous adjustment under this section has been approved for the specific portion of the conservation area and all of the following are met:

1. Conservation setback averaging is employed to maintain the same total area within the /WR conservation area within the development site that would have existed without the reduction in the conservation setback distance. Conservation setback averaging shall be accomplished by expanding the /WR conservation area in an undeveloped area of the development site in compensation for reducing it in another area of the site, such that the total area of the /WR conservation area on the development site remains constant;

2. The conservation setback distance may be reduced in one or more locations by up to 30%.

3. The portion of the development site removed from the /WR conservation area complies with EC 9.4980(2)(a)(4), (4)(b), (5)(a), (8), and (10);

4. The portion of the development site outside the /WR conservation area, including the area removed, complies with EC 9.4980(7);

5. The portion of the development site remaining in the /WR conservation area complies with EC 9.4980(2) through (5);

6. For Category A wetland sites, reduction in the width of the /WR conservation area shall occur first in areas where the adjacent wetland is of lower quality or is more disturbed by human activities and expansion of the width of the /WR conservation area shall occur first in areas where the adjacent wetland is of higher quality or is less disturbed by human activities;

7. For Category A or B streams, reduction in the width of the conservation setback area shall occur to the extent practicable, according to the following priority order:

a. Where the reduction area does not include an adjacent Goal 5 resource site designated for protection in the Goal 5 Water Resources Conservation Plan,

b. Where the adjacent habitat quality is lower,

c. Where the setback area can be expanded in compensation on the opposite bank of the stream from the reduction area if it is within the same development site. If the development site does not include the opposite bank for the stream, the expansion of the conservation setback shall occur elsewhere on the development site; and

8. The proposed adjustment is consistent with EC 9.8030(21)(e).

(d) For property containing a /WR conservation area due to a resource identified in the Goal 5 Water Resources Conservation Plan as a wetland, upland wildlife habitat or riparian site, an adjustment to the provisions of EC 9.4930 and EC 9.4980 may be approved if all of the following are met:

1. The applicant has shown that: a. The parcel is not already developed with a building suitable for occupancy; b. The strict application of the provisions of EC 9.4930 and 9.4980 would prohibit construction of a building suitable for occupancy on any portion of the parcel due to special circumstances that apply to the property, including location, shape, size, surroundings, and topography and the relationship of the characteristics to the resource site or applicable conservation area.

2. The applicant has demonstrated that the adjustments described under subsections (a), (b) and (c) above would not allow the use or uses specified under 1.;

3. The adjustment allowed is the minimum necessary to allow the use or uses specified under 1.;

4. The portion of the development site removed from the /WR conservation area complies with EC 9.4980(2)(a)(4), (4)(b), (5)(a), (8), and (10) except to the extent that a standard in one of those subsections is the subject of the adjustment application;

5. The portion of the development site outside the /WR conservation area, including the area removed, complies with EC 9.4980(7);

6. The portion of the development site that remains in a /WR conservation area complies with EC 9.4980(1) through (5); and

7. The proposed adjustment is consistent with EC 9.8030(21)(e).

(e) The applicant demonstrates that restoration or habitat enhancement activities within the remaining conservation area will result in a net increase in overall natural functions and values proportional to the requested adjustment, and will specifically result in a net increase in two or more of the following functions and values of the conservation area as applicable to the site:

1. For streams and wetlands within stream channels:

a. Effective shade of stream channel during peak solar input;

b. Species diversity, structural diversity, density, and percent cover of native riparian vegetation;

c. Bank stability due to native riparian plant roots;

d. Absence of non-native invasive plant species;

e. Effective filtering of overland stormwater flow to the stream;

f. Presence of soils and hydrology appropriate to the site and appropriate to support native plants;

g. Habitat characteristics required by any state or federally listed threatened or endangered species that have been documented on the site.

2. For wetlands not within stream channels:

a. Species diversity, density, and coverage of native vegetation within the wetland and setback area;

b. Bank stability due to native plant roots;

c. Absence of non-native invasive plant species;

d. Effective filtering of overland stormwater flow to the wetland;

e. Presence of soils and hydrology appropriate to the site and appropriate to support native plants;

f. Habitat characteristics required by any state or federally listed threatened or endangered species that have been documented on the site.

For purposes of this subsection, the demonstration of the increase in functions and values shall be based upon a comparison between the functions and values of the /WR conservation area as it existed on the date of application for an adjustment under this subsection and the functions and values of the proposed reduced /WR conservation area with proposed enhancements and restoration.

(22) Pedestrian Circulation On-site Adjustment. Where this land use code provides that on-site pedestrian circulation may be adjusted, the standards may be adjusted upon finding that, considering site constraints or practical difficulties, the proposed design provides adequate pedestrian connections:

(a) Between building entrances and streets or accesways;

(b) Between new and existing buildings on the development site, including recreation and community facilities;

(c) From proposed employment and industrial, commercial and institutional uses to adjacent parcels having similar existing or planned uses;

(d) To nearby transit stops, parks and other recreation facilities; and

(e) Between parking lots and main buildings.

(23) S-C Chambers Special Area Zone. The following standards applicable within the S-C Chambers Special Area Zone may be adjusted upon a finding that the adjustment is consistent with the criteria of subparagraphs (a) through (e). In all cases, proposed adjustments to the standard shall be the minimum necessary to implement the development proposal:

(a) Residential Building Maximum Front Yard Setback. The maximum front yard setback for residential buildings as established in EC 9.3065(3)(b)(1)(b) may be adjusted if the proposed setback adjustment is consistent with the overall front yard setback pattern of the neighborhood, particularly with existing dwellings on both sides of the front yard and within the immediate block.

(b) Interior Yard Setbacks. An adjustment may be granted to the interior yard setback requirements of EC 9.3065(3)(b)(2) if the proposed adjustment is consistent with the purpose of EC 9.3050 and is necessary for development on a constrained site. However, in no case is an interior yard setback allowed that is less than 5 feet from the interior lot line or less than 10 feet from structures on other lots.

(c) Building Height. The building height standards of EC 9.3065(3)(c)(1)(a) for residential buildings within 60 feet of the street may be increased to a height of up to 30 feet if the applicant can demonstrate that the requested adjustment meets all of the following criteria:

1. The proposed dwelling is shown to be compatible with other dwellings in the immediate vicinity, in terms of scale, mass and setbacks.

2. The additional height will not adversely impact the immediate neighbor’s privacy, considering backyard privacy, location of second story windows facing adjacent yards and dwellings, etc.

3. Constraints on the property necessitate the adjustment in height, with consideration being given to protecting existing mature trees, lot configuration, and existing structures on site.

(d) Roof Pitch. The minimum roof pitch standard of EC 9.3065(3)(d)(1) may be adjusted if the proposed adjustment conforms with prevailing neighborhood context of roof pitch and articulated roof massing. The applicant shall submit examples of other roof forms in the immediate vicinity with the adjustment application.

(e) Driveway Standards. An adjustment to the driveway width standards of EC 9.3065(3)(f) may be granted if the proposed adjustment is necessary for development on a constrained site taking into consideration unique situations such as existing structures on the lot, joint driveway access, and existing mature landscaping.

(24) Stormwater Quality, Flow Control, Oil Control and Source Control Standards Adjustment. (Adjustments under this subsection are not permitted within the /CL Clear Lake Overlay Zone.)

(a) The requirement in EC 9.6792(3)(a) and EC 9.3155(17)(c)4 that selected stormwater quality facilities shall treat all the stormwater runoff that will result from the water quality design storm may be adjusted upon a finding that the stormwater quality facility will treat as much of the runoff as possible; and

(b) The requirement in EC 9.6792(3)(a) and EC 9.3155(17)(c)5 that all stormwater quality facilities be selected from and sited, designed, and constructed according to the Stormwater Management Manual may be adjusted upon finding that all of the following requirements are met:

1. The proposed alternative design will achieve equal, or superior, results for function (reducing pollution), maintainability and safety, and the proposed siting does not adversely affect structures or other properties.

2. The applicant’s written description of the proposed alternative design has been reviewed and approved by the City Engineer. The description of the proposed design submitted for review must include all of the following information for each component of the proposed alternative design:

a. Size, technical description, capacity, capital cost, design life, construction process and costs, consequences of improper construction, operation and maintenance requirements and costs;

b. Data on the effectiveness of proposed alternative technologies, if available, including data from laboratory testing and pilot/full-scale operations, and information regarding the operations of any full-scale installations;

c. Any other available information about the proposed design, including peer review articles, scientific or engineering journals, and approvals from other jurisdictions.

3. The applicant has submitted a method and schedule for monitoring the effectiveness of the proposed design once constructed, and a schedule for its maintenance.

4. The applicant has submitted a signed statement that the applicant will replace the alternative stormwater quality facility if the facility does not function as proposed.

(c) The requirement in EC 9.6792(3)(b)2 that extended filtration (filtration through natural or engineered media) shall be utilized to treat the water quality design storm runoff from the impervious surface areas may be adjusted upon a finding that:

1. An engineering report shows that, due to unique topography, a filtration system would be unreliable or would be likely to have an adverse impact on surrounding properties; or

2. Soil contamination would negatively impact surface water or groundwater quality if a filtration system was used.

(d) The requirement in EC 9.6793(3)(a) and EC 9.6793(3)(b) may be adjusted upon a finding that the flow control facility will control flow rates as much as possible and one of the following applies:

1. The area at issue generating runoff is less than 500 square feet of impervious surface and is isolated from the flow control facility;

2. The area at issue generating runoff is less than 500 square feet of impervious surface and it is not technically feasible to drain the untreated runoff to the flow control facility;

3. Constructing facilities to control the flow of runoff from the area at issue would require removal of trees or damage to other natural resources;

4. The area at issue generating runoff is less than 500 square feet of impervious surface and limited access to the area would prevent regular maintenance of the flow control facility.

(e) The requirements in EC 9.6793(3)(d) that all flow control facilities be selected from and sited, designed, and constructed according to the flow control provisions and the facility design requirements set forth in the Stormwater Management Manual may be adjusted upon finding that all of the following requirements are met:

1. The proposed alternative design will achieve equal, or superior, results for function (maintaining flow or restricting flow or both), maintainability and safety, and the proposed siting does not adversely affect structures or other properties;

2. The applicant’s written description of the proposed alternative design has been reviewed and approved by the City Engineer. The description of the proposed design submitted for review must include all of the following information for each component of the proposed alternative design:

a. Size, technical description, capacity, capital cost, design life, construction process and costs, consequences of improper construction, operation and maintenance requirements and costs;

b. Data on the effectiveness of proposed alternative design, if available, including data from laboratory testing and pilot/full-scale operations, and information regarding the operations of any full-scale installations;

c. Any other available information about the proposed design, including peer review articles, scientific or engineering journals, and approvals from other jurisdictions.

3. The applicant has submitted a method and schedule for monitoring the effectiveness of the proposed design once constructed, and a schedule for its maintenance;

4. The applicant has submitted a signed statement that the applicant will replace the alternative flow control facility if the facility does not function as proposed.

(f) The requirement in EC 9.6794(3) that oil control facilities be sited, designed and constructed according to the oil control provisions and the facility design requirements set forth in the Stormwater Management Manual may be adjusted if the applicant can demonstrate that the selected oil control facility will achieve the same result as those listed in the Stormwater Management Manual.

(g) The requirement in EC 9.6795(3) that source controls be sited, designed and constructed according to source control provisions set forth in the Stormwater Management Manual may be adjusted if the applicant can demonstrate that the selected source control will achieve the same result as those listed in the Stormwater Management Manual. Applicants seeking an adjustment to EC 9.6795(3) must submit a completed authorization request form adopted as part of the Stormwater Management Manual.

(25) /WQ Water Quality Overlay Zone Adjustment. In accordance with EC 9.4784, a provision of the /WQ Water Quality Overlay Zone may be adjusted only upon a finding that the proposed adjustment meets criterion (a), (b), or (c) below:

(a) Adjustment to Applicable Setback to Limit /WQ Management Area to 33% of Development Site. For any parcel greater than 6,000 square feet (not eligible for an automatic setback reduction under EC 9.4778(2)), the city shall make an adjustment to the applicable setback set out at EC 9.4778(1)(b) and (c) if no previous adjustment under this section has been approved for the specific portion of the /WQ Management Area and all of the following are met:

1. More than 33 percent of the development site, as defined in EC 9.0500, is occupied by the /WQ Management Area alone or in combination with a /WR Conservation Area;

2. The proposed reduction in the applicable setback will result in the /WQ Management Area, alone or in combination with a /WR Conservation Area constituting no less than 33 percent of the development site;

3. The new boundary of the /WQ Management Area shall be located:

a. Parallel to the original boundary (closer to the waterway); or

b. Through the application of setback averaging. Setback averaging shall be accomplished by expanding the /WQ Management Area in an undeveloped area of the development site, and reducing it in another area of the development site;

4. For either the parallel adjustment in 3.a above or the setback averaging adjustment in 3.b. above, the applicable setback is not reduced by more than 15 feet for a 25 foot setback or more than 20 feet for a 40-foot setback unless further reduction is necessary to achieve the reduction in the /WQ Management Area to 33%, and in no case shall the setback boundary be located within the waterway channel;

5. For parcels 13,500 square feet or greater, the water quality function rating when the proposed adjustment is implemented will be equal to or greater than the pre-adjustment water quality function rating for the /WQ Management Area based on the city’s Water Quality Function Rating System; and

6. Removal of all refuse, toxics, fill, unauthorized auto bodies, or similar materials located within the /WQ Management Area that are harmful to water quality or that limit the filtration of pollutants from runoff that flows across the /WQ Management Area shall be a condition of approval.

(b) Adjustment to Applicable Setback Due to Development Constraints. For a parcel containing a /WQ Management Area, an adjustment to the applicable setback provisions of EC 9.4778(1)(b) and (c) shall be made if no previous adjustment under this section has been approved for the specific portion of the /WQ Management Area, consistent with the following:

1. The adjustment is necessary due to development constraints on the lot caused by the unique physical characteristics of the lot, including but not limited to narrow lot dimensions, irregular shape, and the relationship of these characteristics to the location and extent of the /WQ Management Area;

2. The adjustment is the minimum necessary to allow the proposed use;

3. Except as provided under (b)4. below, the new setback boundary shall be located through the application of setback averaging with no overall reduction in the /WQ Management Area. Setback averaging shall be accomplished by expanding the /WQ Management Area in an undeveloped area of the development site and reducing it in another area of the development site, provided:

a. At any location, the applicable setback is not reduced by more than 15 feet for a 25-foot setback or by more than 20 feet for a 40-foot setback; and

b. The water quality function rating when the proposed adjustment is implemented will be equal to or greater than the pre-adjustment water quality function rating for the /WQ Management Area based on the city’s Water Quality Function Rating System;

4. If, after applying the provisions of (b)3. above, the parcel remains physically constrained as described in (b)1. above, then the overall /WQ Management Area may be reduced. The new setback boundary shall be located:

a. Parallel to the original boundary (closer to the waterway); or

b. Through the application of setback averaging. Setback averaging shall be accomplished by expanding the /WQ Management Area in an undeveloped area of the development site, and reducing it in another area of the development site.

c. For either the parallel adjustment in 4.a. or the setback averaging adjustment in 4.b., the applicable setback is not reduced by more than 15 feet for a 25-foot setback or by more than 20 feet for a 40-foot setback;

d. For either the parallel adjustment in 4.a. or the setback averaging adjustment in 4.b., the water quality function rating when the proposed adjustment is implemented will be at least 150% of the pre-adjustment water quality function rating for the /WQ Management Area based on the city’s Water Quality Function Rating System.

5. Removal of all refuse, toxics, fill, unauthorized auto bodies, or similar materials located within the /WQ Management Area that are harmful to water quality or that limit the filtration of pollutants from runoff that flows across the /WQ Management Area shall be a condition of approval.

(c) Adjustment to Allowed Uses and Development Standards. For property containing a /WQ Management Area, an adjustment to the provisions of EC 9.4780 or EC 9.4790 shall be made consistent with the following:

1. If the proposed adjustment is to allow a use that is otherwise prohibited under EC 9.4780(4), one of the following shall apply:

a. General Use Adjustment.

(1) The proposed use is of similar nature to a specific use listed in EC 9.4780(2) or (3);

(2) The applicant has submitted evidence through a qualified professional that the proposed use will have a water quality impact similar to the specific use identified pursuant to a.(1) above; and

(3) The applicant has shown compliance with any standards applicable to the specific use identified pursuant to a.(1), above.

b. Public Transportation System Improvements.

(1) The use or activity is:

(a) Necessary to construct a transportation facility included on a financially constrained or illustrative table in the federally approved Regional Transportation Plan; or

(b) Necessary to protect the public safety by ensuring the structural integrity of existing flood control structures; and

(2) The applicant has demonstrated that, based on the city’s Water Quality Function Rating System (see EC 9.4782), the project will result in a water quality function rating equal to or greater than previously existed.

(3) If the applicant demonstrates that it is not feasible to meet the standards described in (c)1.a.(3) above, the applicant shall, instead, make improvements to another /WQ waterway over which the applicant also has management control. The applicant shall demonstrate that, based on the city’s Water Quality Function Rating System (see EC 9.4782), such improvements will result in an increase in the water quality function rating of that waterway by an amount that is equal to or greater than the rating of the subject waterway prior to the approved adjustment.

2. If the proposed adjustment is to a development standard of EC 9.4790, the applicant has provided evidence that the proposed alternative approach for effectively addressing a specific water quality concern is equal to or greater than the standard that would be otherwise required.

(26) S-JW Jefferson Westside Special Area Zone. The following standards applicable within the S-JW Jefferson Westside Special Area Zone may be adjusted upon a finding that the adjustment is consistent with the following criteria.

(1) Driveway width. An additional two feet of width is allowed for any portion of a driveway that takes access from a street based on the following criteria:

a. The additional driveway width is necessary to avoid an unsafe condition, to comply with the requirements of EC 9.6420 (Parking Area Standards) or to provide reasonable maneuvering room around an obstacle that cannot be practicably relocated to a different location that would not create a driveway obstacle; and

b. The additional area allowed under this adjustment is the minimum necessary to accomplish the objective under (1)(a), above.

(2) Means of primary vehicle access. A dwelling considered to have its primary vehicle access from the alley, according to EC 9.3625(3)(a)(2)(b), may be considered to have its primary vehicle access from the street if the applicant demonstrates that physical conditions or code standards preclude the establishment of vehicle parking on any part of the lot that could be accessed from the alley.

(27) Driveways and Internal Circulation. The driveway requirement of EC 9.6703(3)(a) may be adjusted if the site developer demonstrates with an Alternative Traffic Safety Study that a shorter driveway stacking area will provide safe ingress and egress to the development site, will not negatively impact the efficiency of the public right-of-way, and will not result in a hazard to the bicycle, pedestrian or vehicular traffic using the right-of-way.

(28) Public Access Required. The public access requirement of 9.6735(2) may be adjusted if the site developer demonstrates any of the following:

(a) Physical conditions preclude compliance with EC 7.420. Such conditions may include, but are not limited to, topography, trees, existing buildings or other existing development on the subject property or adjacent property.

(b) The proposed adjustments to the standards will provide safe ingress and egress to the development site, will not negatively impact the efficiency of the public right-of-way, and will not result in a hazard to the bicycle, pedestrian or vehicular traffic using the right-of-way.

(c) The proposed development will not impact one or more of the existing access connections to the development site. Impact to an existing access connection includes, but is not limited to, increasing the number of vehicles, either directly or indirectly, that will utilize an existing access connection for ingress or egress to the development site.

(d) Compliance with EC 7.420(1)(c) will result in traffic patterns inconsistent with the character of the property located within a quarter mile radius of the development site or will increase the number of vehicular trips using the street with the lower classification above the typical daily trip range for that street’s classification.

(29) Street Standards Adjustment. Where this land use code provides that street standards may be adjusted, the standards may be adjusted upon a demonstration by the applicant that the requested adjustment is consistent with the following:

(a) The applicant has submitted a report prepared by an Oregon licensed civil engineer that demonstrates it is not technically or financially feasible to construct the street in accordance with adopted plans and policies, and the adopted “Design Standards and Guidelines for Eugene Streets, Sidewalks, Bikeways, and Accessways.”

(b) The adjustment is necessary due to at least one of the following conditions:

1. Existing on-site or off-site geologic or topographic conditions, or existing wetlands designated for protection by the City of Eugene; or

2. Existing development on lands abutting the development site.

(30) Driveways and Parking Areas in R-3 and R-4. The standards at EC 9.2751(15)(c)(9). may be adjusted if the applicant demonstrates that any hardscaped or non-landscaped areas are separated from the driveway and associated parking area, and that vehicle access and parking is physically precluded.

(31) /ND Nodal Development Overlay Zone. Where this land use code provides that a development standard applicable within the /ND Nodal Development overlay zone may be adjusted, approval of the request shall be given if the applicant demonstrates consistency with all of the following:

(a) The requested adjustment will allow the project to achieve an equivalent or higher quality design than would result from strict adherence to the standards through:

1. A building orientation, massing, articulation and façade that contribute positively to the surrounding urban environment; and

2. An overall site and building design that creates a safe and attractive pedestrian environment. Design elements for this purpose may include special architectural design features, high quality materials, outdoor seating, pedestrian-scaled lighting, prominent entries facing the street, multiple openings or windows, and a significant use of clear, untinted glass.

(b) Impacts to any adjacent residentially-zoned property are minimized. Design elements for this purpose may include treatment of building massing, setbacks, screening and landscaping.

(32) /TD Transit Oriented Development Overlay Zone. Where this land use code provides that a development standard applicable within the /TD Transit Oriented Development overlay zone may be adjusted, approval of the request shall be given if the applicant demonstrates consistency with all of the following:

(a) The requested adjustment will allow the project to achieve an equivalent or higher quality design than would result from strict adherence to the standards through:

1. A building orientation, massing, articulation and façade that contribute positively to the surrounding urban environment; and

2. An overall site and building design that creates a safe and attractive pedestrian environment. Design elements for this purpose may include special architectural design features, high quality materials, outdoor seating, pedestrian-scaled lighting, prominent entries facing the street, multiple openings or windows, and a significant use of clear, untinted glass.

(b) Impacts to any adjacent residentially-zoned property are minimized. Design elements for this purpose may include treatment of building massing, setbacks, screening and landscaping.

(33) Large Employment Facilities Standards Adjustment. Where this land use code provides that the large employment facilities standards may be adjusted, the standards may be adjusted upon finding that the proposed development achieves the purpose of EC 9.2463 through alternative or innovative design solutions.

(34) Accessory Dwellings. Where this land use code provides that the standards for accessory dwellings may be adjusted, the standards may be adjusted upon demonstration by the applicant that the applicable corresponding criteria are met.

(a) Conversion of Existing Building. A legally established building existing as of August 29, 2014, may be converted to an accessory dwelling if it complies with all of the following:

1. The existing structure satisfies all accessory dwelling standards except the applicable sloped setback under Building Height/Interior Setback at EC 9.2571(17)(a)2. or EC 9.2751(17)(b)5.

2. The accessory dwelling is limited to 600 square feet in total building square footage.

3. If the existing structure is closer than 5 feet to an interior property line, there must be a 10-foot separation between the accessory dwelling and buildings on the abutting lot and the owner of the accessory dwelling must secure and record in the office of the Lane County Recorder a maintenance access easement adjacent to the intruding side of the building. The easement shall provide a 5-foot wide access the entire length of the building and 5 feet beyond both ends and require the continuation of a 10-foot separation between buildings on the separate lots. The easement shall be on a form provided by the city and be subject to payment of a fee set by the city manager.

(b) Accessory Dwellings on Flag Lots. Where natural features or other physical conditions make it impracticable to comply with the driveway setback and landscape screening requirements, the following adjustments are allowed:

1. Except as provided in 2. below, the driveway setback may be reduced to no less than four feet; however, in no event shall the setback be reduced more than is necessary to enable the driveway to meet the minimum driveway width, or

2. The driveway setback may be reduced to no less than one foot, and screening requirements may be reduced or eliminated, where

a. The zoning of the adjacent property does not allow for residential uses; and

b. The impacts of the adjacent uses would not be significantly worse under the reduced setback or lessened screening.

(35) Alley Access Lots. Building Height/Interior Setback. A dwelling on an alley access lot may have maximum building height of up to 24 feet if all of the structure that would fall within the scope of the “Building Height/Sloped Setback” standard is at least 20 feet from all interior property lines and within the sloped setback.

(36) /CL Clear Lake Overlay Zone. Where EC 9.4165 provides that the development standards of the /CL Clear Lake Overlay Zone may be adjusted, approval of the request shall be given if the applicant demonstrates consistency with all of the following:

(a) The Purpose of the zone (EC 9.4150);

(b) Development impacts will have negligible effects on school and park users, surrounding residents, and the environment, and alternative mitigation measures will be employed to offset the proposed adjustment;

(c) Development will increase access to open space and improve ecological functions of natural features on-site;

(d) Development is consistent with local and regional economic development goals (e.g., it is one of the targeted industries from the City’s Economic Opportunities Analysis or Regional Prosperity Plan (2010)).

(37) Middle Housing Standards Adjustment. Where EC 9.5550 provides that standards applicable to triplexes, fourplexes, townhouses, or cottage clusters may be adjusted, approval of the request shall be given if the applicant demonstrates consistency with all of the following, as applicable:

(a) Entry Orientation. The requirements set forth in EC 9.5550(4)(c) and 9.5550(5)(d)1. may be adjusted if the overall proposal creates building orientations and entrances that achieve all of the following:

1. Enhances public safety for residents and visitors; and

2. Provides opportunities for community interaction; and

3. Ensures that the main entrance is visible or clearly identifiable from the street or from common open spaces by its orientation or articulation; and

4. Ensures that residents, visitors, and emergency personnel can easily find the main entrance, and so establish how to enter the residence.

(b) Garages, Off-Street Parking Areas, and Driveways for Triplexes and Fourplexes. The requirements set forth in EC 9.5550(4)(a) and (b) may be adjusted if the proposal achieves the following:

1. Supports a pedestrian-friendly street environment by minimizing the visual and safety impacts of garages, parking areas, and vehicle circulation areas.

2. Consistency with EC 9.8030(28).

(c) Townhouse Unit Features. The requirements set forth in EC 9.5550(5)(b) may be adjusted if the proposed building design utilizes architectural masses, features or details to distinguish elements of the building, such as entryways, windows, garages, and other elements.

(d) Townhouse Driveway Access and Parking. The requirements set forth in EC 9.5550(5)(c) may be adjusted if the proposal supports a pedestrian-friendly street environment by minimizing the visual and safety impacts of garages, parking areas, and vehicle circulation areas.

(e) General Standards for Cottage Clusters. The requirements set forth in EC 9.5550(6)(a) may be adjusted if the proposal overall achieves an equivalent or higher quality design by including the following:

1. Higher quality design elements, such as durable, high quality materials, architectural detail and craftsmanship, sustainable building design features, enhanced landscaping, or user amenities;

2. An enhanced sense of openness and community for residents by including elements such as abundant and highly functional common open space that is easily accessible and viewable from individual units through abundant windows and porches;

3. Amenities or design that enhance the livability, walkability, and safety of the residents and community, such as enhanced lighting features or easily accessible connectivity to neighborhood amenities;

4. Design that promotes compatibility with adjacent properties and the neighborhood through the scale of buildings and of the overall development pattern, through design elements that may include privacy screening, enhanced landscape buffers, or frontage improvements and amenities that are supportive of an active, walkable, and neighborly streetscape;

5. Enhanced design elements for cottage clusters over 8 units, such as design elements that enhance the common courtyard and open space and provide connectivity and access to shared amenities consistent with the intent of openness and community for residents. A single cottage cluster shall contain a maximum of 12 cottages;

6. An Accessory building must not exceed 600 square feet in floor area and shall comply with standards in EC 9.2751(16).

(f) Cottage Cluster Orientation Standards. The requirements set forth in EC 9.5550(6)(b) may be adjusted if the overall proposal achieves all of the following:

1. Provides a sense of community within a cottage cluster by including design features such as porches, outdoor living areas, and other features that incorporate transparency and openness to encourage passive observation and neighborly interactions, and

2. Each dwelling has pedestrian access to a common courtyard.

3. Dwellings within 20 feet of a front property line that abuts a street shall provide a pedestrian-friendly frontage that includes design features such as street facing porches, abundant windows, gateway elements, and other architectural features.

(g) Common Courtyard Design Standards. The requirements set forth in EC 9.5550(6)(c) may be adjusted if the requested adjustment will allow the project to achieve an equivalent or higher quality design of open space than would result from strict adherence to the standards through:

a. Enhanced spaces that contribute positively to the site, streetscape, and adjoining properties by including design elements such as high-quality materials, outdoor seating, enhanced pedestrian space, pedestrian-scaled lighting, canopy trees and other landscape materials and other user amenities; and

b. An overall design that promotes safety and security for residents and visitors.

(h) Community Building Standards. The requirements set forth in EC 9.5550(6)(d) may be adjusted if the community building is compatible in scale with dwellings in the cottage cluster, including, but not limited to, building height and building size.

(i) Cottage Cluster Parking Design Standards. The requirements set forth in EC 9.5550(6)(f) may be adjusted if the proposal achieves all of the following:

1. Supports a pedestrian-friendly street environment; and

2. Supports livability for cottage cluster residents by minimizing the impacts of parking areas and garages.

3. Consistency with EC 9.8030(28).

(38) River Road/Santa Clara Neighborhood Specific Standards. Where this land use code provides that the River Road/Santa Clara Neighborhood Specific Standards can be adjusted, the standards may be adjusted upon finding that the design achieves all of the following:

(a) Contributes to the continuity of building facades along the street;

(b) Creates an attractive pedestrian environment along all adjacent streets; and

(c) Is compatible with adjacent development.

(Section 9.8030, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20267, enacted November 12, 2002, effective March 3, 2003; Ordinance No. 20271, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20275, enacted January 13, 2003, effective February 12, 2003; administratively corrected March 31, 2003; amended by Ordinance 20285, enacted March 10, 2003, effective April 9, 2003; Ordinance 20297, enacted August 11, 2003, effective September 10, 2003; Ordinance No. 20299, enacted October 22, 2003, effective November 21, 2003, remanded on February 25, 2005 and provisions administratively removed on April 11, 2005; administratively corrected April 5, 2004; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28,2005, effective January 1, 2006; Ordinance No. 20355, enacted December 12, 2005, effective January 13, 2005; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance 20433, enacted June 8, 2009, effective July 10, 2009; Ordinance 20449, enacted December 14, 2009, effective January 16, 2010; Ordinance 20457, enacted March 8, 2010, effective April 10, 2010; Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010; Ordinance No. 20492, enacted May 14, 2012, effective June 15, 2012; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20514, enacted July 22, 2013, effective August 24, 2013; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20526, enacted March 12, 2014, effective April 12, 2014; Ordinance No. 20528, enacted May 14, 2014, effective June 23, 2014; Ordinance No. 20541, enacted July 28, 2014, effective August 29, 2014; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20594, enacted June 11, 2018, effective July 1, 2018, remanded on November 29, 2018, and provisions administratively removed; Ordinance No. 20619, enacted July 22, 2019, effective August 25, 2019; Ordinance No. 20625, enacted January 21, 2020, effective February 22, 2020, remanded on November 24, 2020, and provisions administratively removed; Ordinance No. 20659, enacted September 15, 2021, effective September 17, 2021; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023; Ordinance No. 20699, enacted November 13, 2023, effective December 31, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20708, enacted April 22, 2024, effective May 30, 2024; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025; Ordinance No. 20724, enacted March 10, 2025, effective July 1, 2025.)

9.8035 Annexation Application Requirements and Criteria.

The provisions for processing annexation applications are found in EC 9.7800 through 9.7835, Annexation Application Procedures and Criteria.

(Section 9.8035, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20400, enacted December 10, 2007, effective January 1, 2008.)

9.8040 Purpose of Cluster Subdivisions.

The cluster subdivision provisions are designed to provide for flexibility in achieving the allowed density while protecting natural resources or creating open space on development sites in residential zones.

(Section 9.8040, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8045 Applicability of Cluster Subdivisions.

Cluster subdivision provisions shall be applied when requested by the property owner and when the proposed subdivision meets the definition of cluster subdivision in section 9.0500 of this land use code. A subdivision application proposing housing to be reviewed with clear and objective approval criteria shall be processed pursuant to EC 9.8520 Subdivision, Tentative Plan Approval Criteria – Housing/Clear and Objective. No development permit shall be issued by the city prior to approval of the cluster subdivision.

(Section 9.8045, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8050 Cluster Subdivision Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements shall apply to tentative cluster subdivision plan applications.

(1) All cluster subdivision applications shall include the standard subdivision requirements set forth in EC 9.8510 Subdivision, Tentative Plan Application Requirements except for 9.8510(4).

(2) The cluster subdivision application shall identify a project coordinator that is either licensed in the state of Oregon to practice architecture or landscape architecture. For applications that include 4 acres or more, the application shall also include a professional design team consisting of at least the following professionals:

(1) Architect.

(2) Civil Engineer or Land Surveyor.

(3) Landscape Architect or Planner.

(Section 9.8050, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8055 Cluster Subdivision – Approval Criteria – General/Discretionary.

The planning director shall approve, approve with conditions, or deny a proposed cluster subdivision. Approval or approval with conditions shall be based on the following:

(1) The proposed subdivision complies with:

(a) EC 9.8515 Subdivision, Tentative Plan Approval Criteria – General/Discretionary except for the standards related to EC 9.2760 Residential Zone Lot Standards; and

(b) EC 9.2750 Residential Zone Development Standards;

(c) Within the /WR Water Resources Conservation Overlay Zone or the /WQ Water Quality Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would be occupied by either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area;

(d) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

With the exception of density requirements, the residential development standards of EC 9.2750 Residential Zone Development Standards and EC 9.2751 Special Development Standards for Table 9.2750 may be relaxed based on compliance with the remainder of the cluster subdivision criteria. An exception or an adjustment to a development standard constitutes compliance with the standard.

(2) For areas not included on the city’s acknowledged Goal 5 inventory, the proposed subdivision includes at least 25% of the development site in common open space that either is suitable area for natural resource protection or for use by residents. Areas used for motor vehicle parking and maneuvering shall not be considered as open space.

(3) For areas not included on the city’s acknowledged Goal 5 inventory, the proposed subdivision shall maintain open space around natural features, such as steep slopes, wooded areas, and natural waterways or wetlands where those exist, or create common open space with amenities for community activities for residents such as picnic areas, playgrounds, sports features, or gardens.

(4) The cluster subdivision will provide an appropriate transition to surrounding properties including, but not limited to, anticipated building locations, bulk, and height.

(5) The proposed residential density, accounting for any duplex, tri-plex and fourplex lots, shall comply with Table 9.2750 Residential Zone Development Standards.

(6) The proposed development provides adequate degree of light, air circulation, and privacy for residents within the development.

(7) For areas included on the city’s acknowledged Goal 5 inventory, natural resource protection shall be consistent with the acknowledged level of protection provided for the resource.

(Section 9.8055, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003;and administratively corrected June 5, 2003; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; amended by Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; administratively corrected August 28, 2006 and February 5, 2007; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; amended by Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8060 General Requirements.

Sections 9.8060 through 9.8065 apply to amendments to this land use code, which shall be processed as provided in EC 9.7500 through EC 9.7560, under Type V Application Procedures.

(Section 9.8060, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8065 Code Amendment Approval Criteria.

If the city council elects to act, it may, by ordinance, adopt an amendment to this land use code that:

(1) Is consistent with applicable statewide planning goals as adopted by the Land Conservation and Development Commission.

(2) Is consistent with applicable provisions of the comprehensive plan and applicable adopted refinement plans.

(3) In the case of establishment of a special area zone, is consistent with EC 9.3020 Criteria for Establishment of an S Special Area Zone.

(Section 9.8065, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; and Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8070 Envision Eugene Comprehensive Plan Amendment – Purpose.

The Envision Eugene Comprehensive Plan is intended to reflect the community’s long-term vision. The Envision Eugene Comprehensive Plan must be flexible to adapt to changing conditions and emerging needs in the community and to respond to new data that relates to assumptions and projections in the plan. To ensure the plan remains effective, desirable and relevant, amendments are expected. The provisions of EC 9.8070 through EC 9.8074 set out the procedures and criteria that apply to amendments to the Envision Eugene Comprehensive Plan. These procedures apply to all amendments to the Envision Eugene Comprehensive Plan, whether a minor revision to a portion of the plan or a comprehensive update to the plan.

(Section 9.8070 added by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8072 Envision Eugene Comprehensive Plan Amendment – Applicability.

EC 9.8070 through EC 9.8074 apply only to amendments to the Envision Eugene Comprehensive Plan. For procedures and criteria applicable to amendments to the Eugene – Springfield Metropolitan Area General Plan, see EC 9.7700. For procedures and criteria applicable to amendments to refinement plans, see EC 9.8421.

(Section 9.8072 added by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8073 Envision Eugene Comprehensive Plan Amendment – Application and Approval Process.

(1) Initiation. Amendments to the Envision Eugene Comprehensive Plan may be proposed only as described in this subsection. The city council may initiate consideration of any amendment to the Envision Eugene Comprehensive Plan without the need for an application form.

(2) Approval Process.

(a) Proposed amendments to the Envision Eugene Comprehensive Plan shall be reviewed under the Type IV process for site-specific amendments pursuant to EC 9.7400 – 9.7455 or, otherwise, a Type V process pursuant to EC 9.7500 – 9.7560.

(b) A proposed amendment to the Envision Eugene Comprehensive Plan requires approval of both the City of Eugene and Lane County only when the proposed amendment would apply to land located between the Eugene city limits and the Eugene urban growth boundary. Except as provided in subsection (c), below, when an amendment to the Envision Eugene Comprehensive Plan requires approval of both the City of Eugene and Lane County, both jurisdictions shall follow the EC Type IV or Type V process, with a joint hearing held before the Eugene planning commission and the Lane County planning commission and a joint hearing held before the city council and the board of commissioners. Deliberations may be held separately.

(c) If a proposed amendment to the Envision Eugene Comprehensive Plan is being reviewed concurrently with a proposed amendment to the Metro Plan, the Metro Plan amendment process shall be used to consider both proposed amendments instead of the Type IV or V process.

(Section 9.8073 added by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8074 Envision Eugene Comprehensive Plan Amendment – Amendment Approval Criteria.

If the city council decides to act, the application shall be approved, approved with modifications or denied based on compliance with the following criteria:

(1) The proposed amendment is consistent with the Statewide Planning Goals.

(2) The proposed amendment is consistent with the Eugene-Springfield Metropolitan Area General Plan.

(3) The proposed amendment is consistent with the remaining portions of the Envision Eugene Comprehensive Plan.

(4) The proposed amendment will not result in a deficit in the city’s needed supply of employment or residential land, based on the most recently adopted and acknowledged employment land study or residential land study.

(Section 9.8074 added by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8075 Purpose of Conditional Use Permits.

Certain types of uses require special consideration before being permitted in particular zones. The reasons for requiring special consideration include, for example, the size of the area required for the full development of those uses, the nature of traffic problems incidental to operation of those uses, the effect those uses might have on adjoining land uses, potential environmental impacts, and their effect on the growth and development of the community as a whole. Uses permitted only with a conditional use permit may also possess unique or special characteristics that make it unacceptable to permit them in particular zones without conditions. In zones where a use may be conditionally permitted, the location and operation of the use is subject to conditional use permit review and approval under a Type III application procedure. One purpose for the review is to determine if the characteristics of the use can be made reasonably compatible with the type of uses permitted outright in surrounding areas. Another purpose is to provide reasonable and necessary conditions so the basic purposes of this land use code are served.

(Section 9.8075, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8080 Applicability.

Conditional use permits apply to the initiation or expansion of a use listed as being subject to the conditional use permit review process in this land use code. When a conditional use permit is required, no development permit shall be issued by the city prior to approval of the conditional use permit.

(Section 9.8080, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8085 Conditional Use Permit Application Requirements.

(1) Conditional use applications shall be processed in accordance with the application procedures contained in EC 9.7000 through 9.7925, Application Procedures.

(2) When a conditional use permit is required for the proposed use, no development permit application shall be accepted by the city until the hearings official or planning commission approves the conditional use permit, and then only in accordance with the terms and conditions of that conditional use permit.

(3) If the proposal includes housing, the written statement submitted with the conditional use permit application shall clearly state whether the applicant is electing to use the discretionary approval criteria in EC 9.8090 Conditional Use Permit Approval Criteria – General/Discretionary instead of the approval criteria found in EC 9.8100 Conditional Use Permit Approval Criteria – Housing/Clear and Objective.

(Section 9.8085, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; administratively corrected on March 22, 2018; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8090 Conditional Use Permit Approval Criteria – General/Discretionary.

A conditional use permit shall be granted only if the proposal conforms to all of the following criteria:

(1) The proposal is consistent with applicable provisions of the Metro Plan and applicable refinement plans.

(2) The location, size, design, and operating characteristics of the proposal are reasonably compatible with and have minimal impact on the livability or appropriate development of surrounding property, as they relate to the following factors:

(a) The proposed building(s) mass and scale are physically suitable for the type and density of use being proposed.

(b) The proposed structures, parking lots, outdoor use areas or other site improvements which could cause substantial off-site impacts such as noise, glare and odors are oriented away from nearby residential uses and/or are adequately mitigated through other design techniques, such as screening and increased setbacks.

(c) If the proposal involves a residential use, the project is designed, sited and/or adequately buffered to minimize off-site impacts which could adversely affect the future residents of the subject property.

(3) The location, design, and related features of the proposal provides a convenient and functional living, working, shopping or civic environment, and is as attractive as the nature of the use and its location and setting warrant.

(4) The proposal demonstrates adequate and safe circulation exists for the following:

(a) Vehicular access to and from the proposed site, and on-site circulation and emergency response.

(b) Pedestrian, bicycle and transit circulation, including related facilities, as needed among buildings and related uses on the development site, as well as to adjacent and nearby residential areas, transit stops, neighborhood activity centers, office parks, and industrial parks, provided the city makes findings to demonstrate consistency with constitutional requirements. “Nearby” means uses within 1/4 mile that can reasonably be expected to be used by pedestrians, and uses within 2 miles that can reasonably be expected to be used by bicyclists.

(5) The proposal is designed and sited to minimize impacts to the natural environment by addressing the following:

(a) Protection of Natural Features.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the preservation of significant natural features to the greatest degree attainable or feasible, including:

a. Significant on-site vegetation, including rare plants (those that are proposed for listing or are listed under state or federal law), and native plant communities.

b. All documented habitat for all rare animal species (those that are proposed for listing or are listed under state or federal law).

c. Prominent topographic features, such as ridgelines and rock outcrops.

d. Wetlands, intermittent and perennial stream corridors and riparian areas.

e. Natural resource areas designated in the comprehensive plan diagram as “Natural Resource” and areas identified in any city-adopted natural resource inventory.

2. For areas included on the city’s acknowledged Goal 5 inventory, the preservation of natural features shall be consistent with the acknowledged level of preservation provided for the area.

(b) Tree Preservation. The proposed project shall be designed and sited to preserve significant trees to the greatest degree attainable or feasible, with trees having the following characteristics given the highest priority for preservation:

1. Healthy trees that have a reasonable chance of survival considering the base zone or special area zone designation and other applicable approval criteria

2. Trees located within vegetated corridors and stands rather than individual isolated trees subject to windthrow.

3. Trees that fulfill a screening function, provide relief from glare, or shade expansive areas of pavement.

4. Trees that provide a buffer between potentially incompatible land uses.

5. Trees located along the perimeter of the lot(s) and within building setback areas.

6. Trees and stands of trees located along ridgelines and within view corridors.

7. Trees with significant habitat value

8. Trees adjacent to public parks, open space and streets.

9. Trees along water features.

10. Heritage trees.

(c) Restoration or Replacement.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the proposal mitigates, to the greatest degree attainable or feasible, the loss of significant natural features described in criteria (a) and (b) above, through the restoration or replacement of natural features such as:

a. Planting of replacement trees within common areas; or

b. Re-vegetation of slopes, ridgelines, and stream corridors; or

c. Restoration of fish and wildlife habitat, native plant habitat, wetland areas, and riparian vegetation.

To the extent applicable, restoration or replacement shall be in compliance with the planting and replacement standards of EC 6.320.

2. For areas included on the city’s acknowledged Goal 5 inventory, any loss of natural features shall be consistent with the acknowledged level of preservation provided for the resource.

(d) Street Trees. If the proposal includes removal of any street tree(s), removal of those street tree(s) has been approved, or approved with conditions according to the process at EC 6.305 of this code.

(6) The proposal provides adequate public facilities and services including, but not limited to utilities, streets, and other infrastructure.

(7) The proposal does not create any significant risk to public health and safety, including but not limited to soil erosion and flood hazard, or an impediment to emergency response.

(8) The proposal complies with all applicable standards, including but not limited to:

(a) EC 9.2000 through 9.4170 regarding lot dimensions, solar standards, and density requirements for the subject zone and overlay zone;

(b) EC 9.6500 through EC 9.6505 Public Improvement Standards;

(c) EC 9.6735 Public Access Required.

(d) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance; and

(e) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and other Public Ways;

(f) Where the proposal is to establish non-residential uses subject to residential density requirements on development sites in the residential zone category, it shall achieve the minimum and maximum density requirements in accordance with Table 9.2750 Residential Zone Development Standards, unless specifically exempted elsewhere in this code or granted a modification through an approved conditional use permit. For purposes of calculating “net density,” the acreage of land considered shall include the entire development site and exclude public property, such as public streets, parks, and other public facilities. In considering whether to grant a modification to the density requirements, the hearings official shall evaluate the following factors:

1. The availability of the development site for residential use on August 1, 2001. The term “availability” in this section shall include consideration of whether the site was already developed with non-residential uses or had other site constraints impacting its suitability for residential use.

2. The necessity of the development site to be developed with residential uses to be able to achieve the minimum residential density for the area designated on the comprehensive plan diagram for either medium – or high-density residential use.

3. Adopted plan policies indicate the suitability and appropriateness of the site for non-residential use.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard. Additional criteria may also be required based on the applicability of other sections of this land use code.

(9) The proposal complies with the Traffic Impact Analysis Review provisions of EC 9.8650 through 9.8680 where applicable.

(Section 9.8090, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance No. 20457, enacted March 8, 2010; effective April 10, 2010; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; and Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8100 Conditional Use Permit Approval Criteria – Housing/Clear and Objective.

The hearings official shall approve, conditionally approve, or deny the conditional use permit application. Unless the applicant elects to use the discretionary criteria contained in EC 9.8090 Conditional Use Permit Approval Criteria – General/Discretionary, where the applicant proposes housing, the hearings official shall approve or approve with conditions a conditional use based on compliance with the following criteria:

(1) The proposal complies with EC 9.5860 Transition Standards.

(2) If applicable, the proposal complies with the standards contained in EC 9.5500 Multiple-Unit Standards.

(3) For areas not included on the city’s acknowledged Goal 5 inventory, the proposal will preserve existing natural resources by compliance with the provisions of EC 9.6880 to EC 9.6885 Tree Preservation and Removal Standards.

(4) The proposal complies with:

(a) EC 9.2000 through EC 9.4170 regarding lot dimensions and density requirements for the subject zone and any applicable overlay zones.

(b) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(c) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(d) EC 9.6710(6) Geological and Geotechnical Analysis.

(e) EC 9.6730 Pedestrian Circulation On-Site.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(l) All other applicable development standards for features explicitly included in the application.

(m) An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(5) Public improvements as required by this land use code or as a condition of approval will be completed prior to issuance of a development permit, or:

(a) A performance bond or suitable substitute as agreed upon by the city has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the conditional use permit, and the petition has been accepted by the city engineer.

(6) If the standards addressed under EC 9.8100(4) require a public street, or if the applicant proposes the creation of a public street, the proposal will provide pedestrian and bicycle circulation to transit stops and neighborhood activity centers located within 1/4 mile of the development site, provided the city makes findings to demonstrate consistency with constitutional requirements. The distance between the development site and a transit stop or neighborhood activity center shall be determined using the shortest distance as measured in a straight line between a point along the perimeter of the development site and:

(1) A sign identifying a transit stop; or

(2) A point along a property line of a neighborhood activity center.

(Section 9.8100, see chart at front of Chapter 9 for legislative history from 2/26/01 to 6/1/02; amended by Ordinance No. 20297, enacted August 11, 2003, effective September 10, 2003; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8105 Conditional Use Permits within the NR Natural Resource Zone or /WB Wetland Buffer Overlay Zone.

(1) Purpose. This classification of conditional use is provided in order to facilitate special review of certain uses within the natural resource zone or the wetland buffer overlay zone. It is intended to implement policies in the adopted West Eugene Wetlands Plan or other applicable plans.

(2) Criteria for Hearings Official Approval. Applications for conditional use permits within the NR natural resource zone or /WB wetland buffer overlay zone shall be processed and scheduled for public hearings in the same manner as other conditional use permit applications, except that NR standards (2) through (19) listed in EC 9.2530 Natural Resource Zone Development Standards shall be considered as additional criteria along with the criteria listed in EC 9.8090 Conditional Use Permit Approval Criteria – General/Discretionary.

(Section 9.8105, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8107 Modifications to Approved Conditional Use Permit.

After the effective date of the approval of the conditional use permit, modifications to the approved conditional use permit may be considered in accordance with the Type II application procedures contained in EC 9.7200 through 9.7230, Type II Application Procedures. The planning director shall approve the request only if it complies with the following criteria.

(1) The proposed modification is not materially inconsistent with the conditions of the original approval; and

(2) The proposed modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If the requested modification does not meet the criteria for approval, the application will be denied. The applicant may submit the requested modification as a new conditional use permit application based on Type III procedural requirements. Nothing in this land use code shall preclude the applicant from initially submitting the requested modification as a new conditional use permit application.

(Section 9.8110, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; renumbered as 9.8107 by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8109 Conditional Use Permit, Revocation.

The hearings official may revoke a conditional use permit based on the criteria in EC 9.0260 Revocation of Conditional Use Permits, in the manner provided in that section.

(Section 9.8113, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; renumbered as 9.8109 by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8110 Design Review – Purpose.

The design review process is intended to provide an alternative path for design proposals that respond to the intent of the code and creatively meet or exceed the specific development standards.

(Section 9.8110 added by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8111 Design Review – Applicability.

Applicants within the S-WS Walnut Station Special Area Zone or S-DR Downtown Riverfront Special Area Zone may seek approval through the Design Review process per EC 9.3980 or EC 9.3190. These applications for review shall be considered under a Type II process, or concurrently with a related Type III application process. No development permit shall be issued by the city prior to completion of the design review.

(Section 9.8111 added by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010; amended by Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013.)

9.8112 Design Review – Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, applications for Design Review shall be subject to the following requirements:

(1) Unless waived by the planning director, the application shall be prepared by one or more of the following professionals:

(a) Oregon licensed architect.

(b) Oregon licensed civil engineer.

(c) Oregon licensed landscape architect.

(2) The application shall include a site plan that shows sufficient detail and supporting narrative information to demonstrate compliance with applicable criteria. Unless waived by the planning director, the site plan shall be prepared by an Oregon licensed architect, landscape architect, civil engineer or Oregon licensed surveyor.

(Section 9.8112 added by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8113 Design Review – Approval Criteria.

The decision-maker shall determine whether the application is in compliance with the Design Review criteria set out in the code section that authorizes Design Review.

(Section 9.8113 added by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8114 Design Review – Modification.

Modification of an approved Design Review may be requested following the Type II process. The planning director shall approve the request if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will result in insignificant changes in the physical appearance of the development and the impact on surrounding properties.

If the planning director determines that the modification is not consistent with the above criteria, the proposed modification may not occur until a new Design Review application is submitted and reviewed based on the Type II application procedures. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new Design Review application.

(Section 9.8114 added by Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8115 Extra-Territorial Extension of Water or Sewer Service – Purpose.

Sections 9.8115 through 9.8121 govern the approval of requests that the city extend water service or sewer service from inside the city limits to serve property located outside of the city limits. Except as specifically permitted in EC 9.8121, extensions may not go beyond the urban growth boundary. These regulations are intended to accomplish the orderly development of land within the urban growth boundary, ensure the adequate provision or public facilities and services, protect the public health and safety of the community and enable development to occur consistent with applicable provisions of the comprehensive plan. Terms and criteria may be more specifically explained in adopted city resolutions concerning extra-territorial extensions.

(Section 9.8115 added by Ordinance No. 20400, enacted December 10, 2007, effective January 1, 2008; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8117 Extra-Territorial Extension of Water or Sewer Service – Applicability.

(1) The provisions of EC 9.8115 through 9.8121 apply to applications requesting the extension of water service or sewer service from inside the city limits to serve property located outside of the city limits, except as provided in subsection (2) below.

(2) Approval for extra-territorial extension of water or sewer service to property located within the boundary of the Industrial Corridor Community Organization as shown on Map 9.8117 Industrial Corridor, is automatic upon approval of a building or development permit so long as the property owner executes an irrevocable consent to annexation form approved by the city attorney, authorizing the city council to annex the property whenever the annexation is authorized by state law. This subsection (2) shall not apply to property that is eligible for annexation.

(Section 9.8117 added by Ordinance No. 20400, enacted December 10, 2007, effective January 1, 2008; amended by Ordinance No. 20581, enacted May 22, 2017, effective June 23, 2017.)

9.8119 Extra-Territorial Extension of Water or Sewer Service – Application Requirements.

In addition to the provisions of EC 9.7010 Application Filing, an application for extra-territorial extension of water or sewer service shall include the following:

(1) A list of all tax lots proposed to be served, including street addresses;

(2) The proposed number of service connections and their locations;

(3) A written narrative addressing the proposal’s consistency with the approval criteria in EC 9.8121.

(Section 9.8119 added by Ordinance No. 20400, enacted December 10, 2007, effective January 1, 2008.)

9.8121 Extra-Territorial Extension of Water or Sewer Service – Procedures and Approval Criteria.

The city council shall hold a public hearing to consider an application for an extra-territorial extension of water or sewer service.

(1) Notice of the public hearing shall be:

(a) Mailed at least 30 days prior to the public hearing to:

1. The applicant;

2. Owners and occupants of properties located within 750 feet of the perimeter of the subject property; and

3. The neighborhood group or community organization officially recognized by the city council that includes the area of the subject property and any neighborhood group or community organization officially recognized by the city council for the area that is located within 750 feet of the perimeter of the subject property

(b) Published in a local newspaper with general circulation at least 20 days prior to the public hearing; and

(c) Posted on the property that is the subject of the application in a location clearly visible from adjacent streets.

(2) The city council shall adopt a resolution approving or denying the application. The city council’s decision is final, and shall be based on compliance with the following criteria:

(a) The property proposed for service is located within the city’s urban growth boundary, is located within the property boundaries of the Mahlon Sweet Airport, or, for purposes of water extension only, Lane Community College;

(b) In no case shall the city extend services extra-territorially to a property that could, instead, be annexed. Further, to receive extra-territorial water or sewer service an applicant must demonstrate the inability to satisfy either EC 9.7825(2) or (3);

(c) The applicant has entered into an annexation agreement on forms provided by the city pertaining to the property proposed to be served or will enter into such an annexation agreement as a condition of approval;

(d) The property proposed for service is not vacant;

(e) The provision of service will not prolong uses which are nonconforming uses under the Eugene Code, 1971;

(f) In the case of an application for extension of water service, the property to be served is connected with an approved means of sewage disposal;

(g) The proposed extension is consistent with adopted resolutions, policies, plans and ordinances concerning extra-territorial extensions; and

(h) Even if a proposed extension is inconsistent with the criteria above, the city may approve an extra-territorial extension of water or sewer service consistent with adopted city resolutions, policies, plans and ordinances:

1. Where a communicable disease hazard exists and the extension is the only practical remedy; or

2. To property within a dissolved water district within which EWEB is providing service to some properties.

(Section 9.8121added by Ordinance No. 20400, enacted December 10, 2007, effective January 1, 2008; and amended by Ordinance No. 20411, enacted June 9, 2008, effective July 11, 2008.)

9.8130 Purpose of Hazardous Materials Review.

The purpose of Hazardous Materials Review is to ensure that a development or use proposed to be located in an area with either known or potential special hazardous materials is established only if necessary steps have been taken to address issues of public health, safety and welfare.

(Section 9.8130, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8135 Applicability.

Hazardous material review is required when the development or use is proposed to be located in an area with either known or potential special hazardous materials, as defined in this code or rules issued thereunder, based on the prior use of the site or the existence of hazardous materials located on or adjacent to the site.

(Section 9.8135, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8140 General Application Requirements.

An application for Hazardous Materials Review shall contain each of the items required by the American Society for Testing and Materials (ASTM) Standards E-1527 and E-1528, available at the city’s public works department.

(Section 9.8140, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8145 Approval Criteria.

The planning director shall approve, conditionally approve, or deny an application for Hazardous Materials Review, following a Type II process. Approval or conditional approval shall be based on compliance with the following criteria:

(1) The proposed development or use will have no adverse health or safety impacts on the community.

(2) The proposed development or use will meet adopted city standards related to hazardous materials.

(3) All mitigating measures necessary to alleviate impacts to public health, safety and welfare have been identified and provided for.

(4) The design and construction of building foundations and public and private utilities and infrastructure improvements meet adopted city standards.

(Section 9.8145, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8150 Purpose of Historic Property Applications.

To help make the citizens of the community and its visitors aware of the origin, development, and historic significance of property, this land use code contains regulations for the preservation of historic property.

(Section 9.8150, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8155 Applicability.

These regulations are applicable to historic property as defined in this land use code.

(Section 9.8155, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8160 General Application Requirements.

All historic property applications shall be submitted on a form approved by the city manager and in the manner provided in EC 9.7000 through EC 9.7030, and shall also comply with the following additional requirements for historic property applications:

(1) Historic Landmark Designation. The historic landmark designation follows a Type III process and may be initiated by the property owner, planning director, or city council.

(2) Historic Landmark – Removal of Designation. The property owner of a historic landmark or the planning director may initiate the process to remove historic landmark designation. Removal applications shall follow a Type I process.

(3) Historic Property Demolition. A pre-application conference is required prior to submittal of a historic property demolition application. The demolition application shall follow a Type II application process (EC 9.7010 Application Filing). In order for the city to determine that a historic property demolition application is complete, the owner shall establish that within the previous year the owner has solicited purchase offers for the historic property by giving notice of sale of the property as follows:

(a) Listing the property for sale in both The Register Guard and Oregonian at least six times and at regular intervals;

(b) Posting and maintaining visible for sale sign(s) on the property as specified by the planning director; and

(c) Making a financial prospectus on the status of the property available to interested parties.

As part of the historic property demolition application, the applicant shall prepare and submit a historic property mitigation report.

(Section 9.8160, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8165 Historic Landmark – Designation Approval Criteria.

The historic review board shall designate a historic resource as a historic landmark if it finds that the following criteria are met:

(1) Designation is consistent with applicable provisions of the Metro Plan and applicable refinement plans.

(2) Designation is based on a determination of historic significance according to one or more of the following:

(a) Is associated with events that have made a significant contribution to the broad patterns of history.

(b) Is associated with the lives of persons significant to our past.

(c) Embodies the distinctive characteristics of a type, period, or method of construction, or represents the work of a master, or possesses high artistic values, or represents a significant and distinguishable entity whose components may lack individual distinction.

(d) Yields, or may be likely to yield, information important to prehistory or history.

(3) In addition to EC 9.8165(1) and (2) above, criteria for designation of a historic resource that was moved, is primarily commemorative in intent, or less than fifty years of age shall include the following considerations:

(a) A historic resource moved from its original location or a place that has historic significance can be eligible if it has historic architectural significance or is the surviving property most importantly associated with a historic person or event.

(b) A historic resource that is primarily commemorative in intent can be eligible if design, age, tradition, or symbolic value has invested it with its own historic significance.

(c) A historic resource achieving significance within the last fifty years can be eligible if it is of exceptional importance.

(Section 9.8165, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8170 Historic Landmark – Removal of Designation Approval Criteria.

The planning director shall remove a historic property from the local list of landmark designations if any of the following conditions are met:

(1) Upon verification that the historic landmark is demolished or moved.

(2) The property owner requests that the local historic landmark designation be removed.

(Section 9.8170, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8175 Historic Property – Alteration Approval Criteria.

The planning director shall approve, approve with conditions or deny an application for historic property alteration. Approval, or conditional approval shall be granted if all of the following criteria for historic rehabilitation or historic restoration work are met:

(1) The historic significance of the property is retained and preserved by minimizing the removal of distinctive materials or alteration of features, spaces, and spatial relationships that characterize the historic property.

(2) The historic property remains recognizable as a physical record of its time, place, and use. The alteration will not create a false sense of historical development by adding conjectural features or elements from other historic properties or time periods.

(3) Changes to the property that have acquired historic significance in their own right are retained and preserved to the extent possible.

(4) Distinctive materials, features, finishes, construction techniques, or examples of skilled craftsmanship that characterize the property are retained to the extent possible.

(5) Deteriorated historic features are repaired rather than replaced. Where the severity of deterioration requires replacement of a distinctive feature, the new feature matches the old in design, color, texture, and where possible, materials. Whenever possible replacement of missing features, including identified historic landscape features, is substantiated by historic, pictorial, or physical evidence rather than on conjectural designs.

(6) New additions, exterior alterations, or related new construction do not unnecessarily destroy historic materials, features, and spatial relationships that characterize the property. The new work is differentiated from the old and is compatible with the historic materials, features, size, scale and proportion, and massing to protect the integrity of the property and its environment. If a historic property alteration is removed in the future, the essential form and integrity of the historic property and its environment will be unimpaired to the extent possible.

(7) If applicable, the proposed alteration is consistent with development standards or design guidelines adopted by the historic review board.

(8) Every reasonable effort is made to protect known archeological resources affected by and adjacent to any alteration project. If such resources must be disturbed, mitigation measures shall be undertaken.

(9) The proposed alteration complies with all applicable standards or adjustments thereto made pursuant to provisions beginning at EC 9.8015 of this land use code.

(Section 9.8175, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8180 Historic Property – Demolition Approval Criteria.

No person may demolish a historic property unless the planning director has approved, with or without conditions, an application to do so and a demolition permit has been obtained from the city manager. (Refer to EC 9.8160 General Application Requirements concerning pre-application requirements.) The planning director may condition approval of the application upon a postponement of the demolition if it will likely result in preservation of the historic property at its current site. A postponement shall be for a maximum of 60 days from the time the city determines the application is complete. If a postponement is a condition of approval, the decision of the planning director shall be in writing and contain findings and conclusions. The planning director shall consider the following in assessing the likelihood of preservation:

(1) The state of repair of the historic property and the financial and physical feasibility of historic rehabilitation, historic property moving, or leaving the property in its current state or location.

(2) The effects of the moving upon the use and development of the historic property.

(3) The marketability of the property and the willingness of the property owner to sell the property.

As a condition of approval of a demolition permit the planning director may impose certain documentation or artifact preservation requirements as outlined in the application form. These application provisions may be waived by the planning director based on public safety concerns and an immediate need to allow the structure to be demolished. Waiver under this section however does not waive the requirement for a demolition permit that would be applicable for property without historic property designation.

(Section 9.8180, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8185 Historic Property – Moving Approval Criteria.

No person may move a historic property unless the planning director has approved an application to do so and the necessary permits have been obtained. The planning director shall approve the application unless a postponement will likely result in preservation of the historic property at its current site. A postponement shall be for a maximum of 60 days from the time the city determines the application is complete. If the planning director requires postponement, the decision shall be in writing and contain findings and conclusions. The planning director shall consider all of the following in assessing the likelihood of historic preservation:

(1) Relocation is the only viable alternative for preservation of the historic property.

(2) The effects of the moving upon the use and development of the historic property.

(3) The historic property is structurally capable of relocation.

(4) The proposed new relocation site will not reduce the historic significance or historic architectural significance of the historic property.

When a historic property is moved to a new location, the historic property status is automatically removed for that property at the new site unless the planning director, using the process required for designation, determines that the historic landmark designation is appropriate.

(Section 9.8185, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8187 Interpretations.

Interpretations of this land use code and decisions issued pursuant to this land use code shall be determined as provided in EC 9.0040 Land Use Code and Decision Interpretation.

(Section 9.8187, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8190 Metro Plan Amendments Application Requirements and Criteria.

Provisions for Metro Plan amendment applications are found beginning at EC 9.7700 Metro Plan Amendment Procedures.

(Section 9.8190, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8191 Purpose of Middle Housing Land Division, Tentative Plan.

Sections 9.8191 through 9.8199 govern the approval of middle housing land divisions. These regulations are intended to accomplish the orderly development of land within the community, ensure the adequate provision of public facilities and services, protect public health and safety, enable development to occur consistent with applicable provisions of the comprehensive plan, enable home ownership, and comply with state laws requiring the allowance of land divisions to create small lots for individual units of middle housing.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8192 Applicability of Middle Housing Land Division, Tentative Plan Applications.

(1) Except as provided in subsection (2), Middle housing land divisions are subject to the application procedures in EC 9.7900 through EC 9.7925.

(2) An applicant may elect to have a Middle Housing Land Division application reviewed concurrently with a subdivision or partition application. If the applicant elects concurrent review, the procedures that will apply to review and appeal of the Middle Housing Land Division application are the procedures applicable to review and appeal of the subdivision or partition application. EC 9.7640 through 9.7644 and EC 9.7900 through 9.7925 do not apply to Middle Housing applications reviewed concurrently with subdivision or partition applications. All other provisions of this code continue to apply to each application, including but not limited to approval criteria.

(3) The creation of middle housing lots through a middle housing land division is permitted:

(a) On a lot or parcel prior to the development of middle housing, consistent with the approval criteria in subsections (1) and (3)-(9), of EC 9.8194.

(b) On a lot or parcel developed with middle housing, consistent with the approval criteria in subsections (2) and (3)-(9), of EC 9.8194.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8193 Middle Housing Land Division, Tentative Plan Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements apply to middle housing land division tentative plan applications:

(1) The tentative plan included in the middle housing land division application must be prepared by an Oregon licensed land surveyor.

(2) The application must include a preliminary title report.

(3) The application must identify all contiguous property under the same ownership as the property to be divided.

(4) The application must be signed by the owner of the property to be divided.

(5) The property to be divided must be a legal lot.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8194 Middle Housing Land Division, Tentative Plan Approval Criteria.

The planning director shall approve, conditionally approve, or deny the middle housing land division tentative plan application based on compliance with the following criteria:

(1) If the property to be divided is not yet developed with middle housing:

(a) The application proposes development of middle housing on the lot or parcel to be divided; and

(b) The lot or parcel or be divided is developable with middle housing consistent with the following:

1. EC 9.2750;

2. EC 9.2751;

3. EC 9.2760;

4. EC 9.2761;

5. EC 9.2775; and

6. EC 9.5550.

(2) If the property to be divided is developed with middle housing:

(a) The middle housing complies with EC 9.5550; or

(b) The certificate of occupancy for the middle housing was issued before June 30, 2022, and the middle housing complied with applicable land use requirements at the time the certificate of occupancy was issued.

(3) The proposed middle housing land division complies with all of the following:

(a) EC 9.2777, Middle Housing Lot standards;

(b) EC 9.6505, Improvements, Specifications for any street frontage improvements required for middle housing lots that abut a street;

(c) EC 9.6805, Dedication of Public Ways; and

(d) All other applicable development standards for features explicitly included in the application.

(4) The following easements are shown on the tentative plan:

(a) Easements necessary for locating, accessing, replacing, and servicing all utilities;

(b) Easements for pedestrian access from each dwelling unit to a street;

(c) Easements necessary for any common areas or shared building elements;

(d) Easements necessary for any shared driveways or parking.

(5) Separate utilities are provided for each dwelling unit.

(6) The middle housing land division results in one dwelling unit on each middle housing lot, except lots, parcels or tracts that include a common area. Lots, parcels or tracts that include a common area, but do not include a dwelling unit, are permitted.

(7) The application demonstrates that buildings or structures on the middle housing lots created by the middle housing land division will comply with applicable building code provisions related to new property lines; and, notwithstanding the creation of new lots or parcels, that structures or buildings located on the middle housing lots will comply with the Oregon Residential Specialty Code.

(8) The following notes are included on the tentative plan:

(a) The middle housing lots shown on the tentative plan were created pursuant to a middle housing land division and may not be further divided.

(b) The middle housing developed on the middle housing lots shown on the tentative plan shall remain middle housing and shall not be considered to be any other housing type as a result of the middle housing land division.

(9) The proposed middle housing land division will not cause any existing improvements on the middle housing lots to be inconsistent with applicable standards in this land use code.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8195 Purpose of Middle Housing Land Division, Final Plat.

The middle housing land division process includes both a tentative plan and final plat procedure. Sections 9.8195 through 9.8199 provide the regulations for processing middle housing land division final plat applications to ensure that tentative plan approval conditions have been met.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8196 Applicability of Middle Housing Land Division, Final Plat Applications.

A middle housing land division final plat application may not be submitted unless the subject property has received tentative plan approval and any required approval conditions have been met.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8197 Middle Housing Land Division, Final Plat – Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, final plat applications shall:

(1) Be signed by the owner of the property.

(2) Contain a proposed final plat stamped and signed by an Oregon licensed land surveyor, complying with state and local platting and surveying requirements.

(3) Contain documentation addressing all conditions of tentative plan approval and state and local platting requirements.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8198 Middle Housing Land Division, Final Plat – Approval Criteria.

The planning director shall approve or deny the final plat for the middle housing land division. Approval shall be based on compliance with the following criteria, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(1) The city surveyor has approved the final plat for compliance with applicable platting requirements in accordance with state law.

(2) Streets, bicycle paths, accessways, and alleys for public use have been dedicated without any reservation or restriction other than reversionary rights upon vacation.

(3) Public improvements as required by this land use code or as a condition of tentative plan approval are completed, or:

(a) A performance bond or suitable substitute as agreed upon by the city and applicant has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the partition and the petition has been accepted by the city engineer.

(4) Public assessments, liens, and fees with respect to the middle housing land division have been paid, or:

(a) A segregation of assessments and liens has been applied for and granted by the city, or

(b) An adequate guarantee in a form acceptable to the city manager has been provided assuring the liens, assessments and fees will be paid prior to recording the final plat.

(5) All conditions of tentative middle housing land division approval have been met and the final plat substantially conforms to the provisions of the approved tentative middle housing land division.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8199 Middle Housing Land Division, Final Plat – Recordation.

(1) The city surveyor and planning director shall note their approval of the middle housing land division on the final plat along with the effective date of approval, which constitutes the city’s acceptance of any dedications to the public contained therein. After approval, the city shall forward the final plat for the middle housing land division to Lane County for signature by the county assessor and recording.

(2) A notice of middle housing land division shall be recorded for each middle housing lot with the Lane County Deeds and Records that states:

(a) The middle housing lot may not be further divided.

(b) No more than one unit of middle housing may be developed on each middle housing lot.

(c) The dwelling developed on the middle housing lot is a unit of middle housing and is not a single attached or detached dwelling, or any other housing type.

(Added by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; amended by Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8200 Purpose of Partitions, Tentative Plan.

Sections 9.8200 through 9.8245 govern the approval of partitions. These regulations are intended to accomplish the orderly development of land within the community, ensure the adequate provision of public facilities and services, protect the public health and safety of the community and enable development to occur consistent with applicable provisions of the comprehensive plan.

(Section 9.8200, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8205 Applicability of Partition, Tentative Plan Applications.

(1) Except as provided in subsections (2) and (3) of this section, requests to create 2 or 3 parcels shall be subject to the partition provisions of this land use code, and shall follow a Type II application procedure.

(2) Partition applications that meet the approval criteria in EC 9.8215(7) or EC 9.8220(5) may be processed pursuant to the expedited land division procedures in EC 9.7900 through EC 9.7925.

(3) Concurrent applications may be processed as provided in EC 9.8005.

(4) A tentative plan application to partition land may be submitted and reviewed concurrently with a tentative PUD application following a Type III application procedure. If a partition application that also involves a PUD application is not submitted concurrently with the tentative PUD application, the partition application may not be submitted until a tentative PUD is approved. (Refer to EC 9.8305 Applicability.)

(5) If a partition tentative plan application is not reviewed concurrently with a tentative PUD application, no development permit shall be issued by the city prior to approval of the tentative partition application. If a tentative partition is reviewed concurrently with a tentative PUD application, no development permit shall be issued by the city prior to approval of the final PUD application in accordance with EC 9.8305.

(Section 9.8205, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8210 Partition, Tentative Plan Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements apply to partition tentative plan applications:

(1) Applications are prepared by an Oregon licensed land surveyor and contain a preliminary title report.

(2) Applications include all contiguous property under the same ownership as the subject property, and are signed by the owner of the property.

(3) The lot proposed to be divided in the partition application is a legal lot.

(4) If the proposal includes housing, the written statement submitted with the partition application shall clearly state whether the applicant is electing to use the discretionary approval criteria in EC 9.8215 Partition, Tentative Plan Approval Criteria – General/Discretionary instead of the approval criteria found in EC 9.8220 Partition, Tentative Plan Approval Criteria – Housing/Clear and Objective.

(5) The written statement submitted with the partition application shall clearly state whether the applicant believes that the proposal qualifies for the expedited land division procedures in EC9.7900 through EC 9.7925, and whether the applicant is electing to use the expedited land division procedures in EC 9.7900 through EC 9.7925.

(Section 9.8210, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20269, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8215 Partition, Tentative Plan Approval Criteria – General/Discretionary.

The planning director shall approve, approve with conditions, or deny a partition, with findings and conclusions. Approval, or approval with conditions, shall be based on compliance with the following criteria:

(1) The proposed partition complies with all of the following, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(a) Lot standards of EC 9.2000 through 9.4170 regarding applicable parcel dimensions and density requirements. Within the /WR Water Resources Conservation Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would occupy either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(c) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(d) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(e) EC 9.6710 Geological and Geotechnical Analysis.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) All other applicable development standards for features explicitly included in the application.

(l) The applicable adopted plan policies beginning at EC 9.9500.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(2) The proposed partition will not create a new nonconforming situation.

(3) Partitions abutting collector and arterial streets comply with access management guidelines of the agency having jurisdiction over the street.

(4) If the provisions of EC 9.8215(1) require a public street, or if the applicant proposes the creation of a public street, all of the following criteria also apply:

(a) The proposal will not impede the future best use of the remainder of the property under the same ownership or adversely affect the development of the remainder or any adjoining land or access thereto.

(b) The proposed partition will:

1. Not result in significant risk of fire, flood, geological hazards, or other public health and safety concerns;

2. Provide adequate transportation systems, water supply, sewage disposal, drainage, and other public utilities;

3. Not hamper the adequate provision of publicly owned open space for recreation needs.

(c) The proposed partition provides direct bicycle and pedestrian access to nearby and adjacent residential areas, transit stops, neighborhood activity centers, commercial areas, and employment and industrial areas, and provides safe, convenient and direct transit circulation, provided the city makes findings to demonstrate consistency with constitutional requirements. “Nearby” means uses within 1/4 mile that can reasonably be expected to be used by pedestrians, and uses within 2 miles that can be reasonably expected to be used by bicyclists.

(5) As far as is practicable, lot side lines run at right angles to the street upon which the lots face, except that on curved streets they are radial to the curve.

(6) On R-1 zoned property, if the partition results in a parcel greater than 13,500 square feet in size based on EC 9.2761(5)(b), the application shall indicate the location of parcel lines and other details of layout that show future division of the parcel may be made without violating the requirements of this land use code and without interfering with the orderly extension of adjacent streets, bicycle paths, and accessways. If the planning director deems it necessary for the purpose of future land division, any restriction of buildings within future street, bicycle path, and accessway locations shall be made a matter of record in the tentative plan approval.

(7) If the applicant elects to use the expedited land division procedures in EC 9.7900 through EC 9.7925, the application must meet the following additional approval criteria in subparagraphs (a)–(c):

(a) The proposed partition only includes land zoned for residential uses;

(b) The parcels created will only be developed for residential use, including recreational or open space accessory to residential use; and

(c) The parcels created will either allow construction of residential units at a density of 80 percent or more of the maximum net density per acre permitted in the zone and identified in Table 9.2750; or, existing and future dwellings located on the property that is the subject of the partition application will be sold or rented to households with incomes below 120 percent of the median family income for Lane County.

(Section 9.8215, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003; Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance 20528, enacted May 14, 2014, effective June 23, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8220 Partition, Tentative Plan Approval Criteria – Housing/Clear and Objective.

Unless the applicant elects to use the discretionary criteria contained in EC 9.8215 Partition, Tentative Plan Approval Criteria – General/Discretionary, for housing applications entitled to clear and objective review pursuant to state statute, the planning director shall approve, conditionally approve, or deny the partition application based on compliance with the following criteria:

(1) The proposed partition complies with all of the following:

(a) EC 9.2000 through 9.4170 regarding applicable parcel dimensions and density requirements for the subject zone and any applicable overlay zones. Within the /WR Water Resources Conservation Overlay Zone or /WQ Water Quality Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would be occupied by either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(c) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(d) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(e) EC 9.6710(6) Geological and Geotechnical Analysis.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) All other applicable development standards for features explicitly included in the application.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(2) The proposed partition will not cause any existing improvements on proposed lots to be inconsistent with applicable standards in this land use code.

(3) If the provisions of EC 9.8220(1) require a public street, or if the applicant proposes the creation of a public street, the following criteria also apply:

(a) The proposed land uses and densities within the partition are consistent with the land use designation(s) shown on the comprehensive plan diagram, as refined in any applicable refinement plan.

(b) The proposal will provide pedestrian circulation to transit stops and neighborhood activity centers located within 1/4 mile of the development site and bicycle circulation to transit stops and neighborhood activity centers located within 2 miles of the development site, provided that the city makes findings to demonstrate consistency with constitutional requirements. The distance between the development site and a transit stop or neighborhood activity center shall be determined using the shortest distance as measured in a straight line between a point along the perimeter of the development site and:

1. A sign identifying a transit stop; or

2. A point along a property line of a neighborhood activity center.

(4) On R-1 zoned property, if the partition results in a parcel greater than 13,500 square feet in size based on EC 9.2761(5)(b), the application shall indicate the location of parcel lines and other details of layout that show future division may be made without violating the requirements of this land use code and without interfering with the orderly extension of adjacent streets, bicycle paths, and accessways. Any restriction of buildings within future street, bicycle path, and accessway locations shall be made a matter of record in the tentative plan approval.

(5) If the applicant elects to use the expedited land division procedures in EC 9.7900 through EC 9.7925, the application must meet the following additional approval criteria in subparagraphs (a)–(c):

(a) The partition only includes land zoned for residential uses;

(b) The parcels created will only be developed for residential use, including recreational or open space accessory to residential use; and

(c) The parcels created will either allow construction of residential units at a density of 80 percent or more of the maximum net density per acre permitted in the zone and identified in Table 9.2750; or, existing and future dwellings located on the property that is the subject of the partition application will be sold or rented to households with incomes below 120 percent of the median family income for Lane County.

(Section 9.8220, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003; administratively corrected July 9, 2003; amended by Ordinance No. 20297, enacted August 11, 2003, effective September 10, 2003; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; by Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; amended by Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8225 Purpose of Partition, Final Plat.

The partition process includes both a tentative plan and final plat procedure. Sections 9.8225 through 9.8245 provide the regulations for processing partition final plat applications to ensure that tentative plan approval conditions have been met.

(Section 9.8225, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8230 Applicability of Partition, Final Plat Applications.

A partition final plat application is applicable when the subject property has received tentative plan approval and any required approval conditions have been met.

(Section 9.8230, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8235 Partition, Final Plat – Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, final plat applications shall:

(1) Be signed by the owner of the property.

(2) Contain a proposed final plat stamped and signed by an Oregon licensed land surveyor, complying with state and local platting and surveying requirements.

(3) Contain documentation addressing all conditions of tentative plat approval and state and local platting requirements.

(Section 9.8235, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8240 Partition, Final Plat – Approval Criteria.

The planning director shall approve or deny the partition’s final plat. Approval shall be based on compliance with the following criteria, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(1) The city surveyor has approved the final plat for compliance with applicable platting requirements in accordance with state law.

(2) Streets, bicycle paths, accessways, and alleys for public use have been dedicated without any reservation or restriction other than reversionary rights upon vacation.

(3) Public improvements as required by this land use code or as a condition of tentative plan approval are completed, or:

(a) A performance bond or suitable substitute as agreed upon by the city and applicant has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the partition and the petition has been accepted by the city engineer.

(4) Public assessments, liens, and fees with respect to the partition have been paid, or:

(a) A segregation of assessments and liens has been applied for and granted by the city, or

(b) An adequate guarantee in a form acceptable to the city manager has been provided assuring the liens, assessments and fees will be paid prior to recording the final plat.

(5) All conditions of tentative partition approval have been met and the final plat substantially conforms to the provisions of the approved tentative partition.

(Section 9.8240, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013.)

9.8245 Partition, Final Plat – Recordation.

The city surveyor and planning director shall note their approval of the partition on the partition’s final plat along with the effective date of approval, which constitutes the city’s acceptance of any dedications to the public contained therein. After approval, the city shall forward the partition plat to Lane County for signature by the county assessor and recording.

(Section 9.8245, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8300 Purpose of Planned Unit Development.

The planned unit development (PUD) provisions are designed to provide a high degree of flexibility in the design of the site and the mix of land uses, potential environmental impacts, and are intended to:

(1) Create a sustainable environment that includes:

(a) Shared use of services and facilities.

(b) A compatible mix of land uses that encourage alternatives to the use of the automobile.

(c) A variety of dwelling types that help meet the needs of all income groups in the community.

(d) Preservation of existing natural resources and the opportunity to enhance habitat areas.

(e) Clustering of residential dwellings to achieve energy and resource conservation while also achieving the planned density for the site.

(2) Create comprehensive site plans for geographic areas of sufficient size to provide developments at least equal in quality to those that are achieved through the traditional lot by lot development and that are reasonably compatible with the surrounding area.

(Section 9.8300, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8305 Applicability.

PUD provisions shall be applied when any of the following conditions exist:

(1) The proposal is subject to review and approval through the PUD process according to an adopted refinement plan, including but not limited to, property within the boundary of the South Hills Study where all or a portion of a development site is:

(a) Between an elevation of 500 feet and 701 feet, and the development site is at least 4 acres with areas of the development site containing slopes that exceed 20%.

(b) On property above 701 feet in elevation, except partitions that do not include the creation of a public street, unless an alternate review procedure is approved pursuant to EC 9.9630(3)(a).

(c) Above an elevation of 900 feet, except for a land division undertaken by or on behalf of a governmental entity in order to preserve, manage, or expand park, open space, or natural resource areas.

(2) The property is zoned with a /PD overlay zone.

(3) One or more land uses proposed for the site are subject to review and approval through the PUD process according to the zoning.

(4) When requested by the property owner.

No development permit shall be issued by the city prior to approval of the final PUD.

(Section 9.8305, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8310 Tentative Planned Unit Development General Application Requirements.

(1) Ownership. The area included in a proposed PUD shall either be under single ownership or common development control. The application shall include all contiguous property under the same ownership or development control, shall be signed by the owner of the property, and include such related information as prescribed by the planning director. Otherwise contiguous parcels that are separated only by a public right-of-way, shall be included in the PUD application unless the public right-of-way is designated an arterial or collector on the street classification map. If otherwise contiguous parcels are separated by an arterial or collector street, the applicant may, at the applicant’s discretion, include those parcels in the PUD application.

(2) Project Coordinator and Professional Design Team. The tentative PUD application shall identify the PUD project coordinator and the professional design team and certify compliance with the following:

(a) Project Coordinator. The project coordinator shall:

1. Be the liaison between the applicant and the city.

2. Ensure that the required plans are prepared and executed according to any required conditions.

3. Either be a member of the American Institute of Certified Planners or licensed in the state of Oregon to practice architecture, civil engineering, or landscape architecture.

The project coordinator, or at least one design team member, shall attend all public meetings at which the proposal is discussed.

(b) Professional Design Team Designation. Unless waived by the planning director, the professional design team shall consist of at least the following professionals:

1. Oregon licensed arborist.

2. Oregon licensed architect.

3. Oregon licensed civil engineer.

4. Oregon licensed landscape architect.

5. Oregon licensed land surveyor.

(c) Plan Certification. Certification of the services of the professionals responsible for particular drawings shall appear on those drawings.

(3) Phasing. The tentative PUD application shall include a phasing plan that indicates any proposed phases for development, including the boundaries and sequencing of each phase. Phasing shall progress in a sequence that promotes street connectivity between the various phases of the development and accommodates other required public improvements.

(4) Density. Dwelling unit densities for PUDs shall be consistent with Table 9.2750 Residential Zone Development Standards. The calculation of the number of dwelling units allowed shall be determined based on the following:

(a) Easement Calculations. If it is demonstrated that easements will benefit residents of the proposed PUD, residential density calculations may include areas in easements, with the exception of private streets or ingress/egress easements.

(b) Dedications. If it is demonstrated that lands dedicated to the city will benefit residents of the proposed PUD, residential density calculations may include areas dedicated to the public for recreation or open space.

(c) Cumulative Density. When final plans are to be approved in phases, at no time shall the cumulative residential density exceed the overall density per acre established at the time of tentative plan approval.

(5) Housing. If the proposal includes housing, the written statement submitted with the PUD application shall clearly state whether the applicant is proceeding under: (a) the approval criteria in EC 9.8320 Tentative Planned Unit Development Approval Criteria – General/Discretionary; or (b) the approval criteria in EC 9.8325 Tentative Planned Unit Development Approval Criteria Housing/Clear and Objective.

(Section 9.8310, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; amended by Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8320 Tentative Planned Unit Development Approval Criteria – General/Discretionary.

The hearings official shall approve, approve with conditions, or deny a tentative PUD application with findings and conclusions. Decisions approving an application, or approving with conditions, shall be based on compliance with the following criteria:

(1) The PUD is consistent with applicable adopted policies of the Metro Plan.

(2) The PUD is consistent with applicable adopted refinement plan policies.

(3) The PUD will provide adequate screening from surrounding properties including, but not limited to, anticipated building locations, bulk, and height.

(4) The PUD is designed and sited to minimize impacts to the natural environment by addressing the following:

(a) Protection of Natural Features.

1. For areas not included on the City’s acknowledged Goal 5 inventory, the preservation of significant natural features to the greatest degree attainable or feasible, including:

a. Significant on-site vegetation, including rare plants (those that are proposed for listing or are listed under State or Federal law), and native plant communities.

b. All documented habitat for all rare animal species (those that are proposed for listing or are listed under State or Federal law).

c. Prominent topographic features, such as ridgelines and rock outcrops.

d. Wetlands, intermittent and perennial stream corridors, and riparian areas.

e. Natural resource areas designated in the comprehensive plan diagram as “Natural Resource” and areas identified in any city-adopted natural resource inventory.

2. For areas included on the City’s acknowledged Goal 5 inventory:

a. The proposed development’s general design and character, including but not limited to anticipated building locations, bulk and height, location and distribution of recreation space, parking, roads, access and other uses, will:

(1) Avoid unnecessary disruption or removal of attractive natural features and vegetation, and

(2) Avoid conversion of natural resource areas designated in the comprehensive plan to urban uses when alternative locations on the property are suitable for development as otherwise permitted.

b. Proposed buildings, road, and other uses are designed and sited to assure preservation of significant on-site vegetation, topographic features, and other unique and worthwhile natural features, and to prevent soil erosion or flood hazard.

(b) Tree Preservation. The proposed project shall be designed and sited to preserve significant trees to the greatest degree attainable or feasible, with trees having the following characteristics given the highest priority for preservation:

1. Healthy trees that have a reasonable chance of survival considering the base zone or special area zone designation and other applicable approval criteria;

2. Trees located within vegetated corridors and stands rather than individual isolated trees subject to windthrow;

3. Trees that fulfill a screening function, provide relief from glare, or shade expansive areas of pavement;

4. Trees that provide a buffer between potentially incompatible land uses;

5. Trees located along the perimeter of the lot(s) and within building setback areas;

6. Trees and stands of trees located along ridgelines and within view corridors;

7. Trees with significant habitat value;

8. Trees adjacent to public parks, open space and streets;

9. Trees located along a water feature;

10. Heritage trees.

(c) Restoration or Replacement.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the proposal mitigates, to the greatest degree attainable or feasible, the loss of significant natural features described in criteria (a) and (b) above, through the restoration or replacement of natural features such as:

a. Planting of replacement trees within common areas; or

b. Re-vegetation of slopes, ridgelines, and stream corridors; or

c. Restoration of fish and wildlife habitat, native plant habitat, wetland areas, and riparian vegetation.

To the extent applicable, restoration or replacement shall be in compliance with the planting and replacement standards of EC 6.320.

2. For areas included on the city’s acknowledged Goal 5 inventory, any loss of significant natural features described in criteria (a) and (b) above shall be consistent with the acknowledged level of protection for the features.

(d) Street Trees. If the proposal includes removal of any street tree(s), removal of those street tree(s) has been approved, or approved with conditions according to the process at EC 6.305.

(5) The PUD provides safe and adequate transportation systems through compliance with the following:

(a) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways (not subject to modifications set forth in subsection (10) below).

(b) Pedestrian, bicycle and transit circulation, including related facilities, as needed among buildings and related uses on the development site, as well as to adjacent and nearby residential areas, transit stops, neighborhood activity centers, office parks, and industrial parks, provided the city makes findings to demonstrate consistency with constitutional requirements. “Nearby” means uses within 1/4 mile that can reasonably be expected to be used by pedestrians, and uses within 2 miles that can reasonably be expected to be used by bicyclists.

(c) The provisions of the Traffic Impact Analysis Review of EC 9.8650 through 9.8680 where applicable.

(6) The PUD will not be a significant risk to public health and safety, including but not limited to soil erosion, slope failure, stormwater or flood hazard, or an impediment to emergency response.

(7) Adequate public facilities and services are available to the site, or if public services and facilities are not presently available, the applicant demonstrates that the services and facilities will be available prior to need. Demonstration of future availability requires evidence of at least one of the following:

(a) Prior written commitment of public funds by the appropriate public agencies.

(b) Prior acceptance by the appropriate public agency of a written commitment by the applicant or other party to provide private services and facilities.

(c) A written commitment by the applicant or other party to provide for offsetting all added public costs or early commitment of public funds made necessary by development, submitted on a form acceptable to the city manager.

(8) Residents of the PUD will have sufficient usable recreation area and open space that is convenient and safely accessible.

(9) Lots proposed for development with single-unit detached dwellings shall comply with EC 9.2790 Solar Lot Standards or as modified according to subsection (10) below.

(10) The PUD complies with all of the following:

(a) EC 9.2000 through 9.4170 regarding lot dimensions, solar standards, and density requirements for the subject zone and overlay zone. Within the /WR Water Resources Conservation Overlay Zone, no new lot may be created if more than 33% of the lot, as created , would occupy either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(c) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(d) EC 9.6710 Geological and Geotechnical Analysis.

(e) EC 9.6730 Pedestrian Circulation On-Site.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) All other applicable development standards for features explicitly included in the application except where the applicant has shown that a proposed noncompliance is consistent with the purposes set out in EC 9.8300 Purpose of Planned Unit Development.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(11) The proposed development shall have minimal off-site impacts, including such impacts as traffic, noise, stormwater runoff and environmental quality.

(12) The proposed development shall be reasonably compatible and harmonious with adjacent and nearby land uses.

(13) If the tentative PUD application proposes a land division, nothing in the approval of the tentative application exempts future land divisions from compliance with state or local surveying requirements.

(14) If the proposed PUD is located within a special area zone, the applicant shall demonstrate that the proposal is consistent with the purpose(s) of the special area zone.

(15) For property with the /SR Site Review Overlay Zone, the PUD complies with any additional site-specific criteria that were specified at the time the /SR designation was applied to the property.

(Section 9.8320, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20266, enacted November 12, 2002, effective December 12, 2002; Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance No. 20417, enacted August 11, 2008, effective July 7, 2009; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8325 Tentative Planned Unit Development Approval Criteria – Housing/Clear and Objective.

Unless the applicant elects to use the discretionary criteria contained in EC 9.8320 Tentative Planned Unit Development Approval Criteria – General/Discretionary, for housing applications entitled to clear and objective review pursuant to state statute, the hearings official shall approve, conditionally approve, or deny the PUD application based on compliance with the following criteria:

(1) The proposal complies with EC 9.5860 Transition Standards.

(2) The proposed land uses and densities within the PUD are consistent with the land use designation(s) shown on the comprehensive plan diagram, as refined in any applicable refinement plan.

(3) For areas not included on the city’s acknowledged Goal 5 inventory, the PUD preserves existing natural resources by compliance with the provisions of EC 9.6880 to EC 9.6885 Tree Preservation and Removal Standards

(4) The PUD provides safe and adequate transportation systems through compliance with all of the following:

(a) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(b) The proposal will provide pedestrian circulation to transit stops and neighborhood activity centers located within 1/4 mile of the development site and bicycle circulation to transit stops and neighborhood activity centers located within 2 miles of the development site, provided that the city makes findings to demonstrate consistency with constitutional requirements. The distance between the development site and a transit stop or neighborhood activity center shall be determined using the shortest distance as measured in a straight line between a point along the perimeter of the development site and:

1. A sign identifying a transit stop; or

2. A point along a property line of a neighborhood activity center.

(5) The PUD complies with all of the following:

(a) EC 9.2000 through EC 9.4170 regarding applicable lot dimensions and density requirements for the subject zone and any applicable overlay zones. Within the /WR Water Resources Conservation Overlay Zone or /WQ Water Quality Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would be occupied by either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6500 through 9.6505 Public Improvement Standards.

(c) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(d) EC 9.6710(6) Geological and Geotechnical Analysis.

(e) EC 9.6730 Pedestrian Circulation On-Site.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) All applicable development standards explicitly addressed in the application.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(6) The applicant has demonstrated that wastewater service, transportation service, stormwater service, water service, and electrical service will be provided to the site prior to the need for those facilities and services. Where the facility or service is not already serving the site, this demonstration requires evidence of at least one of the following:

(a) Prior written commitment of public funds by the appropriate public agencies.

(b) Prior acceptance by the appropriate public agency of a written commitment by the applicant or other party to provide private services and facilities.

(c) A written commitment by the applicant or other party to provide for offsetting all added public costs or early commitment of public funds made necessary by development, submitted on a form acceptable to the city manager.

(7) PUDs proposed on development sites that are two acres or larger must comply with either subparagraph (a) or (b), below:

(a) The PUD is located within 1/2-mile of a public park, public recreation facility, or public school (determined using the shortest distance as measured along a straight line between a point along the perimeter of the development site and a point along a property line of a public park, public recreation facility, or public school); or

(b) The PUD shall provide common open space within the development as follows:

1. Common Open Space Area.

a. If the average lot area is equal to or greater than the minimum lot area of the base zone, then the PUD shall provide common open space within the development site equal to a minimum of 10 percent of the net acres of the development site or 14,500 square feet, whichever is greater.

b. If the average lot area is below the minimum lot area of the base zone, then the PUD shall provide common open space within the development site equal to a minimum of 15 percent of the net acres of the development site or 14,500 square feet, whichever is greater.

For the purpose of this subparagraph, net acres means the total development site area minus area(s) for public or private streets. In no case shall the common open space requirement exceed one acre.

2. Common open space shall be provided in one separate tract of land, except that developments providing more than 29,000 square feet of common open space may include up to three common open space tracts provided no tract is less than 14,500 square feet.

3. Ownership of the common open space tract(s) must be dedicated to all lot or parcel owners within the development site.

4. Each common open space tract must include a portion with minimum dimensions of 70 feet by 70 feet.

5. Except where each lot or parcel in the development abuts one or more of the common open space area(s), common open space tracts must have a minimum of 10 feet of lot frontage along an existing or proposed public way or private street.

6. Common open space tracts do not have to meet lot standards.

(c) For proposals that include multiple-unit development, compliance with subparagraph (a) or (b) shall constitute compliance with the requirements of EC 9.5500(9).

(8) For any PUD located within or partially within the boundaries of the South Hills Study, the following additional approval criteria apply:

(a) No development shall occur on land above an elevation of 901 feet except that either middle housing or one single-unit dwelling may be built on any lot in existence as of August 1, 2001.

(b) Development on any portion of the development site located above 900 feet elevation shall be set back at least 300 feet from the ridgeline unless there is a determination by the city manager that the area is not needed as a connection to the city’s ridgeline trail system. For purposes of this section, the ridgeline shall be considered as the line indicated as being the urban growth boundary.

(c) Residential density is limited as follows:

1. In the area west of Friendly Street, the maximum level of new development per gross acre shall be 8 units per acre.

2. In the area east of Friendly Street, the maximum level of new development per gross acre shall be limited to 5 units per acre.

3. Housing developed as Controlled Income and Rent Housing shall be exempt from the density limitations in subsections 1 and 2 above, but are subject to the other applicable development standards and review procedures.

4. This subsection (c) does not preclude middle housing or the addition of an accessory dwelling on any legal lot.

(Section 9.8325, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; administratively corrected April 18, 2003; amended by Ordinance No. 20297, enacted August 11, 2003, effective September 10, 2003; administratively corrected August 13, 2003; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8330 Site Alteration.

Unless specifically permitted by the hearings official, vegetation, topography, and other natural features of areas proposed for a PUD shall not be substantially altered until final PUD approval, and then only as authorized by the final PUD approval. “Substantially altered” includes, but is not limited to, site grading and removal of trees or other vegetation. If a subdivision is required, site alteration shall not be permitted until after tentative subdivision approval is granted.

(Section 9.8330, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8335 Modifications to Approved Tentative Planned Unit Development.

The applicant may apply for a modification of the approved PUD tentative plan following the Type II process. The planning director shall approve the request only if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If the planning director determines that the proposed modification is not consistent with the above criteria, the proposed modification may not occur. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new tentative PUD application.

(Section 9.8335 added by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006.

9.8350 Purpose of Planned Unit Development, Final Plan.

The PUD process includes both a tentative and final plan. Final plan approval is required primarily to ensure that tentative plan approval conditions have been met.

(Section 9.8350, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8355 Applicability.

A final PUD plan is required for every approved tentative PUD, and every phase of a tentative PUD.

(Section 9.8355, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8360 Planned Unit Development, Final Plan Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements apply to PUD final plan applications:

(1) Applications shall contain final maps and supplemental materials required to demonstrate compliance with tentative plan conditions of approval.

(2) Final PUD plans may be submitted in phases, if such phases were approved as part of the tentative PUD consideration. The boundaries of each phase of the final PUD plans shall coincide with the boundaries of the phasing areas approved at the tentative plan stage. Requests to extend the time frame for a specific phase shall be subject to EC 9.7340 Expiration.

(3) When a PUD or any phase thereof is submitted for final approval, each design team member shall provide written certification that the portion of the project in which he or she was involved continues to comply with the approved tentative plan conditions of approval.

(Section 9.8360, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8365 Final Planned Unit Development Approval Criteria.

The planning director shall approve, approve with conditions, or deny a final PUD application, based on compliance with the following criteria:

(1) The final PUD plan conforms with the approved tentative PUD plan and all conditions attached thereto.

(2) For final PUDs not associated with a land division, public improvements as required by this land use code or as a condition of tentative plan approval will be completed prior to issuance of a development permit, or:

(a) A performance bond or suitable substitute as agreed upon by the city has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the subdivision, and the petition has been accepted by the city engineer.

(Section 9.8365, see chart at front of Chapter 9 for legislative history from 2/26/01 to 6/1/02; amended by Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8370 Modifications to Approved Planned Unit Development.

The applicant for the original PUD may apply for a modification of the final PUD approval following the Type II process. The planning director shall approve the request only if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If the planning director determines that the proposed modification is not consistent with the above criteria, the proposed modification may not occur unless a new tentative PUD application is submitted based on the Type III procedural requirements. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new tentative PUD application.

(Section 9.8370, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8375 Final Planned Unit Development – Landscaping.

If required landscaping cannot be completed prior to occupancy, or as otherwise required as a condition of approval, the planning director may require the applicant to post a performance bond in an amount and for a time period determined by the planning director to be sufficient to assure timely completion.

(Section 9.8375, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8400 Purpose of Property Line Adjustment.

Sections 9.8400 through 9.8420 provide an expedited process for the review of property line adjustments. A property line adjustment is the relocation of a single boundary line or the removal of boundary lines between two legal lots. Property line adjustments shall be considered in accordance with the Type I application procedures contained in EC 9.7100 General Overview of Type I Application Procedures.

(Section 9.8400, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02. Amended by Ordinance No. 20557, enacted July 27, 2015, effective August 30, 2015)

9.8405 Applicability of Property Line Adjustment Applications.

(1) A property line adjustment application is applicable to changes to the property lines of adjoining properties when all of the following exist:

(a) A property line proposed for adjustment will not result in an increase in the number of parcels or lots.

(b) A property line proposed for adjustment will not create more than 2 property line adjustments to any of the boundaries of an individual lot or parcel within a calendar year. This subsection does not apply to proposed property line adjustments undertaken by or on behalf of a governmental entity that affect the ability to preserve, manage, or expand park, open space, or natural resource areas.

(c) The adjustment will result in less than a 200% change in the size of the lot or parcel. This subsection does not apply to proposed property line adjustments undertaken by or on behalf of a governmental entity that affect the ability to preserve, manage, or expand park, open space, or natural resource areas.

(2) A property line adjustment application may not be utilized to effect the reconfiguration of lots or parcels which must be approved through the partition or subdivision procedure.

(3) A property line adjustment application may not be utilized to create flag lots.

(Section 9.8405, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02. Amended by Ordinance No. 20557, enacted July 27, 2015, effective August 30, 2015.)

9.8410 Property Line Adjustment – Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements shall apply to property line adjustment applications:

(1) Except for parallel property line adjustments to platted lots, when the adjusted property line is a distance of even width along the common boundary, all applications shall be prepared by an Oregon licensed Land Surveyor.

(2) Applications shall be signed by at least one of the owners of each parcel involved, and shall include a current preliminary title report issued within one year of the date the application is submitted, for each parcel.

(Section 9.8410, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20269, enacted November 25, 2002, effective December 25, 2002; and amended by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006.)

9.8415 Property Line Adjustment – Approval Criteria.

The planning director shall approve, approve with conditions, or deny the property line adjustment application. Approval or approval with conditions shall be based on compliance with the following criteria:

(1) Any buildings to be retained on the properties comply with the minimum front and interior yard setbacks as defined in this land use code.

(2) The final configuration of property lines shall not reduce an existing lot below the minimum lot standards established in this land use code or otherwise violate standards of this land use code, building codes, fire codes, and Chapter 7.

(3) The final configuration of property lines shall not violate any previous requirements or conditions of approval imposed with a prior applicable land use decision.

(4) Public assessments, liens, and fees with respect to the property line adjustment have been paid, or:

(a) A segregation of assessments and liens has been applied for and granted by the city; or

(b) An adequate guarantee in a form acceptable to the city manager has been provided assuring the liens, assessments and fees will be paid prior to recording the property line adjustment.

Approval of a property line adjustment does not relieve the applicant from complying with all applicable codes or statutory requirements.

(5) Within the /WR Water Resources Conservation Overlay Zone or /WQ Water Quality Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would be occupied by either:

(a) The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

(b) The /WQ Management Area.

(6) Within the R-1 zone in the city-recognized boundaries of Amazon Neighbors, Fairmount Neighbors and South University Neighborhood Association, property lines may only be adjusted up to 5 feet, measured perpendicularly from the current location of the property line. A Property Line Adjustment allowed under this section may be up to 10 feet if the adjustment is necessary to accommodate an encroachment that existed as of April 12, 2014.

(Section 9.8415, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; administratively corrected March 15, 2005; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; amended by Ordinance No. 20457, enacted March 8, 2010, effective April 10, 2010; amended by Ordinance No. 20526, enacted March 12, 2014, effective April 12, 2014.)

9.8420 Post-Approval Requirements.

(1) Upon approval of a property line adjustment, the city shall record with Lane County a Notice of Approval for Property Line Adjustments that contains the revised legal descriptions of the two existing lots affected by the adjustment.

(2) In accordance with state law, the owners of the property affected by the adjustment are responsible for creating and recording a deed with Lane County Deeds and Records that reflects the new location of the property line. The property owners are also responsible for submitting requests to the Lane County Department of Assessment and Taxation for transfers on the assessment roll in accordance with the approved adjustment.

(3) The respective property owners are responsible for payment of any public liens, assessments and fees that may be required prior to recording the notice of approval.

(4) The respective property owners are responsible for meeting the statutory requirements for the survey and monumentation of the new line by an Oregon licensed surveyor.

(Section 9.8420, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8421 Purpose of Refinement Plan Amendments.

An amendment to an existing refinement plan allows changes to be made to portions of the plan without comprehensively updating the entire document. Refinement plan application requirements and criteria are designed to facilitate consideration of amendments to address changes that have occurred, such as changes in state or federal legislation, changes in the comprehensive plan or other applicable local policies, or changes in circumstances that could directly influence public policy choices.

(Section 9.8421, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8422 Applicability.

Refinement plan amendment procedures only apply when specific changes are proposed to an existing refinement plan that covers areas only within the jurisdiction of the city. The procedures are not applicable to comprehensive updates of an entire refinement plan.

(Section 9.8422, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8423 General Requirements.

Applications for refinement plan amendments shall be submitted on a form approved by the city manager and reviewed under a Type IV process for site specific amendments or otherwise, a Type V process according to EC 9.7000 through 9.7925 Application Procedures.

(Section 9.8423, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8424 Refinement Plan Amendment Approval Criteria.

The planning commission shall evaluate proposed refinement plan amendments based on the criteria set forth below, and forward a recommendation to the city council. The city council shall decide whether to act on the application. If the city council decides to act, it shall approve, approve with modifications or deny a proposed refinement plan amendment. Approval, or approval with modifications shall be based on compliance with the following criteria:

(1) The refinement plan amendment is consistent with all of the following:

(a) Statewide planning goals.

(b) Applicable provisions of the comprehensive plan.

(c) Remaining portions of the refinement plan.

(2) The refinement plan amendment addresses one or more of the following:

(a) An error in the publication of the refinement plan.

(b) New inventory material which relates to a statewide planning goal.

(c) New or amended community policies.

(d) New or amended provisions in a federal law or regulation, state statute, state regulation, statewide planning goal, or state agency land use plan.

(e) A change of circumstances in a substantial manner that was not anticipated at the time the refinement plan was adopted.

(Section 9.8424, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8425 Purpose of Site Review.

Site review is used as a means to maintain or improve the character, integrity, and harmonious development of an area, address potential environmental impacts, and to provide a safe, stable, efficient, and attractive on-site environment.

(Section 9.8425, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8430 Applicability.

Site review provisions shall be applied when any of the following conditions exist:

(1) Property is zoned with the /SR overlay zone and the proposal would result in either of the following:

(a) New development of vacant sites (excluding partitions and any development that consists only of new or expanded parking areas).

(b) An expansion of 20 percent or more of the total existing building square footage on the development site.

(2) The proposed use on the property is identified as a use which requires site review under other provisions of this land use code and the proposal would result in either of the following:

(a) New development of vacant sites (excluding development that consists only of new or expanded parking areas).

(b) An expansion of 20 percent or more of the total existing building square footage on the development site.

In lieu of site review, an application that falls within (1) or (2) above, may obtain approval through the Planned Unit Development process. No development permit shall be issued by the city prior to approval of the site review application, or the final planned unit development application.

(Section 9.8430, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20269, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20417, enacted August 11, 2008, effective July 7, 2009; and Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; administratively corrected on October 11, 2017).

9.8435 General Requirements.

Unless waived by the planning director, the application shall be prepared by one or more of the following professional:

(1) Oregon licensed architect.

(2) Oregon licensed civil engineer.

(3) Oregon licensed landscape architect.

(4) A member of the American Institute of Certified Planners.

(Section 9.8435, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8440 Site Review Approval Criteria – General/Discretionary.

The planning director shall approve, conditionally approve, or deny the site review application. Approval or conditional approval shall be based on compliance with the following criteria:

(1) The site review plan’s general design and character is reasonably compatible with surrounding properties, as it relates to building locations, bulk and height, noise, glare and odors.

(2) Proposed lots, buildings, streets, parking lots, recreation areas, and other proposed uses are designed and sited to minimize impacts to the natural environment by addressing the following:

(a) Protection of Natural Features.

1. For areas not included on the City’s acknowledged Goal 5 inventory, the preservation of significant natural features to the greatest degree attainable or feasible, including:

a. Significant on-site vegetation, including rare plants (those that are proposed for listing or are listed under State or Federal law), and native plant communities.

b. All documented habitat for all rare animal species (those that are proposed for listing or are listed under State or Federal law).

c. Prominent topographic features, such as ridgelines and rock outcrops.

d. Wetlands, intermittent and perennial stream corridors, and riparian areas.

e. Natural resource areas designated in the comprehensive plan diagram as “Natural Resource” and areas identified in any city-adopted natural resource inventory.

2. For areas included on the City’s acknowledged Goal 5 inventory the applicant shall show that it has given due consideration to the preservation of attractive and distinctive historical and natural features.

(b) Tree Preservation. The proposed project shall be designed and sited to preserve significant trees to the greatest degree attainable or feasible, with trees having the following characteristics given the highest priority for preservation:

1. Healthy trees that have a reasonable chance of survival considering the base zone or special area zone designation and other applicable approval criteria;

2. Trees located within vegetated corridors and stands rather than individual isolated trees subject to windthrow;

3. Trees that fulfill a screening function, provide relief from glare, or shade expansive areas of pavement;

4. Trees that provide a buffer between potentially incompatible land uses;

5. Trees located along the perimeter of the lot(s) and within building setback areas;

6. Trees and stands of trees located along ridgelines and within view corridors;

7. Trees with significant habitat value;

8. Trees adjacent to public parks, open space and streets.

9. Trees along water features.

10. Heritage trees.

(c) Restoration or Replacement.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the proposal mitigates, to the greatest degree attainable or feasible, the loss of significant natural features described in criteria (a) and (b) above, through the restoration or replacement of natural features such as:

a. Planting of replacement trees within common areas; or

b. Re-vegetation of slopes, ridgelines, and stream corridors; or

c. Restoration of fish and wildlife habitat, native plant habitat, wetland areas, and riparian vegetation.

To the extent applicable, restoration or replacement shall be in compliance with the planting and replacement standards of EC 6.335 and rules adopted thereunder.

2. For areas included on the city’s acknowledged Goal 5 inventory, any loss of significant natural features described in criteria (a) and (b) above shall be consistent with the acknowledged level of protection for the features.

(d) Street Trees. If the proposal includes removal of any street tree(s), removal of those street tree(s) has been approved, or approved with conditions according to the process at EC 6.305 of this code.

(e) Parking. There is a need for parking in the area and the proposed parking area will provide shared parking.

(3) The proposal provides safe and adequate transportation systems through compliance with all of the following:

(a) Compliance with EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(b) Pedestrian, bicycle and transit circulation, including related facilities, as needed among buildings and related uses on the development site, as well as to adjacent and nearby residential areas, transit stops, neighborhood activity centers, office parks, and industrial parks, provided the city makes findings to demonstrate consistency with constitutional requirements. “Nearby” means uses within 1/4 mile that can reasonably be expected to be used by pedestrians, and uses within 2 miles that can reasonably be expected to be used by bicyclists.

(4) The proposal will not be a significant risk to public health and safety, including but not limited to soil erosion, slope failure, stormwater or flood hazard, or an impediment to emergency response.

(5) The proposal complies with all of the following standards:

(a) EC 9.2000 through 9.4170 regarding lot dimensions and density requirements for the subject zone and overlay zone;

(b) EC 9.6500 through 9.6505 Public Improvement Standards.

(c) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(d) EC 9.6710 Geological and Geotechnical Analysis.

(e) EC 9.6730 Pedestrian Circulation On-Site.

(f) EC 9.6735 Public Access Required.

(g) EC 9.6750 Special Setback Standards.

(h) EC 9.6775 Underground Utilities.

(i) EC 9.6780 Vision Clearance Area.

(j) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(k) All other applicable development standards for features explicitly included in the application.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(6) The proposal complies with applicable adopted plan policies beginning at EC 9.9500.

(7) Any additional specific factors applied at the time the /SR designation was applied.

(Section 9.8440, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; and Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8445 Site Review Approval Criteria – Housing/Clear and Objective.

Unless the applicant elects to use the discretionary criteria contained in EC 9.8440 Site Review Approval Criteria – General/Discretionary, for housing applications entitled to clear and objective review pursuant to state statute, the planning director shall approve, conditionally approve, or deny the site review application based on compliance with the following criteria:

(1) The proposal complies with EC 9.5860 Transition Standards.

(2) For a proposal for multiple-unit developments, the proposal complies with the standards contained in EC 9.5500 Multiple-Unit Standards.

(3) For areas not included on the city’s acknowledged Goal 5 inventory, the proposal will preserve existing natural resources by compliance with the provisions of EC 9.6880 through EC 9.6885 Tree Preservation and Removal Standards.

(4) The proposal complies with all of the following:

(a) EC 9.2000 through EC 9.4170 regarding applicable lot dimensions and density requirements for the subject zone and any applicable overlay zones.

(b) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(c) EC 9.6500 through 9.6505 Public Improvement Standards.

(d) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(e) EC 9.6710(6) Geological and Geotechnical Analysis.

(f) EC 9.6730 Pedestrian Circulation On-Site.

(g) EC 9.6735 Public Access Required.

(h) EC 9.6750 Special Setback Standards.

(i) EC 9.6775 Underground Utilities.

(j) EC 9.6780 Vision Clearance Area.

(k) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(l) All other applicable development standards for features explicitly included in the application.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(5) Public improvements as required by this land use code or as a condition of approval will be completed prior to issuance of a development permit, or:

(a) A performance bond or suitable substitute as agreed upon by the city has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the subdivision, and the petition has been accepted by the city engineer.

(6) If the standards addressed under EC 9.8445(4) require a public street, or if the applicant proposes the creation of a public street, the proposal will provide pedestrian and bicycle circulation to transit stops and neighborhood activity centers located within 1/4 mile of the development site, provided the city makes findings to demonstrate consistency with constitutional requirements. The distance between the development site and a transit stop or neighborhood activity center shall be determined using the shortest distance as measured in a straight line between a point along the perimeter of the development site and:

(1) A sign identifying a transit stop; or

(2) A point along a property line of a neighborhood activity center.

(Section 9.8445, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20297, enacted August 11, 2003, effective September 10, 2003; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8450 Final Site Review Approval.

Following the issuance of the final decision approving a site review application, the applicant shall satisfy all applicable conditions. A site review plan shall not be stamped with the city’s approval until all conditions of approval have been met. Once stamped by the city’s approval, a site review plan is deemed to be consistent with all development standards of this land use code.

(Section 9.8450, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8455 Modifications to Approved Site Review Plans.

Modifications of the final approved site review plan may be requested following the Type II process. The planning director shall approve the request if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If the planning director determines that the modification is not consistent with the above criteria, the proposed modification may not occur until a new site review application is submitted and reviewed based on the Type II application procedures in section 9.7200 and the requirements and criteria in sections 9.8425-9.8455. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new site review application.

(Section 9.8455, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8460 Purpose of Standards Review.

The standards review process is intended to provide a way to effectively review specific types of proposed development with standards outlined in this land use code.

(Section 9.8460, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006.)

9.8465 Applicability.

Where this land use code allows a specific use, subject to standards review, the application for review shall be considered under a Type II process, unless the subject land use application is being considered under a Type III application process. If the review requested is a part of a Type III application, the review of standards shall be considered concurrently under a Type III application process. No development permit shall be issued by the city prior to completion of the standards review.

(Section 9.8465, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006.)

9.8470 Standards Review Approval Criteria.

The decision-maker shall determine whether the application is in compliance with the standards setout in the code section that calls for standards review.

(Section 9.8470, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009.)

9.8472 Standards Review – Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, applications for uses subject to standards review under EC 9.4780(3) or EC 9.4930(3) shall be subject to the following requirements:

(1) Unless waived by the planning director, the application shall be prepared by one or more of the following professionals:

(a) Oregon licensed architect.

(b) Oregon licensed civil engineer.

(c) Oregon licensed landscape architect.

(d) For applications submitted under EC 9.4780(3), a professionally trained botanist, biologist, ecologist, or geomorphologist or creek restoration specialist with a bachelor’s degree in the subject field and at least 5 years of applied experience in botany, biology, ecology, geomorphology, or a closely related field, or an Oregon licensed geologist.

(e) For applications submitted under EC 9.4930(3), a professionally trained botanist or biologist, with sufficient training and experience in planning and design to evaluate consistency of the application with all applicable standards.

(2) Unless waived by the planning director, if the application submitted under EC 9.4930(3) is not prepared by a professionally trained botanist or biologist, one or more of the professionals preparing the application shall have sufficient professional expertise and training in field botany or related biological sciences to evaluate consistency of the application with application standards.

(3) The application shall include a site plan that shows sufficient detail and supporting narrative information to demonstrate compliance with applicable standards. Unless waived by the planning director, the site plan shall be prepared by an Oregon licensed civil engineer or Oregon licensed surveyor.

(4) The site plan and application shall be signed by each of the professionals preparing the application, certifying that the application is true and correct to the best of his or her professional ability, and that, if applicable, the professional standards of his or her profession have been met therein.

(Section 9.8472 added by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009.)

9.8474 Standards Review – Modification.

Modification of an approved standards review granted pursuant to EC 9.4780(3) or 9.4930(3) may be requested following the Type II process. The planning director shall approve the request if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will not result in a greater impact to the resource than permitted by the initial approval.

If the planning director determines that the modification is not consistent with the above criteria, the proposed modification may not occur until a new standards review application is submitted and reviewed based on the Type II application procedures in section 9.7200 and the requirements and criteria in sections 9.4770-9.4790 or 9.4900-9.4980. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new standards review application.

(Section 9.8474 added by Ordinance No. 20351, enacted November 14, 2005, effective January 1,2006; and amended by Ordinance 20430, enacted March 9, 2009, effective June 10, 2009.)

9.8475 Purpose of Street Name Changes.

Requests to rename an existing street may be generated by a variety of circumstances. In many cases, there are other existing streets in the city that have similar sounding names resulting in confusion for the postal service, emergency response services and the general public. Applications to rename a street are subject to state law that requires the planning commission to review the request and make a recommendation to the city council for final action.

(Section 9.8475, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8480 Applicability.

Any existing street or highway, other than a county or state road or highway, may be renamed by the city council provided it is within six miles of the limits of the city and within the Eugene Urban Growth Boundary. Street name changes are subject to the Type IV procedural requirements beginning at EC 9.7400.

(Section 9.8480, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8485 Street Name Change Approval Criteria.

The planning commission shall recommend, and the city council shall approve an application for a street name change upon determining that a proposed renaming is in the best interest of the city.

(Section 9.8485, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8490 General Requirements.

The city council by ordinance shall rename a street or highway in accordance with the recommendation of the planning commission, or by resolution shall reject the recommendation. A certified copy of the ordinance shall be filed for record with the county clerk or recorder, and a like copy shall be filed with the county assessor and county surveyor. The county surveyor shall enter the new names of the streets and roads as required by state law.

(Section 9.8490, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8500 Purpose of Subdivision, Tentative Plan.

Sections 9.8500 through 9.8575 governing the approval of subdivisions are established in order to accomplish the orderly development of land within the community. These regulations are intended to ensure adequate provision of public facilities and services, address potential environmental impacts, protect the public health and safety of the community and enable development to occur consistent with the comprehensive plan.

(Section 9.8500, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8505 Applicability of Subdivision, Tentative Plan Applications.

(1) Except as provided in subsections (2) and (3) of this section, requests to create 4 or more lots shall be subject to the subdivision provisions of this land use code and shall follow a Type II application process.

(2) Subdivision applications that meet the approval criteria in EC 9.8515(13) or EC 9.8520(9) may be processed pursuant to the expedited land division procedures in EC 9.7900 through EC 9.7925.

(3) Concurrent applications may be processed as provided in EC 9.8005.

(4) A tentative plan application to subdivide land may be submitted and reviewed concurrently with a tentative PUD application following a Type III application procedure. If a subdivision application that also involves a PUD application is not submitted concurrently with a tentative PUD application, the subdivision application may not be submitted until a tentative PUD application is approved. (Refer to EC 9.8305 Applicability.)

(5) If a subdivision tentative plan application is not reviewed concurrently with a tentative PUD application, no development permit shall be issued by the city prior to approval of the tentative subdivision application. If a subdivision tentative plan application is reviewed concurrently with a tentative PUD application, no development permit shall be issued by the city prior to approval of the final PUD application in accordance with EC 9.8305.

(Section 9.8505, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023.)

9.8510 Subdivision, Tentative Plan Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, the following specific requirements shall apply to tentative subdivision plan applications:

(1) All tentative subdivision applications shall be prepared by an Oregon licensed land surveyor and shall include a preliminary title report.

(2) The application shall include all contiguous undeveloped or partially developed property under the same ownership as the subject property, be signed by the owner of the property, and include such related information as prescribed by the planning director.

(3) The tentative subdivision plan application shall include a phasing plan that indicates any proposed phases for development, including the boundaries and sequencing of each phase. Phasing shall progress in a sequence that promotes street connectivity between the various phases of the development and accommodates other required public improvements.

(4) The lot proposed to be divided in the subdivision application is a legal lot.

(5) If the proposal includes housing, the written statement submitted with the subdivision application shall clearly state whether the applicant is electing to use the discretionary approval criteria in EC 9.8515 Subdivision, Tentative Plan Approval Criteria – General/Discretionary instead of the approval criteria found in EC 9.8520 Subdivision, Tentative Plan Approval Criteria – Housing/Clear and Objective.

(6) The written statement submitted with the subdivision application shall clearly state whether the applicant is electing to use the expedited land division procedures in EC 9.7900 through EC 9.7925 and how the applicant believes that the proposal qualifies for the expedited land division procedures in EC 9.7900 through EC 9.7925.

(Section 9.8510, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20269, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8515 Subdivision, Tentative Plan Approval Criteria – General/Discretionary.

The planning director shall approve, approve with conditions, or deny a proposed subdivision. Approval, or approval with conditions shall be based on compliance with the following criteria:

(1) The proposed subdivision complies with all of the following, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(a) EC 9.2000 through 9.4170 regarding lot dimensions and density requirements for the subject zone and overlay zone. Within the /WR Water Resources Conservation Overlay Zone, no new lot may be created if more than 33% of the lot, as created , would occupy either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways; and

(c) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(2) Approval does not impede the future best use of the remainder of the property under the same ownership or adversely affect the development of the remainder or any adjoining land or access thereto, based on the provisions of this land use code. For subdivisions involving phasing, it shall be demonstrated that each sequential phase will maintain consistency with the provisions of EC 9.8515 Tentative Subdivision Approval Criteria – General/Discretionary.

(3) Any existing improvements on the proposed lots are consistent with the provisions of this land use code.

(4) The proposed subdivision will be consistent with the property’s designation in the comprehensive plan and applicable adopted plan policies as reflected in the sections beginning at EC 9.9500.

(5) The proposed subdivision will:

(a) Not result in unreasonable risk of fire, flood, geological hazards, or other public health and safety concerns;

(b) Provide adequate transportation systems, water supply, sewage disposal, drainage, and other public utilities;

(c) Not hamper the adequate provision of publicly owned open space for recreation needs.

(6) The proposed subdivision provides safe, convenient, and direct bicycle and pedestrian access to nearby and adjacent residential areas, transit stops, neighborhood activity centers, commercial areas, and employment and industrial areas, and provides safe, convenient, and direct transit circulation, provided the city makes findings to demonstrate consistency with constitutional requirements. “Nearby” means uses within 1/4 mile that can reasonably be expected to be used by pedestrians, and uses within 2 miles that can reasonably be expected to be used by bicyclists.

(7) The proposed subdivision is designed and sited such that roads, infrastructure, utilities, and future development of proposed lots will minimize impacts to the natural environment by addressing the following:

(a) Protection of Natural Features.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the preservation of significant natural features to the greatest degree attainable or feasible, including:

a. Significant on-site vegetation, including rare plants (those that are proposed for listing or are listed under state or federal law), and native plant communities.

b. All documented habitat for all rare animal species (those that are proposed for listing or are listed under State or Federal law).

c. Prominent topographic features, such as ridgelines and rock outcrops.

d. Wetlands, intermittent and perennial stream corridors, and riparian areas.

e. Natural resource areas designated in the comprehensive plan diagram as “Natural Resource” and areas identified in any city-adopted natural resource inventory.

2. For areas included on the city’s acknowledged Goal 5 inventory, the preservation of natural features shall be consistent with the acknowledged level of preservation provided for the area.

(b) Tree Preservation. The proposed project shall be designed and sited to preserve significant trees to the greatest degree attainable or feasible, with trees having the following characteristics given the highest priority for preservation:

1. Healthy trees that have a reasonable chance of survival considering the base zone or special area zone designation and other applicable approval criteria;

2. Trees located within vegetated corridors and stands rather than individual isolated trees subject to windthrow;

3. Trees that fulfill a screening function, provide relief from glare, or shade expansive areas of pavement;

4. Trees that provide a buffer between potentially incompatible land uses;

5. Trees located along the perimeter of the lot(s) and within building setback areas;

6. Trees and stands of trees located along ridgelines and within view corridors;

7. Trees with significant habitat value;

8. Trees adjacent to public parks, open space and streets.

9. Trees along water features.

10. Heritage trees.

(c) Restoration or Replacement.

1. For areas not included on the city’s acknowledged Goal 5 inventory, the proposal mitigates, to the greatest degree attainable or feasible, the loss of significant natural features described in criteria (a) and (b) above, through the restoration or replacement of natural features such as:

a. Planting of replacement trees within common areas; or

b. Re-vegetation of slopes, ridgelines, and stream corridors; or

c. Restoration of fish and wildlife habitat, native plant habitat, wetland areas, and riparian vegetation.

To the extent applicable, restoration or replacement shall be in compliance with the planting and replacement standards of EC 6.320.

2. For areas included on the city’s acknowledged Goal 5 inventory, any loss of natural features shall be consistent with the acknowledged level of protection provided for the resource.

(d) Street Trees. If the proposal includes removal of any street tree(s), removal of those street tree(s) has been approved, or approved with conditions according to the process at EC 6.305 of this code.

(8) On R-1 zoned property, if the subdivision results in a lot greater than 13,500 square feet in size based on EC 9.2761(5)(b), the application shall indicate the location of lot lines and other details of layout that show future division of the lot may be made without violating the requirements of this land use code and without interfering with the orderly extension of adjacent streets, bicycle paths, and accessways. If the planning director deems it necessary for the purpose of future land division, any restriction of buildings within future street, bicycle path, and accessway locations shall be made a matter of record in the tentative plan approval.

(9) As far as is practicable, lot side lines shall run at right angles to the street upon which the lots face, except that on curved streets they shall be radial to the curve.

(10) The proposed subdivision complies with all of the following:

(a) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(b) EC 9.6710 Geological and Geotechnical Analysis.

(c) EC 9.6730 Pedestrian Circulation On-Site.

(d) EC 9.6735 Public Access Required.

(e) EC 9.6750 Special Setback Standards.

(f) EC 9.6775 Underground Utilities.

(g) EC 9.6780 Vision Clearance Area.

(h) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

(i) The proposed subdivision complies with other applicable development standards for features explicitly included in the application.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(11) The proposal complies with the Traffic Impact Analysis Review provisions of EC 9.8650 through 9.8680 where applicable.

(12) For applications intended to implement an approved tentative or final planned unit development for the site:

(a) The proposed subdivision is consistent with the approved planned unit development plan;

(b) If full compliance with a tentative subdivision criterion in this section would cause an inconsistency between the tentative subdivision plan and an approved tentative or final planned unit development for the site, the city shall require compliance with that subdivision criterion only to the extent that it can do so without creating the inconsistency.

(13) If the applicant elects to use the expedited land division procedures in EC 9.7900 through EC 9.7925, the application must meet the following additional approval criteria in subparagraphs (a)–(c):

(a) The subdivision only includes land zoned for residential uses;

(b) The lots created will only be developed for residential use, including recreational or open space accessory to residential use; and

(c) The lots created will either allow construction of residential units at a density of 80 percent or more of the maximum net density per acre permitted in the zone and identified in Table 9.2750; or existing and future dwellings located on the property that is the subject of the subdivision application will be sold or rented to households with incomes below 120 percent of the median family income for Lane County.

(Section 9.8515, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003; Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20528, enacted May 14, 2014, effective June 23, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8520 Subdivision, Tentative Plan Approval Criteria – Housing/Clear and Objective.

Unless the applicant elects to use the discretionary criteria contained in EC 9.8515 Subdivision, Tentative Plan Approval Criteria – General/Discretionary, for housing applications entitled to clear and objective review pursuant to state statute, the planning director shall approve, conditionally approve, or deny the subdivision application based on compliance with the following criteria:

(1) The proposed land uses and densities are consistent with the land use designation(s) shown on the comprehensive plan diagram, as refined in any applicable refinement plan.

(2) The proposed subdivision complies with all of the following, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(a) EC 9.2000 through EC 9.4170 regarding applicable lot dimensions and density requirements for the subject zone and any applicable overlay zones. Within the /WR Water Resources Conservation Overlay Zone or /WQ Water Quality Overlay Zone, no new lot may be created if more than 33% of the lot, as created, would be occupied by either:

1. The combined area of the /WR conservation setback and any portion of the Goal 5 Water Resource Site that extends landward beyond the conservation setback; or

2. The /WQ Management Area.

(b) EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and Other Public Ways.

(c) EC 9.6500 through EC 9.6505 Public Improvement Standards.

(d) EC 9.6706 Development in Flood Plains through EC 9.6709 Special Flood Hazard Areas – Standards.

(e) EC 9.6710(6) Geological and Geotechnical Analysis.

(f) EC 9.6730 Pedestrian Circulation On-Site.

(g) EC 9.6735 Public Access Required.

(h) EC 9.6750 Special Setback Standards.

(i) EC 9.6775 Underground Utilities.

(j) EC 9.6780 Vision Clearance Area.

(k) EC 9.6791 through 9.6797 regarding stormwater flood control, quality, flow control for headwaters area, oil control, source control, easements, and operation and maintenance.

An approved adjustment to a standard pursuant to the provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(3) The proposed subdivision will not cause any existing improvements on proposed lots to be inconsistent with applicable standards in this land use code.

(4) The proposed subdivision provides pedestrian, bicycle and transit circulation among buildings located within the development site, as well as pedestrian circulation to transit stops and neighborhood activity centers located within 1/4 mile of the development site and bicycle circulation to transit stops, and neighborhood activity centers located within 2 miles of the development site, provided the city makes findings to demonstrate consistency with constitutional requirements. The distance between the development site and a transit stop or neighborhood activity center shall be determined using the shortest distance as measured in a straight line between a point along the perimeter of the development site and:

(1) A sign identifying a transit stop; or

(2) A point along a property line of a neighborhood activity center.

(5) For areas not included on the city’s acknowledged Goal 5 inventory, the subdivision will preserve existing natural resources by compliance with the provisions of EC 9.6880 through EC 9.6885 Tree Preservation and Removal Standards.

(6) On R-1 zoned property, if the subdivision results in a lot greater than 13,500 square feet in size based on EC 9.2761(5)(b), the application shall indicate the location of lot lines and other details of layout that show future division may be made without violating the requirements of this land use code and without interfering with the orderly extension of adjacent streets, bicycle paths, and accessways. Any restriction of buildings within future street, bicycle path, and accessway locations shall be made a matter of record in the tentative plan approval.

(7) The subdivision complies with development standards explicitly addressed in the application or is granted adjustments thereto pursuant to the provisions beginning at EC 9.8015 of this land use code.

(8) Where all or a portion of a development site is within the South Hills Study and above 700 feet in elevation, the proposed development shall have received initial approval through the Planned Unit Development process. Where all or a portion of the development site is within the South Hills Study and is between 500 feet and 701 feet, and the development site is at least 4 acres with areas of the development site containing slopes that exceed 20%, the proposal shall have received initial approval through the Planned Unit Development process.

(9) If the applicant elects to use the expedited land division procedures in EC 9.7900 through EC 9.7925, the application must meet the following additional approval criteria in subparagraphs (a)–(c):

(a) The subdivision only includes land zoned for residential uses;

(b) The lots created will only be developed for residential use, including recreational or open space accessory to residential use; and

(c) The lots created will either allow construction of residential units at a density of 80 percent or more of the maximum net density per acre permitted in the zone and identified in Table 9.2750; or, existing and future dwellings located on the property that is the subject of the subdivision application will be sold or rented to households with incomes below 120 percent of the median family income for Lane County.

(Section 9.8520, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20285, enacted March 10, 2003, effective April 9, 2003; Ordinance No. 20297, enacted August 11, 2003, effective September 10, 2003; administratively corrected March 15, 2005; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006; Ordinance No. 20369, enacted June 14, 2006, effective July 14, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20521, enacted January 13, 2014, effective March 1, 2014; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20679, enacted November 30, 2022, effective January 1, 2023; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8550 Purpose of Subdivision, Final Plat.

Sections 9.8550 through 9.8575 establish the procedures for processing subdivision final plat applications in a manner that ensures adequate provision of public facilities and services, protects the public health and safety of the community and enables development to occur consistent with tentative subdivision approval and applicable provisions of the comprehensive plan.

(Section 9.8550, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8555 Applicability of Subdivision, Final Plat Applications.

A subdivision final plat application follows a Type I process. Applications for final plat approval cannot be submitted unless the subject property received tentative plan approval and any approval conditions required prior to submittal of the final plat have been met.

(Section 9.8555, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20417, enacted August 11, 2008, effective July 7, 2009.)

9.8560 Subdivision, Final Plat Application Requirements.

In addition to the provisions in EC 9.7010 Application Filing, subdivision final plat applications shall:

(1) Be signed by the owner of the property.

(2) Contain a proposed final plat stamped and signed by an Oregon licensed land surveyor, complying with state and local platting and surveying requirements.

(3) Contain documentation addressing all conditions of tentative plat approval and state and local platting requirements.

(Section 9.8560, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8565 Subdivision, Final Plat Approval Criteria.

The planning director shall approve or deny the subdivision final plat. Approval shall be based on compliance with the following criteria, unless specifically exempt from compliance through a code provision applicable to a special area zone or overlay zone:

(1) Streets, roads, and alleys for public use are dedicated without any reservation or restriction other than reversionary rights upon vacation.

(2) Public improvements as required by this land use code or as a condition of tentative plan approval have been completed, or:

(a) A performance bond or suitable substitute as agreed upon by the city has been filed with the city finance officer in an amount sufficient to assure the completion of all required public improvements; or

(b) A petition for public improvements and for the assessment of the real property for the improvements has been signed by the property owner seeking the subdivision, and the petition has been accepted by the city engineer.

(3) Conservation areas, including natural resource buffers and tree preservation areas, have been designated as required by this land use code or as a condition of tentative approval; and a performance bond, or suitable substitute as agreed upon by the city has been filed with the city finance officer in an amount sufficient to assure the implementation of any natural resource protection or restoration requirements of the tentative subdivision approval.

(4) Public assessments, liens, and fees with respect to the subdivision have been paid, or a guarantee acceptable to the city manager has been provided assuring the liens, assessments, and fees will be paid prior to recordation.

(5) All conditions of tentative approval have been met and the final plat substantially conforms with the provisions of the approved tentative plan.

(6) The city surveyor has approved the final plat for compliance with applicable platting requirements in accordance with state law.

(Section 9.8565, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013.)

9.8570 Subdivision, Final Plat Recordation.

The city surveyor and planning director shall note their approval of the subdivision on the subdivision’s final plat along with the effective date of approval, which constitutes the city’s acceptance of any dedications to the public contained therein. After approval, the city shall forward the subdivision’s final plat to Lane County for signatures and recording.

(Section 9.8570, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8575 Special Platting Standards.

In addition to the partition and subdivision requirements contained in this land use code, the following specific platting standards may also apply to partition and subdivision applications that include lots or parcels designated as conservation parcels and lots or parcels located adjacent to a railroad right-of-way:

(1) Conservation Land Divisions. Conservation land divisions are intended to facilitate the sale or donation of valuable natural resource areas to public or non-profit agencies for long-term protection and management by dividing conservation areas and remaining areas into separate parcels.

(a) Conservation parcels are those set aside and managed to conserve natural resource values including the following:

1. Wildlife habitat.

2. Ecological significance.

3. Rare or endangered species.

4. Water quality.

5. Flood storage and control.

Conservation parcels are primarily undeveloped and natural, and shall have no minimum standards for lot area, frontage, width or depth.

(b) Remainder parcels are those parcels that are not being protected for natural resource values. Remainder parcels may be developed, partly developed, or undeveloped. The planning director may authorize exceptions to the minimum platting standards for lot area, lot frontage, lot width, and lot depth for remainder parcels provided the following standards are met:

1. At least one of the lots created must be a conservation parcel and must be rezoned to NR Natural Resource zone prior to or concurrent with land division.

2. The number of remainder parcels created must be the least number that will accomplish the purpose of the conservation land division.

3. Exceptions to minimum lot and parcel platting standards will not be allowed on residentially zoned remainder parcels.

4. Exceptions to minimum lot and parcel platting standards for remainder parcels in agricultural, commercial and employment and industrial zones will be no more than the minimum needed to accomplish the purpose of the conservation land division.

(c) The city shall keep records of approved remainder parcels to ensure that zoning reviews on future development permit applications are consistent with that approval.

(2) Platting Standards – Railroads.

(a) In accordance with the purpose of EC 9.8400 Purpose of Property Line Adjustments, special requirements may be imposed by the planning director in connection with railroad crossings including, but not limited to, provisions for separation of street and railroad grades, if necessary for the safety of the residents of the partition or subdivision and of the general public.

(b) Where the partition or subdivision is adjacent to a railroad right-of-way, and the surrounding economic and physical conditions indicate the property will be used for employment and industrial purposes, all streets shall be located at a sufficient distance from the right-of-way to allow for reasonable sites for employment and industrial use adjacent to the right-of-way.

(Section 9.8575, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20528, enacted May 14, 2014, effective June 23, 2014.)

9.8580 Modifications to Approved Subdivision Performance Agreement.

The applicant may apply for a modification of the approved subdivision performance agreement following the Type II process. The planning director shall approve the request only if it complies with the following criteria:

(1) The proposed modification is consistent with the conditions of the original approval.

(2) The proposed modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If the planning director determines that the proposed modification is not consistent with the above criteria, the proposed modification may not occur. Nothing in this section shall preclude the applicant from initially submitting the requested modification as a new subdivision tentative plan application.

(Section 9.8580 added by Ordinance No. 20353, enacted November 28, 2005, effective January 1, 2006.)

9.8600 Purpose of Temporary Manufactured Dwelling Hardship Permits.

Sections 9.8600 through 9.8615 regulate the provision of temporary housing to address medical needs. These regulations are intended to ensure adequate provisions exist to accommodate small scale temporary housing on individual lots in low-density areas.

(Section 9.8600, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8605 Applicability.

Requests for temporary manufactured dwelling hardship permits shall be subject to these provisions.

(Section 9.8605, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8610 Temporary Manufactured Dwelling Hardship Permits General Requirements.

All applications for a temporary manufactured dwelling hardship permit shall be processed under a Type I procedure and shall be submitted in the manner and on a form approved by the city manager.

(Section 9.8610, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8615 Temporary Manufactured Dwelling Hardship Permit Approval Criteria.

A temporary manufactured dwelling hardship permit shall be granted if all of the following are met:

(1) A written communication is submitted to the city from a physician, therapist, or other professional counselor establishing that the person on whose behalf the temporary manufactured dwelling hardship permit is sought is suffering either a physical or mental impairment, infirmity, or is otherwise disabled and must be near a designated care giver in order to receive adequate care.

(2) The lot on which the temporary manufactured dwelling would be placed must be zoned R-1.

(3) The temporary manufactured dwelling is limited to a single-wide manufactured dwelling with no more than two bedrooms.

(4) The temporary manufactured dwelling must be set back a minimum of 10 feet from the primary dwelling and all interior property lines.

(5) The temporary manufactured dwelling must be located to the rear of the primary dwelling unit (except on corner lots).

(6) A pedestrian and vehicular access drive to the temporary manufactured dwelling (capable of supporting the weight of emergency vehicles) shall be maintained for the purposes of emergency access and future removal of the manufactured dwelling.

(7) The placement of the temporary manufactured dwelling shall not require a permanent foundation, filling, or grading.

(8) The temporary manufactured dwelling must be screened from abutting properties with a 75 percent opaque site-obscuring fence, wall, or vegetation 6 feet in height. This requirement can be met by existing or new materials.

(9) The temporary manufactured dwelling must be equipped with skirting that in design, color, and texture appears to be an integral part of the adjacent exterior wall of the manufactured dwelling.

(10) The temporary manufactured dwelling must be connected to an on-site sewer system serving an existing dwelling on the same lot.

(11) Construction and installation of plumbing, gas, piping, electrical equipment, wiring, tie-downs, over-the-top ties, and skirting must comply with all applicable federal, state and local rules and regulations.

(12) Temporary manufactured dwellings must comply with the solar access setback standards with respect to structures on adjacent lots.

(13) The temporary manufactured dwelling must comply with all applicable federal, state, and local special flood hazard area rules and regulations.

(14) Within 60 days of the date that the hardship for which a temporary manufactured dwelling hardship permit has been issued ceases, the temporary manufactured dwelling must be disconnected from the sewer system and all utilities, and removed from the lot.

(15) The temporary manufactured dwelling must be a manufactured home or a mobile home as defined in section 9.0500.

(Section 9.8615, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20699, enacted November 13, 2023, effective December 31, 2023.)

9.8650 Purpose of Traffic Impact Analysis Review.

The purpose of Traffic Impact Analysis Review is to ensure that developments which will generate a significant amount of traffic, cause an increase in traffic that will contribute to traffic problems in the area, or result in levels of service of the roadway system in the vicinity of the development that do not meet adopted level of service standards provide the facilities necessary to accommodate the traffic impact of the proposed development. In addition, any Traffic Impact Analysis Review addressing streets in the jurisdiction of Lane County is also designed to ensure that cross sectional elements of streets, such as the wearing coarse or pavement, base material, soils, or storm water structures (bridges or culverts) have the adequate capacity to accommodate developments that utilize vehicles of heavy weight and associated vehicle traffic as part of their activity.

(Section 9.8650, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8670 Applicability.

Traffic Impact Analysis Review is required when one of the conditions in subsections (1) – (4) of this section exist unless the development is within an area (a) shown on Map 9.8670 Downtown Traffic Impact Analysis Exempt Area, or (b) subject to a prior approved Traffic Impact Analysis and is consistent with the impacts analyzed.

(1) The development will generate 100 or more vehicle trips during any peak hour as determined by using the most recent edition of the Institute of Transportation Engineer’s Trip Generation. In developments involving a land division, the peak hour trips shall be calculated based on the likely development that will occur on all lots resulting from the land division.

(2) The increased traffic resulting from the development will contribute to traffic problems in the area based on current accident rates, traffic volumes or speeds that warrant action under the city’s traffic calming program, and identified locations where pedestrian and/or bicyclist safety is a concern by the city that is documented.

(3) The city has performed or reviewed traffic engineering analyses that indicate approval of the development will result in levels of service of the roadway system in the vicinity of the development that do not meet adopted level of service standards.

(4) For development sites that abut a street in the jurisdiction of Lane County, a Traffic Impact Analysis Review is required if the proposed development will generate or receive traffic by vehicles of heavy weight in their daily operations.

For purposes of EC 9.8650 through EC 9.8680, “daily operations” does not include routine services provided to the site by others, such as mail delivery, garbage pickup, or bus service. “Daily operations” does include, but is not limited to, delivery (to or from the site) of materials or products processed or sold by the business occupying the site. For purposes of EC 9.8650 through EC 9.8680, “heavy vehicles” are defined as a single vehicle or vehicle combination greater than 26,000 pounds gross vehicle weight or combined gross vehicle weight respectively.

(Section 9.8670, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20457, enacted March 8, 2010, effective April 10, 2010; amended by Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; amended by Ordinance No. 20514, enacted July 22, 2013, effective August 24, 2013.)

9.8675 General Application Requirements.

An application for Traffic Impact Analysis Review shall contain each of the items required by the “Standards for Traffic Impact Analyses” available from the city. An exception to any or all of the report content requirements listed in the “Standards for Traffic Impact Analyses” for development that generate less than 100 trips in any peak hour may be granted if the applicant demonstrates that the study is not necessary in order to demonstrate compliance with EC 9.8680.

(Section 9.8675, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20457, enacted March 8, 2010, effective April 10, 2010.)

9.8680 Approval Criteria.

The planning director shall approve, conditionally approve, or deny an application for Traffic Impact Analysis Review following a Type II process, or as part of a Type III process when in conjunction with a CUP or PUD. Approval or conditional approval shall be based on compliance with the following criteria:

(1) Traffic control devices and public or private improvements as necessary to achieve the purposes listed in this section will be implemented. These improvements may include, but are not limited to, street and intersection improvements, sidewalks, bike lanes, traffic control signs and signals, parking regulation, driveway location, and street lighting.

(2) Public improvements shall be designed and constructed to the standards specified in EC 9.6505 Improvements – Specifications. The requirement of improvements based on a traffic impact analysis does not negate the ability of the city traffic engineer to require improvements by other means specified in this code or rules or regulations adopted thereunder.

(3) In addition to the above criteria, if the Traffic Impact Analysis Review was required based on EC 9.8670(4), the improvements shall also address the structural capacity of the street in the County’s jurisdiction and address identified structural deficiencies, or reduction in the useful life of existing street structures related to the proposed development. Improvements may be needed to eliminate the identified structural deficiencies and to accommodate vehicle impacts to structures.

(4) In addition to the above criteria, if the development is located within the S-WS Walnut Station Special Area Zone, any increased traffic the development would generate on streets within the Fairmount neighborhood to the south of the Walnut Station Special Area Zone shall be mitigated through the use of traffic calming strategies or other mechanisms designed to discourage such traffic.

(Section 9.8680, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20457, enacted March 8, 2010, effective April 10, 2010; and Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010.)

9.8700 Purpose of Vacations.

In order to ensure the orderly development of land, public ways in the form of streets, roads, alleys, rights-of-way, pedestrian and/or bicycle easements and accessways, or utility easements are established, obtained, or reserved by the city. As land develops, and as land uses change over time, public ways may no longer be necessary for ensuring the orderly development of land. This land use code and state law provide procedures, requirements, and criteria for vacating public ways. The vacation process includes a review of the need for public ways and the manner in which to dispense with public ways. In addition, sections 9.8700 through 9.8725 of this land use code provide a process for the vacation of undeveloped subdivision and partition plats or parts thereof.

(Section 9.8700, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective June 1, 2006.)

9.8705 Applicability of Vacation Procedures.

(1) The vacation process applies to recorded undeveloped subdivision and partition plats and to public ways and public easements under the jurisdiction of the city.

(2) The city’s vacation process does not apply to lands over which Lane County or the state have jurisdiction such as unannexed plats or public ways within the Urban Growth Boundary, or county roads and state highways within the corporate limits of the city where jurisdiction has not been transferred to the city.

(3) Vacation of public ways and public easements may be applied for by private citizens, public agencies, or the city council in accordance with EC 9.7000 through 9.7925 Application Procedures.

(Section 9.8705, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8710 Vacations, Application Requirements.

(1) Vacation of unimproved public easements shall be considered in accordance with the Type I Application Procedures contained in EC 9.7000 through 9.7925 and the approval criteria contained in EC 9.8715. In the case of public utility easements, statements of concurrence with the vacation from affected utility providers must be submitted with the application.

(2) Vacation of improved public easements, unimproved public right-of-way, and vacation and rededication of unimproved public rights-of-way, except improved public easements and public right-of-way located within undeveloped subdivision or partition plats, shall be considered in accordance with the Type II Application Procedures contained in EC 9.7000 through 9.7925 and the approval criteria contained in EC 9.8720. In the case of public utility easements, letters of concurrence to the vacation from affected utility providers must be submitted with the application.

(3) Vacation of any public way acquired with public funds, vacation of improved public right-of-way, and vacation of undeveloped subdivision and partition plats, or parts thereof, including public right-of-way and improved public easements located therein, shall be considered and decided upon by the city council in accordance with the procedures contained in EC 9.7445 through 9.7455 and the approval criteria contained in EC 9.8725.

(4) All applications shall be accompanied by the application fee established by the city manager pursuant to Chapter 2 of this code, and an additional amount sufficient to pay the expenses related to publication of the vacation notice.

(5) In addition to payment of the application and publication fees referenced in subsection (4) above, a vacation of improved or unimproved public right-of-way, any public way acquired with public funds, or any undeveloped subdivision or partition plat, or portions thereof, shall require the payment by the applicant of a deposit equal to the assessment of special benefit that results from the vacation and disposition of property to the benefitted property owners.

(a) The assessed value of special benefit and the amount of money to be deposited shall be determined by the city manager. The assessed value of special benefit shall include:

1. The value of the real property; and

2. The costs incurred by the city in the construction of public improvements.

(b) Notice of the proposed assessment for benefits shall be given by mail to the owners of the property to be assessed no less than 20 days prior to the public hearing of the vacation application before the city council, or in the case of Type II applications, 10 days prior to the issuance of the Planning Director’s decision. The notice shall contain a statement of the names, addresses, and the amount of the proposed assessment of each land owner’s special benefit by the vacation. Where a public hearing is required, the notice shall also include the hour, date, and place of the public hearing at which the city council will hear objections to the vacation or assessment.

(c) At least 5 working days prior to the public hearing, or in the case of a Type II application, 5 working days prior to the decision, the land owner shall deposit with the city the sum of money called for by this subsection (5).

(d) If the vacation application is approved, the deposit shall be retained by the city. If the vacation application is denied, the deposit shall be returned to the land owner.

(6) For vacations of improved or unimproved right-of-way, the application must include the required consent from surrounding property owners as set forth in ORS 271.080(2).

(7) For vacations of unimproved public easements and improved public easements, the application must include the signatures of all property owners and owners of property adjacent to the easement being vacated.

(Section 9.8710, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective June 1, 2006; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)

9.8715 Approval Criteria for the Vacation of an Unimproved Easement.

The planning director shall approve, approve with conditions, or deny the vacation application. Approval or approval with conditions shall be based on all of the following:

(1) The subject area is not presently or in the future needed for public services, facilities, or utilities, and the vacation does not prevent the extension of, or the retention of public services, facilities, or utilities; or if needed, the applicant shall provide for the replacement and abandonment of any existing public services, facilities or utilities in the subject area.

(2) Such public services, facilities, or utilities can be extended in an orderly and efficient manner in an alternate location.

(Section 9.8715, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective June 1, 2006.)

9.8720 Approval Criteria for Vacation of Improved Easements, Unimproved Public Right-of-Way, and Vacation and Rededication of Unimproved Public Right-of-Way.

The planning director shall approve, approve with conditions, or deny the vacation application. The application shall be approved if the vacation is found to be consistent with the all of the following criteria:

(1) The subject area is not presently or in the future needed for public services, facilities, or utilities, and the vacation does not prevent the extension of, or the retention of public services, facilities, or utilities; or if needed, the applicant shall provide for the replacement and abandonment of any existing public services, facilities, or utilities in the subject area.

(2) Such public services, facilities, or utilities can be extended in an orderly and efficient manner in an alternate location.

(3) The vacation does not impede the future best use of the remainder of the property under the same ownership or any adjoining land; or adversely affect the development of the remainder land, or any adjoining land, or access thereto; and the vacation does not conflict with provisions of this land use code including the street connectivity standards and block lengths.

(4) Payment of the special benefit assessment(s) resulting from the vacation of unimproved right-of-way required by EC 9.8710(5)(a), have been made to the city.

(Section 9.8720, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20353, enacted November 28, 2005, effective June 1, 2006.)

9.8725 Approval Criteria for the Vacation of Improved Public Right-of-Way, Public Ways Acquired with Public Funds, and Undeveloped Subdivision and Partition Plats.

The city council shall approve, or approve with conditions and reservations of easements, the vacation of improved public right-of-way, public ways acquired with public funds, or undeveloped subdivision and partition plats, or portions thereof, including public right-of-way and improved public easements located therein, only if the council finds that approval of the vacation is in the public interest.

(Section 9.8725, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8750 Purpose of Variances.

The provisions of EC 9.5750(9), 9.6708, and 9.8750 through 9.8760 allow for partial or full exemption from specific land use code standards only when, because of special circumstances applicable to the property, including location, shape, size, surroundings, or topography, the strict application of those regulations would deny the property owner uses enjoyed by other property owners in the vicinity and under identical zones. Any variance granted shall be subject to conditions that ensure the variance does not constitute a granting of special uses inconsistent with the limitations upon other properties in the vicinity and zone in which the property is situated. The city shall not grant variances which allow uses not on the applicable list of allowed uses specified in EC 9.2000 through 9.3980 of this land use code.

(Section 9.8750, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016.)

9.8755 Applicability.

Unless specified otherwise in another land use code section, the planning director may grant variances only to the standards prescribed in.

(1) EC 9.2000 to 9.3980 for the following:

(a) Building Height.

(b) Fences and Walls.

(c) Front Yard Setbacks.

(d) Interior Yard Setbacks.

(2) EC 9.6410 Motor Vehicle Parking Standards.

(3) EC 9.6600 to 9.6680 Sign Standards.

(4) EC 9.6745 Setbacks – Intrusions Permitted.

(Section 9.8755, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016.)

9.8760 Approval Criteria for Variances.

The planning director shall approve, conditionally approve, or deny a variance, with findings and conclusions thereon following a Type II process. Approval, or conditional approval shall be based on compliance with all the following criteria:

(1) A strict or literal interpretation and enforcement of the specified regulation would result in practical difficulty or undue physical hardship due to at least one of the following conditions:

(a) Size, shape, or dimensions of a site.

(b) Geographic, topographic, or other physical conditions on the site or in the immediate vicinity.

(c) Street locations or traffic conditions in the immediate vicinity.

Economic considerations do not constitute grounds for granting a variance.

(2) There are exceptional or extraordinary circumstances or conditions applicable to the property involved or to the intended use of the property that do not apply generally to other properties classified in the same zone.

(3) The granting of the variance will not be detrimental to the public health, safety or welfare, or materially injurious to properties or improvements in the vicinity.

(4) In addition to the above criteria, the following 3 criteria apply to variances from code sections that apply to EC 9.6410 Motor Vehicle Parking Standards, and from EC 9.2000 to 9.3980 base zone regulations as applied to fences and walls.

(a) Neither present nor anticipated future traffic volumes generated by the use of the site or uses of the sites in the vicinity reasonably require strict or literal interpretation and enforcement of the specified regulation.

(b) The granting of the variance will not result in the parking or loading of vehicles on public streets in such a manner as to interfere with the free flow of traffic on the streets.

(c) The granting of the variance will not create a safety hazard or any other condition inconsistent with the objectives of this land use code.

(5) In addition to the criteria set forth in subsections (2), (3) and ((4) of this section, the following criterion applies to variances from the provisions of EC 9.6600 to 9.6680 Sign Standards:

(a) Strict or literal interpretation and enforcement of the specified regulation would result in practical difficulty or undue physical hardship inconsistent with the objectives of EC 9.6600 to 9.6680 Sign Standards. A practical difficulty or undue hardship may result from the location of existing structures on the site or in the immediate vicinity. The planning director may not grant variances based on the convenience of the applicant, including any hardship of regional or national businesses which wish to use a standard sign when those standard signs do not conform to the provisions of the sign code.

(Section 9.8760, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016.)

9.8800 Purpose of Willamette River Greenway Permits.

The purpose of Willamette River Greenway Permits is to implement Oregon Statewide Planning Goal 15, Willamette River Greenway, which is designed to protect, conserve, enhance, and maintain the natural, scenic, historical, agricultural, economic, and recreational qualities of lands along the Willamette River. Protection, conservation, enhancement, and maintenance of the qualities of lands within the Willamette River Greenway is achieved through the following measures:

(1) Review of intensification of uses, changes in use, and developments proposed within the boundaries of the Willamette River Greenway.

(2) Imposition of conditions of approval as necessary to carry out the purpose and intent of the Willamette River Greenway

(Section 9.8800, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8805 Willamette River Greenway Permits – Applicability.

Willamette River Greenway permit applications are required for intensification of uses, changes in use, or developments within the boundaries of the Willamette River Greenway established by Resolution No. 2592 Adopting a Willamette River Greenway Boundary.

(Section 9.8805, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8810 Willamette River Greenway Permits - Application Requirements.

(1) Willamette River Greenway Permit applications shall be considered in accordance with the Type III application procedures contained in EC 9.7300 through EC 9.7340 Application Procedures unless considered concurrently with a Type IV or Type V application.

(2) If the intensification of use, change in use, or development that triggers the requirement for a Willamette River Greenway Permit includes or proposes housing, the written statement submitted with the Willamette River Greenway Permit application shall clearly state whether the applicant is electing to proceed under the Clear and Objective approval criteria in EC 9.8812, or whether the applicant is electing to proceed under the General approval criteria in EC 9.8815.

(3) No development permit shall be issued by the city when a Willamette River Greenway Permit is required for a proposed development until the Willamette River Greenway Permit has been approved and becomes effective. Development permits shall be consistent with the terms and conditions of that Willamette River Greenway Permit.

(Section 9.8810, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed ; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8811 Willamette River Greenway Setback – Clear and Objective.

(1) The Willamette River Greenway Setback is established to protect, maintain, preserve, and enhance the natural, scenic, historic, and recreational qualities of the Willamette River Greenway.

(2) The Willamette River Greenway Setback is only applicable to a Willamette River Greenway Permit Application when the applicant elects to proceed under the Clear and Objective approval criteria in EC 9.8812.

(3) The location of the Willamette River Greenway Setback is established by the Willamette River Greenway Setback Map adopted as Exhibit A-1 to Ordinance No. 20693.

(4) No structures, other than the structures listed in subsection (5) of this section may be built within the Willamette River Greenway Setback.

(5) For purposes of review under the Clear and Objective Willamette River Greenway Permit approval criteria in EC 9.8812, the City has determined that pedestrian paths and/or public accessways that are proposed or otherwise required pursuant to EC 9.8812(4) are the only structures within the Willamette River Greenway Setback necessary to support water-related and/or water-dependent uses; therefore, pedestrian paths and/or public accessways that are proposed or otherwise required pursuant to EC 9.8812(4) are the only new structures that may be constructed within the Willamette River Greenway Setback pursuant to a Willamette River Greenway Permit approved under EC 9.8812.

(Added by Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8812 Willamette River Greenway Permit Approval Criteria – Clear and Objective.

Unless an applicant proposing an intensification of use, change in use, or development that proposes or includes housing elects to use the General Willamette River Greenway Permit approval criteria in EC 9.8815, approval, approval with conditions, or denial of a Willamette River Greenway Permit that proposes or includes housing shall be based solely on compliance with the following approval criteria:

(1) Greenway Setback.

(a) The application shall include a site plan that clearly depicts the location of the Willamette River Greenway Setback on the subject property, as shown on the Willamette River Greenway Setback Map referenced at EC 9.8811(3).

(b) Consistent with the requirements of EC 9.8811(4), the application shall not propose any new structures located within the Willamette River Greenway Setback except pedestrian paths or public accessways proposed or otherwise required pursuant to EC 9.8812(4).

(2) Building Facade. For any new buildings, the maximum length of any building façade located within 100 feet of the Willamette River Greenway Setback is 75 feet.

(3) Landscaping.

(a) A landscape area that meets the requirements of EC 9.6210 Low Screen Landscape Standard (L-2) shall be provided along the length of the Willamette River Greenway Setback. The landscape area shall be located on the opposite side of the Willamette River Greenway Setback from the river and shall be a minimum depth of 10 feet. These requirements are not adjustable under the provisions of EC 9.6210(2)(b) or EC 9.8030(3)(c).

(b) Solid or Masonry walls are not permitted within the Willamette River Greenway Setback, or within the landscape area required by subparagraph (a).

(c) Fences are not permitted within the Willamette River Greenway Setback. Fences located within Willamette River Greenway Boundary and within 300 feet of the Willamette River Greenway Setback may not be constructed of barbed wire, chain link fencing, or cyclone fencing and must be at least 50 percent open (unobstructed to both light and air) to allow views through the fence.

(d) The landscape area required by subparagraph (a) must be planted exclusively with native plants included on the City’s adopted list of plant species for sites at or below 500 feet in elevation, attached as Exhibit F to Ordinance No. 20351

(4) Access.

(a) The following standards apply to any proposed housing that will result in 5 or more dwelling units on one development site:

1. Where the development site abuts publicly owned land, on-site pedestrian paths shall be provided from the property line nearest to the Willamette River to main building entrances. Where required, these on-site pedestrian paths shall be a minimum of 3 feet wide, and be constructed of concrete, asphalt, or any pervious surface that complies with the Americans with Disabilities Act, unless adjusted in accordance with EC 9.8030(22).

2. Where the development site is identified in Exhibit C-1 to Ordinance No. 20693 as being more than 500 feet from a public access point, and provided the City can make findings to demonstrate consistency with constitutional requirements, the City will require the dedication and improvement of a public accessway to existing public ways that provide a connection to or along the Willamette River. The public accessway shall be a minimum 10 feet in width, constructed in accordance with public improvement standards.

(5) Tree Preservation. Tree preservation is required in accordance with the provisions of EC 9.6885(2), Tree Preservation and Removal Standards.

(Added by Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8815 Willamette River Greenway Permit Approval Criteria – General.

Approval, approval with conditions, or denial of a Willamette River Greenway Permit not otherwise processed according to the provisions of EC 9.8812, shall be based on compliance with the following approval criteria:

(1) To the greatest possible degree, the intensification, change of use, or development will provide the maximum possible landscaped area, open space, or vegetation between the activity and the river.

(2) To the greatest possible degree, necessary and adequate public access will be provided to and along the Willamette River by appropriate legal means.

(3) The intensification, change of use, or development will conform with applicable Willamette River Greenway policies as set forth in the Metro Plan.

(4) In areas subject to the Willakenzie Area Plan, the intensification, change of use, or development will conform with that plan’s use management standards.

(5) In areas not covered by subsection (4) of this section, the intensification, change of use, or development shall conform with the following applicable standards:

(a) Establishment of adequate setback lines to keep structures separated from the Willamette River to protect, maintain, preserve, and enhance the natural, scenic, historic, and recreational qualities of the Willamette River Greenway. Setback lines need not apply to water related or water dependent uses as defined in EC 9.0500.

(b) Protection of significant fish and wildlife habitats as identified in the Metropolitan Plan Natural Assets and Constraints Working Paper. Sites subsequently determined to be significant by the Oregon Department of Fish and Wildlife shall also be protected.

(c) Protection and enhancement of the natural vegetative fringe along the Willamette River to the maximum extent practicable.

(d) Preservation of scenic qualities and viewpoints as identified in the Metropolitan Plan Natural Assets and Constraints Working Paper.

(e) Maintenance of public safety and protection of public and private property, especially from vandalism and trespass in both rural and urban areas to the maximum extent practicable.

(f) Compatibility of aggregate extraction with the purposes of the Willamette River Greenway and when economically feasible, applicable sections of state law pertaining to Reclamation of Mining Lands (ORS Chapter 517) and Removal of Material; Filling (ORS Chapter 541) designed to minimize adverse effects to water quality, fish and wildlife, vegetation, bank stabilization, stream flow, visual quality, noise, safety, and to guarantee necessary reclamation.

(g) Compatibility with recreational lands currently devoted to metropolitan recreational needs, used for parks or open space and owned and controlled by a general purpose government and regulation of such lands so that their use will not interfere with adjacent uses.

(6) The proposed development is designed and sited to minimize impacts to the natural environment by addressing the following:

(a) Tree Preservation. Significant trees are preserved to the greatest possible degree, with trees having the following characteristics given the highest priority for preservation:

1. Healthy trees that have a reasonable chance of survival considering the base zone or special area zone designation and other applicable approval criteria;

2. Trees located within vegetated corridors and stands rather than individual isolated trees subject to windthrow;

3. Trees that fulfill a screening function, provide relief from glare, or shade expansive areas of pavement;

4. Trees that provide a buffer between potentially incompatible land uses;

5. Trees located along the perimeter of the lot(s) and within building setback areas;

6. Trees and stands of trees located along or within view from the river;

7. Trees with significant habitat value;

8. Trees adjacent to public parks, open space and streets;

9. Trees located along a water feature; and,

10. Heritage trees.

(b) Restoration or Replacement. The proposal mitigates, to the greatest possible degree, the loss of significant trees and vegetation through restoration or replacement, as follows:

1. Planting of replacement trees along stream corridors, or within common areas; or,

2. Restoration of fish and wildlife habitat, native plant habitat, wetland areas, and riparian vegetation.

(7) As used in this section, the words "the greatest possible degree" are drawn from Oregon Statewide Planning Goal 15 (F.3.b.) and are intended to require a balancing of factors so that each of the identified Willamette River Greenway criteria is met to the greatest extent possible without precluding the requested use.

(8) When site review approval is required, the proposed development will be consistent with the applicable site review criteria.

(9) The proposal complies with all other applicable development standards for features explicitly included in the application. An approved adjustment to a standard pursuant to provisions beginning at EC 9.8015 of this land use code constitutes compliance with the standard.

(Section 9.8815, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8825 Modifications to a Willamette River Greenway Permit.

After the effective date of Willamette River Greenway Permit approval, modifications of the Willamette River Greenway Permit, as provided in EC 9.7230 and EC 9.7340, may be considered in accordance with the Type II Application Procedures contained in EC 9.7200 through EC 9.7230. The planning director shall decide whether to grant the requested modification based on the following criteria:

(1) The modification will be consistent with the conditions of the original approval; and

(2) The modification will result in insignificant changes in the physical appearance of the development, the use of the site, and impact on the surrounding properties.

If determined to be consistent with the above criteria, the planning director shall approve the request. The applicant retains the ability to submit the requested modification as a new Willamette River Greenway permit application based on the Type III procedural requirements. Nothing in this land use code shall preclude the applicant from initially submitting the requested modification as a new Willamette River Greenway permit application.

(Section 9.8825, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; Ordinance No. 20693, enacted July 12, 2023, effective August 18, 2023.)

9.8850 Purpose of Zone Changes.

As the comprehensive plan is implemented over the years, there will be a need for changes in zoning. As the comprehensive plan is reviewed and periodically revised, other zone changes may be warranted.

(Section 9.8850, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017.)

9.8855 Applicability.

Changes in zoning, including the application of or change of an overlay zone or special area zone shall be processed as a Type III application as provided in EC 9.7300 through EC 9.7340 Type III Application Procedures, with the following exceptions:

(1) The proposed zone change would apply the /ND Nodal Development Overlay Zone, in which case the zone change shall be processed as described in EC 9.4260.

(2) The proposed zone change involves an annexation request that qualifies for an automatic change in zoning, as provided in EC 9.7810 Changes in Zoning.

(3) The proposed zone change involves a concurrent amendment to a refinement plan, the Envision Eugene Comprehensive Plan or the adoption of a new refinement plan, in which case the zone change shall be processed as a Type IV or Type V application as provided in EC 9.7400 through EC 9.7455 Type IV Application Procedures and EC 9.7500 through 9.7560 Type V Application Procedures.

(4) The proposed zone change involves a concurrent amendment of the Metro Plan, in which case the zone change shall be processed consistent with the Metro Plan Amendment Procedures as provided in EC 9.7700 through 9.7730.

(5) The proposed zone change is processed concurrently with an amendment to this land use code; in which case, the zone change shall be processed as a Type IV or Type V application as provided for in EC 9.7400 through EC 9.7455 Type IV Application Procedures and EC 9.7500 through EC 9.7560 Type V Application Procedures.

(6) The proposed zone change is to remove the /WR Water Resources Conservation Overlay Zone, in which case the zone change shall be processed as described in EC 9.4960.

(7) The proposed zone change is to remove the /WQ Water Quality Overlay Zone, in which case the zone change shall be processed as described in EC 9.4786.

(Section 9.8855, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02. Amended by Ordinance No. 20269, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20557, enacted July 27, 2015, effective August 30, 2015; and Ordinance No. 20569, enacted November 14, 2016, effective December 17, 2016; amended by Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; administratively corrected on March 22, 2018.)

9.8860 General Requirements.

(1) Concurrent Review. Zone change applications may be reviewed concurrently with certain other land use applications, but only as provided in EC 9.8005 Applicability and Effect of Application Requirements, Criteria, and Concurrent Review and in EC 9.8855 Applicability.

(2) Overlay Zones. EC 9.1040 Establishment and List of Overlay Zones establishes overlay zones that supplement the base zone regulations. Changes in zoning can include the designation of an overlay zone in addition to the base zone. While some of these overlay zones have been applied to a specific geographic area through a land use code amendment, other overlay zones are applied on a case by case basis. In these cases, the overlay zone can be applied in response to adopted plan policies or where the use of the overlay zone is necessary to address future development considerations.

(Section 9.8860, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02.)

9.8865 Zone Change Approval Criteria.

Approval of a zone change application, including the designation of an overlay zone, shall not be approved unless it meets all of the following criteria:

(1) The proposed change is consistent with applicable provisions of the Metro Plan. The written text of the Metro Plan shall take precedence over the Metro Plan diagram where apparent conflicts or inconsistencies exist.

(2) The proposed zone change is consistent with applicable adopted refinement plans. In the event of inconsistencies between these plans and the Metro Plan, the Metro Plan controls.

(3) The uses and density that will be allowed by the proposed zoning in the location of the proposed change can be served through the orderly extension of key urban facilities and services.

(4) The proposed zone change is consistent with the applicable siting requirements set out for the specific zone in:

(a) EC 9.2150 Commercial Zone Siting Requirements.

(b) EC 9.2430 Employment and Industrial Zone Siting Requirements.

(c) EC 9.2510 Natural Resource Zone Siting Requirements.

(d) EC 9.2610 Park, Recreation, and Open Space Siting Requirements.

(e) EC 9.2681 Public Land Zone Siting Requirements.

(f) EC 9.3055 S-C Chambers Special Area Zone Siting Requirements.

(g) EC 9.3105 S-CN Chase Node Special Area Zone Siting Requirements.

(h) EC 9.3140 S-DR Downtown Riverfront Special Area Zone Siting Requirements.

(i) EC 9.3205 S-DW Downtown Westside Special Area Zone Siting Requirements.

(j) EC 9.3305 S-E Elmira Road Special Area Zone Siting Requirements.

(k) EC 9.3605 S-JW Jefferson Westside Special Area Zone Siting Requirements.

(l) EC 9.3705 S-RP Riverfront Park Special Area Zone Siting Requirements.

(m) EC 9.3805 S-RN Royal Node Special Area Zone Siting Requirements.

(n) EC 9.3905 S-W Whiteaker Special Area Zone Siting Requirements.

(o) EC 9.3955 S-WS Walnut Station Special Area Zone Siting Requirements.

(p) EC 9.4160 /CL Clear Lake Overlay Zone Siting Requirements.

(q) EC 9.4205 /EC East Campus Overlay Zone Siting Requirements.

(r) EC 9.4715 /WP Waterside Protection Overlay Zone Siting Requirements.

(s) EC 9.4776 /WQ Water Quality Overlay Zone Siting Requirements (only for the purposes of adding the overlay zone. See EC 9.4786.).

(t) EC 9.4915 /WR Water Resources Conservation Overlay Zone Siting Requirements (only for the purposes of adding the overlay zone. See EC 9.4960.).

(u) EC 9.4815 /WB Wetland Buffer Overlay Zone Siting Requirements.

(v) An uncodified ordinance establishing a site specific S-H Historic Special Area Zone, a copy of which is maintained at the city’s planning and development department.

(5) In cases where the NR zone is applied based on EC 9.2510(1)(b), the property owner shall enter into a contractual arrangement with the city to ensure the area is maintained as a natural resource area for a minimum of 50 years.

(Section 9.8865, see chart at front of Chapter 9 for legislative history from 2/26/01 through 6/1/02; amended by Ordinance No. 20267, enacted November 12, 2002, effective March 3, 2003; Ordinance No. 20271, enacted November 25, 2002, effective December 25, 2002; Ordinance No. 20275, enacted January 13, 2003, effective February 12, 2003; administratively corrected June 5, 2003; amended by Ordinance No. 20312, enacted March 8, 2004, effective April 7, 2004; Ordinance No. 20330, enacted December 2, 2004, effective January 1, 2005; administratively corrected March 10, 2005; amended by Ordinance No. 20351, enacted November 14, 2005, effective January 1, 2006; Ordinance No. 20355, enacted December 12, 2005, effective January 13, 2006; Ordinance 20430, enacted March 9, 2009, effective June 10, 2009; Ordinance No. 20449, enacted December 14, 2009, effective January 16, 2010; Ordinance No. 20460, enacted July 12, 2010, effective August 14, 2010; Ordinance No. 20513, enacted July 8, 2013, effective August 9, 2013; Ordinance No. 20528, enacted May 14, 2014, effective June 23, 2014; Ordinance No. 20584, enacted July 17, 2017, effective August 24, 2017; Ordinance No. 20667, enacted May 24, 2022, effective June 25, 2022, remanded on October 12, 2023, and provisions administratively removed; Ordinance No. 20705, enacted March 11, 2024, effective March 12, 2024, remanded on July 10, 2024, and provisions administratively removed; Ordinance No. 20716, enacted November 25, 2024, effective January 2, 2025.)