HomeMy WebLinkAboutOrdinance No. 20056ORDINANCE No , 20056
AN ORDINANCE CONCERNING LOCAL STREETS AND PUBLIC
IMPROVEMENTS ; AMENDING SECTIONS 6.300 , 6.305, 7.010 ,
7.085 , 7.140 , 7.290 , 7.640 , 7.650 , 9.015 , 9.030 , 9.033 ,
9.035 , 9.040 , 9.045 , 9.050 , 9.055 , 9.060 , 9.075 , 9 , 085 ,
9.510, 9.512, 9.386, 9.574, 9.68$, AND 9.702 OF THE
EUGENE CODE, 1971 ~ AND ADDING A NEw SECTION 7.280 TO
THAT CODE,
THE CITY OF EUGENE DOES ORDAIN AS FOLLOWS
~r ~. Section 6,300 of the Eugene Code, 1971, is ar~ended by adding
definitions for "Neri tage tree" and "Street tree" i n alphabetical order therein,
to provide:
6.300 ~.f ~ i i n . As used i n section 6.305 to 6.330 of this Code, the
follo~ing definitions apply:
Hari tr Any tree of exceptional value to our community
based on its size ~ rel ati ve to speci es ~ , history, 1 ocati on , or
species , or any combination of these criteria . The speci fi c
methodology for c1 assi fyi ng a tree as a heri Cage tree sha11 be
estab1 i shed by administrative rule of the city manager adopted
pursuant to section Z.D19 of this code.
r ~ r A 1 i vi ng , standing woody plant typi ca 11 y having
a single trunk at 1 east 1-112 inch i n diameter at a poi nt six inches
above mean ground 1 evel at the base of the trunk, that i s 1 ocated
within the street right-of-way,
i Section 6.305 of the Eugene Code, 1971, is amended by adding
new Subsections (3) and (4) thereto, to provide:
6.305 Tree Fel 1 i nq,.,,PrQhi bi ti on ,
..
~ 1 ~ Except as provided i n section 6.33D , no person may fel 1 more
than five trees wi thi n a peri od of 1Z consecutive months from a parcel of private
Ordinance - 1
property consisting of 20,000 or more square feet of area without a permit.
(Z) Except as provided in section 6.330, no person may fell one or
more trees from a parcel of private property consisting of 1 ess than 20 , 000
square feet of area without a permit.
(3) Notwithstanding subsections (1) and (2) of this section and
section 6.330(b) of this code, no person shall remove a street tree without first
obtaining a permit from the city manager specifically authorizing the removal of
a street tree. Permit approval may be conditioned upon replacement of the street
tree with another tree pre-approved by the city, or a requirement to pay to the
city an amount sufficient to fund the planting and establishment by the city of
a tree of similar value. The value of the existing street tree to be removed
shall be calculated using the methods set forth in the edition then in effect of
the Guide for Plant Appraisal published by the International Society of
Arboriculture Council of Tree Landscape Appraisers.
(4) Notwithstanding subsections (1) and (2) of this section and
section 6.330(b) of this code, no person shall fell a heritage tree from within
the public right-of-way except where such removal, and authorization for its
removal, has been granted by the city because its removal is necessary to protect
the public health, safety, or welfare.
Section 7.010 of the Eugene Code, 1971, i s amended by amending
the definition of "Storm sewer" set forth therein , and adding new definitions of
"Block length, " "Heritage tree, " and "Street tree" in alphabetical order therein,
to provide ;
7.010 D ~ For purposes of this chapter, the fol 1 owi ng words and
phrases shal 1 have the meanings ascribed to them by this section
Bl k 1 en h . The distance a 1 ong a street between the
centerline of two intersecting through streets , including "T"
intersections but excluding cul -de-sacs .
r Any tree of exceptional vat ue to our community
based on its size C ref ati ve to species } , history, 1 ocati on , or
species , or any combination of these criteria . The speci f i c
methodology for classifying a tree as a heritage tree shall be
established by administrative rut e of the city manager adopted
pursuant to section Z.Ol9 of this code.
ordinance - Z
Stormwater sewer. A sewer or open channel which carries
stormwater into which wastewater is not intentionally admitted.
r rte. A 1 i vi ng, standing woody plant typi ca11y having
a si ng1 e trunk at 1 east 1-112 inch i n diameter at a poi nt six inches
above mean ground 1 evel at the base of the trunk , that i s 1 ocated
within the street right-of-way.
~, Secti an 7.485 of the Eugene Code, 1971 i s amended to pravi de:
7.085 i f' i n D i n
~ 1 } The city engineer shal 1 prepare design standards and standard
specifications for construction , reconstruction or repai r of public improvements
to be constructed within areas under the city's jurisdiction to be kept on f i 1 e
i n the city engineer's office .
~ 2 ~ Al 1 public improvements sha 11 be cans i stmt with sound
engineering principles and constructed i n accordance with design standards and
standard specifications and plans adopted by the city.
~3) All engineering and inspections on public improvements to be
accepted by the city for maintenance shat 1 be done by the city unless otherwise
specified by this code.
' Section 7,144 of the Eugene Code, 1971 i s amended to provide:
7.14D i n f li zm r v - r P1
Pet_ti over' ~ ,,,,E~,a~ Weer , A peti ti oner may, at petitioner's expense,
empl oy a 1 i censed engineer to prepare the plans for a publ i c improvement . The
original plan based on drafting and design standards set by the city engineer
sha11 be delivered to the city engineer for review and approval before
construction may begin . No prints or transparencies shall be accepted and the
plans submitted shat 1 be retained by the city. The cost of public improvements
constructed under this section are not eligible for financing as 1 ocal
improvement assessments under sections 7.175 to 7.200 .
Anew Section 7.280 is added to the Eugene Code, 1971, to
provide ;
7.280 Street Tree Program -Policy. Standards. Proced~~re.
(1) PolicX. In order to create attractive and healthy neighborhood
environments, no approval shall be granted for a development that involves the
Ordinance - 3
creation of a street unless the applicant has submitted and received approval of
a street tree plan that ensures street trees wi 11 be planted and established i n
accordance with the standards and procedures provided far i n this section and the
adopted policies of the Urban Forest Management Plan. Street trees shall be
planted i n accordance with the approved street tree plan as each 1 of or area i s
developed, and shat 1 be required on streets that abut the development as wel 1 as
on new streets within the level opment site .
~2~ ~n~. The city manager, or designee, shal 1 by
administrative rules adopted pursuant to section 2.019 of this code establish
standards and specifications that ensure that new trees p1 anted are of the
highest quality, require 1 ow maintenance, and do not interfere with publ i c
safety. The standards sha11 include, but not be limited to, the type of trees
that may be planted, and requirements for planting and establishment of the
trees . As used i n this section, "establishment" includes watering, initial
pruning, and replacement of trees, if necessary, for a period of three years from
the date of planting ,
~3} P~~, Upon approval of the street tree plan, and prior
to approval of the final plat for subdivisions, planned unit developments,
partitions , or approved development plans , the applicant shall;
~ a } Pay to the ci ty a fee established by the city manager
pursuant to section 2. D20 of this code that i s equal to the cost of
the purchase, instal 1 ati on and establishment of the street trees
required by the approved street tree plan . Thereafter, the city
shal 1 assume responsi bi 1 i ty for the purchase, i nsta1 l ati on and
establishment of the street trees ; or
~b~ Purchase, instal 1 and establish the street trees i n
accordance with the approved street tree plan, upon ~ i ~ first paying
to the ci ty a fee established by the city manager pursuant to
section 2 , 020 of this code to reimburse the city far its costs i n
connection with plan review, inspection , administration and
monitoring , and t i i 7 f i 1 i ng with the ci ty a securi ty band or depos i t
i n an amount determined by the city to be sufficient to ensure
performance under the approved street tree plan ,
Existing 1 arge-scale street trees on or adjacent to a level opment site shal 1 be
retained un1 ess approved for removal by the city pursuant to section 6.300 to
6, 330 of this code during site development or i n conjunction wi th a street
construction project. Any street tree removed by permit through demolition or
construction within the street right-of-way shall be replaced within the street
right-af -way at a 1 ocati on approved by the city wi th a tree of si mi 1 ar value .
The value of the existing street tree to be removed shal 1 be calculated using the
methods set forth i n the edition then i n effect of the Guide for Plant Appraisal
published by the ~nternati oral Society of Arboriculture Counci 1 of Tree Landscape
Appraisers . The developer shall be responsi b1 e for the cost of the planting ,
Ordinance - 4
maintenance and establishment of the reel acement tree ,
' 7 . Subsection t3} of Section 7. Z90 of the Eugene Code, 1971 i s
amended, Subsection (4) thereof is repealed, and Subsection (5> is renumbered
(4), all to provide:
7.290 Construction and Use of Public Way - Permit Required: Standard
Specifications.
~3} Work affecti ng a .public way shal 1 be performed i n accordance
with this code, the standard specifications and design standards adopted pursuant
to section 7.085 , sound engineering and design practices and such other
reasonab1 e condi ti ons required by the city engineer to protect the public health ,
safety and welfare.
~4} If an applicant for a permi t or the contractor performing the
work for the applicant i s
~ a } Delinquent i n performing the obligations required by
sections 7.290 to 7.308 on permits previously issued , the city
engineer may refuse to i ssue a new permit far other work affecting
a public way unti 1 the delinquency is corrected; and
fib} Has historically been delinquent i n performing the
obligations required by sections 7,290 to 7.308, the city engineer
may requi re a bond or other reasonable security be posted with the
city against which the city may col 1 ect its cost of enforcing thi s
code and the conditions of any permit issued thereunder against the
permi ttee ,
Section 7.640 of the Eugene Code, 1971, i s amended to provide:
7.640 1 i - r i n Tr Pr hi No person shal 1 plant, or cause
to be p1 anted within the city, any species of tree within the
right-of-way of a street, avenue, highway or alley, pedestrian right-of-way or
pedestrian easement which i s not 1 i steel i n the street tree speci eslvari ety 1 i st
adopted by the city manager pursuant to section 2.019 of this code, unless
planting of the proposed species i s speci fi cal 1y authorized i n writing by the
city manager or the manager's designee,
i Section 7.650 of the Eugene Code, 1971, i s amended to provide:
Ordinance - 5
7.65D Fal i aae, - Tri mm nq~, Pr~.ni ng o~~r,,, Remov~,~ .
~ 1 } Subject to the provisions of this secti an , al 1 trees , shrubs ,
plants and vegetation growing within or projecting into the right-of-way of a
street, avenue, highway, alley, pedestrian right-of-way or pedestrian easement ,
may be trimmed, pruned or removed at any ti rye by the city, or the city may
require the person responsible to abate any existing nuisance under chapter 6 of
this code.
~ 2 } Except as provided i n subsection ~3 } of this section , no person
shall tri m or prune a tree growing within the public right of way i n a manner not
i n compliance with the standards adopted by the city manager . The city manager
shall adopt such standards as part of rules promulgated in accordance with
section 2.019 of this code. The standards shat 1 be designed to ensure that trees
are not trimmed ar pruned i n a manner that causes damage to the tree or
diminishes its health.
~3} The prohibitions set forth in subsection ~2} of this section
do not apply to EWEB when the trimming or pruning i s necessary i n order to
protect its 1 i nes or crews .
The definition of "Block 1 ength" set forth i n Section 9.015
of the Eugene Code, 1971 i s amended to provide:
9.015 i i ' n . As used i n this chapter, unless the context requires
otherwise, the fo11 owi ng words and phrases mean
B,1Qc~~th. The distance along a street between the
centerline of two intersecting through streets , including "T"
intersections but excluding cul -de-sacs .
section 11. Subsections (1), (4)(b)1., (4)(b)2., (4)(b)4., and (4)(b)5.,
of Section 9.030 of the Eugene Code , 1971, are amended to provide
9.030 i n r n M' r P rti ti n T n ' v Pl n Pr r,
~1} TntivMinrnM'rPriinPl -A 1' An
app1 i cati on and ref ated information prescribed by the city as required for minor
and major partition tentative plan approval shal 1 be submitted for al 1 contiguous
property under the same ownership by the person proposing the tentative plan,
together wi th a fee set by the city manager as pravi ded by section 2.020 of thi s
code .
ordinance - 6
~4} T n ' v r n M P P - Pl
' llnl ess the applicant agrees to a 1 onger time period , the planning
director shal 1 approve, conditionally approve, or deny a tentati ve partition plan
application with findings and conclusions thereon , within 30 days of receipt of
a complete and accurate application . The planning director's decision sha11 be
based on the fiol 1 owi ng criteria
tb~ In the case of a ma jor
1. Approval does not
safe and healthful development
thereto ;
2. The proposed
applicable adopted plans .
4. Streets and roads ar
for the extension of streets
properties and provide for ev
existing public street system as
street connectivity standards of
The planning director shall perr
only upon finding that the level
public street is not necessary f
and the street connectivity stan
5. The nronosed ma.ior
~laidoutsoastoprovide
to adjoining undeveloped
~ntual connection with the
~peci f i ca 11 y required by the
section 9.045 of this code.
i t private streets or roads
per has demonstrated that a
~r compliance with this code
yards of section 9.045.
oa rt i t i on i s laid out to
provide safe, convenient, and direct bi cyc~ e and pedestrian
access to and from nearby and adjacent residential areas ,
transit stops , neighborhood activity centers , commercial
areas , and industrial areas , and to provide safe, convenient
and direct transit circulation . At a mi ni mum, "nearby" i s
interpreted to mean uses within 114 mi 1 e which can reasonabl y
be expected to be used by pedestrians , and uses within one to
two mi 1 es which can be reasonably expected to be used by
bicyclists.
Section 12. Subsections (1) and (4) of Section 9.035 of the Eugene Code,
1971, are amended to provide:
9.035 Subdivision Tentative Plan Procedure.
(1) Tentative Subdivision Plan - Annlication. An application and
related information prescribed by the city as required for subdivision tentative
plan approval shall be submitted for all contiguous property under the same
partition, that:
impede or adversely affect the
of any ad jai ni ng 1 and or access
partition wi 11 be consistent with
Ordinance - 7
ownership by the person proposing the tentative plan, together wi th a fee set by
the city manager as provided by section ~ . 0~0 of this code .
~4~ 'v i vi i Pl n- P n~ ' r i i
Unless the applicant agrees to a 1 anger time period , the p1 anni ng director sha 11
approve , conditionally approve, or deny a tentati ve plan application with
findings and conclusions thereon , within 30 days of receipt of a compl ete and
accurate application . The planning director's action shall be based on the ful 1
level apment , including the comp1 ete street network and a 11 street connecti ans .
Phasing of portions of the development may occur as part of a fi nal subdivision
approval . The phasing sha11 progress i n a sequence that promotes street
connectivity between the various phases of the level opment . The planning
director's decision shall be based on the following criteria
~a) The proposed subdivision wi 11 comply with al 1 applicable
platting standards of this chapter .
fib} Approval does not impede or adversely affect the safe
and healthful development of any adjoining land or access thereto.
~c} The proposed subdivision wi 1 l be consistent with
applicable adopted plans .
~d7 The proposed subdivision wi 11 not cause unreasanabl e
street congestion, risk of fire, flood, geological hazards,
pal 1 uti an, or si mi 1 ar dangers , hamper adequate provision far
transportati an, water supply, sewage disposal , drainage, education,
recreation , and other public services and foci 1 i ti es , or resu1 t i n
inadequate 1 i ght and air or overcrowding of 1 and.
~e7 Streets and roads are 1 ai d aut so as to provide for the
extension of public streets to adjoining undeveloped properties and
provide for eventual connection with the existing public street
system as specifically required by the street connectivity standards
of section 9.045. The planning director shall permit private
streets and alleys only if the developer can demonstrate that a
public street or alley i s not necessary for compliance with thi s
code, including the street connectivity standards of section 9.045.
~ f 7 The proposed subdivision i s laid out to provide safe,
convenient , and direct bicycle and pedestrian access to and from
nearby and adjacent residential areas , transit stops , nei ghborhoad
activity centers , commercial areas , and industrial areas , and to
provide safe, convenient and direct transit circulation . At a
minimum, "nearby" i s interpreted to mean uses within 114 mi 1 e which
can reasonably be expected to be used by pedestrians, and uses
within one to two mi 1 es which can reasonably be expected to be used
by bicyclists.
~g 7 The street 1 ayout of the proposed subdivision shat 1
Ordinance - 8
disperse motor traffic onto more than one pub1 i c 1 ocal street when
l . The subdivision exceeds 19 1 ots ; or
~. The sum of proposed subdi vi si an 1 ots and the
existing 1 ots uti 1 i zi ng a publ i c 1 oca1 street would exceed 19
lots,
and that public 1 oval street i s the single means of ingress and
egress ; unless the planning director determines i t i s not feasi bl e
due to physical constraints , such as topography, the previous 1 ayout
of the surrounding area , or similar constraints .
th} If the application of subparagraphs fie} and fig} to a
development proposal results in a conflict, the more restrictive
provision shal 1 control .
Section 13. Subsection (3)(a)1. of Section 9.040 of the Eugene Code, 1971
i s amended to provide:
9.040 Subdivision Pl at~~„~„P,r~cedure.
~3} ~ v' i P - ' i .
~ a } Unless the applicant agrees to a 1 onger time period , the
planning director shal 1 approve, conditionally approve, or deny a
subdivision p1 at within 30 days of receipt of a compl ete and
accurate application , with findings and conclusions thereon .
Phasing of portions of the development may occur as part of the
final subdivision approval . The phasing shal 1 progress i n a
sequence that promotes street connectivity between the various
phases of the development . The planning director's decision shal 1
be based on the fall owi ng criteria
1. The plat i s i n substantial conformity with the
provisions of the tentative plan for the subdivision as
approved, except for minor modifications which the applicant
has made to the tentative plan which are consistent with city
engineer approval of public improvements , and requirements for
street connectivity, and do not i nvol ve a ma jar adjustment
~ reconfi gurati on of the street system} which would require
modification of tentative approval or resubmi tta1 of the
tentative plan ,
Section 14. Subsections (2)(a). (2>(b)3.b., (2)(d), and (7) of Section
Drdinance - 9
9.045 of the Eugene Code, 1971, are amended, a new Subsection ~4} is added
thereto, Subsections (5) and (9> thereof are repealed, and current Subsections
(4) and (10) renumbered (5) and (9) respectively, all to provide:
9.045 Pl atti na Standar,ds.~,.,,- Stree ~~„~,.,,~,.~~,n Roads .
(2) Street Width.
(a) Street right-of-way mad. Pursuant to Ordinance No.
19922, the Council has adopted the Street Right-of-Way Map
designating the widths of street right-of-way and street paving for
specific street segments. Any street segment for which no widths
are designated on this map shall have the maximum widths for its
classification as set forth in subparagraph (b)3.b. of this section.
Hereafter the Street Right-of-Way Map may be amended or modified as
provided in paragraph (2>(b) hereof.
(b) Procedures to amend right-of-way mad. Widths for
proposed new streets or specific street segments as shown on the
Street Right-of-Way Map may be determined, amended or modified using
any one of the following procedures:
3. When entering an order concerning the Street
Right-of-Way Map under subparagraph ~b}z above the fol 1 owi ng
criteria shat 1 be considered:
b . The fol 1 owi ng genera 1 determination of
widths by type of street
Right-of-way Paving
Tvae of Street _Width Width* _
Major Arteri a 1 s .......... .
Minor Arterials .......... .
Col lectors:
Commerci a 1, i ndust ri a 1
andlor multi -family
res i dent i a 1 ........ .
Single family residential . ,
Local Streets
Commercial and industrial ....... .
Residential ..................... .
80' - l20' 46' - 90'
70' - lOD' 46' - 70'
60' - 80' 36' - 46'
60' 2S' - 36'
40' - 60' 20' - 34'
55' - 70' 30' - 44'
40' - 60' ~0' - 34'
* Measured from face to face of curbs.
Ordinance - 10
~d} n r ti n r All streets shall be con-
structed i n accordance with adopted counce 1 policy and i n accordance
with specifications adopted pursuant to section 7.085 .
~4} r nn i vi n r f r 1 i n i ,
~ a } Per ose and,,,, Intent . The street connectivity standards
of paragraph fib} of this subsection are established to ensure that
1. Streets are designed to efficiently and safely
accommodate emergency fire and medical service vehicles;
2 . The 1 ayout of a 1 ocal street system does not
create excessive travel 1 engths ;
3. The function of a l acal street i s readily apparent
to the user through its appearance and design i n order to
reduce nan -1 aca 1 traffic on 1 aca 1 res i dent i a 1 streets ;
4. Local streets are interconnected to reduce travel
distance , promote the use of a 1 ternati ve mades , provide for
efficient provision of uti 1 i ty and emergency services , and
provide for more even dispersal of traffic;
5 . New streets are designed to meet the needs of
pedestrians and cyclists and encaurage wa1 ki ng and bicycling
as transportation modes ;
6 . The 1 ocal street circulation pattern provides
connections to and fram activity centers such as schools ,
commerce a1 areas , parks , employment centers , and other ma jar
attractors ;
7. Local street design i s responsive to topography
and other natura 1 features and avoids or minimizes impacts to
water.. rel ated resources and wildlife corridors ;
8. Local ci rcu1 ate on systems and 1 and development
patterns do not detract from the efficiency of adjacent
co11 actor or arterial streets which are designed to
accommodate heavy traffic;
9 . Streets identified as future transit routes shoul d
be designed to safely and efficiently accommodate transi t
vehicles , thus encaurage ng the use of public transit as a
transportation mode; and
10. Where appropriate, the street system and its
infrastructure should be uti 1 i zed as an oppartuni ty to convey
and treat stormwater runoff.
tb} Street ~onnecte„v,t~Y.,, standards .
1. Public right-of-way connections shat 1 be made i n
the direction of an existing or p1 armed arteri al Icol 1 actor
street , schaa1, park , employment center , commerce a 1 area , or
s i mi 1 a r neighborhood activity center . The connecti on ~ s } can
Drdinance - 1~
be completed over time in phases as part of a required overall
street plan . Secondary access for emergency fire and medical
vehicles i s required .
2. A publ i c street connecti an shall be provided to
any existing or approved pub1 i c street or right-of-way stub
abutting the development , unless i t i s demonstrated that a
connection cannot be made because of the existence of one or
more of the fol 1 owi ng conditions :
a. Physical conditions that preclude
development of a publ i c street . Such conditions may
include, but are not 1 i mi ted to, topography or the
existence of natural resaurce areas such as wetlands,
ponds , streams , channels , rivers , 1 akes or upland
wi 1 dl i fe habitat area , or a resource on the National
Wetland Inventory or under protection by state or
federal law; or
b . Bui 1 di ngs or other existing level opment on
adjacent 1 ands , including previously subdivided but
vacant 1 ots or parcels , physically precl ude a connecti on
now or i n the future, considering the potenti a1 for
redevelopment.
3. Public right-of-way shal 1 be extended to adjacent
undeveloped or pa rti a 11 y developed contiguous 1 and ~ i . e . , 1 and
that can be further divided by provisions of this code} i n
locations which will not prevent the adjoining property from
level opi ng consistent with applicable standards , un1 ess i t i s
demonstrated that a connecti on cannot be made because of one
ar more of the fol 1 owi ng conditions
a. Physical conditions that preclude
development of a publ i c street . Such conditions may
include, but are not 1 i mi ted to, topography or the
existence of natural resaurce areas such as wetlands ,
ponds , streams , channels , rivers , 1 akes or upland
wi 1 dl i fe habitat area , ar a resaurce on the National
Wetland Inventory or under protection by state or
federal law, or
b , Bui 1 di ngs or other existing level opment on
adjacent 1 ands , including previously subdivided but
vacant 1 ots or parcels , physi ca 11 y precl ude a connecti on
now or i n the future, considering the potential for
redevelopment.
4 . Street a 1 i gnments sha 11 be selected that relate to
the natural topography and other natural conditions , minimizes
Ordinance - 1~
impacts to grading and impervious surfaces , and avoids andlor
minimizes natural resource sites and water-related features .
5 . As an a1 ternati ve to compliance with the standards
of subparagraphs 1 to 4 of this paragraph ~4} fib} , the
applicant may, at his or her expense, provide to the city a
1 ocal street connecti an study that demonstrates how the
proposed street system meets the intent of street connectivity
provi si ans of this code as expressed i n paragraph ~4} ~a }
above, and how adjoining undeveloped or parti a11y deve1 aped
properties can be adequately served by alternative street
1 ayouts . Approval of the street connection study by the
planning director and public works director shal 1 constitute
compliance with this provision.
6 . Pri vote streets and al 1 eys are prohibited un1 ess
the developer can demonstrate, to the sati sfacti an of the
city, that a public street or alley is not necessary far
compliance with this code and the above street connectivity
standards.
~5} Intersec~~,Q~,~ of Str emits..
~ a } Anal ~s . Streets shal 1 intersect one another at an angl e
as near to a ri ght angle as i s practicable considering topography of
the area and previous adjacent layout; where not so practicable, the
right-of-way and street paving within the acute angle sha11 have a
minimum of 34 feet centerline radius where such angle i s not 1 ess
than 75 degrees . ~n the case of streets intersecting at an angle of
1 ess than 6~ degrees , then such minimum radius as the p1 anni ng and
public works directors may determine .
fib} f0 f~et,~. ~ntersecti ans shal 1 be so designed that na
offset dangerous to the traveling public i s created as a resu1 t of
staggering of intersections ; and i n no case shat 1 there be an offset
of 1 ess than 1~~ feet .
(7) Cul-de-Sacs. There shall be no cul-de-sac more than 400 feet
long from the centerline of the intersecting street to the radius point of the
cul-de-sac bulb. The planning director shall require public accessways from cul-
de-sacs where necessary to provide safe, convenient, and direct circulation for
pedestrians and bicyclists.
(9) Transit Facilities.
(a) The planning director may require provisions, including
easements, for transit facilities where future transit routes are
required on streets extending through or adjacent to the area of the
subdivision, and where a need for bus stops, bus pullouts or other
ordinance - l3
transit facilities within the subdivision or partition has been
identified.
(b) Where the provision of transit stops, bus pullouts or
other facilities along a public street requires aright-of-way or
paving width greater than that listed in the table in section
9.045(2)(b) and where a need for transit service within the
subdivision or partition has been identified, the planning or public
works director may require that additional right-of-way or paving be
provided.
~ecti off. Section 9.050 of the Eugene Code, 1971, i s amended, to
provide
9.050 1 i n n r - A11 s . The planning or public works director
may require adequate and proper al 1 eys to be dedicated to the publ i c
by the land divider of such design and in such location as necessary to provide
for the access needs of the subdivision or partition i n accordance with the
purpose of section 9.020 .
i 1 . Section 9.055 of the Eugene Code, 1971, i s amended to provide:
9.055 Pl atti na Standards,,,W~,-.,.,Blocks ,
~ 17 81 ck E n h . Block 1 ength for 1 ocal residential streets shat 1
not exceed 600 feet , un1 ess the developer demonstrates to the city's satisfaction
that such a bl ock 1 ength i s not possible because of the existence of one or more
of the fol 1 owi ng conditions ;
~ a ~ Physical conditions that preclude level opment of a
public street . Such conditions may include, but are .not 1 i mi ted to,
topography or the existence of natural resource areas such as
wetlands , ponds , streams , channels , rivers , 1 akes or up1 and wi 1 dl i fe
habitat area , or a resource on the National Wetland inventory or
under protection by state or federal 1 aw;
fib} Bui 1dings or other existing development on adjacent
1 ands , including previously subdivided but vacant 1 ats or parcels ,
physically precl ude a connecti on now or i n the future, considering
the potential for redevelopment ; or
~ c 7 Where an existing public street or streets terminating
at the boundary of the development site have a bl ock 1 ength
exceeding 600 feet, or are situated such that the extension of the
street ~ s ~ into the development site would create a bl ock 1 ength
Ordinance - 14
exceeding 600 feet . ~n such cases , the block 1 ength shal 1 be as
close to 600 feet as practical .
~Z} Publ i c__Accesswavs . When necessary to provide safe, convenient
and direct access for pedestrians and bicyclists to and from nearby resi denti a1
areas , trans? t stops , neighborhood activity centers , and other commercial and
industrial areas , or where required by adopted plans , the planning director shal 1
require the 1 and divider to dedicate to the public and improve, accessways to
connect to cul -de-sacs , ar to pass through blocks . At a mi ni mum, "nearby" i s
interpreted to mean uses within 114 mi 1 e which can reasonably be expected to be
used by pedestrians , and uses within one to two mi 1 es which can reasonably be
expected to be used by bicyclists . Public accessways shal 1 conform to design
standards for accessways contained i n the City of Eugene Design Standards for
Streets , Sidewalks , Bikeways and Accessways . When necessary to pravi de street
connectivity, the public works director shal 1 require improvements to existing
unimproved public accessways on praperti es adjacent to the 1 and to be divided .
Said improvements to unimproved public accessways shal 1 connect to the closest
public street or developed accessway. Where possible, accessways may also be
employed to accommodate uses as included i n subsection ~ 3 ~ of this section .
~3~ ,Easements _ for Uti 1 i ti es . Dedication of easements for open
channels and storm water sewers , and for access thereto for maintenance, i n order
to safeguard the public against f1 oad damage and the accumulation of surface
water , and deli cat? on of easements for sanitary sewers , and for access thereto
for maintenance, and dedication of easements for other public uti 1 i ti es , may be
required of the 1 and divider at sufficient widths for their intended uses , by the
planning or public works director along lat ar parcel rear lines or side lines,
or elsewhere as necessary to provide needed foci 1 i ti es for present or future
development of the area i n accordance with the purpose of section 9.020. Before
a partition or subdivision can be .approved, there shall appear thereon a
restriction providing that. no bui 1 di ng , structure, tree, shrubbery or other
obstruction shal 1 be placed or 1 ocated on or i n a publ i c uti 1 i ty easement .
Subsection ~ f ~ 5 . and ~ f ~ 15 . of Section 9.060 of the Eugene
Code , 1971, are amended to pravi de
9.060 1 n r- L P A11 1 ots and parcels shat 1
comply with the fol 1 owi ng requirements . ~n this section "1 ots" and
"parcels" are used interchangeably. When more restrictive, ref ated provisions
in the zoning ordinance apply.
(f) Panhandle Lots. The planning director may authorize
exceptions from frontage requirements for panhandle lots, provided
ordinance - 15
that the fol 1 owi ng standards , applicable to all panhand1 e 1 ots , are
met .
Note: v i n i
f m h fllwin mini 1
5 . Minimum access paving width of the panhandle or
abutting driveway used for access sha 11 be as follows
one rear l of or parcel . 12 feet
Two or more rear 1 ots or parcels ... .. .. 20 feet*
~*To preserve existing natural features , paving width
may be reduced to 17-112 feet, except for the first 25 feet
back from the sidewalk, with the traffic engineer's approval ,
i f both sides of the driveway are 1 andscaped i n accordance
with a landscape plan. } Use of a panhandle for access shall
be permitted only i f creati on of a publ i c street , i nc1 udi ng a
future public street , i s not possi b1 e because :
a . Physical conditions preclude development of
a public street . Such conditions may include, but are
not 1 i mi ted to, topography or the existence of natural
resource areas such as wetlands , ponds , streams ,
channels , rivers , 1 akes or up1 and wi 1 d1 i fe habitat area ,
or a resource on the National Wetland Inventory or under
protection by state or federal law;
b. Buildings or other existing development on
adjacent 1 ands , i nc1 udi ng previ ous1y subdivided but
vacant 1 ots or parcels , physi ca11y precl ude a connecti on
now or i n the future, considering the potential for
redevelopment.
15. The bui 1 di ng affi ci al sha11 not i ssue a certi fi -
cate of occupancy unti 1 the pra jest i s completed i n accordance
with approval conditions and this code. It may be issued
prior to completion i f suffi ci ent funds to complete the
project are placed i n escrow wi th a bank, savings and 1 oan
association, or escrow company.
i n Section 9.075 of the Eugene Code , 1971, i s hereby repea 1 ed .
Section 19. Subsections (1), (2), and (3) of Section 9.085 of the Eugene
Code, 1971 are repealed, and Subsections (4), (5), (6), (7), (8), and (9) are
ordinance - l6
renumbered (1), (2>, (3), (4>, (5), and (6> respectively, and amended to provide:
9.085 Improvements - Specifications.
(1) Improvements -Water Su~~IX. All lots and parcels within
subdivisions and partitions shall be served by the water system of the Eugene
Water & Electric Board.
(2) Improvements - Sewage. All lots and parcels within sub-
divisions and partitions shall, where practicable, as determined by the planning
and public works directors, in accordance with the purpose of section 9.020, be
served by the sewage system of the city.
(3) Improvements -Land Surface Drainage. Such grading shall be
done and such drainage facilities shall be constructed by the land divider as are
adequate for the purpose of proper drainage of the partition or subdivision, of
areas affected thereby, and for the preservation of healthful and convenient
surroundings and conditions for residents of the subdivision or partition, and
for the general public, in accordance with standards and specifications adopted
pursuant to section 7.085 of this code.
(4) Imarovements - Streets and Alleys. The land divider shall
grade and pave all streets and alleys in the subdivision or partition to the
width specified in section 9.045 and provide for drainage of all such streets and
alleys, and construct curbs and gutters within the subdivision or partition in
accordance with standards and specifications adopted pursuant to section 7.085.
Private streets and alleys are prohibited unless the developer can demonstrate
to the city's satisfaction that a public street is not necessary for compliance
with this code and the street connectivity standards of section 9.045.
(5) .Improvements -Sidewalks. Sidewalks shall be located, designed
and constructed in accordance with the provisions of this code and construction
and design standards adopted pursuant to section 7.085.
(6) Imarovements - Bicycle Paths and Accessway~. Pedestrian/
bicycle ways shall be designed and constructed in accordance with provisions of
this code and construction and design standards adopted pursuant to section
7.085.
Section 20. Subsections (3) and (4) of Section 9.510 of the Eugene Code,
1971, are amended to provide
9.510 General Provisions.
(3) Phasing. If approved at the time of tentative plan consider-
ation, final plans may be submitted in phases. The phasing shall progress in a
sequence that promotes street connectivity between the various phases of the
Ordinance - 17
development.
~4} Haase of aoarav~. If the applicant fai 1 s to submi t a fi na1
plan app1 i cati on i n accordance with the schedule approved at the time of
tentative plan consideration, or in the absence of a specified schedule, within
three years of tentative p1 an approval , that approval expires . If the app1 i cant
fai 1 s to obtai n a bui 1 di ng permit within the time period specified i n connection
with the fi na1 plan approval , or i n the absence of a sped fi ed time period,
within one year of final p1 an approval , final plan approval expires . Prior to
expiration of tentative p1 an approval , the hearings authority responsible for
approva 1 may , i f requested , extend the schedule , provided i t i s not contrary to
the public interest or findings required in response to approval criteria.
Unless the hearings offi ci a1 provides otherwise, expi rati an of fi na1 p1 an
approval of any phase automatically voids approval of al 1 phases on which
construction has not begun.
Section 21. Subsections (2), (6)(a), (6)(c)3., and (6)(j) of Section 9.512
of the Eugene Code, 1971, are amended, and a new Subsection (6)(c)5. is added
thereto, to provide:
9.512 Tentative Plan Consideration.
(2) Annlication. A tentative plan application and related
information as prescribed by the city shall be submitted for all contiguous
property under the same ownership by the owner of the affected property, together
with a fee established by the city manager as provided by section 2.020 of this
code.
~ 6 } i i Unless .the applicant agrees to a 1 onger time period ,
the hearings offi ci a1 shal 1 approve, conditionally approve, or deny a tentati ve
plan application with findings and conclusions thereon , within 15 days fol 1 owi ng
the close of the public hearing and the record. Within five days after the
decision i s rendered , the hear? ngs official shall ma i 1 a noti ce thereof to the
app1 i cant , coordinator , and persons who have requested notification . Apprava 1
or denial shal 1 be based on the fu11 development , i nc1 udi ng the campl ete street
network and al 1 street connections . Phasing of portions of the development may
occur as part of final approval . The phasing shal 1 progress i n a sequence that
promotes street connectivity between the various phases of the deve1 opment .
Deci si ans i n al 1 phases shat 1 be based on the fol 1 owi ng criteria
~ a } The proposed development i s consistent with related
policies and development standards , i f appl i cab1 e, adopted
ordinance - 18
refinement p1 ons and specs a1 area studies .
~c} The proposed development's general design and character,
including but not 1 i mi ted to anticipated bus 1 di ng 1 ocati ons , bul k
and height , 1 ocati on and distribution of recreation space, parking ,
roads , access and other uses , wi 11;
3. Disperse motor traffic from planned unit
developments onto more than one public local street when:
(1)the planned unit development exceeds 19 lots (or units): or
(2) the sum of proposed planned unit development lots (or
units) and the existing lots (or units) utilizing a public
local street would exceed 19 lots (or units), and that public
local street is the single means of ingress and egress; unless
a finding i s made that i t i s not feasible due to physical
constraints, such as topography, the previous layout of the
surrounding area, or similar constraints.
5 . Be i n comps i once with the street connectivity
standards of section 9.045. If the application of thi s
subparagraph ~c}5. and ~c}3, to a development proposal results
i n a confl i ct, the more restrictive provision shal 1 control .
~ j } There wi 11 be adequate provision of public pedestrian
and bicycle connections to and from nearby and adjacent resi dents a1
areas , transit stops , neighborhood activity centers , commercial
areas and office and industrial parks . At a mi ni mum, "nearby" i s
interpreted to mean uses within 114 mile which can reasonably be
expected to be used by pedestrians , and uses within one to two mi 1 es
which can reasanabl y be expected to be used by bicyclists .
Section 22. Section 9.386 of the Eugene Code, 1971, is amended by adding
a new Subsection X34} thereto, to provide:
9.386 i1 nrsfr r'n Rni v .
X34} S~r~~t Canne~,~, vi ty. Al 1 residential developments over one-
hal facre i n size which are permitted outright sha11 provide bicycle and
pedestrian connects ons to future development sites and comply with street
connectivity standards of this code.
ordinance - 19
. Section 9.574 of the Eugene Code, X971, i s amended by adding
a new Subsection (4) thereto, to provide:
9.574 Saec a1___Se~~~~k Re ui rement~.
(4) Alley setback. A minimum setback of two feet on each side
shall be required in alleys in order to provide an adequate back-up distance of
24 feet.
Section 24. Subsection (b>8. of Section 9.688 of the Eugene Code, 1971,
is amended to pravide:
9.688 Site Revi ~w Sub-district Initiation . Where necessary to accampl i sh
the purpose for site review as stated i n section 9.686, a si to review
sub-district may be initiated i n either of the fol 1 owi ng ways
fib} On its own initiation, the commi ssi an, counci 1, or
hearings official may consider imposition of a si to review sub-
di stri ct . The commission, council , or hearings official sha11
i ncl ude a statement explaining why the site review sub-district may
be necessary based on one or mare of the following criteria:
8. Adequate provision for public pedestrian, bi cycl e
and transit circulation among bui 1 di ngs and related uses on
the development site as we11 as to and from adjacent and
nearby resi denti a1 areas , transit stops , neighborhood activity
centers , office parks , and industrial parks . At a mi ni mum,
"nearby" i s interpreted to mean uses within 114 mi 1 e whi ch can
reasonably be expected to be used by pedestrians, and uses
within one to two mi 1 es which can reasonably be expected to be
used by bicyclists.
Section 25. Subsection (a) of Section 9.702 of the Eugene Code, 1971, is
amended to provide
9.742 General Condi ti oval Use Perini ~ Cri t~ri a . A condi ti oval use permi t
may be granted only i f the proposal conforms to all the fo11 owi ng
Ordinance - 20
criteria . Additional criteria may also be required depending on the ap-
p1 i cabi 1 i ty of other sections of this code .
~a~ The location, size, design, and operating
characteristics of the proposed development wi l1 be made reasonably
compatible with and have minimal impact on the l i vabi 1 i ty or
appropriate development of abutting properties and the surrounding
neighborhood, with cansi derati an given to harmony, scale, bulk,
coverage, and density; to availability of pub1 is facilities and
uti 1 i ti es , including transi t ~ rel aced foci 1 i ti es ; to traffi c
generation and the capacity and safety of surrounding streets and
al 1 eys ; to the adequate provision of public pedestrian and bi cycl e
connections to and from nearby and adjacent residential areas ,
transit stops , nei ghbarhoad activity centers , commerci a 1 areas , and
office and industrial parks . At a mi ni mum, "nearby" i s interpreted
to mean uses within 114 mi 1 e which can reasonably be expected to be
used by pedestrians , and uses within one to two mi 1 es which can
reasonably be expected to be used by bicyclists; and to other
ref ati ve impacts of the development .
Secti ons z through v~ of the Eugene Local Street Plan, which
are attached as Exhi bi t A hereto and incorporated herei n by reference, are hereby
adopted as the findings and conclusions supporting the revisions to the Eugene
Code, 1971 provided for herein,
~r ~~ on 27 . The City Recorder, at the request of , or with the concurrence
of the City Attorney, may administratively correct any reference errors contained
herein, or i n other provisions of the Eugene Code, 1971 to the provisions added,
amended, or repealed herein.
Passed by the City Council thi s
5th day of August, 1996
City Recorder
Ordinance - 21
Approved by the Mayor this
5th day of August, 1996
Mayor
CITY OF EUGENE
INTER-DEPARI'MENTAI, MEMORANDI7M
CITY ATTORNEY - CIVII, DEPARTMENT
To: date ]~ieland
Dade: Aug~t 1, ~9~7
Deputy City ~eeorder
S~bjert: subsection 9,~12~~~a~ of the ~u ene o
g G de,197~
A pity hearings ~~cial has questioned whether Subsection 9.SI~
Cod ~6~~a} of the Eugene
e, 197 as rt cuixen~y appears in the Cvde ~~ correct, He fndieated to e
T resa Bishow of the
Planning Depaent that it differed frQ.~ a raor version avails a to "
P bl lum and requested that she
detern„~e if the Cvur~cxl had intentionally amended it, and when. T
cress con~cted our o f f ice fvr
assistance.
we have reviewed all the or~Ces amend~g 5ectivn 9 ~ 5 ~ ~ ~ The my '
st recent vrdxr~ances
in which Su~bsec~on ~~}~a~ appears are ~rdiuance 1~77U ~.dv red '
P April 22, ~ 99 ~ , and qrd i~nance
~ODS~ adopted August 5, ~99~. ~n Qrdinance ~977D Subsectio
n ~~}~a~ reads.
"~a~ The proposed deve~ap~e~t is consistent with related . .
pol~ctes and
deveioptnent standards in applicable, ado red nei boyhood r
p gh ef~nement ply and
special area s~dies."
In. Ordinance ~005~, the current ~ersipn in the Cvde it yea
~, d~.
"~a~ The proposed development is consistent wig related ' '
policies aid
development standards} if applicable, ado red refinement '
. p p ana and special area
st~dtes, ?'
we reviewed ~e legislature draft of Ordinance ~OD56 and the v
my ~tztended xe'~iszon to
that subsection was the deletion of the word "nei hborhaod. ~ .
g The leg~slatave draft did not show
~.e addition ^f the contnria after `standards, " or a cha a from ~' ~ ~' ,, .
ng ~n tv if , we belzeve those
changes to be scrivener s errors. P~rsnant to Section 27 of the '
~;~dfnance please consider this
au~,o~adon and a request tQ admiaustra~vety correct Subsection 9.5
~~t~~~a} of the Eugene Code,
~ 97 ~ tv read as retlected in the first sub axa a h a se
~~ ~ P ~' p ~ ~ t forth above, with the word
neighbarhoad deleted to reflect rho amen,d~nent intended b ~Drdi a ce
y n n 2~~5b,
A cop~r of th%s rnetno should be appended to flrd%nance 20456 to reflect e - . .
acti - th a~.strattve
on taken, as au~orized by Section 27 of the ordinance.
RESQLUTI(IN NQ. 4919
A RES4LUTIQN CQNCE1tNING STREETS WIDTHS IN THE CREST
DRIVE AREA, AND AMENDING THE CITY'S DESIGN STANDARDS
AND GUIDELINES FQR EUGENE STREETS SIDEWALKS, BIKEWAYS
AND ACCESSWAYS, THE EUGENE ARTERIAL & CQLLECTQR
STREET PLAN, AND THE EUGENE LOCAL STREET PLAN. -
The City Council of the City of Eugene finds that:
A. The City Council adopted the November 1999 Eugene Street Classification Map
by Ordinance No. 20151 on November 22, 1999, with the streets in the Crest Drive Area left
unclassified pending a study to determine the appropriate classifications and desi n standards for
g
the neighborhood.
B. Design Standards and Guidelines for Eugene Streets, Sidewalks, Bikeways and
Accessways Design Standards and Guidelines} were also adopted by the City Council on
November 22, 1999 by Resolution No. 4605. These Design Standards and Guidelines are also
set forth in the Eugene Arterial and Collector Street Plan adopted as ~.ndings in support of
Ordinance No. 20151, and street width recommendationsare reflected in the Eu ene Local Street
. , .g
Plan adopted as findzngs ~n support of Ordnance No. 20056. The m~n~mum width allowed under
the design standards for local streets and neighborhood streets is 20 feet.
C. The City Council directed the City Manager to implement the Crest Drive
Neighborhood context sensitive solutions ~CSS} process on Ma 5, 2006 with C.SS defined as:
Y
Context sensitive solutions is a collaborative, interdisciplinary project
development approach that involves all stakeholders to develop a transportation
facility that f is its physical setting while maintaining safety and inability for all
users, and reflecting community needs. The goal of CSS is to create early, open,
honest, and continuous communication and sharing of information and knowledge
throughout the design process.
D. The City conducted a topographic survey of all of the streets under consideration,
including all of the trees within the public right-of-way. The City's survey crew surveyed over
15,000 data points including the existing edge of pavement, property corners, public and private
utilities, structures and trees. All of this survey information was used to generate a set of maps to
aid in the street design process.
E. The design process involved City staff working with five separate street teams an
five separate street segments -Upper Crest, 'ddle Crest, Lower Crest, Stacey and Friendl .
y
Each street team presented its conceptual design to the enure Crest_ Dave Community Team
~CDCT}. As part of the design process, each street team evaluated its design using the Themes
and Values developed and approved by the CDCT.
Resolution -1
F. Over the course of two meetings on June 28 and July 13, the CDCT reached
consensus on the conceptual design for all five street segments. However, the CDCT did not
reach agreement on the overall design concept because of an outstanding issue regardin the
.. .. g
minimum street width. Through aconsensus-based decision process, the CDCT determined
there were compelling reasons to support a minimum street width of 18 feet two nine-foot travel
lanes}. Reasons supporting the recommendation included the CDCT's themes and values
regarding preserved neighborhood livability, reduction of traffic s eels, efficient use of urban
p
land in a rural setting, increased safety for all modes of use, and focus on a footprint that fits the
neighborhood's character, As such, an 18-foot street width was perceived. to be more consistent
with .the CDCT's adopted themes and values than a 20-foot street width. Based on those
collaboratively developed values, it was the consensus recommendation of the CDCT to ursue a
. .. ~
legislative change to the minimum street width ~ 18 feet rather than the prescribed minimum of
20 feet} prior to making a decision on the overall design concept.
G. Resolution No. 4608 adopting the Design Standards and Guidelines contains a
provision authorizing administrative amendments to the Design Standards and Guidelines. The
proposal to approve. a minimum street width of 18 feet encompasses a wide range of cammuni
• ~'
interests that are more appropriate for the City Council to resolve, including safety, efficiency,
impacts to adjacent and surrounding residents, and costs assessed to affected property owners.
Therefore city staff referred this matter to the City Council.
H. The City Council held work sessions on the requested amendment to the street
width in the Crest Drive Neighborhood on September 19, 2047 and October 8, 2407, a public
hearing on October 15, 2007, and based on the above findings and the testiinon resented at the
Yp
public hearing, is now ready to take action.
NOW, THEREFORE,
BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF EUGENE, a
Municipal Corporation of the State of Oregon, as follows;
Section 1. The Design Standards and Guidelines far Streets, Sidewalks, Bikeways and
Accessways adopted by Resolution No. 4645 of the City Council is amended by adding the
following paragraph as subsection ~3 ~ to the Vehicle Travel Lane width Desi Standards
provision set forth on page 7, and as subsection ~5} to paragraph A, the Vehicle Lanes provision
of the Local Street Design Standards set forth on page 36:
The minimum travel lane width on streets in the area identified as the Crest Drive
Area on the Eugene Sheet Classification Map is 9'.
Section ~. The City Recorder. is requested to append a copy of this Resolution to
Resolution No. 460$, Ordinance No. 24181 and Ordinance No. 24056. To the extent an of the
.. ~'
provisions contained therein conflict with the amendment set forth in Section 1 of this
Resolution, the amendment contained herein shall prevail.
Resolution - 2
Section 3. This Resolution shall become effective immediately upon its adoption.
The foregoing Resolution adapted the 22~'d day of October, 207.
1
j~,~., City Recorder
Resolution - 3
RESULUTI4N NG. 49Z7
A RESULUTIGN C(]NCERNING SIDEWALK WIDTHS IN THE CREST
DRIVE AREA, AND AMENDING THE CITY'S DESIGN STANDARDS
AND GUIDELINES FGR EUGENE STREETS SIDEWALKS, BIKEWAYS
AND ACCESSWAYS, THE EUGENE ARTERIAL & CULLECTGR
STREET PLAN, AND THE EUGENE LOCAL STREET PLAN,
The City Council of the City of Eugene finds that;
A. The City Council adopted the November 1999 Eugene Street Classification Map
by ordinance No. 201$1 on November 22, 1999, with the streets in the Crest Drive Area left
unclassif ed pending a study to determine the appropriate classifications and design standards for
the neighborhood.
B. Design Standards and Guidelines for Eugene Streets, Sidewalks, Bikeways and
Accessways Design Standards and Guidelines} were also adopted by the City Council on
November 22, 1999 by Resolution No. 4608. These Design Standards and Guidelines are also
set forth in the Eugene Arterial and Collector Street Plan adapted as findings in support of
Grdinance No, 20181, and street width recommendations are reflected in the Eugene Local Street
Plan adopted as findings in support of Grdinance No. 20054. The minimum sidewalk width
allowed under the design standards for local streets and neighborhood streets is five feet.
C. The City Council directed the City Manager to implement the Crest Drive
Neighborhood context sensitive solutions CSS} process on May 8, 2006, with CSS defined as:
Context sensitive solutions is a collaborative, interdisciplinary project
development approach that involves all stakeholders to develop a transportation
facility that fits its physical setting while maintaining safety and mobility for all
users, and reflecting community needs. The goal of CSS is to create early, open,
honest, and continuous communication and sharing of information and knowledge
throughout the design process.
D, The Crest Drive Community Team believes that a sidewalk width of four feet
better meets the themes and values identified as part of the context sensitive solutions process.
E. The City Council held work sessions on the requested amendment to the sidewalk
width in the Crest Drive Neighborhood on January 23, 200$, and a public hearing on February
19, 2008, and based on the above findings and the testimony presented at the public hearing, is
now ready to take action.
Resolution -1
Naw, THEREF[IRE,
BE IT RESOLVED BY THE CITY CGUNCIL OF THE CITY aF EUGENE, a
Municipal Corporation of the State of Gregor, as follows:
Section 1. The Design Standards and Guidelines for Streets, Sidewalks, Bikeways and
Accessways adopted by Resolution No. 4605 of the City Council is amended by adding the
following paragraph as subsection ~5} to the Sidewalks Design Standards provision set forth on
page 10, and as subsection ~6} to paragraph F, the Sidewalks provision of the Local Street Design
Standards set forth an pages 37 and 38:
The minimum sidewalk width in the area identified as the Crest Drive Area on the
Eugene Street Classification Map is four feet.
Section 2. The City Recorder is requested to append a copy of this Resolution to
Resolution No. 46D8, Ordinance Na. 2D 18 ~ and Ordinance Na. 2DD56. To the extent any of the
provisions contained in Resolution No. 4608 conflict with the amendment set forth in Section 1
of this Resolution, the amendment contained herein shall prevail.
Section 3. This Resolution shall become effective immediately upon its adoption,
The foregoing Resolution adopted the 14t" day of April, 2008.
City Recorder
Resolution - Z
EXHIBIT A, Eugene Local Street Plan, May, 1996, not attached. It is
available by written request to the Eugene City Recorder's Office.