Or. Admin. Code § 660-012-0610 - Bicycle System Requirements
(1) This rule describes the minimum planned
bicycle facilities that must be included in plans. Cities or counties may
choose to exceed the requirements in this rule. Cities and counties may choose
to apply bicycle functional classifications to bicycle facilities.
(2) Cities and counties shall plan for a
connected network of bicycle facilities that provides a safe, low stress,
direct, and comfortable experience for people of all ages and abilities. All
ages and abilities includes:
(a) School-age
children;
(b) People over 65 years
of age;
(c) Women;
(d) People of color;
(e) Low-income riders;
(f) People with disabilities;
(g) People moving goods, cargo, or other
people; and
(h) People using shared
mobility services.
(3) A
connected network is comprised of both the ability to access key destinations
within a community and enough coverage of safe and comfortable facilities to
ensure most people within the community can travel by bicycle.
(a) Cities and counties must design the
connected network to connect to key destinations identified as provided in OAR
660-012-0360, and to and within
each climate-friendly area or Metro Region 2040 center.
(b) Cities and counties must design the
connected network to permit most residents of the planning area to access the
connected network with an emphasis on mitigating uncomfortable or unsafe
facilities or crossings.
(c) The
connected network shall consist of connected bicycle facilities including, but
not limited to, separated and protected bicycle facilities, bicycle boulevards,
and multi-use or bicycle paths. The connected network must include a series of
interconnected bicycle facilities and provide direct routes to key
destinations. Cities and counties must design comfortable and convenient
crossings of streets with high volumes of traffic or high-speed
traffic.
(4) Cities and
counties shall plan and design bicycle facilities considering the context of
adjacent motor vehicle facilities and land uses.
(a) Cities and counties shall design bicycle
facilities with higher levels of separation or protection along streets that
have higher volumes or speeds of traffic.
(b) Cities and counties shall plan for
separated or protected bicycle facilities on streets in climate-friendly areas,
Metro Region 2040 Centers, and other places with a concentration of
destinations. Cities and counties are not required to plan separated or
protected bicycle facilities on streets with very low levels of motor vehicle
traffic, with slow speeds of motor vehicles, or near a high-quality parallel
bicycle facility on the connected network.
(c) Cities and counties shall identify
locations with existing bicycle facilities along high traffic or high-speed
streets where the existing facility is not protected or separated, or parallel
facilities do not exist. Cities and counties shall plan for a transition to
appropriate facilities in these locations.
(5) Cities and counties shall adopt standards
for bicycle system planning and facilities that will result in a safe, low
stress, and comfortable experience for people of all ages and abilities. In
adopting standards, cities and counties may use one or more of the following:
(a) The Urban Bikeway Design Guide, second
edition, published by the National Association of City Transportation
Officials;
(b) Designing for All
Ages & Abilities, December 2017, published by the National Association of
City Transportation Officials; and
(c) For state facilities, The Blueprint for
Urban Design, 2019, published by the Oregon Department of
Transportation.
(6)
Cities and counties shall use the transportation prioritization framework in
OAR 660-012-0155 when making
decisions about bicycle facilities.
Notes
Statutory/Other Authority: ORS 197.040
Statutes/Other Implemented: ORS 197.012 & ORS 197.712
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.