ZOA2002-00004 110 • t
CITY OF TIGARD
Community Development
• Shaping A Better Community
LAND USE PROPOSAL DESCRIPTION
120 DAYS = N/A
FILE NO.: ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
FILE TITLE: TSP Implementation
APPLICANT: City of Tigard OWNER: N/A
13125 SW Hall Blvd
Tigard, OR 97223
REQUEST: Amend the Tigard Development Code to reflect the Transportation System Plan and
Comprehensive Plan changes adopted in January 2002. The proposed amendments
also reflect the State of Oregon's Transportation Planning Rules (TPR) which include
provision of skinny streets. The specific code sections meeting amended include:
18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810.
LOCATION: Citywide
ZONE: N/A— Citywide 7
APPLICABLE
REVIEW
CRITERIA: Statewide Planning Goals 1, 2 and 12; Oregon Administrative Rule (OAR) 660, Metro
Regional Transportation System Plan; Comprehensive Plan Policies 1.1.1(a), 2.1 .1 ,
8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 and Community Development Code Chapters
18.380.020 and 18.390.060.G.
CIT AREA: City wide CIT FACILITATOR:
COMMENTS SENT: June 20, 2002 DUE: July 5, 2002
DATE DLCD NOTICE WAS SENT:June 19, 2002
DECISION MAKING BODY BELOW: ❑ TYPE I ❑TYPE II ❑ TYPE III ® TYPE IV
® PLANNING COMMISSION (MON.)DATE OF HEARING: August 5, 2002 TIME: 7:00 PM
® CITY COUNCIL (TUES.) DATE OF HEARING:. September 10, 2002 TIME: 7:30 PM
COMPONENTS RELATED TO THE PROJECT AVAILABLE FOR VIEWING IN THE PLANNING DIVISION
• PROPOSED ® STAFF REPORT (at least ® DLCD NOTICE
ORDINANCE/AMENDMENTS 7 days prior to the 1st
hearing)
❑ VICINITY MAP ❑ SITE PLAN
STAFF CONTACT: Julia Hajduk, Associate Planner (503) 639-4171
, •1.
120 DAYS = N/A
CITY OF TIGARD
Community Development
Shaping A Better Community
CITY OF TIGARD
WASHINGTON COUNTY, OREGON
NOTICE OF FINAL ORDER BY THE TIGARD CITY COUNCIL
Case Number: ZONE ORDINANCE AMENDMENT (ZOA) 2002 -00004
Case Name: TSP IMPLEMENTATION
Names of Owners: N/A
Name of Applicant: City of Tigard
Address of Applicant: 13125 SW Hall Blvd., Tigard, OR 97223
Address of Property: Citywide
Tax Map /Lot Nos.: Citywide
A final order incorporating the facts, findings and conclusions APPROVING a request for a Zone Ordinance
Amendment.
The City of Tigard Planning Commission and City Council have reviewed the applicant's plans, narrative, materials,
comments of reviewing agencies, the Planning Division's staff report and recommendations for the application
described in further detail in the staff report. The Planning Commission held a public hearing to receive testimony on
August 5, 2002 for the purpose of making a recommendation to the city council on the request. The City Council
also held a public hearing to receive testimony on September 10, 2002 prior to making a decision on the request.
This decision has been based on the facts, findings and conclusions contained within this final order.
P UEST: Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections meeting
amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. LOCATION: Citywide ZONE: N/A
— Citywide APPLICABLE REVIEW CRITERIA: Statewide Planning Goals 1, 2 and 12; Oregon Administrative Rule
(OAR) 660, Metro Regional Transportation System Plan; Comprehensive Plan Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2,
8.1.3, 8.1.5 and 8.2.3 and Community Development Code Chapters 18.380.020 and 18.390.060.G.
Action: > ® Approval as Requested ❑ Approval with Conditions ❑ Denial
Notice: Notice was published in the newspaper, posted at City Hall and mailed to:
® Affected Government Agencies ® The Affected Citizen Involvement Team Facilitator
The adopted findings of fact, decision and statement of conditions can be obtained from the
Planning Division /Community Development Department at the City of Tigard City Hall.
Final Decision:
THIS IS THE FINAL DECISION OF THE CITY AND BECOMES EFFECTIVE ON OCTOBER 10, 2002.
The adopted findings of fact, decision and statement of conditions can be obtained from the City of
Tigard Planning Division, Tigard City Hall, 13125 SW Hall Boulevard, Tigard, Oregon.
Appeal: A review of this decision may be obtained by filing a notice of intent with the Oregon Land Use Board
of Appeals (LUBA) according to their procedures.
Q ions: If you have any questions, please call the City of Tigard Planning Division or the City Recorder at
(503) 639 -4171.
Attachment 1
CITY OF TIGARD, OREGON
ORDINANCE NO. 02- S3
AN ORDINANCE ADOPTING CHANGES TO THE DEVELOPMENT CODE IN ORDER
TO IMPLEMENT THE TRANSPORTATION SYSTEM PLAN (TSP).
WHEREAS, the TSP was developed with the help of a 12 member citizen Task Force and
addressed Transportation Planning Rule (TPR) requirements, Metro's Regional Transportation Plan
(RTP) updates and the City needs; and
WHEREAS, Tigard adopted its Transportation System Plan in January 2002 with the intent to
return at a later date with amendments to the development code; and
WHEREAS, the TSP is not fully implemented until changes have been made to the development
code; and
WHEREAS, development code changes have been prepared which implement the TSP
recommendations, address TPR narrow street requirements and clarify existing code language as
shown in Exhibits A -1 through A -4; and
WHEREAS, the Planning Commission held a public hearing, which was noticed in accordance
with the City standards, on August 5, 2002 and voted to forward the amendments to the City
Council, and
WHEREAS, the Citizen Involvement Team was informed of the proposed changes and of the City
Council hearing at its September 5, 2002 meeting; and
WHEREAS, the City Council held a public hearing on September 10, 2002, which was noticed in
accordance with City standards, and voted to approve the TSP and Comprehensive Plan changes
proposed, and
WHEREAS, the decision to adopt was based on compliance with Oregon Statewide Planning
Goals #1, #2, and #12; OAR 660; the Regional Transportation Plan, Comprehensive Plan policies
1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 and Community Development Code chapter
18.380.020 and 18.390.060.G as detailed in the TPR compliance matrix (Exhibit B) and the staff
report/Planning Commission recommendation (Exhibit C),
NOW, THEREFORE, THE CITY OF TIGARD ORDAINS AS FOLLOWS:
SECTION 1: The attached Development Code Changes (Exhibit A -1 through A -4) are
adopted based on the findings in the staff report and the supplemental TPR
compliance matrix.
ORDINANCE NO. 02-
Page 1 of 2 (updated 8/19/02 12:17 PM)
SECTION 2: If any section of the TSP or resulting Development Code changes trigger a
Measure 7 claim, the City may make a determination regarding whether the TSP
or Development Code provision should be applied on a case by case basis.
SECTION 3: This ordinance shall be effective 30 days after its passage by the Council,
signature by the Mayor, and posting by the City Recorder.
PASSED: By vote of all Council members present after being read by number
and title only, this day of , 2002.
•
Catherine Wheatley, City Recorder
APPROVED: By Tigard City Council this day of , 2002.
James E. Griffith, Mayor
Approved as to form:
City Attorney
Date
is \lrpin \julia \TSP \implementation \cc packet \TSP implementation ord.doc
ORDINANCE NO. 02-
Page 2 of 2 (updated 8/19/02 10:15 AM)
Exhibit A -1
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Traffic Flow Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right -of -way, the setback for a
structure must be no less than the required setback plus 1/2 the required right -of -way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on- street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP /DLCD -TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1 of 2
(Updated 5 -3 -02)
Added sections requiring street connections to be spaced no less than 530 feet apart to address
connectivity requirements. (18.810.030.6.1) (TSP /Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul -de -sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the measurement of block length from the right -of -way to centerline and adjusted the
maximum block length perimeter from 1,800 feet to 2,000 feet to accommodate the revised way of
measuring. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of "not possible ". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right -of -way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation /POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2 of 2
(Updated 5 -3 -02)
Exhibit A -1
Chapter 18.705
ACCESS, EGRESS, AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply. The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures (see Section 18.360.050), and
to a change of use which increases the on -site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
,presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures, or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title, provided:
I. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
Proposed Development Code changes to implement the TSP Page 1
•
2. Copies of the deeds, easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient
connections between buildings in multi - building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two - family dwellings) and multi- family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6 -inch vertical
separation (curbed) or a minimum 3 -foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping, pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes. Soft - surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director, the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety, and general welfare.
2. Direct individual access to arterial or collector streets from single - family dwellings and duplex
lots shall be discouraged. Direct access to collector or arterial streets shall be considered only
Proposed Development Code changes to implement the TSP Page 2
if there is no practical alternative way to access the site. If direct access_ is the.
City, the applicant will he_ yequired to miti a:ate__ for any safety or neighborhood traffic
management (NIM) impacts deemed applicable by the City Engineer. This may include, but
will_ no_t be limited to, the constrnc_tion_ofa vehicle_turnaround on_the site to eliminate_ the need
for a yehicletobackont,ontothe roadway.
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street, other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
H. Access Management
1 .An _access report _shall he submitted with_an new_deyelopment,pr_o_posals_which_yerifies_desig_n
of driyeways and_ streets _are _safe_ by,imaitig_adequate stacking needs,sidt_distance and
deceleration_ standords assaby 00()T,A_Vnshingtori_Conrity, the. City_ nud_AASI-ITO
(depending_on_ jurisdiction of
2. Driveways shall not he permitted tp_heplaced __in the_intliienee area of collector or arterial street
intersections, Influencearea of intersections is that area where queues of traffic commonly
formon „approach to aninterseebon._ The_mitlirotimitiycway setbackfrom a_ collcctor or
arterialstrcct intersectlQ11_shall_be _ 150 feet,measured fromtheridit,of ljneof the
intersecting, _street to the throat of.. the- proposed_driyeway. 1 =he setback mu be greater
depending_upon the irj flnencearca, as determined_ from City_Engineer review of a traffic impact
report submitted_by the App_heant'straffic engineer, In a case where projeethasiess than_ 150
feet of street frontage,tbeqpplipapt must explore any option for shared access with the adjacent
parcel. If sharedaccess is not possible or practical, the driveway shall be placed as far from the
intersection as possible,
__ The rnirnintint_smeing_of_dbyewnys and_streets _along n collector_ shn_11 be 200 feet_The
minimumsp_acing_of drivew_a_ys_aridstrects ,,,,,,,,, an arterial _shall be €00 feet,
The minimum_spacing_of local streets along a lca seet _shalI _b_e, 125 feet
Minimum access requirements for residential use.
1. Vehicular access and egress for single-family, duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less than as provided in Table
18.705.1 and Table 18.705.2;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE (6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
1 or 2 1 15' 10'
3-6 1 20' 20'
Proposed Development Code changes to implement the TSP Page 3
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI - FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks, Etc.
1 -2 1 15' 10'
3 -19 1 30' 24' if two -way, 15' if
one -way: Curbs and 5'
walkway required
20 -49 1 30' 24' if two -way
or
2 30' 15' if one -way: Curbs and
5' walkway required
50 -100 2 30' 24' Curbs and 5' walkway
_ required
2. Vehicular access to multi - family structures shall be brought to within. 50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead - configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5 %.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
•
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed Development Code changes to implement the TSP Page 4
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0 -99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One -way vehicular access points. Where a proposed parking facility indicates only one -way
traffic flow on the site, it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems, the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets, upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles; or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health, safety, and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties, parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic, access and parking area plans shall provide
efficient sidewalk and/or pathway connections, as feasible, between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1. -3. above may be appealed by means of a Type
II procedure, as regulated by Section 18.390.040, using criteria contained in Section 18.370.020 C3
Proposed Development Code changes to implement the TSP Page 5
Exhibit A -2
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non - residential zone may be built to a
maximum height of 75 feet; provided:
1. The total floor area of the building does not exceed 1 -1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially -zoned land.
2. The maximum height for an attached or detached single - family, duplex, or multiple - family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1 -1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2 -1/2 stories or 35 feet, whichever is less, provided:
Proposed Development Code changes to implement the TSP Page 6
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1 -1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple - family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R -4.5 and R -7 zoning
districts and are limited to single - family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or _
3. An application for partitioning approval under the provisions of Chapter 18.420, Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10 -foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right -
of -way or easement line; and
d. A five -foot non - exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed Development Code changes to implement the TSP Page 7
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings; and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10 -foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10 -foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance with Chapter 18.350, Planned Developments, Chapter 18.430,
Subdivisions, or Chapter 18.420, Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
A. Additional setback from sped- roadways. To ensure improved light, air, and sight distance and
Proposed Development Code changes to implement the TSP Page 8
Where—the—street is not improved, the measurement shall be made at right angles from the
1Arial Streets. The required setback distance for buildings on arterial streets is the setback
centerline of the street as contained in Table 18.730.1.
of the street as contained in Table 18.730.1.
1 I . . • _ .• . '.. • .. . • ' ... e . ". .. '.• .
Street-Names Requirement
Arterial Streets:
SW Pacific Highway (within City Limits) 50 feet
SW Hall Boulevard 45 feet
intersections with Old Scholls Ferry Road) 50 feet
.
Upper Booncs Ferry) 45
SW Upper Booncs Ferry Road 15 feet
Collector Streets:
SW Ash Avenue 30 feet
SW Atlanta Haines ( st of 68th Avenue) 30 feet
SW Atlanta (west of 68th Avenue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
SW Durham Road (between Pac • - .
•
Hall Boulevard) 30 feet
SW Franklin Street 30 feet
SW Gaarde Street 30 feet
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
, SW Hunziker Road 30 feet
ti
SW Main Street 30 feet
SW - McDonald Street 30 feet
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak (west of Hall Boulevard) 30 feet
SW Pfaffle Street 30 feet
SW Sattler Street (40 ft pavement between 100th/Hall) 30 feet
Old Scholls Ferry Road) 30 feet
Proposed Development Code changes to implement the TSP Page 9
TABLE 18.730.1 (CON'T)
Street Names Requirement
SW Summerfield Drive 30 feet
SW Tiedeman Avenue 30 feet
SW— Tigard Street 30 feet
SW Walnut Street 30 feet
SW 68th Avenue 30 feet
SW 68th Avenue (south of Pacific Highway) 30 feet
SW 70th Avenue (south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
Planned, SW Hampton to 69th (westerly loop road) 30 feet
3 The minimum yard requirement shall be increased in the event a yard abuts a street having a right -
of -way width less than required by its functional classification on the City's transportation plan map
and, in such case, the setback shall be not less than the setback required by the zone plus one -half of the
projected road width as shown on the transportation map.
d. The minimum distance from the wall of any structure to the centerline of an abutting street,
- -- r.
B. Distance between multi - family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development, the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25 -foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15 -foot
separation;
c. Buildings with opposing blank walls shall have a 10 -foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections; and
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1 -3 above for walls in separate buildings.
Proposed Development Code changes to implement the TSP Page 10
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non - conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone, the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots.
B. When one abutting property has a non - conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one -half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats, trailers, campers, camper bodies, house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
D. Projections into required yards.
Proposed Development Code changes to implement the TSP Page 11
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
AREA NOT INCLUDED
IN LOT AREA
LO ARE
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.
Proposed Development Code changes to implement the TSP Page 12
Exhibit A -3
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction, reconstruction or repair of streets,
sidewalks, curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99 -22)
E. Except as provided in Section 18_810.030S, as used in this chapter, the term "streets" shall mean
Proposed Development Code changes to implement the TSP Page 13
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99 -22)
18.810.030 Streets
A. Improvements.
1. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half -street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets; or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6:- The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed Development Code changes to implement the TSP Page 14
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights -of -way for streets and related purposes. Rights -of -way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use; or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right -of -way not in full compliance with
the regulations applicable to the standards, the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public," as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
I by deed without full compliance with this title provided such an easement is the only reasonable
Method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.H and 18.705.030I.
D. Street location, width and grade. Except as noted below, the location, width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed Development Code changes to implement the TSP Page 15
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
for the continuation or appropriate rojection of existing streets in the surrounding
Provide fo projection g g
areas, or
the Commission, if it is impractical to conform to existing
to a plan adopted by C
b. Conform p p y p g
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights -of -way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right -of -way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision - making authority based upon anticipated average daily traffic (ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining These are presented in Table
improvement requirements within the specified ran es.
g P q ranges.) P
18.810.1.
1. The decision - making body shall make its decision about desired right -of -way width and
pavement width of the various street types within the subdivision or development . after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On -street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists, bicyclists, and pedestrians;
k. Access needs for emergency vehicles.
Proposed Development Code changes to implement the TSP Page 16
TABLE .18:810:1
Tree -o€- Street R4g1 t. of Way 3 n" 4;'
.W104 -14fe0} ti4440 rett)-
Aitern1 60' ,90 F12'_'1'aric 2
• 60 4:)1: 2; 4
_Minor Collector 40 4.0Z. 2 i
dal - tr ei Conuuurcial and industrial
Less -Than 1500 ADT 50' 2° 2
Less Than 500 ADT 16' 2S 1`.2
Less Than 200 ADT 12'. 24- it?
b. Cul de sac dead end streets:
=Less Than 200 ADT 42- 24;
(Cul de sacs shall be nn -roere--thatt -200
feet-long and-serve ne-- z- than -24)
d eThn ts)
Turn Aroundls -tor Dzad end: Struts "in 50' radm ,
Turn 'Arbunds ter Cul de sic Dead End 17' radin., 1`0,' "' =aili is
$si is in._Res dential Zones.Qnly
Alley nt o4 16' t;C'
.-_ _..._ ".7.4WA 14.1 2Q 20'
� v
Proposed Development Code changes to implement the TSP Page 17
Table 18.810.1
Minimum Widths for Street Characteristics
.c ../ .c
LLI
1! § e"
! C LL aJ . NM
Type of Street
..:4„ u.
E .
a) ' (.) . .... ......
I a) 13 J
....J
Ai 64'. Valles. 2 - 7 (Refer 12! NLA 51(Ne_w_atfets) 8_8,_ Jad,Zon_e_s_) 5' 12
to TSP)
.5!-5' (Existing,51reets) :10.'. (Qom rt.L.Zones)
Collector 58'-96' Vanes 2- 5_(Refer 11: N/A 61(New Streets) 6'(Res. 8,_ Ind,Zones) 5. 12'
to TSP)
5'-6' (Existing Streets) 8' (Comm. Zones)
N_eighbgrho„od. Ro.ute 5c)'-58. 27_36: 2 :i.„v a: 5'.,6! 5,_6,(2) 5' N/A
taut .
ind_u_s_tdaitc_o_m_meroi_al 5.0: 3_5! 2 N/A 5,76,(2) 5' N/A
Loel.:_llesid_enital N/A
• Under 1 500 ADT 54'/50' 32728 2 8' (both sides) . N/A 56,(2)
5'_
• Under 500 ADT 50,146,(J) 28'/24' 2 8' (one side) N/A
• Under 200 ADT . 46'/42''' 24720 2 No Parking.) NLA
Cul-de-sac bulbs in 50' 42' radius NIA N/A N/A N/A
Industrial and radius
Commercial zones
Cul-de-sac bulbs in 4T 40' radius N/A N/A N/A
Residential zones radius
Alley: Residential 16' 16' N/A N/A N/A N/A N/A
.
Alley: Business a 20' N/A N/A N/A N/A N/A
1 Med ian . cs_rearoadwayslite_yarasakInalfQratane roadways.
Sidewalk widths for these streets shall be 5 ft with landscape strip: 6 ft if against curb (if permitted in accordance with 18.810,070,C).
3 "Skinny Street" roadway widths are permitted where cross section and review criteria are met. Refer to corresponding cross sections
.(ficLuLes .1 a.ma 18.810.4 and 1a,1110-5) for details and conditions,
Proposed Dew.' Ipment Code changes to implement the TSP Page 18
, .
. _
. .
Figure _18.8101
Artcriikls Sample cross SQctidris
ft ' • .
-,-
.5' 8-10', 5.5' 6'Bike , 12 12' 6'like 5.5' 8-10' .
7 1— ,
P,/VV 64-68'
2 Lane 64 RMI
,... - ..--
,-•-: , !------
.,■••■:
t
5 12' MediaN
' .5'
F8'0 ' 5 5' ; 6' Bike 12' : Turn Lane 12' 6'Bike 5.5' 43-10' i
R/VV 7680'
h –
3 Lane 76'-80' RIW
,.; €11.1111W __,.Q.--cao I i
—
';;:a7:71:11i= Vika, F '-- - — .. ■ r
12' MediaN
. 8 ; 6' ,631<e 12' 4 12' TUI 11 Lane_ 1 12' 1 , 12' i &Bike 5 5' ; 8-10 f 5 '
R/W 100104'
5 Lane 100 MN
,, _,.
, —,
,,,. ,_
.-..',.
W. '1 :,>-!=•-• &
- - .--Aiik, AINIIIL. 1 • —
- - .
L - `t' '. .": ,,- --- 4 - , ...-34
12' MediaN 5'
8-10' I 5.5' 6'Bike 12' 12' 12' Turn Inn 12' 12' 12' Bike 6' I 5.5' 8-10'
1 I 1 I i
i -- - - tvw 124'-128'
7 Lane 124 FeW
—_—_______-_-- ____ _____—, _-_-==== __----__. . • __
,
Proposed Development Code changes to implement the TSP Page 19
Figure 18.810.2 ,
Collector Sample Cross Sections
.- -, ..,•
'
• ---.76.--i-
F.7___ .......FV::,•:•=1:_ 0,-; 1
5 ' 6-8' 5.5' , &Bike 11' 11' 6'Bike t 5.5' • 6-8' ..
1 i
RNV 58'-62'
2 Lane 58'-62' R/W
,._--,J,-
7.,aryz,
12' Median/
•P.: 6-8' : 5.5' 'ne F _ 11' i Turn Lane F 11' .,6'Bike 5.5' 5 '
! R/V1170'-74' -I
3 Lane 70'-74' R/W
... ;:::::Q
:' ,; ?:"":::'-' :-.> 5.-e-c;r
4, ---- ... ,,,, !
,.. _
4. 411--11
. ■■ i .
.
- -- i-- ■ ale'-'1T16— I 6-k
.5' 12' Median/ .5'
5.5' 6'Bike , 11' ! 11' F Turn Lane : 11' , 11' : 6'Bike
[VW 92'-96'
F 1
5 Lane 92'-96' R/W
- ,
Proposed Development Code changes to implement the TSP Page 20
. .
Figure 1 8,8 1 0.3
Neighborhood Routes
Sturiple_ CLQ5,5_ Sqc_tiQnS
' ..:1-,,,, • --..e
28 5.5 5' ..5 : 5' . 5.5' , 0 32' r2 5.5' 1 5'
IV, y_ y 50' .
No Parking on One Side With Parking on Both Sides
,.------_. . „--,
. ,
-
"). , w
t -
36'
.5 1 ,
. ', 5 1-5.5' 1 8 Bike. 12'
__ f
12/W 58'
—I
With Bike Lanes/No Parking
F
1..ocal_Residential Street . . . I vpd
A. Standard (sample) B. Skinny Street Option (criteria)
v--
Awilme = B
. 5' f _ 5.5' rj , 32' 5.•
-••• I _,..._-25 --- - - 1 AIL
RkAl 54' Travel(a..,,Lanr)
PL•otim3; 5' : 5.
On-street Parking ;dew:4 5 " 25' ) 5 " 5
Pave In ent
<1500 vpd *
RI.3i,t-d-way
If parking on both sides,
block length not to exceed 600 feet Criteria:
• Traffic Flow Plan must be submitted and approved.
-.„
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
- I
Proposed Development Code changes to implement the TSP Page 21
Fioure 188 10.5
Local Residential Streets < 500 vpd
A. Standard (sample) B. Skinny Street Option (criteria)
5'
5' : 5.5' Q 28' 5.5' 5' : t
t — - -; r w
R/W 50' i r 6-17
• !.!' :GY41rg Towel tone ! !' ::
Residential Local Street /Cul -de -sac " s ""` = -` y
5alan i 24' Sufp 561.11:
One Side On- street Paring hymen
<500 vpd Rleht -of,n;
Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of (1) off - street parking space for
every 20 feet of restricted street frontage.
Fi gure _1$. $1_0,6
Local Residential. Street <_200 vpd
A. Standard (sample) B. Skinny Street Option (criteria)
) • • .
5 T
5' 24' 55 5' ' !
�... .
lu..on say
5 " sw,..0
46
Cul - de - sac /Residential Local Street Ryht- e.,vay,
<200 vpd Criteria:
• Must provide a minimum of (l) off - street parking space
(No parking) for every 20 feet of restricted street frontage.
• No parking permitted within 30 feet of an intersection.
F. Future street plan and extension of streets.
I. A future street plan shall:
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall ma_y_.._prepare
a future streets proposal. _Costs_of_the_City preparing __a_ future _streets shall_be
Proposed Development Code changes to implement the TSP Page 22
reimbursed. ._for the :time ..._involved, A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus routes, pullouts or other transit facilities, bicycle routes and
pedestrian facilities on or within 530 feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs -de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul -de -sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
___ Street spacing and_access management_ Refer..to_18.705 030.H_
OH Street alignment and connections.
I . Full street connections with_ spacing of no_ more than 530 . feet_ between connections is required
except \vhere prevented_ by bamers such__as topography railroads,__ pm : existing
devTelopments, lease prov_istonS,_easernents, covenants or other restrictions existinprior to May
1._1995 whichpreclude street connectiot A full street connection may also be_exempted due to
_regulated wa ter feature if regulations would not permit con truetion.. •
Staggering of streets making "T" intersections at collectors and arterials shall not be designed so
street.
2=3. All local and minor=-.,. neighborhood routes__and collector streets which abut a development site
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such as schools, shopping
areas and parks.
45. All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed Development Code changes to implement the TSP Page 23
14I. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75 unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right -of -way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right -of -way lines of the acute angle; and
3. Right -of -way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
U. Existing rights -of -way. Whenever existing rights -of -way adjacent to or within a tract are of less than
standard width, additional rights -of -way shall be provided at the time of subdivision or development.
3K. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs -de -sacs. A cul -de -sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs -de -sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul -de -sac shall be measured from the centerline intersection point of the two
streets to the_radius point of the bulb_along the centerline of the roadway from the n it side of the
intersecting street to the farthest point of the cul de sac.
3. If a cul -de -sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
LM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and as a • proved b the City
Engineer.,
MN. Grades and curves.
_ L ` — Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet), and
—1-2. Centerline radii of curves shall boas determined by the_City_ Engineer_not -be less than 700 feet on
and
2. Streets intersecting with a minor collector or greater functional classification street, or streets
Proposed Development Code changes to implement the TSP Page 24
percent or less. Landings are that portion of the street within 20 feet of the edge of the
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required; except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards.
OP. Streets adjacent to railroad right -of -way. Wherever the proposed development contains or is adjacent I
to a railroad right -of -way, provision shall be made for a street approximately parallel to and on each
side of such right -of -way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right -of -way in
nonindustrial areas.
PQ. Access to arterials and major collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major-collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the
following:
1. A parallel access street along the arterial or major-collector;
2. Lots of suitable depth abutting the arterial or major- collector to provide adequate buffering with
frontage along another street;
3. Screen planting at the rear or side property line to be contained in a nonaccess reservation along
the arterial or major-collector; or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR., Alleys, public or private.
1. Alleys shall be no less than 20 feet in width. In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off -street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS. Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed Development Code changes to implement the TSP Page 25
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST. Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks, and multi - family residential developments.
TU.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
UV. Street signs. The City shall install all street signs, relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
WX. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XY. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
1/27. Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
ZAA. Street cross - sections. The final lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development, whichever is less.
I . Sub -base and leveling course shall be of select crushed rock;
Proposed Development Code changes to implement the TSP Page 26
2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1 -1/2 inches in thickness. (Ord. 99 -22)
AB,,: Traffic When, in the opinion of the City Engineer the •ro•osed development will
create a negative traffic condition on existing neighborhood streets. such as excessive seeding, the
•
developer ma be required to •rovide traffic calming measures. These measures ma be re•uired
within the development and /or offsite as deemed_appropriate_ As an alternative. the developer_may
be_ required_ to_ deposit funds with the City_ to_ help pay_ for traffic calming measures that _become
necessary once the development is occupied_and the City Engineer determines that the additional
traffic from the development has triggered the need for traffic calming measures. The City Engineer
will determine the amount of funds required. and will collect said funds from the developer prior to the
issuance of_a_certificato ofoccupancy or in the case of subdivision,prior to the approval of the final
plat __The funds willbe _held .. by the City- for_a_period of five -(5) yeors._from_the date of issuance of
certificate of occupancy, or_.in_the case of a subdivision the date of final plat_approval._- Any funds not
used_b the Cit_y_within the five -year time .period will be refunded to the developer..
AC. Traffic study
I. A traffic study shall _be required ._for all new orex anded_ uses _or developments under any of the
followin circumstances
a __ when „ they_ genera te_a_ % _or greatel._increase_in ex stin T_h_aftic to_hi >h_ collis O n intersections
identified_by_ W.-ashington County.
b, Trip _generations from eLoprncnt onto the City street_atthe__point_of access and _the _existing
adt 1DT_fall within the tollowina ranges_
Existing AP_T ADTto he added b._
0. -3,000 vps1 2,000 yid.
3,001 -6,000 ypd 1.000vpd
>6,000 vpd 500 vpd or more
I..f any y cafthe_following issues became evident to the City- engineer
fl)__}hgh. traffic volumes . on the adjacent - roadway that may affect_mov_ement_into or_ out _of the
site
(2) Lack of existing l eft -turn lanes onto the_adjacent roadway the _proposed access drive(s)
• (3) Inadequate horizontal or vertical sight distance at access points
(4) 1'he. prohnni of the_ proposed access_ other existinyg_ drives_- o r_ intersections
hazard
O_ The proposal regt>ires a conditional useoermit or_i_nvolves a drive through operation
(fi)__The_proposed development may result rn excesive tra: volumes On _adjacent local streets,
2. In addition a traffic study_may_be_reguired for all new or expanded_ uses or developments_ under
any of the following circumstances:
a___ t` hen_ the site is within _500_fe..et ofan QI_OT facility and/or
h.___ trip g1 erati.on from a development acids 300 or more vehicle trips_per day to_an ODOT facility
Proposed Development Code changes to implement the TSP Page 27
andlor
c. trip generation from a development adds 50 _more_Eeakhour trills to an ODOT facility_.
18.810.040 Blocks
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing
adequate building sites for the use contemplated, consideration of needs for convenient access,
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2 1800 feet measured along the
centerline of the streets right of way line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre- existing development; or
b. For blocks adjacent to arterial streets, limited access highways, major collectors or railroads.
c. For non - residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right -of -ways shall be provided when
full street connection is not-pessibleexempted_by B.1_ above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns, or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse, or drainageway, there shall be provided a storm water easement or drainage right -of -way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make arrangements with the
City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated, and:
1. No lot shall contain part of an existing or proposed public right -of -way within its dimensions;
2. The depth of all lots shall not exceed 2 -1/2 times the average width, unless the parcel is less than
1 -1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off -street parking and service facilities required by the type of use proposed.
Proposed Development Code changes to implement the TSP Page 28
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single - family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation, and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights -of -way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are likely to be
redivided, the Commission may require that the lots be of such size and shape, and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
Sidewalks. All industrial streets and, p iyi.te. streets_. -shall have sidewalks meeting City standards
along at_leastone side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development, even if no sidewalk exists on the other side of the street
B. _Requirement of developers -
__ As _part_of any developmentproposal ,_or_change_in_use resulting - in an additional_1,000
vehicle trips or more_per day an applicant shall be re_quire_d_to identify_ direct _(1 25 x thestraieht line
di stance) pedestnan routes within112 mi _of their site to all transit_faciltties and Neighborhood Activity
Ceutet_s_(schools,_p_arks libraries, del_ _ n ad3itton,_the developer may be required to_participate in the
removal _of any_ aps_in the _pedestrian_ sy -stem off site ifiustitied by the_development.
_ 2..._.__It there is an existing side alk, on the . a m e s i d e of the street a s The . development, wi thin .3QQ
feet of a development__ site in either direction the sidewalk shall be extended from the site to meet the
existing sidewalk, subiect_to rough_proportionalit ___even_ if the sidewalk does not serve a nei_hborhood
activity center)
BC.l'lanter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of any arterial or collector streets where parking is prohibited
, except where the following conditions exist: there is inadequate right -of -way;
the curbside sidewalks already exist on predominant portions of the street; or it would conflict with
the utilities there are _significant_ natural__ features (large_ trees water features, etc) that would be
destroyed if _the sidewalk _ were .lo ated_asrequiree _ w_here_ there aree lstin .strt-e t s_ in__chm
proximity to the, : street_ (15 feet, or. less) A dditional__ considera...tion. for..exem._tin 7__the. 1_anter_ grip
requirement maybe & e n . Ona c a s e by_easebdsis if a _ _ p r o p e r t y _ a b _ u t s _ m o r e than one street frontage,
Proposed Development Code changes to implement the TSP Page 29
CD. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
in width, and:
I. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
FF. Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed, then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property in question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right -of -way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
FG. Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings, commercial buildings or public buildings and/or parks; and
Proposed Development Code changes to implement the TSP Page 30
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord. 99 -22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park, playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord. 99 -22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over - sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
operation of the sewage treatment system.
18.810.100 Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
Proposed Development Code changes to implement the TSP Page 31
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, draina ewa , channel or stream,
P Y � g Y
there shall be provided a storm water easement or drainage right -of -way conforming substantially
with the lines of such watercourse and such further width• as will be adequate for conveyance and
maintenance.
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
18.810.110 Bikeways and Pedestrian Pathways
A. A—Bikeway extension.
. __As a standardhike _lanes shall be required along all Arterial and Collector routes and where
identified on_th_e City's adopted bicycle plan in the_ Transportation System Plan (TSP_).
2. Developments adjoining proposed bikeways identified on the - City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights -of -way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3_ __AnX new street improv
ement protect shall include bicycle lanes as required, in this document
and_on.._the_adoj ted_bicycle_plan.
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
width for bikeways within the roadway is five feet per bicycle travel lane.
? Minimum width : • • multi -use paths separated from the road is eight -ten
1O)_feet. _The_ Width maybe reduced to_eight_Mfeet if there are environmental or other constraints,
_____..-_ _3 __ _Tbe minnnlm_width for pedestrian only off_street_paths s _fiv_e
d. __. Designstandardsfor_l?ike _ and_ pedestrian - r :ays_shall_he_delermined_ The (,'ity. Engineer_
Proposed Development Code changes to implement the TSP Page 32
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above, and:
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer, shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information, easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under - grounding requirement.
1. The developer shall pay a fee in -lieu of under - grounding costs when the development is proposed
to take place on a street where existing utilities whichr are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under - grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case -by -case basis. The most common, but not the
only, such situation is a short frontage development for which undergrounding would result in the
placement of additional poles, rather than the removal of above - ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right -of -way from the applicant's property shall pay the fee in -lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in -lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in -lieu of undergrounding.
Proposed Development Code changes to implement the TSP Page 33
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in -lieu of undergrounding for utilities if the
development does not provide underground utilities, unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front -foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front -foot basis.
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prim r. to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City, permit fee paid, and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Proposed Development Code changes to implement the TSP Page 34
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management (as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments) shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices, and are of high grade, prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements (To be completed.)
Proposed Development Code changes to implement the TSP Page 35
Exhibit A -4
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions . in alphabetical order and renumber the remaining
definitions accordingly:
Neighborhood Activity Center'_ - Ause such as schools. parks libraries, shopping areas,
employment centers or pools which_provide recreational or social _services for groups of
people.
------ - - - - -. - - --
"Traffic Flow Plan" — A plan submitted with a proposal for skinny streets that shows the
potential queuing_ pattern that will allow= for safe and efficient -travel of emergency
vehicles, service vehicles and passenger vehicles with minimal disturbance. This may
include a combination of strategic driveway locations, turnouts or other mechanisms
which will foster safe and efficient travel.
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B -
change the 3` sentence from:
Separated from other commercially -zoned areas by at least one -half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
change to:
Separated from other commercially -zoned areas by at least one -half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
Additional TSP implementation code amendments Page I
The site shall have access to be approved by the City Engineer to an arterial or faajof
collector street.....
18.745.050.C.2.b
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
Additional TSP implementation code amendments Page 2
TPR Compliance Matrix Exhibit B 1
•
Attached are the TPR requirements with an explanation of how they are addressed in the existing City of Tigard
Development Code and in the proposed amendments.
(Where there is a dashed line- it indicates that there is not a standard to be addressed, just an intro in to the
standards.)
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
(3) Local governments shall adopt land use or subdivision
regulations for urban areas and rural communities as set forth
below. The purposes of this section are to provide for safe and
convenient pedestrian, bicycle and vehicular circulation
consistent with access management standards and the function
of affected streets, to ensure that new development provides
on -site streets and accessways that provide reasonably direct
routes for pedestrian and bicycle travel in areas where
pedestrian and bicycle travel is likely if connections are
provided, and which avoids wherever possible levels of
automobile traffic which might interfere with or discourage
pedestrian or bicycle travel.
(a) Bicycle parking facilities as part of new multi - family 18.765.050.E states the minimum
residential developments of four units or more, new retail, parking requirements for all use
office and institutional developments, and all transit transfer types. This is required as part of
stations and park- and -ride lots; any land use review.
18.765.050 provides bike parking 18.810.070 is being amended to include a
(b) On -site facilities shall be provided which p p g g
accommodate safe and convenient pedestrian and bicycle design standards requirement of the developer to show connections
access from within new subdivisions, multi - family to neighborhood activity centers within 'A. mile of
developments, planned developments, shopping centers, and 18.705.030.F (Access, Egress and development and require consideration of
commercial districts to adjacent residential areas and transit Circulation — required walkway improvement requirements depending on
stops, and to neighborhood activity centers within one -half location) addresses walkway proportionality. The amendment also required the
requirements for multi - family, removal of gaps in the sidewalk within 300 feet on
Page 1
•
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
mile of the development. Single - family residential industrial or commercial the same side of the street as a development
developments shall generally include streets and accessways. development. (subject to rough proportionality).
Pedestrian circulation through parking lots should generally
be provided in the form of accessways. 18.810.040 (Street and Utility
Improvement Standards — Blocks)
addresses pedestrian connections
when full street connections are
not possible
18.810.070 (sidewalks) requires
all public streets to have
sidewalks
(A) "Neighborhood activity centers" includes, but 18.120.030 is being amended to include a
is not limited to, existing or planned schools, parks, definition of Neighborhood Activity Center.
shopping areas, transit stops or employment centers;
(B) Bikeways shall be required along arterials and Sidewalks currently are required 18.810.110.A is amended to include the
major collectors. Sidewalks shall be required along along all public streets. requirement that bike lanes be located on all
arterials, collectors and most local streets in urban areas, Development code does not have arterials and collectors and any additional routes
except that sidewalks are not required along controlled a bike lane requirement but refers identified in the TSP for any new construction or
access roadways, such as freeways; to the City's comprehensive plan. improvement project.
(C) Cul -de -sacs and other dead -end streets may be 18.810.030.K regulated cul -de-
used as part of a development plan, consistent with the sacs and states that they can't be
purposes set forth in this section; more than 200 feet long. IF a
variance is granted and the cul-
de -sac is greater than 300 feet,
pedestrian connections are
required. This is in addition to
the block length standards which
may also require additional
pedestrian connections through a ,
block.
Page 2
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
(D) Local governments shall establish their own 18.810 establishes standards that There are amendments which address street
standards or criteria for providing streets and accessways regulate street spacing and block spacing and block lengths, however, they continue
consistent with the purposes of this section. Such lengths intending on limiting out to limit out -of- direction travel and provide greater
measures may include but are not limited to: standards for of direction travel. clarification to increase efficiency and safety.
spacing of streets or accessways; and standards for
excessive out -of- direction travel;
(E) Streets and accessways need not be required where 18.810.040 — Block length
one or more of the following conditions exist: standards provide for this
(i) Physical or topographic conditions make a exception in the standard.
street or accessway connection impracticable.
Such conditions include but are not limited to
freeways, railroads, steep slopes, wetlands or
other bodies of water where a connection could
not reasonably be provided;
(ii) Buildings or other existing development on
adjacent lands physically preclude a
connection now or in the future considering the
potential for redevelopment; or
(iii) Where streets or accessways would violate
provisions of leases, easements, covenants,
restrictions or other agreements existing as of
May 1, 1995 which preclude a required street
or accessway connection.
(c) Where off -site road improvements are otherwise Any road is required to be
required as a condition of development approval, they shall constructed to the standards
include facilities accommodating convenient pedestrian and called for in our code. As shown
bicycle travel, including bicycle ways along arterials and within this matrix, the code
major collectors; requires sidewalks but additional
amendments have been made to
Page 3
4
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
define required bikeway
locations.
(d) For purposes of subsection (b) "safe and convenient"
means bicycle and pedestrian routes, facilities and
improvements which:
(A) Are reasonably free from hazards, particularly The City's Municipal code
types or levels of automobile traffic which would interfere prohibits obstructions on public
with or discourage pedestrian or cycle travel for short sidewalks
trips;
(B) Provide a reasonably direct route of travel The access standards, block
between destinations such as between a transit stop and a length standards and requirement
store; and for sidewalks provides a In addition, an amendment is proposed to have the
(C) Meet travel needs of cyclists and pedestrians reasonably direct route of travel developer review routes within 300 feet
considering destination and length of trip; and considering between destinations and meets (approximately Y4 mile) from the development site
that the optimum trip length of pedestrians is generally 1/4 the travel needs of cyclists and and, if proportional, make necessary
to 1/2 mile. pedestrians improvements to complete "gaps"
(e) Internal pedestrian circulation within new office parks 18.705.030.E requires walkways
and commercial developments shall be provided through within commercial developments
clustering of buildings, construction of accessways, walkways
and similar techniques.
..) To support transit in urban areas containing a
population greater than 25,000, where the area is already
served by a public transit system or where a determination has
been made that a public transit system is feasible, local
governments shall adopt land use and subdivision regulations
as provided in (a) -(f) below:
(a) Transit routes and transit facilities shall be designed to SDR standards 18.360.090.11
support transit use through provision of bus stops, pullouts requires development to provide
and shelters, optimum road geometrics, on -road parking transit amenities as required by
Page 4
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
restrictions and similar facilities, as appropriate; tri-met during the development
review (if proportional and
justified)
(b) New retail, office and institutional buildings at or near
major transit stops shall provide for convenient pedestrian
access to transit through the measures listed in (A) and (B)
below.
(A) Walkways shall be provided connecting
building entrances and streets adjoining the site; 18.705.030.f
(B) Pedestrian connections to adjoining properties
shall be provided except where such a connection is 18.810.070 — sidewalks
impracticable as provided for in OAR
660 - 012- 0045(3)(b)(E). Pedestrian connections shall
connect the on site circulation system to existing or
proposed streets, walkways, and driveways that abut
the property. Where adjacent properties are
undeveloped or have potential for redevelopment,
streets, accessways and walkways on site shall be laid
out or stubbed to allow for extension to the adjoining
property;
(C) In addition to (A) and (B) above, on sites at
major transit stops provide the following: 18.360.090.11 requires
(i) Either locate buildings within 20 feet of consideration of transit facility
the transit stop, a transit street or an improvements as part of
intersecting street or provide a development review (which
pedestrian plaza at the transit stop or a covers ii to v). Building
street intersection; placement standards are already
(ii) A reasonably direct pedestrian in place in the Tigard Triangle
connection between the transit stop and and as part of the Washington
building entrances on the site; Square Regional Center.
(iii) A transit passenger landing pad Additional standards for building
Page 5
•
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
accessible to disabled persons; placement outside of these transit
(iv) An easement or dedication for a oriented areas are not appropriate.
passenger shelter if requested by the
transit provider; and
(v) Lighting at the transit stop.
(') Local governments may implement 4(b)(A) and (B) While not specifically designated
_we through the designation of pedestrian districts and pedestrian districts, the Tigard
adoption of appropriate implementing measures regulating Triangle and the Washington
development within pedestrian districts. Pedestrian districts Square Regional Center
must comply with the requirement of 4(b)(C) above; implement the requirements of
4(b) (C)
(d) Designated employee parking areas in new 18.765.030.F required parking
developments shall provide preferential parking for carpools lots in excess of 20 long -term
and vanpools; parking spaces to provide
preferential long -term carpool
and vanpool parking for
employees and other visitors to
the site.
(e) Existing development shall be allowed to redevelop a Not specifically provided for, but
nortion of existing parking areas for transit - oriented uses, would not be disallowed since
Aiding bus stops and pullouts, bus shelters, park and ride nothing on the code prohibits it.
stations, transit - oriented developments, and similar facilities,
where appropriate;
(f) Road systems for new development shall be provided 18.810 has street standards that
that can be adequately served by transit, including provisions provides for adequate width of
of pedestrian access to existing an identified future transit pavement and turning radius, etc
routes. This shall include, where appropriate, separate that will provide for transit.
accessways to minimize travel distances. Sidewalks are required along all
public streets
Page 6
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
(g) Along existing or planned transit routes, designation Existing zoning along transit
of types and densities of land uses adequate to support transit. routes is transit supportive — no
changes are needed
(5) In MPO areas, local governments shall adopt land use The Tigard Triangle area,
and subdivision regulations to reduce reliance on the Washington Square Regional
automobile which: Center area and Central Business
(a) Allow transit oriented developments (TODs) on lands District zone have provisions for
along transit routes; mixed use development and
street and design standards which
(b) Implements a demand management program to meet encourage transit oriented
the measurable standards set in the TSP in response to 660- development
012 - 0034(4).
(6) In developing a bicycle and pedestrian circulation plan TSP provides bike and pedestrian Proposed amendments specifically require
as required by 660 - 012- 0020(2)(d), local governments shall master plan. The development pedestrian or bike improvements if shown on the
identify improvements to facilitate bicycle and pedestrian code currently requires walkways pedestrian or bikeway plan, if roughly
trips to meet local travel needs in developed areas. and sidewalks, however we need proportional.
Appropriate improvements should provide for more direct, to amend the code to specifically
convenient and safer bicycle or pedestrian travel within and require if shown on the pedestrian
between residential areas and neighborhood activity centers or bikeway plan.
(i.e., schools, shopping, transit stops). Specific measures
include, for example, constructing walkways between cul -de-
sacs and adjacent roads, providing walkways between
buildings, and providing direct access between adjacent uses.
(7) Local governments shall establish standards for local Current code required pavement The TSP, which provides the foundation for the
streets and accessways that minimize pavement width and width between 24' and 32' for amendments being proposed, was developed with
total right -of -way consistent with the operational needs of the local streets (actual width the help of a Citizen Task Force and Technical
facility. The intent of this requirement is that local depends on ADT and whether Advisory Committee and involved several public
Page 7
660 -12 -0045 How Addressed in current code Proposed amendments
TPR Requirement
governments consider and reduce excessive standards for parking is provided on the street) information meetings to gather input and
local streets and accessways in order to reduce the cost of and up to 12 feet per lane for comments and 2 formal public hearings. After the
construction, provide for more efficient use of urban land, arterial streets development and adoption of the TSP, a group of
provide for emergency vehicle access while discouraging City Staff from Planning and Engineering and a
inappropriate traffic volumes and speeds, and which representative from Tualatin Valley Fire and
accommodate convenient pedestrian and bicycle circulation. Rescue met over several months to develop code
Not withstanding subsection (1) or (3) of this section, local language to implement the TSP. The discussions
eet standards adopted to meet this requirement need not be included the TPR "skinny street" requirement.
adopted as land use regulations. After review and discussion, it was determined
that the safe harbor widths were acceptable,
provided a traffic flow plan was submitted to
verify that the distribution of driveways, no
parking areas, etc would allow efficient queuing
and traffic flow as the State's "Neighborhood
Streets Design Guidelines" assumed. Additional
assurances were needed to ensure that adequate
off- street parking was provided for streets that had
parking on one side only. It was determined that
the existing width standards would remain for
those that did not want to submit a traffic flow
plan or provide additional assurances for off - street
parking, but the option to go to narrower streets
would be provided as well. While technically, the
wider street width is the default because no
additional documentation is required, both street
width standards are acceptable and available for
developments on local streets.
d
Page 8
Exhibit C
PLANNING COMMISSION
RECOMMENDATION-TO,
- ' CITY OF TIGARD
TIGARD CITY COUNCIL Community Development
Shaping A, Better
- Cominnriity
SECTION I: APPLICATION SUMMARY
FILE NAME: TRANSPORTATION SYSTEM PLAN
CASES: Zone Ordinance Amendment (ZOA) 2002 -00004
PROPOSAL: The proposal is to formally adopt Development Code standards to
fully implement the Transportation System Plan (TSP) that was
adopted in January 2002.
APPLICANT: City of Tigard
13121 SW Hall Boulevard
Tigard, OR 97223
LOCATION: All areas within the City of Tigard.
APPLICABLE
REVIEW
CRITERIA: Oregon's Statewide Planning Goals 1, 2 and 12; Oregon Administrative
Rule 660; Metro Regional Transportation Plan (RTP); Comprehensive
Plan Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3, and
Community Development Code Chapter 18.380.020 and 18.390.060.G.
SECTION II: PLANNING COMMISSION RECOMMENDATION:
The Planning Commission moved to forward the Development Code amendments to
implement the Transportation System Plan ( TSP) ;to`the City Council° as shown in ,Exhibit A-
1 through A-4, and in the summary of proposed changes based on the findings that all
relevant criteria are satisfied. The TPR compliance matrix (Exhibit B) and this
recommendation report provide the analysis and findings Which demonstrate compliance .
with all relevant criteria.
STAFF REPORT ZOA 2002 -00004 Page 1
SECTION III: BACKGROUND INFORMATION
The City of Tigard began looking at updating the Transportation System Plan (TSP)
several years ago. With the help of a 12 member task force, agencies and staff, a draft
TSP was produced which takes into account the existing traffic conditions in Tigard,
community needs and goals and the anticipated future demands on the transportation
system. The TSP and Comprehensive Plan amendments were adopted by the City
Council in January 2002. An additional step necessary to fully implement the TSP was
developing amendments to the Development Code to reflect changes to the TSP. The
Planning Commission and City Council held work sessions on the proposed Development
Code amendments in June. The proposed changes reflect the comments received at the
work sessions. The Planning Commission held a public hearing on August 5, 2002. No
testimony was offered at the hearing. As an addition to the Planning Commission's motion
Y 9 9
to forward the amendments to the City Council, the Commission recommended that staff
provide a presentation to the CIT prior to the Council's public hearing. In accordance with
the Commission's recommendation, a CIT presentation is scheduled for the September 5,
2002 meeting prior to the Council's September 10, 2002 hearing.
SECTION IV. SUMMARY OF APPLICABLE CRITERIA
Chapter 18.380 states that legislative text amendments shall be undertaken by
means of a Type IV procedure, as governed by Section 18.390.060G.
Chapter 18.390.060G states that the recommendation by the Commission and the
decision by the Council shall be based on consideration of the following factors:
A. The Statewide Planning Goals and Guidelines adopted under Oregon Revised
Statutes Chapter 197;
B. Any federal or state statutes or regulations found applicable;
C. Any applicable Metro regulations;
D. Any applicable Comprehensive Plan Policies; and
E. Any applicable provisions of the City's implementing ordinances.
SECTION V: APPLICABLE REVIEW CRITERIA AND FINDINGS
STATEWIDE GOALS
Citizen Involvement: Goal 1 requires a citizen involvement program that ensures the
opportunity for citizens to be involved in the planning process.
Tigard Comprehensive Plan Policy 2.1.1 and Tigard Community Development Code Chapter
18.390 provide for citizen participation and notice. Notice of the Planning Commission and
City Council hearings and opportunity for response was advertised in the local newspaper.
Notice was sent to Department of Land Conservation and Development in accordance with
their notice requirements. This goal is satisfied.
STAFF REPORT ZOA 2002 -00004 Page 2
Land Use Planning: Goal 2 requires, in part, that adopted comprehensive plans be
revised to take into account changing public policies and circumstances.
This goal is met because the City has applied all relevant Statewide Planning Goals, City
Comprehensive Plan policies and Community Development Code requirements in the
review of this proposal as discussed throughout this staff report.
Transportation: Goal 12 requires a safe, convenient and economic transportation
system.
The TSP has been prepared in accordance with the Statewide Planning Goals and
requirements. Oregon Administrative Rule 666, the compliance with which is discussed
further in this report, implements the Statewide Transportation Goal 12. The plan has been
reviewed by ODOT and DLCD.
COMPLIANCE WITH FEDERAL AND STATE STATUTES OR GUIDELINES
Oregon Administrative Rule: Section 660 -12 -0000 through 0070 is intended to
implement Statewide Planning Goal #12 by providing guidelines for local
governments to demonstrate compliance with Goal #12 through their Transportation
System Plans.
When the TSP was adopted, it was recognized that Development Code amendments were
needed to fully comply with the TPR. Attached as Exhibit B is a chart identifying how each
of the TPR requirements are addressed. Based on the information provided in Exhibit B and
in this section, staff finds that the TSP complies with the state statutes. There are no
specific federal standards that apply.
COMPLIANCE WITH METRO REGULATIONS
Regional Transportation Plan (RTP): The RTP takes the place of Metro Functional Plan
Title 6 (Regional Accessibility), and is consistent with Chapter 2 of the Regional
Framework Plan. The RTP provides a regional framework for transportation systems
and has its own criteria that must be addressed that are in addition to the
Transportation Planning Rule (TPR) requirements.
The TSP is consistent with the RTP and the proposed amendments include all language
required to be adopted by local jurisdictions. The only specific language that needed to be
changed to implement the RTP was the requirement to have local street spacing no less
than 530 feet apart to address connectivity requirements.
COMPLIANCE WITH COMPREHENSIVE PLAN POLICIES
General Policies: Policy 1.1.1(a) requires that legislative changes are consistent with
statewide planning goals and the regional development plan.
The proposal is consistent with statewide planning goals as addressed above under
`Statewide Goals'. The proposal conforms with the applicable portions of the Metro
Functional Plan that was approved for adoption on October 24, 1996 by the Metro Council.
This policy is satisfied.
STAFF REPORT ZOA 2002 -00004 Page 3
Citizen Involvement: Policy 2.1.1 states that the City shall maintain an ongoing
citizen involvement program and shall assure that citizens will be provided an
opportunity to be involved in all phases of the planning process. Policy 2.1.2 states
that opportunities for citizen involvement shall be appropriate to the scale of the
planning effort. Policy 2.1.3 states that the City shall ensure that the information on
planning issues is available in an understandable format.
A request for comments was sent to all affected jurisdictions and agencies. The Planning
Commission hearing was legally advertised with notice published in the Tigard Times. The
TSP had extensive notice and opportunities to comment. Because the current proposal is
simply an implementation of a previously adopted plan, the same level of public notice is not
necessary.
Transportation: Transportation Policies 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 were
adopted at the same time the TSP was adopted to incorporate the TSP
recommendations into the Comprehensive Plan. The policies are specifically
addressed below:
8.1.1 — requires the planning of transportation facilities to be done in a way that
enhances livability through the proper location of facilities, encouraging pedestrian
traffic and addressing issues of through traffic and speeding on local residential
streets.
8.1.2 — requires a balanced transportation system that incorporates all modes of
transportation.
8.1.3 — requires the effort be made to develop a safe transportation system through
the street standards and access management policies.
8.1.5 — requires the development of transportation facilities that are accessible to all
citizens and minimize out -of- direction travel.
8.2.3 — provides the minimum improvement level and dedication that should be
required of developers as a precondition of development to ensure that the
community's transportation system functions adequately.
The code amendments provide greater clarification of where bike lanes are required,
requires the identification and removal of gaps in sidewalks (if roughly proportional), has
local street spacing standards that will minimize out -of- direction travel, provide greater
access spacing standards and greater clarification of when transit amenities are required.
The proposed development code amendment changes are directly implementing the TSP
and Comprehensive Plan policies, therefore, the applicable Comprehensive Plan
standards have been satisfied.
COMPLIANCE WITH THE CITY'S IMPLEMENTING ORDINANCES:
The implementing ordinances are contained in the Tigard Community Development Code.
The applicable criteria identified in the Development Code are summarized in Section IV —
STAFF REPORT ZOA 2002 -00004 Page 4
Summary of Applicable Criteria and addressed in Section V — Applicable Review Criteria
and Findings. As this staff report demonstrates, all applicable criteria have been satisfied.
SECTION VI: COMMENTS (AGENCY, STAFF AND OTHER)
City of Tigard Engineering, City of Tigard Current Planning Division, City of Tigard
Operations, City of Tigard Public Works, City of Tigard Police, City of Beaverton, City of
Durham, City of King City, Washington County, Tigard - Tualatin School District, and Tri-
met have reviewed the proposal and offered no comments or objections.
Tualatin Valley Fire and Rescue reviewed the proposed amendments and indicated that
they find no conflicts with their interests. The provisions for skinny streets are acceptable
to the Fire District. They also state that the Fire District is currently developing traffic
calming device design criteria that will be submitted upon completion. The general
statement in the Development Code indicates only when they are to be installed. The Fire
District hopes that their criteria will be considered for design details.
DLCD reviewed the proposed amendments and offered comments which are summarized
below:
• They want to make sure that Tigard documents its process used to develop the local
street standards regarding narrow streets;
• They suggested changes which have been incorporated into the proposed
amendments that presents the narrow street option in a way that does not discourage
someone from using that method and as a method that is not favored.
• They provided suggested language which has been incorporated into the proposed
amendments for "Traffic Flow Plan" (formerly referred to as a queuing plan).
• They recommend against changing the block length standard from 1,800 feet to 2,120
feet and provided language that Washington County uses that they suggest we
consider.
Staff response: The change from 1,800 foot block length to 2,120 foot block length was
suggested to be consistent with the street spacing standards, however staff is not
opposed to retaining the original block length concept. Because the measurement system
is being changed from right -of -way line to centerline, the maximum block length dimension
will be 2,000 feet. This will result roughly in the same block length requirement as
currently existing and as recommended by DLCD staff.
Metro reviewed the proposed amendments and generally offered the same comments as
DLCD, specifically, they suggested changes that present the narrow street option in a way
that does not discourage someone from using that method and as a method that is not
favored and they recommend against changing the block length standard from 1,800 feet
to 2,120 feet.
The City of Tigard Urban Forester reviewed the proposed changes and offered the
following comments: "The planter strips should be at least five feet wide so that large trees
can be planted in order to create more tree canopy. I think that planter strips are a good
idea since the trees will be shading much more of the street, thus reducing the heat island
effect too common in this City!"
STAFF REPORT ZOA 2002 -00004 Page 5
Oregon Department of Transportation (ODOT) reviewed the proposed amendments
and offered comments summarized as follows: They appreciate our efforts to clarify when
a traffic study is required, however a traffic study is not always needed to address ODOT
interests. They suggest changing 18.810.030.AC to state that a traffic study MAY (instead
of shall) be required if a site is within 500 feet of an ODOT facility and /or trip generation
from the development adds 300 or more trips per day to an ODOT facility and /or trip
generation from the development adds 50 or more peak hour trips to an ODOT facility.
They request that ODOT be notified of pre - applications to help make the determination of
whether a traffic study is required prior to a formal application being submitted and
deemed complete.
Staff response: The proposed development code language has been amended to include
ODOT's recommended changes
EXHIBITS:
EXHIBIT A -1 through A - Proposed Development Code changes
EXHIBIT B: Chart addressing TPR criteria and Tigard's compliance status
. 4
- a2
PREPA D BY: u lia Hajduk, DATE
Associate Planner
"
SIGNED: �k Padgett
adgett
Planning Commission Chair DATE
I:Irplanlulia/TSP /implementation /cc packet/staff report — exhibit C.doc
STAFF REPORT ZOA 2002 -00004 Page 6
Attachment 2
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Traffic Flow Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right -of -way, the setback for a
structure must be no less than the required setback plus % the required right -of -way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on- street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP /DLCD -TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1
(Updated 5 -3 -02)
Added sections requiring street connections to be spaced no less than 530 feet apart to address
connectivity requirements. (18.810.030.G.1) (TSP /Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul -de -sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
9 9 9 p 9
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline radii curves shall be as determined by the
' City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the measurement of block length from the right -of -way to centerline and adjusted the
maximum block length perimeter from 1,800 feet to 2,000 feet to accommodate the revised way of
measuring. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of "not possible ". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right -of -way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation /POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2
(Updated 5 -3 -02)
• •
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Queuing Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right-of-way, the setback for a
structure must be no less than the required setback plus '/2 the required right-of-way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on-street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP/DLCD-TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1 of 2
(Updated 5-3-02)
• •
Added sections requiring street connections to be spaced no less than 520 feet apart to address
connectivity requirements. (18.810.030.G.1) (TSP/Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul-de-sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the requirement that blocks not exceed 1,800 feet to 2,120 feet to be consistent with Metro
connectivity requirements of streets every 530 feet. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of"not possible". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right-of-way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation/POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2 of 2
(Updated 5-3-02)
• •
Chapter 18.705
ACCESS, EGRESS, AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply. The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures(see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures, or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title, provided:
1. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
Proposed Development Code changes to implement the TSP Page 1
• •
2. Copies of the deeds, easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping, pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
• purposes. Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director, the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety,and general welfare.
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to collector or arterial streets shall be considered only
Proposed Development Code changes to implement the TSP Page 2
• •
if there is no practical alternative way to access the site. If direct access is permitted by the
City, the applicant will be required to mitigate for any safety or neighborhood traffic
management (NTM) impacts deemed applicable by the City Engineer. This may include, but
will not be limited to, the construction of a vehicle turnaround on the site to eliminate the need
for a vehicle to back out onto the roadway.
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street, other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
H. Access Management
1. An access report shall be submitted with all new development proposals which verifies design
of driveways and streets are safe by meeting adequate stacking needs,sight distance and
deceleration standards as set by ODOT, Washington County,the City and AASHTO
(depending on jurisdiction of facility.)
2. Driveways shall not be permitted to be placed in the influence area of collector or arterial street
intersections. Influence area of intersections is that area where queues of traffic commonly
form on approach to an intersection. The minimum driveway setback from a collector or
arterial street intersection shall be 150 feet,measured from the right-of-way line of the
intersecting street to the throat of the proposed driveway. The setback may be greater
depending upon the influence area, as determined from City Engineer review of a traffic impact
report submitted by the applicant's traffic engineer. In a case where a project has less than 150
feet of street frontage,the applicant must explore any option for shared access with the adjacent
parcel. If shared access is not possible or practical,the driveway shall be placed as far from the
intersection as possible.
3. The minimum spacing of driveways and streets along a collector shall be 200 feet. The
minimum spacing of driveways and streets along an arterial shall be 600 feet.
4. The minimum spacing of local streets along a local street shall be 125 feet.
I. Minimum access requirements for residential use.
1. Vehicular access and egress for single-family, duplex or attached single-family dwelling units
• on individual lots and multi-family residential uses shall not be less than as provided in Table
18.705.1 and Table 18.705.2;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width .
1 or 2 1 15' 10'
3-6 1 20' 20'
Proposed Development Code changes to implement the TSP Page 3
1111 •
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:.
MULTI-FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15' if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24' if two-way
or
2 30' 15' if one-way: Curbs and
• 5' walkway required
50-100 2 30' 24' Curbs and 5' walkway
required
2. Vehicular access to multi-family structures shall be brought to within 50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing .
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
•
21 as provided in Table 18.705.3;
Proposed Development Code changes to implement the TSP Page 4
• •
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site, it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets, upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles; or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health, safety, and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties, parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic, access and parking area plans shall provide
efficient sidewalk and/or pathway connections, as feasible,between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
II procedure, as regulated by Section 18.390.040, using criteria contained in Section 18.370.020 C3
Proposed Development Code changes to implement the TSP Page 5
• •
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet;provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are.equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2-1/2 stories or 35 feet, whichever is less,provided:
Proposed Development Code changes to implement the TSP Page 6
410 •
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420, Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line; and
•
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed Development Code changes to implement the TSP Page 7
• •
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings; and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and •
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
•
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance. with Chapter 18.350, Planned Developments, Chapter 18.430,
Subdivisions, or Chapter 18.420, Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
2. A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
A. Additional setback from specified roadways. To ensure improved light, air, and sight distance and
arterial and collector str cts shall be set back a minimum distance from the centerline of the street.
Proposed Development Code changes to implement the TSP Page 8
• •
•
Where the street is not improved, the measurement shall be made at right angles from the
centerline or general extension of the street right of way:
1. Arterial Streets. The required setback distance for buildings on arterial streets is the setback
distance required by the zoning district plus the following distances measured from the
centerline of the street as contained in Table 18.730.1.
2. Collector Streets. The required setback distance for buildings on the following collector streets •
is the setback distance required by the zoning district plus 30 feet measured from the centerline
of the street as contained in Table 18.730.1.
•
TABLE 1.8.730.1
Street Names Requirement
Arterial Streets:
SW Pacific Highway (within City Limits) 50 feet
SW Hall Boulevard 45 feet
SW Scholls Ferry Road(except between its
intersections with Old Scholls Ferry Road) 50 feet•
Upper Boones Ferry) 45 feet
SW Upper Boonas Ferry Road 45 feet
Collector Streets:
SW Ash Avenue 30 feet
SW Atlanta Haines(cast of 68th Avenue) 30 feet
SW Atlanta(west of 68th Avenue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
•
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
SW Durham Road(between Pacific Highway and
Hall Boulevard) 30 feet
• SW Franklin Street 30 feet
SW Gaarde Street 30 feet
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
•
•
SW Hunziker Road 30 feet
SW Main Street 30 feet
SW McDonald Street 30 feet
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak(west of Hall Boulevard) 30 feet
SW Pfaffle Street 30 feet
SW Sattler Street (10 ft pavement between 100th'Hail) 30 feet
SW Scholls Ferry(between its intersections with
Old Scholls Ferry Road) 30 feet
Proposed Development Code changes to implement the TSP Page 9
•
• •
TABLE 18.730.1 (CON'T)
•
•
Street Names Requirement
SW Summerfield Drive 30 feet
SW Ticdcman Avenue 30 feet
SW Tigard Street 30 feet
•
SW Walnut Street 30 feet
SW 68th Avenue. 30 feet
SW 68th Avenue (south of Pacific Highway) 30 feet
SW 70th Avenue (south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW's' 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
Planned, SW Hampton to 69th (westerly loop road) 30 feet
3. The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
of-way width less than required by its functional classification on the City's transportation plan map
and, in such case, the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
. . .- -enterline of an abutting street,
however, shall not be less than 25 feet plus the yard required by the zone. This provision shall
not apply to rights of way of 50 feet or greater in width.
B. Distance between multi-family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
•
within a development, the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15-foot
separation;
•
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections; and
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
Proposed Development Code changes to implement the TSP Page 10
• •
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone, the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots.
B. When one abutting property has a non-conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats,trailers, campers, camper bodies, house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
•
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
D. Projections into required yards.
Proposed Development Code changes to implement the TSP Page 11
• •
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
--I
AREA NOT INCLUDED
IN LOT AREA
LO ARE
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.
Proposed Development Code changes to implement the TSP Page 12
• •
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction, reconstruction or repair of streets,
sidewalks, curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed Development Code changes to implement the TSP Page 13
• 1 •
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets
A. Improvements.
1. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets; or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6. The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed Development Code changes to implement the TSP Page 14
• •
•
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use; or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards, the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
•
b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public," as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
by deed without full compliance with this title provided such an easement is the only reasonable
method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.H and 18.705.030I.
D. ,Street location, width and grade. Except as noted below, the location, width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed Development Code changes to implement the TSP Page 15
• •
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas, or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticipated average daily traffic (ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. • Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists,bicyclists, and pedestrians;
k. Access needs for emergency vehicles.
Proposed Development Code changes to implement the TSP Page 16
• •
TABLE 18:81'0.1
. 6: A. I . a T: ..:, , S .
Te it'S rest, .l I } �x v ittnc •
Arterial 60"90' a
eater 60=88' 44= 44
. . 6e 40' 2'3
a9' 14'
Residential.Acceasi Streets
tz: Through street.With:
• ' Less"Than.1500ADT 5$ 32'
Less Ttiatt. 500 ADT 464- 28' 4-4
Less Than 200 ADT 4 2 '1 2
b. Cul do sac dead end streets:
.Less Than• 500.APT 16' 28' 1-?-
LessThan 200.ADT 42-a 242- 44
t:.ct lori8;and scivc no more than.24
dwell i units)
Turn Arotinds for Dead end Streets,in 50246444s 12:radius
a
Tura-Arounds for Cul dc sac"Dead End 17'radius 14':radius
Streets.-iii Residential.Zones Only
Alley: :Residctitial 1-64. 16'
Alley: Business orIndustrial 202- 20=
Proposed Development Code changes to implement the TSP Page 17
•
Table 18.810.1
Minimum Widths for Street Characteristics
L {l1 y.
Type of Street ® de C .- J .IC ,� ' �.w�
4.0 .v mar . E 2 c �' ,� cv - io u.�.+ °a
z � 3 Co- cX a.� c�• J I
Arterial 64'-128' Varies 2 - 7 (Refer 12' N/A 6' (New Streets) 8' (Res. & Ind. Zones) • 5' 12'x"
to TSP)
5'-6' (Existing Streets) 10' (Comm. Zones)
Collector 58'-96' Varies 2 - 5 (Refer 11' N/A 6' (New Streets) 6' (Res. & Ind. Zones) 5' 12'(1)
to TSP)
5'-6' (Existing Streets) 8' (Comm. Zones)
Neighborhood Route 50'-58' 28'-36' 2 10' 8' 5'-6' 5'-6'(2) 5' N/A
Local:
Industrial/Commercial 50' 36' 2 N/A 5'-6'(2) 5' N/A
Local: Residential N/A
• Under 1500 ADT13> 54' 32' 2 8' (both sides) N/A 5'-6'(2) 5'
• Under 500 ADT(3) 50' 28' 2 N/A
• Under 200 ADT{3} 46' 24' 2 8' (one side) N/A
No Parking)
Cul-de-sac bulbs in 50' 42' radius N/A N/A N/A N
Industrial and radius
Commercial zones
Cul-de-sac bulbs in 47' 40' radius N/A N/A N/A N/A N/A
Residential zones radius
Alley: Residential 16' 16' N/A N/A N/A N/A N/A
Alley: Business 20' 20' N/A N/A N/A N/A N/A
' Medians required for 5 and 7 lane roadways. They are optional for 3 lane roadways.
2 Sidewalk widths for these streets shall be 5 ft with landscape strip: 6 ft if against curb (if permitted in accordance with 18.810.070.C).
3"Skinny Street" roadway widths are permitted only if the cross section criteria are met. Refer to corresponding cross sections (Figures
18.810.3, 18.810.4 and 18.810.5) for details and conditions.
Proposed Development Code changes to implement the TSP Page 18
• 0
„..
Figure 18.810.1
Arterials Sample Cross Sections
„-----,, -,---'7'‘
._____-_•,,,cttz., ' - '
„
-;-:;:_ .1 Ft;---=:-= -- •
,, , "ektc&-ifft,- , •
• I 5'8-10' I 5.5' 6'13ke I 12' 12' ,6'Bike t 5.5' ,8-10',.P'
H
R/W 64'-68'
F--
2 Lane 6448'R/W
— ,,--,-,---,..
"'''
I4A
,,,.--ii •
.5' 12'MediaN
8-10', 5.5',6'Bike I 12' Turn Lane , 12' -6'Bike I 5.5' ,8-10',
I 1 , I , , , I
76'-80'
R/W .I
3 Lane 761-80'R/W
5 ''' -,...,
.-7:S.-r •----
41
4,1",
:t
12'MediaN
5:8-10'. 6' .6'Bire 12 12' Turnlane i 12' ; 12' 16'Bike, 5.5' 8-10'
1 f I
100 '
R/VV -104
; I
5 Lane 1001-104'R/W
.:-.%•••" *.=.> -,.. .‹.„.
_, ,..., ..,, --..›
- ._,
—-----•-,,r,..::2.1-,
' ■., : , - -., , --- ,-
=...■,. .-.... -MEM . ,
. 12'Median/ , ,.
.5'
i5: 8-10' --1--
12' _i _12' EuraLane._ ; 12' i 12 _i; 12' l_Bike 8-10' ._;
I-- /VV 124-128'
7 Lane 124'-128'R1W
•
Proposed Development Code changes to implement the TSP Page 19
e 0
Figure 18.810.2
Collector Sample Cross Sections
- r --------. ----c,-4. ,'--
5.5' ke 11' ; 11' ,6'Bke 5 I-
.5' 6-8' .5'
t 1- -1
R/W 58'-62'
I
. • 2 Lane 58'-62'R/W
---,,.
•
p }
' )
lwir777, cil. _i
12'Median/
•5'6-8', 5.5',6'Bke 11' Turn Lane 11' 6'Bike,5.5' 6-8' •5'
I
R/W 70'-74'
. f I
3 l_ane 70'-74'RAN .
7
1 r ' ___ 2,-401/)-,.:------
- - '- —
/I ...m.,
iTimiLik. Z "Z:IEL.::::
.5' 12'Median/
i ; 6-.0' i 5.5' 11' , 11' Tuin Lane . 11 . 11' 6'Bike 5.5' 6-8' .•5.
12,61V 9T-96' I
5 Lane 92'-96'R/VV
•
Proposed Development Code changes to implement the TSP Page 20
• 0
. .
•
. ..
•
Figure 18.810.3 •
Neighborhood Routes
Sample Cross Sections
...-...,
,:,;„.• $ -4,r4i
--
„....._,..
28 5.5'. 5' ;5' ',5: 5' , 5.5' .0 32' 0 ; 5.5'
1 R/W 50' R/Vs/54' •
No Parking on One Side With Parking on Both Sides
. •
,------,J 7
-,1
MI
• . 36'
.5'
—I
5' 5.5' 6'Bike, 12' 12' 6'Bike,
1-i 1 ---i ---i ■ i
R/W 58'
I
• With Bike Lanes/No Parking
Figure 18.810.4
Local Residential Streets-<L500 vpd
•
A. Standard(sample) B. Skinny Street Option(criteria)
.--,
-- --, ...-----
, .-5
TaiF1 7-
' •-•,'Ii'wfilli—a . -‘---;''Q' . :::.,: .
: . .::.-,„', r •'.. r, r El
32' 5.' -
5' 4 5•5'i-Q Q : 5•5' 1-5' ,.. # am.
R/W 54' T: - • ; 1.4.
i. . .
1— i !■ : ,.T 7furo.. Travel Lans 'ftru..*”; ,.5' : :;
.5' .5. ;Planting (Gb...Ina) Planting:,5.i'9.
On-street Parking siamsic 5thr' i...._ 20' ..., Siols.Aik
ravenunt
<1500 vpd * :
•
, .. _.
: RIgms-d-way. :
If parking on both sides,
block length not to exceed 600 feet
Criteria:
• Queuing Plan must be submitted and approved.
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
Figure 18.810.5 .
Local Residential Streets<500 vpd
Proposed Development Code changes to implement the TSP Page 21
•
• •
A. Standard(sample) B. Skinny Street Option(criteria)
›•--
__ ::yea.-> G i?p:
li isli • \v kr dik .
5 5' : 5-54-r2 28'__ k 5.5'. 5' ;5 ® fF .. ti ..
R/W•50' ` r
T 161T
' e.e' �P.si.j rra.a lane ! 9!•
Residential Local Street/Cul-de-sac Sii.v.i k w i. 2.' "a" == y
Sla...ei
One Side On-street Parking f'^tr^^t
<500 vpd RaM-a.,l,•
•
Criteria:
• Queuing Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of(1)off-street parking space for
•
every 20 feet of restricted street frontage.
Figure 18.810.6
Local Residential Street<200 vpd
A. Standard(sample) B. Skinny Street Option(criteria) •
ri
. 9
• , = 1
A ci.
:: ,.5' 5 S.5' 24, 5,5 5 .5' !.!•w 20'f ttn..c �.�
.S•�• P4..Wy •-Vbnuel: 6'
Cul-de-sac/Residential Local Street .,...<-•y •
<200 vpd
(No parking) •
F. Future street plan and extension of streets.
•
1. A future street plan shall: .
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
-adjacent to the proposed land division. At the applicant's request, the City shall mav prepare
a future streets proposal. Costs of the City preparing a future streets proposal shall be
Proposed Development Code changes to implement the TSP Page 22
• •
reimbursed for the time involved. A street proposal may be mod ified when subsequent
subdivision proposals are submitted:
b. Identify existing or proposed bus routes, pullouts or other transit facilities, bicycle routes and
pedestrian facilities on or within 530 feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
G. Street spacing and access management. Refer to 18.705.030.H.
GH. Street alignment and connections.
1. Full street connections with spacing of no more than 530 feet between connections is required
except where prevented by barriers such as topography, railroads, freeways. pre-existing
developments, lease provisions, easements, covenants or other restrictions existing prior to May
1. 1995 which preclude street connections. A full street connection may also be exempted due to
a regulated water feature if regulations would not permit construction.
-1-. Staggering of streets making "T" intersections at collectors and arterials shall not be designed so
that jogs of less than 300 feet on such streets are created, as measured from the centerline of such
f,trcet.
—2. Spacing between local street intersections shall have a minimum separation of 125 feet.
23.. All local and minor , neighborhood routes and collector streets which abut a development site .
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such as schools, shopping
areas and parks.
45. All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed Development Code changes to implement the TSP Page 23
• •
111. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
1J. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
3K. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul-de-sac shall be measured from the centerline intersection point of the two
streets to the radius point of the bulb.along the centerline of the roadway from the near side of the
intersecting street to the farthest point of the cul de sac.
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
bM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and as approved by the City
Engineer..-
MN. Grades and curves.
1. Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet), and
--1-2. Centerline radii of curves shall be as determined by the City Engineer.not be less than 700 feet on
arterials. 500 feet on major collectors, 350 feet on minor collectors. or 100 feet on other streets;
a4
•
Proposed Development Code changes to implement the TSP Page 24
• •
intended to be posted with a stop sign or signalization, shall provide a landing averaging five
percent or less. Landings arc that portion of the street within 20 feet of the edge of the
intersecting street at full improvement.
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required; except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards.
AP.Streets adjacent to railroad right-of-w ay. Wherever the proposed development contains or is adjacent
. to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major-collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the
following:
1. A parallel access street along the arterial or major-collector;
2. Lots of suitable depth abutting the arterial or major collector to provide adequate buffering with
frontage along another street;
3. Screen planting at the rear or side property line to be contained in a nonaccess reservation along
the arterial or major=-collector; or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR. Alleys,public or private.
1. Alleys shall be no less than 20 feet in width. In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed Development Code changes to implement the TSP Page 25
• •
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks, and multi-family residential developments.
TU.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
4\'. Street signs. The City shall install all street signs, relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
W . Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XY. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
VZ.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
AAA. Street cross-sections. The final lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development, whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed Development Code changes to implement the TSP Page 26
• •
2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1-1/2 inches in thickness. (Ord. 99-22)
AB Traffic Calming. When, in the opinion of the City Engineer, the proposed development will
create a neqative traffic condition on existing neighborhood streets, such as excessive speeding, the
developer may be required to provide traffic calming measures. These measures may be required
within the development and/or offsite as deemed appropriate. As an alternative, the developer may
be required to deposit funds with the City to help pay for traffic calming measures that become
necessary once the development is occupied and the City Engineer determines that the additional
traffic from the development has triggered the need for traffic calming measures. The City Engineer
will determine the amount of funds required, and will collect said funds from the developer prior to the
issuance of a certificate of occupancy, or in the case of subdivision, prior to the approval of the final
plat. The funds will be held by the City for a period of five (5) years from the date of issuance of
certificate of occupancy, or in the case of a subdivision, the date of final plat approval. Any funds not
used by the City within the five-year time period will be refunded to the developer.
AC. A traffic study shall be required for all new developments under any of the following
circumstances:
1. when they generate a 10% or greater increase in existing traffic to high collision intersections
identified by Washington County.
2. Trip generations from development onto the City street at the point of access and the existing
ailtADT fall within the following ranges:
Existing ADT ADT to be added by development
0-3.000 vpd 2,000 vpd
3,001-6,000 vpd 1,000vpd
>6.000 vpd 500 vpd or more
3. If any of the following issues become evident to the City engineer:
a. High traffic volumes on the adjacent roadway that may affect movement into or out of the
site
b. Lack of existing left-turn lanes onto the adjacent roadway at the proposed access drive(s)
c. Inadequate horizontal or vertical sight distance at access points
d. The proximity of the proposed access to other existing drives or intersections is a potential
hazard
e. The proposal requires a conditional use permit or involves a drive-through operation
•f. The proposed development may result in excessive traffic volumes on adjacent local streets.
4. When the site is within 500 feet of an ODOT facility.
18.810.040 Blocks
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing
adequate building sites for the use contemplated, consideration of needs for convenient access,
Proposed Development Code changes to implement the TSP Page 27
• •
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
•
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2.1201,800 feet measured along the
centerline of the streets a except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or
b. For blocks adjacent to arterial streets, limited access highways, major collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is not by B.1 above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse, or drainageway, there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make arrangements with the
• City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
•
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated, and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the.minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single-family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
Proposed Development Code changes to implement the TSP Page 28
• •
•
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation, and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are.likely to be
redivided, the Commission may require that the lots be of such size and shape, and be so divided into
building-sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
A. A. Sidewalks. All industrial streets and private streets shall have sidewalks meeting City standards
along at least one side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development,even if no sidewalk exists on the other side of the street
B. Requirement of developers
1. As part of any development proposal. or change in use resulting in an additional 1,000
vehicle trips or more per day, an applicant shall be required to identify direct,safe (1.25 x the straight line
distance)pedestrian routes within 1/2 mile of their site to all transit facilities and Neighborhood Activity
Centers (schools. parks, libraries, etc.). In addition, the developer may be required to participate in the
removal of any gaps in the pedestrian system off-site if justified by the development.=
2. If there is an existing sidewalk, on the same side of the street as the development. within 300
feet of a development site in either direction, the sidewalk shall be extended from the site to meet the
existing sidewalk, subject to rough proportionality (even if the sidewalk does not serve a neighborhood
activity center)
BC.Planter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of streets where parking is prohibited
except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; or it would conflict with
the utilities, there are significant natural features (large trees. water features, etc) that would be
destroyed if the sidewalk were located as required, or where there are existing structures in close
proximity to the street(15 feet or less)-
ED. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
•
in width, and:
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
Proposed Development Code changes to implement the TSP Page 29
• •
F. Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed, then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property in question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk; -
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
FG.Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings,commercial buildings or public buildings and/or parks; and
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord. 99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
Proposed Development Code changes to implement the TSP Page 30
•
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park,playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall •
be released to the subdivider. (Ord. 99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval.. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
• the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
operation of the sewage treatment system.
18.810.100 . Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
Proposed Development Code changes to implement the TSP Page 31
• •
C. Accommodation of upstream drainage: A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
•
18.810.110 Bikeways and Pedestrian Pathways
. A. A. Bikeway extension.
1. As a standard, bike lanes shall be required along all Arterial and Collector routes and where
identified on the City's adopted bicycle plan in the Transportation System Plan(TSP).
2. Developments adjoining proposed bikeways identified on the City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3. Any new street improvement project shall include bicycle lanes as required in this document
and on the adopted bicycle plan.
- B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
1. Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
2. Minimum width multi-use paths separated from the road is eight ten
(10) feet. The width may be reduced to eight(8) feet if there are environmental or other constraints.
3. The minimum width for pedestrian only off-street paths is five(5) feet.
4. Desium standards for bike and pedestrian-ways shall be determined by the City Engineer.
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above,and:
Proposed Development Code changes to implement the TSP Page 32
• •
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer, shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information,easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement.
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common, but not the
only, such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities,unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front-foot basis.
Proposed Development Code changes to implement the TSP Page 33
• •
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section.
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City, permit fee paid, and permit issued.
B. Permit fee. .The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
• A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments) shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
Proposed Development Code changes to implement the TSP Page 34
• •
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices, and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)■
Proposed Development Code changes to implement the TSP Page 35
• •
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions in alphabetical order and renumber the remaining
definitions accordingly:
"Neighborhood Activity Center"-- A use such as schools. parks, libraries. or pools which
provide recreational or social services for mops of people.
"Queuing Plan" - A plan submitted with a proposal for skinny streets that shows the
potential queuing pattern that will allow for safe and efficient travel of emergency
vehicles, service vehicles and passenger vehicles with minimal disturbance.
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B
change the 3rd sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
Additional TSP implementation code amendments Page 1
• •
18.745.050.C.2.b
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
Additional TSP implementation code amendments Page i
� pF •
Q "MTV; o Department of Landonservation and Development
635 Capitol St. NE,Suite 150
Salem,Oregon 97301-2540
5 e John A.Kitzhaber,M.D.,Governor Phone (503) 373-0050
Director's Fax (503) 378-5518
Main Fax (503) 378-6033
Rural/Coastal Fax (503) 378-5518
TGM/Urban Fax (503) 378-2687
NOTICE OF ADOPTED AMENDMENT Web Address:http://www.lcd.state.or.us
September 19, 2002
TO: Subscribers to Notice of Adopted Plan
or Land Use Regulation Amendments
FROM: Tamara Good, Plan Amendment Program Specialist
SUBJECT: City of Tigard Plan Amendment
DLCD File Number 004-02
The Department of Land Conservation and Development(DLCD) received the attached notice of
adoption. A copy of the adopted plan amendment is available for review at the DLCD office in
Salem and the local government office. This amendment was submitted without a signed ordinance.
Appeal Procedures*
DLCD ACKNOWLEDGMENT or DEADLINE TO APPEAL: October 3, 2002
This amendment was submitted to DLCD for review 45 days prior to adoption. Pursuant to
ORS 197.830 (2)(b) only persons who participated in the local government proceedings leading to
adoption of the amendment are eligible to appeal this decision to the Land Use Board of Appeals
(LUBA).
If you wish to appeal, you must file a notice of intent to appeal with the Land Use Board of Appeals
(LUBA)no later than 21 days from the date the decision was mailed to you by the local government.
If you have questions, check with the local government to determine the appeal deadline. Copies of
the notice of intent to appeal must be served upon the local government and others who received
written notice of the final decision from the local government. The notice of intent to appeal must be
served and filed in the form and manner prescribed by LUBA, (OAR Chapter 661, Division 10).
Please call LUBA at 503-373-1265, if you have questions about appeal procedures.
*NOTE: THE APPEAL DEADLINE IS BASED UPON THE DATE THE DECISION
WAS MAILED BY LOCAL GOVERNMENT. A DECISION MAY HAVE
BEEN MAILED TO YOU ON A DIFFERENT DATE THAN IT WAS MAILED
TO DLCD. AS A RESULT YOUR APPEAL DEADLINE MAY BE EARLIER
THAN THE ABOVE DATE SPECIFIED.
Cc: Jim Hinman, Urban Coordinator DLCD
Darci Rudzinski, Regional Representative DLCD
Larry Ksionzyk, Transportation Specialist DLCD
•
Julia Hajduk, City of Tigard
<paa>yl
DEPT O
Form 2 • 0, SEP 13 2002
DLCD NOTICE OF ADOPTION LAND CONSERVATION
DEVELOPMENT
This form must be mailed to DLCD within 5 working days after the final decision
per ORS 197.610 and OAR Chapter 660- Division 18
(See reverse side for submittal requirements)
Jurisdiction: City of Tigard Local File No.: ZOA 2002-00004
(If no number,use none)
Date of Adoption: September 10, 2002 Date Mailed: September 12, 2002
(Must be filled in) (Date mailed or sent to DLCD)
Date this proposal was sent or mailed: June 19, 2002
(Date mailed or sent to DLCD)
_ Comprehensive Plan Text Amendment _ Comprehensive Plan Map Amendment
X Land Use Regulation Amendment _ Zoning Map Amendment
New Land Use Regulation _ Other:
(Please Specify Type of Action)
Summarize the adopted amendment. Do not use technical terms. Do not write "See Attached."
Amend the Tigard Development Code to reflect the Transportation System Plan and
Comprehensive Plan changes adopted in January 2002. The proposed amendments also reflect
the State of Oregon's Transportation Planning Rules (TPR)which include provision of skinny
streets. The specific Tigard Development Code sections meeting amended include: 18.120
(definitions), 18.360 (Site Development Review), 18.520 (Commercial zoning), 18.530 (Industrial
zoning), 18.705 (Access Egress and Circulation), 18.745 (Landscaping and screening)and
18.810(Street and Utility Improvement Standards).
Describe how the adopted amendment differs from the proposed amendment. If it is the same,
write "Same." If you did not give notice for the proposed amendment, write "N/A."
Same
Plan Map Change from: N/A to
Zone Map Change from: N/A to
Location: Citywide Acres Involved:
Specify Density: Previous: N/A New:
Applicable Statewide Planning Goals: 1, 2, and 12
Was an Exception adopted? Yes: _ No X
DLCD File No.: o6 l (( O `)
. Form 2
Did the Department of Land Conservation and Development receive a Notice of Proposed
Amendment FORTY FIVE (45) days prior to the first evidentiary hearing? Yes: X No: _
If no, do the Statewide Planning Goals apply. Yes: _ No:
If no, did The Emergency Circumstances Require immediate adoption. Yes: _ No:
Affected State or Federal Agencies, Local Governments or Special Districts: DLCD, Metro and
ODOT
Local Contact: Julia Haiduk Area Code + Phone Number: 503-639-4171
Address: 13125 SW Hall Boulevard
City: Tigard, OR Zip Code + 4: 97223-8189
ADOPTION SUBMITTAL REQUIREMENTS
This form must be mailed to DLCD within 5 working days after the final decision
per ORS 197.610 and OAR Chapter 660-Division 18
1. Send this Form and Two (2) Copies of the Adopted Amendment to:
ATTENTION: PLAN AMENDMENT SPECIALIST
DEPARTMENT OF LAND CONSERVATION AND DEVELOPMENT
635 CAPITAL STREET NE, SUITE 150
SALEM, OREGON 97301-2540
COPY TO:
Metro Land Use & Planning ODOT—Region 1, District 2-A
600 NE Grand Avenue Jane Estes, Permit Specialist
Portland, OR 97232-2736 5440 SW Westgate Drive,Suite 350
Portland, OR 97221-2414
2. Submit Two (2) copies of adopted material, if copies are bounded please submit
two (2) complete copies of documents and maps.
3. Please Note: Adopted materials must be sent to DLCD not later than
five (5) working days following the date of the final decision on the amendment.
4. Submittal of this Notice of Adoption must include the text of the amendment plus adopted
findings and supplementary information.
5. The deadline to appeal will be extended if you do not submit this Notice of Adoption within
five working days of the final decision. Appeals to LUBA may be filed within
TWENTY-ONE (21) days of the date, the"Notice of Adoption" is sent to DLCD.
6. In addition to sending the "Notice of Adoption" to DLCD, you must notify persons who
participated in the local hearing and requested notice of the final decision.
7. Need More Copies? You can copy this form to 8-1/2x11 green paper only ; or call the
DLCD Office at (503) 373-0050; or Fax your request to: (503) 378-5518; or Email your
request to Larry.French(cr7state.or.us —ATTENTION: PLAN AMENDMENT SPECIALIST.
• Attachment 1
CITY OF TIGARD,OREGON
ORDINANCE NO. 02-
AN ORDINANCE ADOPTING CHANGES TO THE DEVELOPMENT CODE IN ORDER ,
TO IMPLEMENT THE TRANSPORTATION SYSTEM PLAN(TSP).
WHEREAS, the TSP was developed with the help of a 12 member citizen Task Force and
addressed Transportation Planning Rule (TPR)requirements, Metro's Regional Transportation Plan
(RTP)updates and the City needs; and
WHEREAS, Tigard adopted its Transportation System Plan in January 2002 with the intent to
return at a later date with amendments to the development code; and
WHEREAS, the'TSP is not fully implemented until changes have been made to the development
code; and
WHEREAS, development code changes have been prepared which implement the TSP
recommendations, address TPR narrow street requirements and clarify existing code language as
shown in Exhibits A-1 through A-4;and
WHEREAS, the Planning Commission held a public hearing, which was noticed in accordance
with the City standards, on August 5, 2002 and voted to forward the amendments to the City
Council,and
WHEREAS, the Citizen Involvement Team was informed of the proposed changes and of the City •
Council hearing at its September 5,2002 meeting; and
WHEREAS, the City Council held a public hearing on September 10, 2002, which was noticed in
accordance with City standards, and voted to approve the TSP and Comprehensive Plan changes
proposed,and
WHEREAS, the decision to adopt was based on compliance with Oregon Statewide Planning
Goals#1, #2, and #12; OAR 660; the Regional Transportation Plan, Comprehensive Plan policies
1.1.1(a), 2.1.1, 8.1.1, 8.L2, 8.1.3, 8.1.5 and 8.2.3 and Community Development Code chapter
18.380.020 and 18.390.060.G as detailed in the TPR compliance matrix (Exhibit B) and the staff
report/Planning Commission recommendation(Exhibit C),
NOW,THEREFORE,THE CITY OF TIGARD ORDAINS AS FOLLOWS:
SECTION 1: The attached Development Code Changes (Exhibit A-1 through A-4) are
adopted based on the findings in the staff report and the supplemental TPR
compliance matrix.
•
ORDINANCE NO. 02-
Page 1 of 2 (updated 8/19/02 12:17 PM)
•
SECTION 2: If any section of the TSP or resulting Development Code changes trigger a
Measure 7 claim, the City may make a determination regarding whether the TSP
or Development Code provision should be applied on a case by case basis.
SECTION 3: This ordinance shall be effective 30 days after its passage by the Council,
signature by the Mayor, and posting by the City Recorder.
PASSED: By vote of all Council members present after being read by number
and title only,this day of , 2002.
•
Catherine Wheatley, City Recorder
APPROVED: By Tigard City Council this day of ,2002.
• •James E. Griffith,Mayor
•
Approved as to form:
City Attorney
Date
i:Urpin\julia\TSP\implementation\cc packet\TSP implementation ord.doc
ORDINANCE NO. 02-
Page 2 of 2 • (updated 8/19/02 10:15 AM)
• Exhibit A-1
Chapter 18.705
ACCESS,EGRESS,AND CIRCULATION
•
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply.The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures(see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. . When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
.,presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures,or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title,provided:
I. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
Proposed Development Code changes to implement the TSP Page I
4111 •
•
2. Copies of the deeds, easements,leases or.contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping,pavement markings, or contrasting pavement materials are used. Walkways shall
be.'a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards; .
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes. Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director,the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health,safety, and general welfare.
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to collector or arterial streets shall be considered only
Proposed Development Code changes to implement the TSP Page 2
if there is no practical alternative way to access the site. If direct access is permed b� the
City the_applicant will_be .required to mitigate for any safety or_neighborhood traffic
management (NTM)impacts deemed applicable by the City Engineer. This may include, but
will not be limited to the construction of a vehicle turnaround on the site to eliminate the need
for_a to back out onto the road _ay__
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street, other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
H. Access Management
1_t1n access_relnrt shall be submittedWith_all ne v__developrnent_proposals which verifies design
of driveways and streets are safe by meeting_adequate stac_kingaeeds,siglit distance and
deceleration standards as set by ODOT,Washington Comity.the City and AASHTO
(amending on jurisdiction of facility
2. Driveways shall not be permitted to be placed in the influence area of collector or arterial street
intersections. Influence area of intersections is that area where queues of traffic commonly
form on approachio an intersection. The minimum driveway setback from a collector or
arterial streetintersecttionshall be 15_feet,.neasured_ om theij hl of-way lineof the
intersecting street to_the throat of the p_roposed driveway, The setback may._be greater
de nding upj n t e influence area,asdete,,,►ined room City Engineer review of a traffic impact
report submitted by_the ap_p_lic nt's traffic engineer. Ina case where a project has less than 150
feet of street frontage.the applicant must explore any option for shared access with the adjacent
parcel. If shared access is no possible or_practical,the driveway shall be placed as far from the
intersection as possible,
3. The minirnmarrlspacing of dri_yeways and streets along collector shall be 209 feet The
minimum spacingof driveways jstreets along_an arterial shall be 60k feet.
4. The minimumspacingotheal streets aIonig__a local street shall be 125 feet. .
Minimum access requirements for residential use.
1. Vehicular access and egress for single-family,duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less than as provided in Table
18.705.1 and Table 18.705.2;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Numb, r Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
1 or 1 15' 10'
3-6 1 20' 20'
Proposed Development Code changes to implement the TSP Page 3
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI-FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15'if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24'if two-way
or
2 30' 15'if one-way: Curbs and
5'walkway required
50-100 2 30' 24' Curbs and 5'walkway
required
2. Vehicular access to multi-family structures shall be brought to.within.50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
`least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed Development Code changes to implement the TSP Page 4
• •
TABLE 18.7053
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site,it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets,upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles; or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health,safety,and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties,parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic,access and parking area plans shall provide
efficient sidewalk and/or pathway connections,as feasible,between neighboring developments
or land uses;
4. A decision by the.Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
II procedure,as regulated by Section 18.390.040,using criteria contained in Section 18.370.020 C3
Proposed Development Code changes to implement the TSP Page 5
r`
•
Exhibit A-2
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator_
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet;provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2-1/2 stories or 35 feet,whichever is less,provided:
Proposed Development Code changes to implement the TSP Page 6
•
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420,Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on fmdings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line; and
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed Development Code changes to implement the TSP Page 7
•
• •
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings; and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and -
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in. accordance with Chapter 18.350, Planned Developments, .Chapter 18.430,
Subdivisions, or Chapter 18.420,Partitions,and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
A. Additional setback from speeded-roadways. • - . - . . . , .' , : _ . . - .
Proposed Development Code changes to implement the TSP Page 8
•
•
1. Arterial Streets. The required setback distance for buildings on arterial streets is the setback
. . - - - - - -. . - .. . .. • - - -. - . : . . , . , -
Street Names Requirement
Arterial-Streets.
SW Pacific Highway(within City Limits) 50 feet
SW Hall Boulevard 45 feet •
intersections with Old Scholls Ferry Road) 50 feet
. • ! . . - - .. . -: -. . - . : . . . . ..
Upper Boones Ferry) 45 feet
SW Upper Boones Ferry Road 45 feet
Corrector Streets.
SW Ash Avenue 30 feet
SW Atlanta Haines(east of 68th Avenue) 30 feet
SW Atlanta(west of 68th Avenue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
30-feet
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
Hall Boulevard) 30 feet
SW Franklin Street 30 feet
SW Gaarde Street 30.feet
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
,SW Hunziker Road 30 feet
SW Main Street 30 feet
SW McDonald Street 30 feet
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak(west of Hall Boulevard) 30 feet
SW Pfafflc Street 30 feet
Old Scholls Ferry Road) 30 feet
Proposed Development Code changes to implement the TSP Page 9
• •
TABLE 1Q 730 1 (CON'')
Street Names Requirement
SW Summerfield Drive 30 feet
SW Tiedeman Avenue 30 feet
SW Tigard Street 30 feet
SW Walnut Street 30 feet
SW 68th Avenue 30 feet
SW 68th Avenue(south of Pacific Highway) 30 feet
SW 70th Avenue(south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
- . . . 1 , . ° - .. . .. .
3. The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
_
- of-way width less than required by its functional classification on the City's transportation plan map
and, in such case, the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
. . . , Y. .
B. Distance between multi-family residential structure and other structures on site. -
•
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development,the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15-foot
separation;
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections; and
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
Proposed Development Code changes to implement the TSP Page 10
• •
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone,the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
Iots.
B. When one abutting property has a non-conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats,trailers, campers, camper bodies,house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following: -
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
D. Projections into required yards.
Proposed Development Code changes to implement the TSP Page 11
•
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
AREA NOT INCLUDED
IN LOT AREA
\%\\\cr \\
[..,()
F. Front yard determination. The owner or developer of a flag lot may determine the.location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.
Proposed Development Code changes to implement the TSP Page 12
• •
Exhibit A-3
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets,sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction,reconstruction or repair of streets,
sidewalks,curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
fit application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type I1 procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed Development Code changes to implement the TSP Page 13
•
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets
A. Improvements.
1. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets; or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6` The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands,steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed Development Code changes to implement the TSP Page 14
• •
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use;or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards;the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
b. The recommendation, if any, shall be based itipon a fmding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public,"as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
.13sy deed without full compliance with this title provided such an easement is the only reasonable
m'thod by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207; _
2. Access shall be in accordance with Sections 18.705.030.11 and 18.7O5.03OI.
D. Street location, width and grade. Except as noted below, the location,width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed Development Code changes to implement the TSP Page 15
• •
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas,or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
•
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticipated average daily traffic(ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide. guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists,bicyclists,and pedestrians;
k. Access needs for emergency vehicles. -
Proposed Development Code changes to implement the TSP Page 16
o •
LE- 1$1i.8104
L * _ ' ISA.
Type ofStitet ‘•
•
Arterial mt#44.,
M401tC.0110443f
MiliPI70410610f 604 ;PS
a, ,Through street with:
•
Less Than t. 50'
Less Than 500 ADT
4e ff7
Let:,:o.Than 200 APT -E•1
b. Cul de sac Aearl;en4 streets;
. Less Than 5001DT
Less Than .200-APT 441
4. Iiiagtti3*.4
4ginit4s414 $.6!.radius
Alletesictential
•
•
•
Proposed Development Code changes to implement the TSP Page 17
Table 18.810.1
6` Minimum Widths for Street Characteristics
,.
Cti. C
Type of Street 3 u. I
0, ..... j C
. ;:
.,
__
Ar erial 64'-128' Varies 2-7 (Refer 12' NLA 6 (New Street 61.(gesAJ.nd. Zones 5 10 0
to TSP)
5'-6'(.Existing.atr_eet.$) 1.0' (Cmitr. onea).
Collector 58'-96' Varies 2- 5 (Refer If NLA 6' (New Streets) 6' (Res. & Ind. Zones) 5 12'x15
- to TSP) •
5'-6''Existing Streets) 8' (Comm, Zones)
Neigkai.orhoo .Bo t 50'-58' 2.8_!f16: - 2 1Q'. 5_6: 5:_6'2) 5 NIA
LQ.oal: .
lnslu_slrra.1/Commercial 5S2. 36' 2 NLA 54±2) 5' .NLA
Local: Residential W6
• Under 1500 ADT 54'/5043} 32728435 2 8' (both sides) NLA 5'-6'x�5
• Under 500 ADT 50746°J 28'I2446j 2 8' (one side) NIA
• Under 200 ADT , 46742'x35 24720435 2 No Parking.) N ,
Cul-de-sac bulbs in 5Q 42' radius NLA NLA NLA NLA
Industrial and radius
Commercial zones
Cul-de-sac bulbs in 4Z 40' radius NIA NLA NIA VILA NLA
Residential zones radius
Alley: Residential 16! 162' N/A N/A NL NIA N/A
Alley: Business • 2Q 20' NIA N/A N/A N/A N/A
1 Medians required for 5 anti 7 lane roadways. They are optional for 3 lane roadways.
1 Sidewalk widths for these streets shall be 5 ft with landscape strip: 6 ft if against curb (if permitted in accordance with 18.810.070.C).
3"Skinny Street" roadway widths are permitted where cross section and review criteria are met. Refer to corresponding cross sections
'4 - ; ; 0.3 ; 1 ' -i. : 1 • • .I! •i•• •ii.
Proposed Development Code changes to implement the TSP Page 18
41,
•
Figure 18.810.1
Arterials Sample Cross_Sections
___,,,,, .-
.5'8-10'5.5' 6'ffKe• 12' 12' .6'Bile 5.5' ,810'-5'
i t I . --1-4
R/W 64' '-68
i
2 Lane 641-68'RAN
— ....
, • .,_:-,__..
Ii ........ 1
■. .- 1--- -..--:::---_-- "-;i. ""■...m.,01$1..."..„.:,Lof
5' 12'Median/ .5'
I 18-10'1 5.5'16'Mel 12' Turn Lane 12' 6' 5.5' -10'
1 1 I 81(ei 1 8 I 1
R/W 76'-80'
4 4
3 Lane 76'-80'R/W
IN: -N1 9, . „ '4—N1 - . •'—(1
;I —_.„. )1
1....„.—....,;, :aA IMMO
12'Median/
6' I 6'Bike 12'—I 12' jun Lane_i_ 12' ____i_ 12' _F6'llice 5.5' 4310' r5
1--1- I i--
RM 100'104'
5 Lane 100t104'RIW
S--.• ->
'' '.. D......... -,- .-
2s: r.i
4 q
1(.^•' 9
,
!
•mlatv." -.maw ; •
7.ria' .L--4--•--*---,, -"""' ...%..H.'7
12'Median/ .5'
8-10' I 5.5 ,61311e, 12' , 12' 1 12' :Turn Lone , 12' I 12' 1 12' ,Bike 6's 5.5' 1 8-10'
1 R/W 124.-128'
'
— 7 Lane 1241-128'R/W
—
S.
Proposed Development Code changes to implement the TSP Page 19
•
4114
•
Figure 18.810.2
Collector Sample Cross Sections '
' � y�
N`y
6-8',5.5' i_631cei- 111 11' i6'Bdce 5.5' f 6-8'f-5•
F--— — RPN 58'-62'
2 Lane 58'-62'R/W
f -BFI :EA
12'Median/
15f 6-8'1 5.5',6'B&ce I 11' Turn Lane 11' f6':;of 5.5' i6-8
f – --
RAN 70'-74' {
3 Lane 70'-74'R/W
•
•
5' 12'Median/ 5
H 5.5' i 6'Bike 11' 11 gym Lone 11' 11' 16'Bike f 5,5' 6-8' 1.1*
t — –— R/W 92'-96' c
5 Lane 921-96'R/W
•
•
•
•
•
•
•
•
Proposed Development Code changes to implement the TSP Page 20
•
•
•
i
Figure 18.810.3
1`_e_ighb_o_thood Route
Sample Cros . ec ions
`, r
}
't`t if r I• . r '{ P°
i5, 5' ;5.5'I O 28' 15.5' 5' 5' j5' 5' 5.5',t� 32' A 5.5' S, 5:
I R/W 50' -I I R/W 54' - --— —I
No Parking on One Side With Parking on Both Sides
r
I 36' i
51 5' ! 5.5' !6'Bike 1 12' 1 12' 16'Bikes 5.5' ! 5' 5'
I R/W 58' I
With Bike Lanes/No Parking
Figure 18.810.4
Local Residential Streets-<1,500 vpd
A. Standard(sample) B. Skinny Street Option(criteria)
%, Y „
f r a_.: 3 n;` :Ai",
5' ! 5.5'I 0 32' Q 15.5' 1 5. 5.' „ :.e '_` �a
R/W 54' . : ; , 7 i µ' I * I
A' 'ir,.ntcy (a+elno) 'n.etty a.r
On-street Parking Stalmollt st"' id '"'►Skl..,a
<1500 vpd *
If panting on both sides,
block length not to exceed 600 feet Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
Proposed Development Code changes to implement the TSP Page 21
•
• •
•
Figure 18.810.5
Local Residential Streets<500 vpd
A. Standard(sample) B. Skinny Street Option(criteria)
cs t v7• _
+ 5' 5.5'}--Q 28' 5�5'}5' }5 ® �l' 1'1-el C4 !r
R/W 50' ',•s
` e.a• :'ors' nyaLams e.5. •:
Residential Local Street/Cul-de-sac 5'.
, 24. 1.4414/:
,
One Side On-street Parking
w•
<500 vpd 1.,114-e,..ay.
Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of(1)off-street parking space for
• every 20 feet of restricted street frontage.
F 0_1181Q.6
Local Residential Street<200 vpd
•
A. Standard(sample) B. Skinny Street Option(criteria)
°fie 5 e 1
tr.•• _ Q�
5' •5.5 24' 5' 5'
i a.r 7D nw..rt ar }
5' ' ' 5. '
r
pbwyM. .h ._7•
k 1 SY.op ",* 5'67 5414...4‘
k--- R/W 46' 1 .�
Cul-de-sac/Residential Local Street R -o
•
<200 vpd Criteria:
• Must provide a minimum of(1)off-street parking space
(No parking) for every 20 feet of restricted street frontage.
• No parking permitted within 30 feet of an intersection.
•
F. Future street plan and extension of streets.
1. A future street plan shall:
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall-may prepare
a future streets proposal. Costs of the City__preparing a future_streets proposal shall be
Proposed Development Code changes to implement the TSP Page 22
•
reimbursed .for the_iime involved A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus routes, pullouts or other transit facilities,bicycle routes and
pedestrian facilities on or within 530 feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
G. Streetspacin_ and acre.s management Refer to 18 705.030.IL
G.H. Street alignment and connections.
1. Full street connections with spacing of no more than 530 feet between connections is required
except where_prevented bylharriers such as topography railroads, freeways, :pie_ xisting
develonments,_leao_p or visions, easements, covenants or other restrictions existing prior to May
1_, 1295 which_preclude street connections. A fu11 street connection may also be exem_ptect±ue to
a regulated water feature if regulations would not permit constiuctom
-_ . _ .. , « ,, . . . . . - .
street.
23. All local and-minor; neighborhood routes and collector streets which abut a development site I
shall be extended within the site. to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such.as schools, shopping
areas and parks.
45. All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed Development Code changes to implement the TSP Page 23
•
#II. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
Ti. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
JK. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul-de-sac shall be measured from the centerline intersection point of the two
streets to the radius point of the bulb.: _ -- - .- - - - -- .• - - --• - - . -
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
LM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets: Street names and
numbers shall conform to the established pattern in the surrounding area and as approved by the City
Engineer.-
MMV. Grades and curves.
1.-‘ Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet),and:
1-2. Centerline radii of curves shall be as determined by the City_Engineer.not be le than 700 f et on
and
Proposed Development Code changes to implement the TSP Page 24
• •
percent or less. Landings are that portion of the street within 20 feet of the edge of the
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts,_ wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required;except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards.
OP.Streets adjacent to railroad right-of-way. Wherever the proposed development contains or is adjacent
to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major-collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major-collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts: The design shall include any of the
following:
1. A parallel access street along the arterial or major-collector;
2.. Lots of suitable depth abutting the arterial or major-collector to provide adequate buffering with
frontage along another street;
3. Screen planting at the rear or side property line to be contained in a nonaccess reservation along
the arterial or major collector;or I
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
4a, Alleys,public or private.
1. Alleys shall be no less than 20 feet in width. In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed Development Code changes to implement the TSP Page 25
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks,and multi-family residential developments.
T1J.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director.and approved
by the Commission.
UV. Street signs. The City shall install all street signs, relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be.provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to fmal plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
WX. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XY. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
Z.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
ZAA. Street cross-sections. The fmal lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall,also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development,whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed Development Code changes to implement the TSP Page 26
• •
2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1-1/2 inches in thickness. (Ord. 99-22) •
AB__ _ i c .,ina When '1 th- ()titian • t - Cit •i ee th- .ro•os-d 'even. -it w'
r-ate . -•. i e t affi olditio • exis • • n-i•h•orh••d t -ets sucl .s - es iv- Ss--d'1• t1
•- - ••- m. •e r-• i -• • • •yid- t . 'c c. fin• i-asu 1- - e.su -s ii- .- e. _'re•
w't ' t - •ev-lo• e a • • el it- - see ed a•• o• late. As .n . t-r -tive th- devel.•e a
be required to deposit funds with the City to el• for traffic calmi measures that become
- -ss.i (31 - Ii- •-v-I••i el i • ••-d .i_ ,- t 1•'j -- . -te i - h. le . .
traffic from the develo•ment has trictoered the need for traffic calming L=.s -s T1_- iLv
will .et-niin- th- . Is _nt • fu1• -• _ir-• .1• wil o ect .idf n•s rou tie •e eo.e •rio totl -
issuance of a certificate of occupancy or in the case of subdivision prior to the approval of the final
plat The funds will be held by the Cit f• . •er'•• • f e 5) years from the date of issuance of
cer ificate of occupancy, or in the case of a subdue ton the date of final lat approval. Any funds not
used by the City within the five-year time period will be refunded to the developer.
Traffic study
1. A c is y shall be requiredfor alLnew or_expandedjtses or developrne i tuider any he
following circumstances:
a_ when theygenerate a 10% or greater increase in existing affic to_high_clliaion intersections
identified by Washington County
b. Tripgenerations_from development onto the City street at the point of access and the existing
adtADT fall within the following ranges:
Existin CDT ADT to be added by devejopetent
0-3,000 vpd 2_,000 vpd
MAO 14 00v d
>6,000 ypd 500 vpd_or more
c. Iff any of the followiri ues become evident to the ity engineer:.
(i) High traffic volumes on the adjacent roadway that may affect movement into or out of the
site
(2) Lack of existing left-turn lanes onto the adjacent roadwa at the •ro,osed access drive()
La) Inadeau.to horizontal or vertical sight distance at access points
(4) The proximity of the proposed access to other existing drives or intersections is a potential
hazard
5 e roposal require_s_a conditional use permit or involves a drive-through_oReratien
(6) The proposed development may result in excessive traffic volumes on adjacent local streets.
2. In addition a traffic study may be required for all new or expanded uses or developments under
any of the following circumstances:
a. when the site is within 500 feet of an ODOT facility and/or
b. trip generation_from a development adds 300 or more vehicle trips per day to an QDOT facility
Proposed Development Code changes to implement the TSP Page 27
and/or
c. trip_generation from a development adds 50 or more peak hour trips to an ODOT facility.
18.810.040 Blocks
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing ,
adequate building sites for the use contemplated, consideration of needs for convenient access,
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2,00000 feet measured along the
c nterline of the stets right e way line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or.
b. For blocks adjacent to arterial streets,limited access highways,major-collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is net-possibleexempted by B.1 above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse,or drainageway, there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make- arrangements with the
City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated, and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
Proposed Development Code changes to implement the TSP Page 28
•
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, fora width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C)applies, or unless the lot is for an attached single-family dwelling unit,in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided ex cept where they are essential to provide separation of
residential development from major traffic arterials or to overcome specific, disadvantages of
topography and orientation,and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some, future time are likely to be
redivided, the Commission may require that the lots be of such size and shape, and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public.facilities.
18.810.070 Sidewalks
A,A,,—Sidewalks. All industrial streets an5lprirate streets shall have sidewalks meeting City standards
along at leastone side of the street. All other streets shall have sidewalks.meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development,even if no sidewalk exists on the other side of the street
B, Requirement of developers
1 • .. I a. _ devel•. -,t ._. ., a o ch. 'e _.. u e re • • • . •,. •dd• ".n: 1 111
vehicle trips or more per day, an applicant shall be_required to identifydirect, safe (1.25 x the straight line
.distance) pedestrian routes within 1/2 mile of their site to all transit facilities and Neighborhood Activity
Centers (schools,_parks, libraries. etc.). In addition, the developer may be required to participate in the
remove o a aps_ n_the pedestrian systernoff-site if justified by the development.
2, If there is an existi ng sidewalk,on the same side of the street as the development.within 300
feet of a development site in either direction, the sidewalk shall be extended from the site to meet the
existin sidewalk. sub-ect to rough proportionality (even if the sidewalk does not serve a neighborhood
aetivi center).
BC.,Planter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of. - . street • - ... - : • . .•
adjacent to the curb, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; of it would conflict with
the utilities - .re s'a ifican at a ea .e are . -e . er fea A - -tc that .uld .-
destroyed if the sidewalk were located as required, or where there are existingstructures in close
proximity to the street (15 feet or less)-Additional consideration for exempting the planter strp
requirement may be .iven on a case by case basis if a property abuts more than one street frontage,
Proposed Development Code changes to implement the TSP Page 29
• •
FD. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
in width, and:
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
EF.Application for permit and inspection. If the construction of a sidewalk is not included in a I
performance bond of an approved subdivision or the performance bond has lapsed,then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property in question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
FG.Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists.for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings,commercial buildings or public buildings and/or parks; and
Proposed Development Code changes to implement the TSP Page 30
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord.99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park,playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may requite the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park,playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord. 99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
.operation of the sewage treatment system.
18.810.100 Storm Drainage .
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system; .
Proposed Development Code changes to implement the TSP Page 31
•
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
, Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
18.810.110 Bikeways and Pedestrian Pathways
A. A. Bikeway extension.
1. As a standard, bike lanes shall be required along all Arterial a_ , '. -c • • . s and where
identified on the City's adopted bicycle plan in the Transportation System Plan (TSP).
2Developments adjoining proposed bikeways identified on the _ City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3. Any new street improvement project shall include bicycle lanes as required in this document
and on the adoptedhicycle plan.
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
1. Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
2. Minimum width multi-use paths separated from the road is eight-ten
(10)feet. The width may be reduced to eight(8) feet if there are environmental or other constraints.
width for pedestrian onlyoff-street paths is five (5)feet.
for hike and pedestrian-ways_s_ball be determined by the City ineer
Proposed Development Code changes to implement the TSP Page 32
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above, and:
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer,shall be constructed prior to the surfacing of the streets;and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the'development
plan or in the explanatory information,easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement. •
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common,but not the
only,such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
Proposed Development Code changes to implement the TSP Page 33
• •
_-
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities,unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front-foot basis.
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City,permit fee paid, and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
•
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Proposed Development Code changes to implement the TSP Page 34
.•
• •
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments)shall be a part of the City's adopted installation standard(s);other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
•
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason,it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices,and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)
Proposed Development Code changes to implement the TSP Page 35
• •
• Exhibit A-4
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions.in alphabetical order and renumber the remaining
definitions accordingly:
"Neighborhood Activity Center"— A use such as schools, parks, libraries, shopping as
are ,
em plovment centers or pools which provide recreational or social services for groups of
people.
"Traffic Flow Plan" — A plan submitted with a proposal for skinny streets that shows the
potential queuing_pattern that will allow for safe and efficient travel of emergency
vehicles service vehicles and p assert•er vehicles with minimal disturbance. This ma
include a combination of strategic driveway locations,turnouts or other mechanisms
which will foster safe and efficient travel.
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
•
18.520.020.B
change.the 3`d sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets.
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more collector streets.
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street .
change to:
Additional TSP implementation code amendments Page 1
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
18.745.050.C.2.b
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street. -
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or collector street.
•
Additional TSP implementation code amendments Page 2
TPR Compliance Matrix Exhibit B
Attached are the TPR requirements with an explanation of how they are addressed in the existing City of Tigard
Development Code and in the proposed amendments.
(Where there is a dashed line- it indicates that there is not a standard to be addressed,just an intro in to the
standards.)
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(3) Local governments shall adopt land use or subdivision
regulations for urban areas and rural communities as set forth •
below. The purposes of this section are to provide for safe and
convenient pedestrian, bicycle and vehicular circulation
consistent with access management standards and the function
of affected streets, to ensure that new development provides
on-site streets and accessways that provide reasonably direct
routes for pedestrian and bicycle travel in areas where
pedestrian and bicycle travel is likely if connections are
provided, and which avoids wherever possible levels of
automobile traffic which might interfere with or discourage
pedestrian or bicycle travel. . .
(a) Bicycle parking facilities as part of new multi-family 18.765.050.E states the minimum
residential developments of four units or more, new retail, parking requirements for all use
office and institutional developments, and all transit transfer types. This is required as part of
stations and park-and-ride lots; any land use review.
(b) On-site facilities shall be provided which 18.765.050 provides bike parking 18.810.070 is being amended to include a
accommodate safe and convenient pedestrian and bicycle design standards requirement of the developer to show connections
access from within new subdivisions, multi-family to neighborhood activity centers within %Z mile of
developments, planned developments, shopping centers, and 18.705.030.F (Access, Egress and development and require consideration of
commercial districts to adjacent residential areas and transit Circulation—required walkway improvement requirements depending on
stops, and to neighborhood activity centers within one-half location) addresses walkway proportionality. The amendment also required the
requirements for multi-family, removal of gaps in the sidewalk within 300 feet on
Page 1
•
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
mile of the development. Single-family residential industrial or commercial the same side of the street as a development
developments shall generally include streets and accessways. development. (subject to rough proportionality).
Pedestrian circulation through parking lots should generally
. be provided in the form of accessways. 18.810.040 (Street and Utility
Improvement Standards-Blocks)
addresses pedestrian connections
when full street connections are
. not possible
18.810.070 (sidewalks)requires
all public streets to have
sidewalks
(A) "Neighborhood activity centers" includes,but 18.120.030 is being amended to include a
is not limited to, existing or planned schools, parks, definition of Neighborhood Activity Center.
shopping areas, transit stops or employment centers;
(B) Bikeways shall be required along arterials and Sidewalks currently are required 18.810.110.A is amended to include the
major collectors. Sidewalks shall be required along along all public streets. requirement that bike lanes be located on all
arterials, collectors and most local streets in urban areas, Development code does not have arterials and collectors and any additional routes
except that sidewalks are not required along controlled a bike lane requirement but refers identified in the TSP for any new construction or •
access roadways, such as freeways; to the City's comprehensive plan. improvement project.
• (C) Cul-de-sacs and other dead-end streets may be 18.810.030.K regulated cul-de-
used as part of a development plan, consistent with the sacs and states that they can't be
purposes set forth in this section; more than 200 feet long. IF a
variance is granted and the cul-
de-sac
is greater than 300 feet,
pedestrian connections are
required. This is in addition to .
the block length standards which .
may also require additional
pedestrian connections through a �
block.
Page 2
•
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(D) Local governments shall establish their own 18.810 establishes standards that There are amendments which address street
standards or criteria for providing streets and accessways regulate street spacing and block spacing and block lengths, however, they continue
consistent with the purposes of this section. Such lengths intending on limiting out to limit out-of-direction travel and provide greater
measures may include but are not limited to: standards for of direction travel. clarification to increase efficiency and safety.
spacing of streets or accessways; and standards for
excessive out-of-direction travel;
(E) Streets and accessways need not be required where 18.810.040—Block length
one or more of the following conditions exist: standards provide for this
(i) Physical or topographic conditions make a exception in the standard.
street or accessway connection impracticable.
Such conditions include but are not limited to
freeways, railroads, steep slopes,wetlands or
other bodies of water where a connection could
not reasonably be provided;
(ii) Buildings or other existing development on
adjacent lands physically preclude a
connection now or in the future considering the
potential for redevelopment; or
(iii) Where streets or accessways would violate
provisions of leases, easements, covenants,
restrictions or other agreements existing as of
May 1, 1995 which preclude a required street 410,
or accessway connection.
(c) Where off-site road improvements are otherwise ' Any road is required to be
required as a condition of development approval, they shall constructed to the standards
include facilities accommodating convenient pedestrian and called for in our code. As shown
bicycle travel, including bicycle ways along arterials and within this matrix, the code
major collectors; requires sidewalks but additional
amendments have been made to
Page 3
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
define required bikeway •
locations.
(d) For purposes of subsection(b) "safe and convenient"
means bicycle and pedestrian routes, facilities and
improvements which:
(A) Are reasonably free from hazards,particularly The City's Municipal code
types or levels of automobile traffic which would interfere prohibits obstructions on public
with or discourage pedestrian or cycle travel for short sidewalks
trips;
(B) Provide a reasonably direct route of travel The access standards,block
between destinations such as between a transit stop and a length standards and requirement
store; and for sidewalks provides a In addition, an amendment is proposed to have the
(C) Meet travel needs of cyclists and pedestrians reasonably direct route of travel developer review routes within 300 feet
considering destination and length of trip; and considering between destinations and meets (approximately 1/4 mile) from the development site
that the optimum trip length of pedestrians is generally 1/4 the travel needs of cyclists and and, if proportional, make necessary
to 1/2 mile. pedestrians improvements to complete"gaps"
(e) Internal pedestrian circulation within new office parks 18.705.030.E requires walkways
and commercial developments shall be provided through within commercial developments
clustering of buildings, construction of accessways, walkways
and similar techniques.
.) To support transit in urban areas containing a
population greater than 25,000,where the area is already
served by a public transit system or where a determination has
been made that a public transit system is feasible, local
governments shall adopt land use and subdivision regulations
as provided in(a)-(f)below:
(a) Transit routes and transit facilities shall be designed to SDR standards 18.360.090.11
support transit use through provision of bus stops, pullouts requires development to provide
and shelters, optimum road geometrics, on-road parking transit amenities as required by
Page 4
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
restrictions and similar facilities, as appropriate; tri-met during the development
review(if proportional and
justified)
(b) New retail, office and institutional buildings at or near
major transit stops shall provide for convenient pedestrian
access to transit through the measures listed in(A) and (B)
below.
(A) Walkways shall be provided connecting
building entrances and streets adjoining the site; 18.705.030.f
(B) Pedestrian connections to adjoining properties
shall be provided except where such a connection is 18.810.070—sidewalks
impracticable as provided for in OAR
660-012-0045(3)(b)(E). Pedestrian connections shall •
connect the on site circulation system to existing or
proposed streets, walkways, and driveways that abut
the property. Where adjacent properties are
undeveloped or have potential for redevelopment,
streets, accessways and walkways on site shall be laid
out or stubbed to allow for extension to the adjoining
property;
(C) In addition to (A) and(B) above, on sites at
major transit stops provide the following: 18.360.090.11 requires •
•
(i) Either locate buildings within 20 feet of consideration of transit facility 111"
the transit stop, a transit street or an improvements as part of
intersecting street or provide a development review(which
pedestrian plaza at the transit stop or a covers ii to v). Building
street intersection; • placement standards are already
(ii) A reasonably direct pedestrian in place in the Tigard Triangle
connection between the transit stop and and as part of the Washington
building entrances on the site; • Square Regional Center.
(iii) A transit passenger landing pad Additional standards for building
Page 5
660-12-0045 • How Addressed in current code Proposed amendments
TPR Requirement
accessible to disabled persons; placement outside of these transit
(iv) An easement or dedication for a oriented areas are not appropriate.
passenger shelter if requested by the
transit provider; and.
(v) . Lighting at the transit stop.
Local governments may implement 4(b)(A) and (B) While not specifically designated
ive through the designation of pedestrian districts and pedestrian districts,the Tigard
adoption of appropriate implementing measures regulating Triangle and the Washington
development within pedestrian districts. Pedestrian districts Square Regional Center
must comply with the requirement of 4(b)(C) above; implement the requirements of
4(b) (C)
(d) Designated employee parking areas in new 18.765.030.F required parking
developments shall provide preferential parking for carpools lots in excess of 20 long-term
and vanpools; parking spaces to provide
preferential long-term carpool
and vanpool parking for
employees and other visitors to
the site.
(e) Existing development shall be allowed to redevelop a Not specifically provided for,but
Iprtion of existing parking areas for transit-oriented uses, would not be disallowed since
duding bus stops and pullouts,bus shelters,park and ride nothing on the code prohibits it.
stations, transit-oriented developments, and similar facilities,
where appropriate; .
(f) Road systems for new development shall be provided ,18.810 has street standards that
that can be adequately served by transit, including provisions provides for adequate width of
of pedestrian access to existing an identified future transit pavement and turning radius, etc
routes. This shall include, where appropriate, separate that will provide for transit.
accessways to minimize travel distances. Sidewalks are required along all
public streets
Page 6
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement ,'
(g) Along existing or planned transit routes, designation Existing zoning along transit
of types and densities of land uses adequate to support transit. routes is transit supportive—no
changes are needed
(5) In MPO areas, local governments shall adopt land use The Tigard Triangle area,
and subdivision regulations to reduce reliance on the Washington Square Regional
automobile which: Center area and Central Business
(a) Allow transit oriented developments (TODs) on lands District zone have provisions for
along transit routes; mixed use development and
street and design standards which
(b) Implements a demand management program to meet encourage transit oriented
the measurable standards set in the TSP in response to 660- development
012-0034(4).
(6) In developing a bicycle and pedestrian circulation plan TSP provides bike and pedestrian Proposed amendments specifically require
as required by 660-012-0020(2)(d), local governments shall master plan. The development pedestrian or bike improvements if shown on 4Ih
identify improvements to facilitate bicycle and pedestrian code currently requires walkways pedestrian or bikeway plan, if roughly
trips to meet local travel needs in developed areas. and sidewalks, however we need proportional.
Appropriate improvements should provide for more direct, to amend the code to specifically
convenient and safer bicycle or pedestrian travel within and require if shown on the pedestrian Ask
between residential areas and neighborhood activity centers or bikeway plan.
(i.e., schools, shopping,Aping, transit stops). Specific measures
include, for example, constructing walkways between cul-de-
sacs and adjacent roads,providing walkways between
buildings, and providing direct access between adjacent uses.
(7) Local governments shall establish standards for local Current code required pavement The TSP, which provides the foundation for the
streets and accessways that minimize pavement width and width between 24' and 32' for amendments being proposed, was developed with
total right-of-way consistent with the operational needs of the local streets (actual width the help of a Citizen Task Force and Technical
facility.The intent of this requirement is that local depends on ADT and whether Advisory Committee and involved several public
Page 7
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
governments consider and reduce excessive standards for parking is provided on the street) information meetings to gather input and
local streets and accessways in order to reduce the cost of and up to 12 feet per lane for comments and 2 formal public hearings. After the
construction, provide for more efficient use of urban land, arterial streets development and adoption of the TSP, a group of
provide for emergency vehicle access while discouraging City Staff from Planning and Engineering and a
inappropriate traffic volumes and speeds, and which representative from Tualatin Valley Fire and
accommodate convenient pedestrian and bicycle circulation. Rescue met over several months to develop code
�t withstanding subsection(1) or(3) of this section, local language to implement the TSP. The discussions
eet standards adopted to meet this requirement need not be included the TPR"skinny street"requirement.
adopted as land use regulations. After review and discussion, it was determined
that the safe harbor widths were acceptable,
provided a traffic flow plan was submitted to
verify that the distribution of driveways, no
parking areas, etc would allow efficient queuing
and traffic flow as the State's "Neighborhood
Streets Design Guidelines" assumed. Additional
assurances were needed to ensure that adequate
off-street parking was provided for streets that had
parking on one side only. It was determined that
• the existing width standards would remain for
those that did not want to submit a traffic flow
• plan or provide additional assurances for off-street
parking,but the option to go to narrower streets
would be provided as well. While technically, the
wider street width is the default because no
additional documentation is required, both street
width standards are acceptable and available for
developments on local streets.
Page 8
•
: • • Exhibit C
{
k 'C
LANNING•,,CONlMFSCON r
RECOMMENDAT 0 0 TNT : ` . °,,
: ,
L Iiy OF Tt(iARD::..
C
IGARD= IYCOUNCI =e om
�' vei `ent'r
..-._.,•rr ...:,,.....,•.:. .::;.....:.. ,a..�_a:;G�•=de.::.:..........:_9... .-:. ...'.'„VOfTlifllll!_�,-,_..- .:i
SECTION I: APPLICATION SUMMARY
FILE NAME: TRANSPORTATION SYSTEM PLAN
CASES: Zone Ordinance Amendment (ZOA) 2002-00004
•
PROPOSAL: The proposal is to formally adopt Development Code standards to
fully implement the Transportation System Plan (TSP) that was
adopted in January 2002.
APPLICANT: City of Tigard
13121 SW Hall Boulevard
Tigard, OR 97223
LOCATION: All areas within the City of Tigard.
APPLICABLE •
REVIEW
CRITERIA: Oregon's Statewide Planning Goals 1, 2 and 12; Oregon Administrative
Rule 660; Metro Regional Transportation Plan (RTP); Comprehensive
Plan Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3, and
Community Development Code Chapter 18.380.020 and 18.390.060.G. . -
SECTION II: PLANNING COMMISSION RECOMMENDATION:
•• s
The !Plannin g Commission moved to •forward h e= e uef�p�ent . '6 >r i ydr
ta
implement the.Trans-ortation,:Sy stem_ :Plan: T.SP t`o'� h'`� -- 1. `°'`:�
P Y (. _)_. _,,ihe_C`icy,Corancil,.as��st�mwrl.,•�n,Exkibit:A�;
1:~through A-4 and in:the summa'. _of ro.osed=y , . :3:
9 and ry P . p anges!:'�sased: o
p-�t;e=,itidmgsLL t,.at;:alb:;
relevant criteria are :satisfied: The TPA. com-liance `ri 'atriz: ` xh'ibit. :B and` this
recommendation :report provide::thp anal sis and`fndin g s.whiic f:demonstrate`com=`fiance`.
with all relevant criteria.
•
STAFF REPORT ZOA 2002-00004 Page 1
• .
SECTION III: BACKGROUND INFORMATION
The City of Tigard began looking at updating the Transportation System Plan (TSP)
several years ago. With the help of a 12 member task force, agencies and staff, a draft
TSP was produced which takes into account the existing traffic conditions in Tigard,
community needs and goals and the anticipated future demands on the transportation
system. The TSP and Comprehensive Plan amendments were adopted by the City
Council in January 2002. An additional step necessary to fully implement the TSP was
developing amendments to the Development Code to reflect changes to the TSP. The
Planning Commission and City Council held work sessions on the proposed Development
Code amendments in June. The proposed changes reflect the comments received at the
work sessions. The Planning Commission held a public hearing on August 5, 2002. No
testimony was offered at the hearing. As an addition to the Planning Commission's motion
to forward the amendments to the City Council, the Commission recommended that staff
provide a presentation to the CIT prior to the Council's public hearing. In accordance with
the Commission's recommendation, a CIT presentation is scheduled for the September 5,
2002 meeting prior to the Council's September 10, 2002 hearing.
SECTION IV. SUMMARY OF APPLICABLE CRITERIA
Chapter 18.380 states that legislative text amendments shall be undertaken by
means of a Type IV procedure, as governed by Section 18.390.060G.
Chapter 18.390.060G states that the recommendation by the Commission and the
decision by the Council shall be based on consideration of the following factors:
A. The Statewide Planning Goals and Guidelines adopted under Oregon Revised
Statutes Chapter 197;
B. Any federal or state statutes or regulations found.applicable;
C. Any applicable Metro regulations;
D. Any applicable Comprehensive Plan Policies; and
E. Any applicable provisions of the City's implementing ordinances.
SECTION V: APPLICABLE REVIEW CRITERIA AND FINDINGS
STATEWIDE GOALS
Citizen Involvement: Goal 1 requires a citizen involvement program that ensures the
opportunity for citizens to be involved in the planning process.
Tigard Comprehensive Plan Policy 2.1.1 and Tigard Community Development Code Chapter
18.3Q0 provide for citizen participation and notice. Notice of the Planning Commission and
City Council hearings and opportunity for response was advertised in the local newspaper.
Notice was sent to Department of Land Conservation and Development in accordance with
their notice requirements. This goal is satisfied.
STAFF REPORT ZOA 2002-00004 Page 2 •
• •
Land Use Planning: Goal 2 requires, in,part, that adopted comprehensive plans be
revised to take.into account changing public policies and circumstances.
This goal is met because the City has applied all relevant Statewide Planning Goals, City
Comprehensive Plan policies and Community Development Code requirements in the
review of this proposal as discussed throughout this staff report.
Transportation: Goal 12 requires a safe, convenient and economic transportation
system.
The TSP has been prepared in accordance with the Statewide Planning Goals and
requirements. Oregon Administrative Rule 666, the compliance with which is discussed
further in this report, implements the Statewide Transportation Goal 12. The plan has been
reviewed by ODOT and DLCD.
COMPLIANCE WITH FEDERAL AND STATE STATUTES OR GUIDELINES
Oregon Administrative Rule: Section 660-12-0000 through 0070 is intended to
implement Statewide Planning Goal #12 by providing guidelines for local
governments to demonstrate compliance with Goal #12 through their Transportation
System Plans.
When the TSP was adopted, it was recognized that Development Code amendments were
needed to fully comply with the TPR. Attached as Exhibit B is a chart identifying how each
of the TPR requirements are addressed. Based on the information provided in Exhibit B and
in this section, staff finds that the TSP complies with the state statutes. There are no
specific federal standards that apply.
COMPLIANCE WITH METRO REGULATIONS
Regional Transportation Plan (RTP): The RTP takes the place of Metro Functional Plan
Title 6 (Regional Accessibility), and is consistent with Chapter 2. of the Regional
Framework Plan. The RTP provides a regional framework for transportation systems
and has its own criteria that must be addressed that are in addition to the
Transportation Planning Rule (TPR) requirements.
The TSP is consistent with the RTP and the proposed amendments include all language
required to be adopted by local jurisdictions. The only specific language that needed to be
changed to implement the RTP was the requirement to have local street spacing no less
than 530 feet apart to address connectivity requirements.
COMPLIANCE WITH COMPREHENSIVE PLAN POLICIES
General Policies: Policy 1.1.1(a) requires that legislative changes are consistent with
statewide planning goals and the regional development plan.
The proposal is consistent with statewide planning goals as addressed above under
'Statewide Goals'. The proposal conforms with the applicable portions of the Metro
Functional Plan that was approved for adoption on October 24, 1996 by the Metro Council.
This policy is satisfied.
STAFF REPORT ZOA 2002-00004 Page 3
• •
Citizen Involvement: Policy 2.1.1 states that the City shall maintain an ongoing
citizen involvement program and shall assure that citizens will be provided an
opportunity to be involved in all phases of the planning process. Policy 2.1.2 states
that opportunities for citizen involvement shall be appropriate to the scale.of the
planning effort. Policy 2.1.3 states that the City shall ensure that the information on
planning issues is available in an understandable format..
A request for comments was sent to all affected jurisdictions and agencies. The Planning
Commission hearing was legally advertised with notice published in the Tigard Times. The
TSP had extensive notice and opportunities to comment. Because the current proposal is
simply an implementation of a previously'adopted plan,the same level of public notice is not
necessary.
Transportation: Transportation Policies 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 were
adopted at the same time the TSP was adopted to incorporate the TSP
recommendations into the Comprehensive Plan. The policies are specifically
addressed below:
8.1.1 — requires the planning of transportation facilities to be done in a way that
enhances livability through the proper location of facilities, encouraging pedestrian
traffic and addressing issues of through traffic and speeding on local residential
streets.
8.1.2 — requires a balanced transportation system that incorporates all modes of
transportation. .
8.1.3 — requires the effort be made to develop a safe transportation system through
the street standards and access management policies.
8.1.5 — requires the development of transportation facilities that are accessible to all
citizens and minimize out-of-direction travel. _
8.2.3 — provides the minimum improvement level and dedication that should be
required of developers as a precondition of development to ensure that the
community's transportation system functions adequately.
The code amendments provide greater clarification of where bike lanes are required,
requires the identification and removal of gaps in sidewalks (if roughly proportional), has
local street spacing standards that will minimize out-of-direction travel, provide greater
access spacing standards and greater clarification of when transit amenities are required.
The proposed development code amendment changes are directly implementing the TSP
and Comprehensive . Plan policies, therefore, the applicable Comprehensive Plan
standards have been satisfied.
COMPLIANCE WITH THE CITY'S IMPLEMENTING ORDINANCES:
The implementing ordinances are contained in the Tigard Community-Development Code.
The applicable criteria identified in the Development Code are summarized in Section IV—
STAFF REPORT ZOA 2002-00004 _ Page 4
• •
Summary of Applicable Criteria and addressed in Section V — Applicable Review Criteria
and Findings. As this staff report demonstrates, all applicable criteria have been satisfied.
SECTION VI: COMMENTS (AGENCY. STAFF AND OTHER),
City of Tigard Engineering,. City of Tigard Current Planning Division, City of Tigard
Operations, City of Tigard Public Works, City of Tigard Police, City of Beaverton, City of
Durham, City of King City, Washington County, Tigard-Tualatin School District, and Tri-
met have reviewed the proposal and offered no comments or objections. •
Tualatin Valley Fire and Rescue reviewed the proposed amendments and indicated that
they find no conflicts with their interests. The provisions for skinny streets are acceptable
to the Fire District. They also state that the Fire District is currently developing traffic
calming device design criteria that will be submitted upon completion. The general
statement in the Development Code indicates only when they are to be installed. The Fire
District hopes that their criteria will be considered for design details.
DLCD reviewed the proposed amendments and offered comments which are summarized
below:
• They want to make sure that Tigard documents its process used to develop the local
street standards regarding narrow streets;
• They suggested changes which have been incorporated into . the proposed
amendments that presents the narrow street option in a way that does not discourage
someone from using that method and as a method that is not favored.
• They provided suggested language which has been incorporated into the proposed
amendments for "Traffic Flow Plan" (formerly referred to as a queuing plan).
• They recommend against changing the block length standard from 1,800.feet to 2,120
feet and provided language that Washington County uses that they suggest we
consider.
Staff response: The change from 1,800 foot block length to 2,120 foot block length was
suggested to be consistent with the street spacing standards, however staff is not
opposed to retaining the original block length concept. Because the measurement system
is being changed from right-of-way line to centerline, the maximum block length dimension
will be 2,000 feet. This will result roughly in the same block length requirement as
currently existing and as recommended by DLCD staff.
Metro reviewed the proposed amendments and generally offered the same comments as
DLCD, specifically, they suggested changes that present the narrow street option in a way
that does not discourage someone from using that method and as a method that is not
favored and they recommend against changing the block length standard from 1,800 feet
to 2,120 feet. .
The City of Tigard Urban Forester reviewed the proposed changes and offered the
following comments: "The planter strips should be at least five feet wide so that large trees
can be planted in order to create more tree canopy. I think that planter strips are a good
idea since the trees will be shading much more of the street, thus reducing the heat island
effect too common in this City!"
STAFF REPORT ZOA 2002-00004 Page 5
• •
Oregon Department of Transportation (ODOT) reviewed the proposed amendments
and offered comments summarized as follows: They appreciate our efforts to clarify when
a traffic study is required, however a traffic study is not always needed to address ODOT
interests. They suggest changing 18.810.030.AC to state that a traffic study MAY (instead
of shall) be required if a site is within 500 feet of an ODOT facility and/or trip generation
from the development adds 300 or more trips per day to an ODOT facility and/or trip
generation from the development adds 50 or more peak hour trips to an ODOT facility.
They request that ODOT be notified of pre-applications to help make the determination of
whether a traffic study is required prior to a formal application being submitted and
deemed complete. _
Staff response: The proposed development code language has been amended to include
ODOT's recommended changes
EXHIBITS:
•
EXHIBIT A-1 through Ail:- Proposed Development Code changes
EXHIBIT B: Chart addressing TPR criteria and Tigard's compliance status
/jA/ .�
PREPA D BY: ulia Hajduk, DATE
Associate Planner
N D: ���
SI
G E Mark Padgett _
Planning Commission Chair DATE
1:Irplan lulia/TSPlimplementation/cc packet/staff report—exhibit C.doc
STAFF REPORT ZOA 2002-00004 Page 6
U.S. Postal Service
CERTIFIED MAIL RECEIPT
(Domestic Mail Only;No Insurance Coverage Provided)
rl
a 2014 1oo. - 0000'-( Jerre
Postage $ 01/4
Certified Fee �d/ i/113:Z f
f Ot�C•. �'' Postmark
1-r1 Return Receipt Fee 4 3 ) Here
(En brsement Required)
1:3 Restricted Delivery Fee 4C6 '.JJL/Citp
ti (Endorsement Required)
1=1 Total Postage&Fees $ •
��
S m Recipient's Name(Please Print Clearly))(to be completed by mailer)
p— Street,< DLCD
Q ATTN: PLAN AMENDMENT SPECIALIST
City,Sta 635 CAPITAL STREET NE,SUITE 150
r` SALEM,OR 97301-2540
PS Form 3800,February 2000 See Reverse for Instructions
SENDER: COMPLETE THIS SECTION COMPLETE THIS SECTION ON DELIVERY
• Complete items 1,2,and 3.Also complete A. Received by(Please Print Clearly) B. Date of Delivery
item 4 if Restricted Delivery is desired. •
• Print your name and address on the reverse
so that we can return the card to you. C. Signature
• Attach this card to the back of the mailpiece, •Agent •
or on the front if space permits. !1 . +J. �� ❑Addressee
D. Is delivery address•ifferent from item 1? ❑Yes
1. Article Addressed to:. If YES,enter delivery address below: ❑ No
•
DEPT. OF LAND CONSERVATION & DEVELOP
ATTN: PLAN AMENDMENT SPECIALIST
635 CAPITAL STREET NE, SUITE 150
SALEM, OR 97301-2540 3. S rvice Type
Certified Mail ❑ Express Mail
❑ Registered ❑ Return Receipt for Merchandise
❑ Insured Mail ❑C.O.D.
4. Restricted Delivery?(Extra Fee) ❑Yes
2. Article Number(Copy from service label) ft
70.9e. 3il00 oois 7740 / /-7
I PS Form 3811,July 1999 Domestic Return Receipt 102595-00-M-0952 •
Form 2 • S
DLCD NOTICE OF ADOPTION
This form must be mailed to DLCD within 5 working days after the final decision
per ORS 197.610 and OAR Chapter 660- Division 18
(See reverse side for submittal requirements)
Jurisdiction: City of Tigard Local File No.: ZOA 2002-00004
(If no number,use none)
Date of Adoption: September 10, 2002 Date Mailed: September 12, 2002
(Must be filled in) (Date mailed or sent to DLCD)
Date this proposal was sent or mailed: June 19, 2002
(Date mailed or sent to DLCD)
Comprehensive Plan Text Amendment _ Comprehensive Plan Map Amendment
X Land Use Regulation Amendment _ Zoning Map Amendment
New Land Use Regulation _ Other:
(Please Specify Type of Action)
Summarize the adopted amendment. Do not use technical terms. Do not write "See Attached."
Amend the Tigard Development Code to reflect the Transportation System Plan and
Comprehensive Plan changes adopted in January 2002. The proposed amendments also reflect
the State of Oregon's Transportation Planning Rules (TPR)which include provision of skinny
streets. The specific Tigard Development Code sections meeting amended include: 18.120
(definitions), 18.360 (Site Development Review), 18.520 (Commercial zoning). 18.530 (Industrial
zoning), 18.705 (Access Egress and Circulation), 18.745 (Landscaping and screening) and
18.810 (Street and Utility Improvement Standards).
Describe how the adopted amendment differs from the proposed amendment. If it is the same,
write "Same." If you did not give notice for the proposed amendment, write "N/A."
Same
• Plan Map Change from: N/A to
Zone Map Change from: N/A to
Location: Citywide Acres Involved:
Specify Density: Previous: N/A New:
Applicable Statewide Planning Goals: 1, 2, and 12
Was an Exception adopted? Yes: _ No X
DLCD File No.:
. Form 2 • 110
Did the Department of Land Conservation and Development receive a Notice of Proposed
Amendment FORTY FIVE (45) days prior to the first evidentiary hearing? Yes: X No:
If no, do the Statewide Planning Goals apply. Yes: — No:
If no, did The Emergency Circumstances Require immediate adoption. Yes: No:
Affected State or Federal Agencies, Local Governments or Special Districts: DLCD, Metro and
ODOT
Local Contact: Julia Hajduk Area Code + Phone Number: 503-639-4171
Address: 13125 SW Hall Boulevard
City: Tigard, OR Zip Code + 4: 97223-8189
ADOPTION SUBMITTAL REQUIREMENTS
This form must be mailed to DLCD within 5 working days after the final decision
per ORS 197.610 and OAR Chapter 660- Division 18
1. Send this Form and Two (2) Copies of the Adopted Amendment to:
ATTENTION: PLAN AMENDMENT SPECIALIST
DEPARTMENT OF LAND CONSERVATION AND DEVELOPMENT
635 CAPITAL STREET NE, SUITE 150
SALEM, OREGON 97301-2540
COPY TO:
Metro Land Use & Planning ODOT-Region 1, District 2-A
600 NE Grand Avenue Jane Estes,Permit Specialist
Portland, OR 97232-2736 5440 SW Westgate Drive, Suite 350
Portland, OR 97221-2414
2. Submit Two (2) copies of adopted material, if copies are bounded please submit
two (2) complete copies of documents and maps.
3. Please Note: Adopted materials must be sent to DLCD not later than
five (5) working days following the date of the final decision on the amendment.
4. Submittal of this Notice of Adoption must include the text of the amendment plus adopted •
findings and supplementary information. •
5. The deadline to appeal will be extended if you do not submit this Notice of Adoption within
five working days of the final decision. Appeals to LUBA may be filed within
TWENTY-ONE (21) days of the date, the "Notice of Adoption" is sent to DLCD.
. 6. In addition to sending the "Notice of Adoption" to DLCD, you must notify persons who
participated in the local hearing and requested notice of the final decision.
7. Need More Copies? You can copy this form to 8-1/2x11 green paper only ; or call the
DLCD Office at (503) 373-0050; or Fax your request to: (503) 378-5518; or Email your
request to Larry.French @state.or.us -ATTENTION: PLAN AMENDMENT SPECIALIST.
c. -ti • •
Agenda Item No. A
Meeting of 9 .2-?- 02.-
MINUTES
TIGARD CITY COUNCIL MEETING
September 10, 2002
Mayor Griffith called the meeting to order at 6:34 p.m.
Council Present: Mayor Griffith; Councilors Dirksen, Moore, and Scheckla
• STUDY SESSION
> DISCUSS AGENDA FOR OCTOBER 7, 2002, SPECIAL MEETING
The Council and City Manager Monahan discussed potential agenda topics
for the upcoming special meeting with the Tualatin City Council and the
Tigard-Tualatin School District. The top three discussion topics were
identified as follows:
a. New Library and school district building plans/schedules/sequence
b. Pedestrian bridge
C. Clean Water Services Master Plan
Other topics suggested were:
a. How building fees are charged — which fees are dedicated and
possible fee waivers for school district building projects
b. City of Tigard experience with juvenile cases
c. Joint use of/sharing equipment
ADMINISTRATIVE ITEMS
a. Assistant to the City Manager Liz Newton explained a correction
made to the Office Depot and Boise Cascade office supply
contracts. Copies of the corrected contracts are on file in the City
Recorder's Office.
b. Liz Newton handed out an agenda for the 9-11 event to be held at
6:45 p.m. on September 11 in Cook Park
c. Mayor Griffith announced an ecumenical service scheduled for 7
a.m. on September 11 in Cook Park
d. City Manager Monahan told Council about the upcoming candidate
orientation scheduled for September 12 at 6:30 p.m.
e. Mr. Monahan provided a brief update on recent PERS legislation
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 1
• •
f. Mr. Monahan provided a brief update on the police chief
recruitment
g. Mr. Monahan discussed the new library, architect, and resource
team input. Public meetings are slated for October 16 and
December 11. Five firms have been selected for interviews for the
construction manager/general contractor contract. Mr. Fields has
been notified of the City's intent to execute the purchase option.
A discussion ensued regarding the two homes and other structures
located on the property. Mr. Monahan inquired if the Council had
any objection to the City using the structures or seeing if other
agencies or individuals would be interested in moving them. He
stated that if the City could not use the buildings, they could be
offered to social service organizations and then private individuals.
The City will own the property in mid-October and would need to
remove the structures soon after. Councilor Moore stated that such
an arrangement could save the City demolition money. Councilor
Dirksen said he saw no reason not to move forward. No Council
members expressed opposition to Mr. Monahan's suggestions.
h. Mr. Monahan initiated a discussion of the October meeting
schedule. Mayor Griffith and Councilor Moore are not able to
attend the October 22 meeting. This meeting will be cancelled. It
was suggested that the Council meet, instead, on October 29.
Councilor Moore is not available on this date; other members of
the Council agreed to check their schedules for this date.
j. Mr. Monahan noted an upcoming meeting with ODOT. It appears
that the buyer of the Zander property intends to proceed with their
project. This may mean that Wall Street can be located further
south and would allow for a better location of the pond.
Signalization, road widening, and location are some of the topics
slated for discussion at the ODOT meeting.
k. Councilor Scheckla inquired about the status of Bonita Villa. Ms.
Sydney Sherwood, a candidate for Council, was observing the study
session and responded to the question. Washington County has
taken over Bonita Villa. New landscaping and exterior upgrades are
taking place, but most improvements are occurring inside the
apartments. There is a security guard on site. Many problem
residents have moved out.
Councilor Scheckla inquired about the status of church on Bonita
Road. Mr. Monahan said he would check on the status of the
church.
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 2
• •
Study Session recessed at 7:23 p.m.
• EXECUTIVE SESSION: No Executive Session was held.
1. BUSINESS MEETING
1.1 The meeting of the Tigard City Council & Local Contract Review Board
was called to order by Mayor Griffith at 7:32 p.m.
1.2 Council Present: Mayor Griffith, Councilors Dirksen, Moore, and Scheckla
1.3 Pledge of Allegiance
1.4 Council Communications 81 Liaison Reports — None
1.5 Call to Council and Staff for Non-Agenda Items — None
2. PROCLAMATIONS — Mayor Griffith proclaimed the following:
2.1 Week of September 17th as Constitution Week
2.2 September 21'as Kids Day America/International
2.3 September 1 1t' as Always Remember 9-1 1 Day
2.4 Week of September 23rd as Race Equality Week
3. VISITOR'S AGENDA
• Tigard High School Student Envoy, Paul Brems, addressed the Council. Mr.
Brems distributed a calendar of events and updated the Council on student
activities. A copy of the handout is on file in the City Recorder's Office.
4. CONSENT AGENDA
Motion by Councilor Moore, seconded by Councilor Dirksen to approve the
Consent Agenda as follows:
4.1 Approve Council Minutes for August 20 and 27, 2002
4.2 Receive and File:
a. Council Calendar
b. Tentative Agenda
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 3
• •
4.3 Approve Budget Amendment #2 to the Fiscal Year 2002-03 Budget to
Add Wages and Benefits for an Approved Senior Library Assistant Position
— Resolution No. 02 - 55
4.4 Approve Budget Amendment #3 to the Fiscal Year 2002-03 Budget to
Transfer Approved Capital Improvement Projects and Amend the Fiscal
Year 2002-07 Approved Capital Improvement Plan - Resolution No. 02
- 56
4.5 Amend City Wide Personnel Policies Regarding the Reporting of Vehicular
and/or Occupational Accidents — Resolution No. 02 - 57
4.6 Local Contract Review Board:
a. Award Annual Contracts for Office Supplies to Office Depot and
Boise Cascade
b. Award the Project Management Services Contract for the New
Tigard Library to Shiels Obletz Johnsen, Inc.
c. Award the Engineering Design Services Contract for the Proposed
Wall Street Local Improvement District to DeHaas at Associates
The motion was approved by a unanimous vote:
Mayor Griffith - Yes
Councilor Dirksen - Yes
Councilor Moore - Yes
Councilor Scheckla - Yes
5. VISION MID-YEAR REPORT— ACCOMPLISHMENTS UPDATE
Risk Manager Loreen Mills introduced this agenda item. A PowerPoint
presentation was given and is on file in the City Recorder's Office. Various
executive staff discussed the City's accomplishments in the areas of:
• Community Character and Quality of Life
• Growth and Growth Management
• Public Safety
• Schools and Education
• Transportation and Traffic
• Urban and Public Services
6. PUBLIC WORKS DEPARTMENT OVERVIEW
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 4
• •
Pub • , Director Ed Wegner int •, • -' this agenda item. A PowerPoint
presentation was given . 1,:-' i e in the City Recorder's Office. Mr. Wegner's
presentation etMi • the work perform•s ' blic Works Department staff, and
how the-department connects with the community.
7. PUBLIC HEARING (LEGISLATIVE) TO CONSIDER AN ORDINANCE
ADOPTING CHANGES TO THE TIGARD MUNICIPAL CODE IN ORDER
TO IMPLEMENT THE TRANSPORTATION SYSTEM PLAN (TSP)
a. Mayor Griffith opened the public hearing.
b. Associate Planner Julia Hajduk presented the staff report. Ms. Hajduk
gave a brief history of the item. She explained that to fully implement the
TSP, amendments to Chapter 18 of the Tigard Municipal Code were
needed. Ms. Hajduk indicated that the amendments were designed to:
• clarify language
• implement TSP recommendations
• address Department of Land Conservation and Development
requirements related to the Transportation Planning Rule
• address Metro Regional Transportation Plan requirements
Significant changes are as follows:
• Street Width
- creating an option for a "skinnier" street of 28 feet
• Sidewalks
- requires sidewalks to be setback with planter strip with exceptions
- asks developers to identify sidewalk gaps and to remove these gaps
under certain circumstances
• Access Management
- requires developers to verify driveway designs are safe
- provided greater detail regarding driveway locations near
intersections
- if direct access is provided onto an arterial or collector street, the
applicant may be required to mitigate any safety or traffic
management impacts
• Traffic Calming
- if there is a potential for a negative impact on existing
neighborhood streets, requires a developer to deposit funds toward
traffic calming. Funds would be returned if it is determined that
traffic calming measures are not needed.
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 5
• •
Ms. Hajduk listed the applicable review criteria:
Oregon's Statewide Planning Goals 1, 2 and 12; Oregon
Administrative Rule 660; Metro Regional Transportation Plan
(RTP); Comprehensive Plan Policies 1.1.1 (a), 2.1.1, 8.1.1,
8.1.2, 8.1.3, 8.1.5 and 8.2.3, and Community Development
Code Chapter 18.380.020 and 18.390.060.G.
Mayor Griffith asked for clarification regarding sidewalk requirements and
whether such requirements could be appealed.
Councilor Scheckla inquired if a "skinnier" street were constructed, would
sidewalks also be narrower. Ms. Hajduk responded that the sidewalk width
was not effected by street width.
c. Public Testimony: None.
d. Staff recommended the Council adopt the proposed ordinance.
e. Mayor Griffith closed the public hearing.
f. Motion by Councilor Moore, seconded by Councilor Dirksen, to adopt
Ordinance No. 02-33
ORDINANCE NO. 02-33 — AN ORDINANCE ADOPTING
CHANGES TO THE DEVELOPMENT CODE IN ORDER TO
IMPLEMENT THE TRANSPORTATION SYSTEM PLAN
The motion was approved by a unanimous vote:
Mayor Griffith - Yes
Councilor Dirksen - Yes
Councilor Moore - Yes
Councilor Scheckla - Yes
8. PREVIEW OF SEPTEMBER 11Th REMEMBRANCE EVENT
Assistant to the City Manager Liz Newton introduced this agenda item. Ms.
Newton advised that there would be an event to commemorate the events
September 11, 2001. The affair will be held on September 11, 2002, in Cook
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 6
• •
Park beginning at 6:45 p.m. Music, the National Anthem, a candlelight moment
of silence, and food donations to the Oregon Food Bank are planned. The public
was invited to attend.
Mayor Griffith announced an ecumenical service scheduled for 7 a.m. on the
same day in Cook Park.
9. UPDATE ON SUMMER READING
Library Director Margaret Barnes introduced this agenda item. A PowerPoint
presentation was given and is on file in the City Recorder's Office. Ms. Barnes
described summer reading activities and program statistics. Over 1,100
participants registered for the summer reading program.
10. UPDATE ON THE NEW LIBRARY
Library Director Margaret Barnes introduced this agenda item. A PowerPoint
presentation was given and is on file in the City Recorder's Office. Ms. Barnes
described the progress of the new library. A project update, timeline, upcoming
meetings, and ways to communicate with citizens were discussed.
Councilor Dirksen stressed the importance of citizen involvement in the process
of creating the new library and encouraged citizens to attend the October 16
community meeting to give their input.
11. STATUS REPORT ON THE PURCHASE OF LIBRARY PROPERTY
Assistant to the City Manager Liz Newton introduced this agenda item. Ms.
Newton provided background information on the new library property. The City
has exercised its option to purchase the property and surveys and level one
environmental assessments are being finalized. Although bonds should be issued
by the State in November, funds will be available in October. The City expects to
close on the property on October 15.
12. COUNCIL LIAISON REPORTS — None.
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 7
•
• •
13. NON AGENDA ITEMS — None.
14. EXECUTIVE SESSION: No Executive Session was held.
15. ADJOURNMENT: 9:38 p.m.
Attest:
Greer A. Gaston, Deputy City Recorder
. or,
ate: -
I:\ADM\CATHY\CCM\020910.DOC
TIGARD CITY COUNCIL MINUTES — September 10, 2002 page 8
w5 , • •
Attachment 1
CITY OF TIGARD, OREGON
ORDINANCE NO. 02- 3,3
AN ORDINANCE ADOPTING CHANGES TO THE DEVELOPMENT CODE IN ORDER
TO IMPLEMENT THE TRANSPORTATION SYSTEM PLAN(TSP).
WHEREAS, the TSP was developed with the help of a 12 member citizen Task Force and
addressed Transportation Planning Rule (TPR) requirements, Metro's Regional Transportation Plan
(RTP)updates and the City needs;and
WHEREAS, Tigard adopted its Transportation System Plan in January 2002 with the intent to
return at a later date with amendments to the development code; and
WHEREAS, the TSP is not fully implemented until changes have been made to the development
code;and
WHEREAS, development code changes have been prepared which implement the TSP
recommendations, address TPR narrow street requirements and clarify existing code language as
shown in Exhibits A-1 through A-4;and
WHEREAS, the Planning Commission held a public hearing, which was noticed in accordance
with the City standards, on.August 5, 2002 and voted to forward the amendments to the City
Council,and
WHEREAS,the Citizen Involvement Team was informed of the proposed changes and of the City
Council hearing at its September 5,2002 meeting;and
WHEREAS,the City Council held a public hearing on September 10, 2002, which was noticed in
accordance with City standards, and voted to approve the TSP and Comprehensive Plan changes
proposed, and
WHEREAS, the decision to adopt was based on compliance with Oregon Statewide Planning
Goals #1, #2, and #12; OAR 660; the Regional Transportation Plan, Comprehensive Plan policies
1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 and Community Development Code chapter
18.380.020 and 18.390.060.G as detailed in the TPR compliance matrix (Exhibit B) and the staff
report/Planning Commission recommendation(Exhibit C),
NOW,THEREFORE,THE CITY OF TIGARD ORDAINS AS FOLLOWS:
SECTION 1: The attached Development Code Changes (Exhibit A-1 through A-4) are
adopted based on the findings in the staff report and the supplemental TPR
compliance matrix.
ORDINANCE NO. 02- 33
Page 1 of 2 (updated 8/19/02 12:17 PM)
•
SECTION 2: If any section of the TSP or resulting Development Code changes trigger a
Measure 7 claim,the City may make a determination regarding whether the TSP
or Development Code provision should be applied on a case by case basis.
SECTION 3: This ordinance shall be effective 30 days after its passage by the Council,
signature by the Mayor,and posting by the City Recorder.
PASSED: By l lll3f tm1 mote of all Council members present after being read by number
and title only,this /O' day of .poem r ,2002.
C dli iiiic Wheatley, City d1.1
Greer A. Gaston,Deputy City Recorder
APPROVED: By Tigard City Council this 0111 day of seen Lt--- , 2002.
i,
•
7mcs E. Grif th,Mayl
Approved as to form:
Ci Attorney
ci I ( DZ
Date
is\Irpin\julia\TSP\implementation\cc packet\TSP implementation ord.doc
ORDINANCE NO. 02- 33
Page 2 of 2 (updated 8/19/02 10:15 AM)
•
TIGARD CITY COUNCIL A1�
MEETING
September 10, 2002 6:30 p.m. CITY OF TIGARD
OREGON
TIGARD CITY HALL
13125 SW HALL BLVD
TIGARD, OR 97223
PUBLIC NOTICE:
Anyone wishing to speak on an agenda item should sign on the appropriate sign-up
sheet(s). If no sheet is available, ask to be recognized by the Mayor at the beginning of
that agenda item. Visitor's Agenda items are asked to be two minutes or less. Longer
matters can be set for a future Agenda by contacting either, the Mayor or the City
Manager.
Times noted are estimated; it is recommended that persons interested in testifying be
present by 7:15 p.m. to sign in on the testimony sign-in sheet. Business agenda items
can be heard in any order after 7:30 p.m.
Assistive Listening Devices are available for persons with impaired hearing and should be
scheduled for Council meetings by noon on the Monday prior to the Council meeting.
Please call 503-639-4171, Ext. 2410 (voice) or 503-684-2772 (TDD -
Telecommunications Devices for the Deaf).
Upon request, the City will also endeavor to arrange for the following services:
• Qualified sign language interpreters for persons with speech or hearing
impairments; and
• Qualified bilingual interpreters.
Since these services must be scheduled with outside service providers, it is important to
allow as much lead time as possible. Please notify the City of your need by 5:00 p.m. on
the Thursday preceding the meeting by calling: 503-639-4171, x2410 (voice) or 503-
684-2772 (TDD - Telecommunications Devices for the Deaf).
SEE ATTACHED AGENDA
COUNCIL AGENDA — September 10, 2002 page 1
•
AGENDA
TIGARD CITY COUNCIL MEETING
September 10, 2002
6:30 PM
• STUDY SESSION
> DISCUSS AGENDA FOR OCTOBER 7, 2002, SPECIAL MEETING
• EXECUTIVE SESSION: The Tigard City Council may go into Executive Session. If an
Executive Session is called to order, the appropriate ORS citation will be announced
identifying the applicable statute. All discussions are confidential and those present
may disclose nothing from the Session. Representatives of the news media are allowed
to attend Executive Sessions, as provided by ORS 192.660(3), but must not disclose
any information discussed. No Executive Session may be held for the purpose of
taking any final action or making any final decision. Executive Sessions are closed to
the public.
7:30 PM
1. BUSINESS MEETING
1.1 Call to Order - City Council 81 Local Contract Review Board
1.2 Roll Call
1.3 Pledge of Allegiance
1.4 Council Communications 8i Liaison Reports
1.5 Call to Council and Staff for Non-Agenda Items
2. PROCLAMATIONS
2.1 Proclaim the Week of September 17th as Constitution Week
2.2 Proclaim September 21St as Kids Day America/International
2.3 Proclaim September 11 di as Always Remember 9-1 1 Day
2.4 Proclaim Week of September 23rd as Race Equality Week
• Mayor Griffith
3. VISITOR'S AGENDA (Two Minutes or Less, Please)
• Tigard High School Student Envoy Paul Brems
COUNCIL AGENDA — September 10, 2002 page 2
•
4. CONSENT AGENDA: These items are considered to be routine and may be
enacted in one motion without separate discussion. Anyone may request that an
item be removed by motion for discussion and separate action. Motion to:
4.1 Approve Council Minutes for August 20, and 27, 2002
4.2 Receive and File:
a. Council Calendar
b. Tentative Agenda
4.3 Approve Budget Amendment #2 to the Fiscal Year 2002-03 Budget to
Add Wages and Benefits for an Approved Senior Library Assistant Position
— Resolution No. 02 -
4.4 Approve Budget Amendment #3 to the Fiscal Year 2002-03 Budget to
Transfer Approved Capital Improvement Projects and Amend the Fiscal
Year 2002-07 Approved Capital Improvement Plan - Resolution No. 02 -
4.5 Amend City Wide Personnel Policies Regarding the Reporting of Vehicular
and/or Occupational Accidents — Resolution No. 02 -
4.6 Local Contract Review Board:
a. Award Annual Contracts for Office Supplies to Office Depot and
Boise Cascade
b. Award the Project Management Services Contract for the New
Tigard Library to Shiels Obletz Johnsen, Inc.
c. Award the Engineering Design Services Contract for the Proposed
Wall Street Local Improvement District to DeHaas 81 Associates
• Consent Agenda - Items Removed for Separate Discussion: Any items requested
to be removed from the Consent Agenda for separate discussion will be
considered immediately after the Council has voted on those items which do not
need discussion.
5. VISION MID-YEAR REPORT — ACCOMPLISHMENTS UPDATE
a. Staff Report: Administration Staff
b. Council Discussion
6. PUBLIC WORKS DEPARTMENT OVERVIEW
a. Staff Report: Public Works Staff
b. Council Discussion
COUNCIL AGENDA — September 10, 2002 page 3
• •
7. PUBLIC HEARING (LEGISLATIVE) TO CONSIDER AN ORDINANCE
ADOPTING CHANGES TO THE TIGARD MUNICIPAL CODE IN ORDER TO
IMPLEMENT THE TRANSPORTATION SYSTEM PLAN
a. Open Public Hearing
b. Summation by Community Development Staff
c. Public Testimony
d. Staff Recommendation
e. Council Discussion
f. Close Public Hearing
g. Consideration by Council: Ordinance No. 02 -
8. PREVIEW OF SEPTEMBER 11TH REMEMBRANCE EVENT
a. Staff Report: Administration Staff
b. Council Discussion
9. UPDATE ON SUMMER READING
a. Staff Report: Library Staff
b. Council Discussion
10. UPDATE ON THE NEW LIBRARY
a. Staff Report: Library Staff
b. Council Discussion
11. STATUS REPORT ON THE PURCHASE OF LIBRARY PROPERTY
a. Staff Report: Administration Staff
b. Council Discussion
12. COUNCIL LIAISON REPORTS
13. NON AGENDA ITEMS
COUNCIL AGENDA — September 10, 2002 page 4
•
14. EXECUTIVE SESSION: The Tigard City Council may go into Executive Session. If
an Executive Session is called to order, the appropriate ORS citation will be
announced identifying the applicable statute. All discussions are confidential and
those present may disclose nothing from the Session. Representatives of the news
media are allowed to attend Executive Sessions, as provided by ORS 192.660(3),
but must not disclose any information discussed. No Executive Session may be
held for the purpose of taking any final action or making any final decision.
Executive Sessions are closed to the public.
15. ADJOURNMENT
I:\AD M\CATHY\CCA\020910.DOC
COUNCIL AGENDA — September 10, 2002 page 5
•
411
AGENDA ITEM#
FOR AGENDA OF September 10, 2002
„, CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
ISSUE/AGENDA TITLE Development Code Amendments to Implement the Transportation System Plan
PREPARED BY: Julia Hajduk DEPT HEAD OK \V CITY MGR OK V444 1 "V
ISSUE BEFORE THE COUNCIL
Should the Council adopt the proposed development code amendments which implement the previously adopted
Transportation System Plan?
STAFF RECOMMENDATION
Adopt the proposed Development Code changes by adopting the attached Ordinance.
INFORMATION SUMMARY
The City of Tigard began updating the Transportation System Plan (TSP)several years ago. With the help of a 12
member Task Force made up of the Planning Commission and 3 citizens, agencies, staff and the consulting firm
DKS, a draft TSP was produced. The Tigard TSP was adopted in January, 2002 along with Comprehensive Plan
amendments and became effective in February. An additional step that was necessary to fully implement the TSP
was developing amendments to the Development Code to reflect changes to the TSP. The planning staff, along
with staff from the engineering department and Tualatin Valley Fire and Rescue, completed the review of the
Development Code and began processing the recommended amendments. The changes implement
recommendations of the TSP such as access management, sidewalk location and traffic calming. The changes
also provide revised right-of-way requirements in accordance with the TSP recommendations and the
Transportation Planning Rule requirements. A complete summary of the proposed changes is provided in
Attachment 2. A hearing before the Planning Commission was held on August 5, 2002, and notice of the City
Council hearing was announced at the September 5, 2002 CIT meeting as requested by the Planning Commission.
OTHER ALTERNATIVES CONSIDERED
Provide additional comments or changes to the TSP and/or Comprehensive Plan.
• VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEGY
Transportation and Traffic,Goal#2—Improve traffic flow.
ATTACHMENT LIST
.Attachments: 1 —Proposed Ordinance adopting the proposed development code changes
Exhibit A-1 to A-4: Proposed code changes
Exhibit B: TPR compliance matrix-
Exhibit C: Staff Report
2—Summary of changes to implement the TSP
3 —Draft Planning Commission minutes recommending adoption
FISCAL NOTES
N/A
• I,•lrplan/Julia/TSP/implementation\cc presentation\implementation ais.doc
•
Attachment 1
CITY OF TIGARD, OREGON
ORDINANCE NO. 02-
AN ORDINANCE ADOPTING CHANGES TO THE DEVELOPMENT CODE IN ORDER
TO IMPLEMENT THE TRANSPORTATION SYSTEM PLAN(TSP).
WHEREAS, the TSP was developed with the help of a 12 member citizen Task Force and
addressed Transportation Planning Rule (TPR) requirements, Metro's Regional Transportation Plan
(RTP)updates and the City needs; and
WHEREAS, Tigard adopted its Transportation System Plan in January 2002 with the intent to
return at a later date with amendments to the development code; and
WHEREAS, the TSP is not fully implemented until changes have been made to the development
code; and
WHEREAS, development code changes have been prepared which implement the TSP
recommendations, address TPR narrow street requirements and clarify existing code language as
shown in Exhibits A-1 through A-4; and
WHEREAS, the Planning Commission held a public hearing, which was noticed in accordance
with the City standards, on August 5, 2002 and voted to forward the amendments to the City
Council, and
WHEREAS, the Citizen Involvement Team was informed of the proposed changes and of the City
Council hearing at its September 5, 2002 meeting; and
WHEREAS, the City Council held a public hearing on September 10, 2002, which was noticed in
accordance with City standards, and voted to approve the TSP and Comprehensive Plan changes
proposed, and
WHEREAS, the decision to adopt was based on compliance with Oregon Statewide Planning
Goals #1, #2, and #12; OAR 660; the Regional Transportation Plan, Comprehensive Plan policies
1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 and Community Development Code chapter
18.380.020 and 18.390.060.G as detailed in the TPR compliance matrix (Exhibit B) and the staff
report/Planning Commission recommendation(Exhibit C),
NOW,THEREFORE,THE CITY OF TIGARD ORDAINS AS FOLLOWS:
SECTION 1: The attached Development Code Changes (Exhibit A-1 through A-4) are
adopted based on the findings in the staff report and the supplemental TPR
compliance matrix.
•
ORDINANCE NO. 02-
Page 1 of 2 (updated 8/19/02 12:17 PM)
• * f
� r
SECTION 2: If any section of the TSP or resulting Development Code changes trigger a
Measure 7 claim, the City may make a determination regarding whether the TSP
or Development Code provision should be applied on a case by case basis.
SECTION 3: This ordinance shall be effective 30 days after its passage by the Council,
signature by the Mayor, and posting by the City Recorder.
PASSED: By vote of all Council members present after being read by number
and title only, this day of , 2002.
Catherine Wheatley, City Recorder
APPROVED: By Tigard City Council this day of , 2002.
James E. Griffith, Mayor
Approved as to form:
City Attorney
Date
is\Irpin\julia\TSP\implementation\cc packet\TSP implementation ord.doc
ORDINANCE NO. 02-
Page 2 of 2 (updated 8/19/02 10:15 AM)
•
Exhibit A-1
Chapter 18.705
ACCESS, EGRESS,AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply. The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures(see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
• A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures, or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title, provided:
1. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
Proposed Development Code changes to implement the TSP Page 1
• • '
•
2. Copies of the deeds, easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping,pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes. Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director,the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety,and general welfare.
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to collector or arterial streets shall be considered only
Proposed Development Code changes to implement the TSP Page 2
• •
if there is no practical alternative way to access the site. I f dircet_a_c_cess_is_permitted_by the
City, the applicant will he required_to rnitiizate_ for_any_ safety or neighborhood traffic
management asTmilrppact deemed appilpble by .t1. CjtV Engineer. Thistpayjnclude, but
will not be limited to,„the construction of yebieleturnaroundon_the siteto_eliminate_the need
for ayehiele to haekout onto the roadway..
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street,other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
Management
1_,_Anacces_s report shall he=spbronteciwitkallnovdeveloprnentprrongs,als.which_yerifiesdesjo
of driveways and streets are safe_b_ymeetingudequate stackingneeds,_SightthStanCQ and
deceleration as_sethy ODOL„Washington_County,the_City and AAUP:0
cdcpcnding_on jurisdiction of faeility,)
Driveways shall_not he permitted to_beplaced intlieinfluence_area of collector or arterial street
intersections.__Influence area ofintersections is that area where_queues of traffic commonly
form_on approach to aninterseetion, The minimum drivewaLsethack from a_collector_or
arterial street inter_seetion shallhe 150 feetoneasured from_the right:of:way lin_eofthe
intersectingstreet to=the,throatsf die proposed drivewayThe„setback may=hel7sater
depending upon theinflUeligc._area,as determined fromcity_Engineerreyiew of a_traftIeltnpact
report submitted by the applicant:1s traffic_cnginem Ilia ease_where_a project has_jg5S than 159_.
feet of street:frontage,the applicant-must explore_any_option for shared access with the adjacent
paisel,_If sharedaccess not_possible_or practical,the driveway shall be placed_as*from the
intersection ietion as possib he.
.3„,„_The_minimpinspaeing of driveways,and,streets„alonit,a_col_l_ector=shallhe .200,5get,=The
minimum spacing ofdriveways„andstrcetsulong an arte rial.shal b feet
4.__Theininimu_m_.spaeing_of local greets_along IQUISINOLSitati_bt 125 feet,
. .
Minimum access requirements for residential use.
1. Vehicular access and egress for single-family, duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less than as provided in Table
18.705.1 and Table 18.705.2;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
1 or 2 1 15' 10'
3-6 1 20' 20'
Proposed Development Code changes to implement the TSP Page 3
• •
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI-FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15' if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24'if two-way
or
2 30' 15'if one-way: Curbs and
5' walkway required
50-100 2 30' 24' Curbs and 5'walkway
required
2. Vehicular access to multi-family structures shall be brought to within 50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
•
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed Development Code changes to implement the TSP Page 4
• 110
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' _ 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site,it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets,upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles; or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health,safety, and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties,parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic, access and parking area plans shall provide
efficient sidewalk and/or pathway connections, as feasible,between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
II procedure, as regulated by Section 18.390.040, using criteria contained in Section 18.370.020 C3
Proposed Development Code changes to implement the TSP Page 5
0-
•
Exhibit A-2
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet; provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2-1/2 stories or 35 feet, whichever is less, provided:
Proposed Development Code changes to implement the TSP Page 6
• •
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420,Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line; and
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed Development Code changes to implement the TSP Page 7
• •
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings; and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance with Chapter 18.350, Planned Developments, Chapter 18.430,
Subdivisions, or Chapter 18.420,Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
2. A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
A. Additional setback from speei€ed-roadways. -- . - •- . , .• , . . . - .
Proposed Development Code changes to implement the TSP Page 8
• •
Where the street is not improved, the measurement shall be made at right angles from the
centerline or general extension of the street right of way:
centerline of the street as contained in Table 18.730.1.
•
2. Collector Streets. The required setback distance for buildings on the following collector streets
of the street as contained in Table 18.730.1.
•
• . .1. ' . . • • . „ . •
Street Names Requirement
Arterial Streets:
SW Pacific Highway(within City Limits) 50 feet
SW Hall Boulevard 45 feet
intersections with Old Scholls Ferry Road) 50 feet
- . -- - -
Upper Boones Ferry) 45 feet
SW Upper Boones Ferry Road 45 feet
Collector Streets:
SW Ash Avenue 30 feet
SW Atlanta Haines(east of 68th Avenue) 30 feet
SW Atlanta(west of 68th A venue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
Hall Boulevard) 30 feet
SW Franklin Street 30 feet
SW Gaarde Street 30.feet
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
SW Hunziker Road 30 feet
SW Main Street 30 feet
SW McDonald Street 30 feet
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak(west of Hall Boulevard) 30 feet
SW Pfaffle Street 30 feet
I -_
Old Scholls Ferry Road) 30 feet
Proposed Development Code changes to implement the TSP Page 9
•
• ! • ��• '
•
Street Names Requirement
SW Summerfield Drive 30 feet
SW Tiedeman Avenue 30 feet
SW Tigard Street 30 feet
SW Walnut Street 30 feet
SW 68th Avenue 30 feet
SW 68th Avenue(south of Pacific Highway) 30 feet
SW 70th Avenue(south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
3—The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
of-way width less than required by its functional classification on the City's transportation plan map
and, in such case, the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
. Y.
B. Distance between multi-family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development,the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15-foot
separation;
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections; and
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
Proposed Development Code changes to implement the TSP Page 10
•
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and -
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone, the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots.
B. When one abutting property has a non-conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats, trailers, campers, camper bodies, house trailers,recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
D. Projections into required yards.
Proposed Development Code changes to implement the TSP Page 11
•
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36.inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
•
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
"."-J AREA NOT INCLUDED
IN LOT AREA
X\\\\
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.
Proposed Development Code changes to implement the TSP Page 12
•
Exhibit A-3
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction, reconstruction or repair of streets,
sidewalks, curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed Development Code changes to implement the TSP Page 13
• •
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets
A. Improvements.
1. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets; or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6. The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed Development Code changes to implement the TSP Page 14
• •
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use; or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards, the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
• b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public,"as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
by deed without full compliance with this title provided such an easement is the only reasonable
method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.H and 18.705.030I.
D. Street location, width and grade. Except as noted below, the location, width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed Development Code changes to implement the TSP Page 15
•
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas, or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticitated average daily traffic (ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists,bicyclists,and pedestrians;
k. Access needs for emergency vehicles. -
Proposed Development Code changes to implement the TSP Page 16
• •
TABLE■4: n.1" • e . 7', lia .7'1441 _
Type-o•f-S4i-eat
.•Widtli-(fee4
Aite4a4 0±-90= 12 'lane
Major Collector 402--801 444
N14,-nef-C-Ielleetot
a. Through street with:
Less Than 1500 ADT 50'
Less Than 500 ADT 167
Less Than 200 ADT VI
b. Cul de sac dead end streets:
Less Than 500 ADT
Less'Than .200 ADT 12 24;
(Cul de saes shall.ba-no more than 200 •
feet long-and
dwelling-units)
T-iim--,kfennds for.Dcad cud Streets in 50 raditt:i 42 iadvas
InduStfial-and-C-TOmMer-e•iaT.Zones-Only
• :'. 47 radins 4:0 i6aid4
&Tets - -
Alley: Residential
20' 20'
•
•
•
Proposed Development Code changes to implement the TSP Page 17
Table 18.810.1
Minimum Widths for Street Characteristics
G7
Type of Street 3 c _ 3
. „ , ., •
Arterial 64:7_128! rie.5. 2 - 7 (Refer .12,' N/A .'{N.ew Ste_) e.'(.Res. & Ind.,.zon.os-) 5' 12 T
to TSP)
5-6'(Exist_in treets.) 191(Comm, Zones)
Collector 58'-96' Varies 2- 5(Refer 11' N/A 6' (New Streets) 6' (Res. & Ind, Zones) 5' 12'x"
to TSP)
5'-6' (Existing Streets) 8' (Comm. Zones)
Neign9rhoQd._Route 5_0:7...5_8: 28'-36' 2 10: 8: 5'7_ 5'.-6'(2) 5' NIA
Local .
l.nntus1ria.lLCommerciai 52 36' 2 LA 5,756f) 5° . N/A
Local: Residents N/A
• Under 1500 ADT 54'I50'm 32128'3) 2 8' (both sides) N/A 5'-6'(2)
• Under 500 APT 50'/46'(33 28'/24'(3] 2 8' (one side) NLA
• Under 200 ADT , 46'I42'm 24120'3) 2 No Parking) N/A
Cul-de-sac bulbs in 50' 42' radius N/A NIA N/A N/A
Industrial and radius
AD
Commercial zones
Cul-de-sac bulbs in 1 40' radius N/A N/A NIA N[A NIA
Residential zones radius
Al*: Residential L 16' N/A N/A N/A N/A NLA
Alley: Business 20' Q N/A N/A N/A N/A NLA
1 Median r-.uired for 5 and 7 lane roadways. They are optional for 3 lane roadways.
2 Sidewalk widths for these streets shall be 5 ft with landscape strip: 6 ft if against curb (if permitted in accordance with 18.810.070.C).
3"S in Stre- " r..: . .'• s ar- •er 't-• i ii-re c • - t. an. review c iteria are met. Re er to orre •ondin• cross se to s
.( it - :.:10. : : 14 al• 1: : I )for details and conditions.
Proposed Development Code changes to implement the TSP Page 18
• •
- Figure 18 810 1
Ai-WT.411s Sample_Crsns__S_c•ctions
../...7-- .
•••,:"_,•,-;, ...":,-
.11‘'' <,
4 .-_ 7,-.-------- ...4
, _- fr,
.
*'
---.2z-
•5'8-10'5.5' 6.Bie i 12' 12' 16.8kei 5.5' ;8-10y7
i: 1 1 :
R/VV 64-68'
2 Lane 641-68'li/W
.7
Jr-
-.
0.1111.; Ill C . p
___ ,.:,,,,.. ..............--t-- Istim....,..,
.5' 12 Median/
H8-10'1 5.5';6'Bike 17 Turn Lane 17 6.1]ke,5.5' 8-10'
I -i ____H_ , 1- 1H
I-
R/W 76-80"
3 Lane 7640'RAN
,.,
.:-',":'---, - ,..
__ .,,,L.,....
=; : ;•"---:"''
..1., ,.-i C. ,........‘j
i•?! •■ -"t -err,M = -II
I i mow. "MINIIR. li
. .
, Ir..-.....4 -
12'Median/
.5'8-10', 6' 1.6'Bice, 12' 12' i Turn Lane_ 1 12' i_ 12 5.5' i.8-10'451
-1
R/W 100104'
5 Lane 100404'RH
. s-%,
,,,. ..
,,_ _-.=.;---'-'c------,
4,....-_,,..
- Y
—_.
41111111L, ...wow -.1./zoi
Pr
rumgoimel°'" '° ;.-.•11''''';''''
-- 1
12'Median/ -.06,•1*.-:
8-10' 5.5' 6'Bike 12' , 12' 12' , Turn lone 1 12' 12' 12' Bike 6'I 5.5' 8-10' 5'
I I I I I
WW 124-128'
I
7 Lane 1241-128'R/W
____________
Proposed Development Code changes to implement the TSP Page 19
0
0 .
Figure 18.810.2
Collector Sample Cross Sections .
.,.-. .>
N <
‘,1-'-'
:i
MEMO 1,
‘.....:=
IINImiM
r _ 3,'",;(•.5'. ""oV:;I:,. _ ..i
.5' 6-8' 5.5' 6'Bike. 11' 11' .6'Ble 5.5'
I 1-
R/W 58'-62'
2 Lane 58'-62'R/W
...,--,.
----, ,,,Lf
- ------‘9D. --
ii
• rrk...u;---„,z.,-,; b.-_--,-:•=1:LL2., "7-...:,.....witai.,...:....m
12'Median/
.5'
H 6-8': 5.5' 6'Bile 11' Turn Lane 11' s 6'Bike 5 5' 6-8' .5'
3
R/W 70-74'
I I
3 Lane 70'-74'R/W
.,-.;es+ `•,.
4:--. ,.... ...'.:
...,...--11:4:".',,, _:, ,,_......1-7:\)C:4. '.:•• ,,------MC nt:--.
L..-X...jr
>4!"
4.1_!.-_,„ .--.1 ___
.____
......
-
12'Median/
6-8' i 5,5' 6'Bike 11' : 11' I Turn Lane f 1 1' } 1' 5.5' 6-8' 5
My 92-96'
5 Lane 92'-96'RAN
Proposed Development Code changes to implement the TSP Page 20
III •
- Figure 18,81 0.3
Neighborhood Routea
Sample C.EQS.S.Sections_
.-
: . .
,.,•_..„,:--i' 'ii\-4-W • V‘''''.17-;:f,,,,,-1
'--zw,- ...•,-, -- ,— ---..i.
Fl ,i_ ii it,
.5'
:. 5' , 5.5', 0 28' 5.5' 5' :5' ' 5' 5.5'I L
32'
Q : 5.5' I 5' 5."
I I
I R/W 50' i I [VW 54'
No Parking on One Side With Parking on Both Sides
---,- ---,-.
. , .-,-----
ti, 2,--c---4r ,---,•:ir
traisigia---1
36'
6'Bike, 12 12' A.'Bike, 5.5' , 5'
, -t- -}-i
1-- R/W 58' I
With Bike Lanes/No Parking
Figure 18.S10,4 •
Local Residential Streets_-<1_,500_vpd
A. Standard(sample) B. Skinny Street Option(criteria)
. r; , -.,.... .- ---2.•,'-
.,j.::::% ,;,•-..: ...::,,,--ne---......
'-'- .-4•!ti.--"- ',"---:-..-;}D .,..'"
. ,F, •-•,i
It 'aiP
n—.
El
5.'
__ _ I 5.5'in_______ 32 ___r2_i 5.5 5LH -.. I
___RP/V 54' :: I LS' 7P..414' Trml Lane F.7biTer 5 5' : ;:
3': S. Manzi., PIAv.‘--7—'ting I.3.i 5.
On-street Parking '..r.7.:ik 9"ip i._ 20' .1 5crip
i Filvement
<1500 vpd * .. • .1
Eghs-of-.**
If parking on both sides,
block length not to exceed 600 feet Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
Proposed Development Code changes to implement the TSP Page 21 •
•
• •
Figure 18_810.5
Local Residential Streets<500 vpd •
A. Standard(sample) B. Skinny Street Option(criteria)
�''!tatffY33 j1M _�
�I d
G5. 5' , 5.5' 28 5.5'. 5' .5 ® t
R/W 50' T 161T
3.5' Parking Trawl no ,,•
Residential Local Street/Cul-de-sac P"n"P='= s
Sid.ra4 2a' Sidewalk
One Side On-street Parking Pavement
<500 vpd 2.1.54.a5.4ay.
Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd. •
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of(I)off-street parking space for
every 20 feet of restricted street frontage.
Figure 1.$_$10.6
Local Residential.Sheet<200 vpd
•
A. Standard(sample) B. Skinny Street Option(criteria)
it
.5
5 5.5' 24' 5.5' . 5' 7 :PWy
an ,,,,,µ„y,•
Susarall P S'"P 51e..vn
Cul-de-sac/Residential Local Street
<200 vpd Criteria:
• Must provide a minimum of(1)off-street parking space
(No parking) for every 20 feet of restricted street frontage.
• No parking permitted within 30 feet of an intersection.
F. Future street plan and extension of streets.
1. A future street plan shall:
a. Be filed by the applicant in conjunction with an application for a subdivision or partition. •
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall may_prepare
a future streets proposal. Costs_of the City-preparing a future streets proposal shall be
Proposed Development Code changes to implement the TSP Page 22
. •
reimbursed for the time involved. A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus routes, pullouts or other transit facilities, bicycle routes and
pedestrian facilities on or within 530 feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed. -
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
G_—Streetspacingand accessmanagement. Refer.to 18.705.430,11,
( H_. Street alignment and connections.
1. Full street connections with spacing_of no more than 530 feet between connections is required
exce.t. ,_where:_:= re<<ented.__by barriers...__such-_as....._to _o -a hy,._..._railroads._._freewa -s_.... _re.-exitingr
develo meets,_lease_..prod_isions,-easement$,_c9_venailts=4r othei_restl ctigns existingsrior to._May
1,1995_whic h„preelude street_comiections A_ to street connectionmay also be Qurozed dkie to
a regulated water_feature ifregulations_would n4t_permit construction,
-1-. Staggering of streets making "T" intersections at collectors and arterials shall not he designed so
that jogs of less than 300 feet on such streets are created, as measured from the centerline of such
street.
2. Spacing between local street intersections shall have a minimum separation of 125 feet.
2.4. All local and minor ., neighborhood routes_and collector streets which abut a development site
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such,as schools, shopping
areas and parks.
45. All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed Development Code changes to implement the TSP Page 23
• •
#I. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as I
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
IJ. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
3K. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than I
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater I
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul-de-sac shall be measured from the centerline intersection point of the two
streets to the radius point of the bulb.. .- - - - •- - - -- -. -
intersecting street to the farthest point of the cul de sac.
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
EM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and-as approved by the City
Engineer,-
MN. Grades and curves.
______1_._ Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet), and
2. Centerline radii of curves shall be as determ ned_by the C _Engineer.- : :- - -. - !! -- :
! ! -- - ! - -- - !! - - .
and
Proposed Development Code changes to implement the TSP Page 24
• •
. . • • . • . . : .
percent or less. Landings are that portion of the street within 20 feet of the edge of the
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required; except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards.
OP.Streets adjacent to railroad right-of-way. Wherever the proposed development contains or is adjacent
to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the
following:
1. A parallel access street along the arterial or major-collector;
2. Lots of suitable depth abutting the arterial or major-collector to provide adequate buffering with
frontage along another street;
3. Screen planting at the rear or side property line to be contained in a nonaccess reservation along
the arterial or major collector; or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR. Alleys,public or private.
1. Alleys shall be no less than 20 feet in width. In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City,it
Proposed Development Code changes to implement the TSP Page 25
• •
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks, and multi-family residential developments.
TI,
J.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
UV. Street signs. The City shall install all street signs, relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
L'-X. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
Xi. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
=Z.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
ZAA. Street cross-sections. The final lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development,whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed Development Code changes to implement the TSP Page 26
• •
2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1-1/2 inches in thickness. (Ord. 99-22)
AB Traffic Calming. When, in the opinion of the City Engineer, the proposed development will
create a negative traffic condition on existing neighborhood streets, such as excessive speeding. the
developer may be required to provide traffic calming measures. These measures may be required
within the development and/or offsite as deemed appropriate. As an alternative, the developer may
be required to deposit funds with the City to help pay for traffic calming measures that become
necessary once the development is occupied and the City Engineer determines that the additional
traffic from the development has triggered the need for traffic calming measures. The City Engineer
will determine the amount of funds required, and will collect said funds from the developer prior to the
issuance of aa_ertfficuteof oocupancy cr in thesa_se Qf suh- ivision,-prior to_the_approval_of the_final
plat. The funds will be held to ty he City for a_perikd of five (5) years from the date of issuance of
certificate of occu ancy.,_.Qr in_thacasoof a Skit/division. the clatepf anal prat approval_Any-funds of
u-sed_by the_Cit_y_within the five-year timo.period will Ike refunded t4 the dey_aloper.
AC. Traffic study_
__1__A._tra..ffic stud _shah he required for all ne«�or_expanded_uses_or developments under any of_the
followin 7 circumstances
h en,..they_generate_a_10%or_.greater increase in existing traffic-to high collision_intersections
identif ed_by__Washington_Count_y_.
b, Trip generations from de_v_elot)ment_onto the City street_atthe_point of access and_the existing
a. DT fall within the following ranges:
Existig A D T ADT_to he added by development
0-3.,000_y d 2.00fiv d
3,041-6,0J ypd I OQO vpd
>0,000 yhd 500 ypd or more
c_. If any of the following issues become evident to_the City engineer:_
(1)_.}_Iih traffc__v_o]urnes on_the adjacent roadway_that mayaffect_rnovement_ nto_2r out of the
site,
(2) Lack of existing left-turn lanes onto the adjacent roadway at theoroposedaccess rive()
(3) Inadequate horizontal_or yertical sight distance at access points
(4)_The proximity_of the proposed access to other existing drives or intersections is_a potential
hazard
(5) The proposal requires a conditional useermit or involves a drive-through operation
(6) The proposed deve_lop_ment may result in excessive traffic volumes on adjacent tocalstreets:
2. In addition, a traffic study may be required for all new or expanded uses_or developments under
any-_of the following circumstances:
a _when the site is within_5Q0 feet of an QDQT facility and/or
h.._—trip_generation from a development_adds 300 or more vehicle tripsper day_to an_ODOT facility
Proposed Development Code changes to implement the TSP Page 27
•
and/or
c. trip generation from a development_adds 50 or more peak_hour trips to an ODOT facility.
18.810.040 Blocks
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing
'adequate building sites for the use contemplated, consideration of needs for convenient access,
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2,0001,800 feet measured along the
centerline_of the streets right of way line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or
b. For blocks adjacent to arterial streets, limited access highways,major collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is net pessibleexempted by B_1_ above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
_ be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse, or drainageway, there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make arrangements with the
City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated, and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
Proposed Development Code changes to implement the TSP Page 28
•
•
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single-family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation, and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are likely to be
redivided, the Commission may require that the lots be of such size and shape, and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
A,_._..A. Sidewalks. All industrial streets and_pr yate__streets:._shall have sidewalks meeting City standards
along at_teastone side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development, even if no sidewalk exists on the other side of the street
B. 12equirement of developers
_ ___ 1.._- As_part_of_any development_proposal,_or_change_in use_resul ting_in an_additiopal_ 1,000
ve hicle trips or more per day an plicant shall be required to identify.direct, safe (125 x the_straight line
distaneeLpedestnan routers within 1/2 mile of their site to_alt transit facilities and Neighborhood_Activi
Centers (schools,_.parks, libraries etc,)_ additionthe developer may be required toarticipate in the
removal of any aps in the edestrian system off—site if justified by the development.
_Where js an existing sidewalk,on the same side ofthe street asthe development_,within 300
feet of a development_site-in-either-direction, the sidewalk_sha11_be extended from the site_tomeet the
existing-sidewalk, subject to iough_proportionality__(even if the sidewalk does not serz e a neighborhood
aetivitycenter).
BC.Planter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of any arterial or collector streets where parking is prohibited
adjacent to the curb, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; of it would conflict with
the utilities, there_are significant natural features (large trees, water features, etc) that would be
destroyed if the sidewalk werebcated as required.,,orwhere there are existin structures in close
proximity to the street (15 feet or less)-Additional consideration for exempting—the_pl_anter strip
requirement may begi_en on a case hy_case basis if a property_abuts more than one street frontage.
•
Proposed Development Code changes to implement the TSP Page 29
•
CD. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
in width, and:
•
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
EE.Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed,then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property in question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
EG.Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings, commercial buildings or public buildings and/or parks; and
Proposed Development Code changes to implement the TSP Page 30
• •
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord. 99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park, playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord. 99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
operation of the sewage treatment system.
18.810.100 Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
Proposed Development Code changes to implement the TSP Page 31
• •
2. Where possible, inlets shall be provided so surface watei is not carried across any intersection or
• allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
, Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
18.810.110 Bikeways and Pedestrian Pathways
A. ---Bikeway extension.
a_standard�bike lanesshah be required aloe all Arterial and Collector routes and where
identified on the City's adopted bicycle plan in the Transportation System-Plan (TSP)_
2. Developments adjoining proposed bikeways identified on the City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3._Anynew street improv=ement project shall include b iev-cle lanes asrequired in this document
and_on the adopted bi.cyde plan.
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
•be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
2. Minimum width T. - . multi_use paths separated from the road is eight ten
(10)_-feet._1Thew dth maybe reduced tq eight afeet if there are environmental or other.constraints_
3,. The_nlninumwidth for pedestrian onlyoff-street_paths is five(5)feet.
_4Design standards._for dike and .pedestrian-ways_shall be_determined_by the_City_Eng ieer,
Proposed Development Code changes to implement the TSP Page 32
• •
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above, and:
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer, shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information, easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement.
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common, but not the
only, such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
Proposed Development Code changes to implement the TSP Page 33
• •
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities,unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front-foot basis.
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
• existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City,permit fee paid, and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Proposed Development Code changes to implement the TSP Page 34
• •
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments) shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 . Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices,and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)
Proposed Development Code changes to implement the TSP Page 35
•
•
Exhibit A-4
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions.in alphabetical order and renumber the remaining
definitions accordingly:
"Neighborhood Activity Center"- Ause such as schoels,_parks,libraries. shopping areas,
employment centers_or_pools whicl p ovide recreational or social for groups of
people. ---.-- services_-..�..- ---
"Traffic Flow Plan" - A plan submitted with a proposal for skinny streets that shows the
potential queu.ing_._pattern that will allow for safe and efficient travel of emergency
vehicles, service vehicles_and_passenger vehicles with minimal disturbance. This may
include a combination of strategic driveway locations, turnouts or other mechanisms
which_will foster safe and efficient travel.
18.360.090.A.11.a '
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B
change the 3`d sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets ...
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
•
Additional TSP implementation code amendments Page 1
• •
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
18.745.050.C.2.b •
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
•
i
Additional TSP implementation code amendments Page 2
TPR Compliance Matrix Exhibit B
Attached are the TPR requirements with an explanation of how they are addressed in the existing City of Tigard
Development Code and in the proposed amendments.
(Where there is a dashed line- it indicates that there is not a standard to.be addressed,just an intro in to the
standards.)
660-12-0045 How Addressed in current code I Proposed amendments
TPR Requirement •
(3) Local governments shall adopt land use or subdivision
regulations for urban areas and rural communities as set forth
below. The purposes of this section are to provide for safe and
convenient pedestrian, bicycle and vehicular circulation
consistent with access management standards and the function
of affected streets, to ensure that new development provides
on-site streets and accessways that provide reasonably direct
routes for pedestrian and bicycle travel in areas where
pedestrian and bicycle travel is likely if connections are
provided, and which avoids wherever possible levels of
automobile traffic which might interfere with or discourage
pedestrian or bicycle travel.
(a) Bicycle parking facilities as part of new multi-family 18.765.050.E states the minimum
residential developments of four units or more, new retail, parking requirements for all use
•
office and institutional developments, and all transit transfer types. This is required as part of
stations and park-and-ride lots;
any land use review.
(b) On-site facilities shall be provided which 18.765.050 provides bike parking 18.810.070 is being amended to include a
accommodate safe and convenient pedestrian and bicycle design standards requirement of the developer to show connections
access from within new subdivisions, multi-family to neighborhood activity centers within /z mile of
developments, planned developments, shopping centers, and 18.705.030.F (Access, Egress and development and require consideration of
commercial districts to adjacent residential areas and transit Circulation—required walkway improvement requirements depending on
stops, and to neighborhood activity centers within one-half location) addresses walkway proportionality. The amendment also required the
requirements for multi-family, removal of gaps in the sidewalk within 300 feet on
Page 1
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
mile of the development. Single-family residential industrial or commercial the same side of the street as a development
developments shall generally include streets and accessways. development. (subject to rough proportionality).
Pedestrian circulation through parking lots should generally
be provided in the form of accessways. 18.810.040 (Street and Utility
Improvement Standards—Blocks)
addresses pedestrian connections
when full street connections are
not possible
18.810.070 (sidewalks) requires
all public streets to have
sidewalks
(A) "Neighborhood activity centers" includes, but 18.120.030 is being amended to include a
is not limited to, existing or planned schools, parks, definition of Neighborhood Activity Center.
shopping areas, transit stops or employment centers;
(B) Bikeways shall be required along arterials and Sidewalks currently are required 18.810.110.A is amended to include the
major collectors. Sidewalks shall be required along along all public streets. requirement that bike lanes be located on all
arterials, collectors and most local streets in urban areas, Development code does not have arterials and collectors and any additional routes
except that sidewalks are not required along controlled a bike lane requirement but refers identified in the TSP for any new construction or
access roadways, such as freeways; to the City's comprehensive plan. improvement project.
(C) Cul-de-sacs and other dead-end streets may be 18.810.030.K regulated cul-de-
• used as part of a development plan, consistent with the sacs and states that they can't be
purposes set forth in this section; more than 200 feet long. IF a
variance is granted and the cul-
de-sac
is greater than 300 feet,
pedestrian connections are
required. This is in addition to
the block length standards which
may also require additional
pedestrian connections through a
block.
Page 2
•
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(D) Local governments shall establish their own 18.810 establishes standards that There are amendments which address street
standards or criteria for providing streets and accessways regulate street spacing and block spacing and block lengths, however, they continue
consistent with the purposes of this section. Such lengths intending on limiting out to limit out-of-direction travel and provide greater
measures may include but are not limited to: standards for of direction travel. clarification to increase efficiency and safety.
spacing of streets or accessways; and standards for
excessive out-of-direction travel;
(E) Streets and accessways need not be required where 18.810.040—Block length •
one or more of the following conditions exist: standards provide for this
(i) Physical or topographic conditions make a exception in the standard.
street or accessway connection impracticable.
Such conditions include but are not limited to
freeways, railroads, steep slopes, wetlands or
other bodies of water where a connection could
not reasonably be provided;
(ii) Buildings or other existing development on
adjacent lands physically preclude a
connection now or in the future considering the
potential for redevelopment; or
(iii) Where streets or accessways would violate
provisions of leases, easements, covenants,
restrictions or other agreements existing as of •
May 1, 1995 which preclude a required street
or accessway connection.
(c) Where off-site road improvements are otherwise Any road is required to be
required as a condition of development approval, they shall constructed to the standards
include facilities accommodating convenient pedestrian and called for in our code. As shown
bicycle travel, including bicycle ways along arterials and within this matrix, the code
major collectors; requires sidewalks but additional
amendments have been made to
Page 3
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
define required bikeway
locations.
(d) For purposes of subsection(b) "safe and convenient"
means bicycle and pedestrian routes, facilities and
improvements which:
(A) Are reasonably free from hazards, particularly The City's Municipal code
types or levels of automobile traffic which would interfere prohibits obstructions on public
•with or discourage pedestrian or cycle travel for short sidewalks
trips;
(B) Provide a reasonably direct route of travel The access standards,block
between destinations such as between a transit stop and a length standards and requirement
store; and for sidewalks provides a In addition, an amendment is proposed to have the
(C) Meet travel needs of cyclists and pedestrians reasonably direct route of travel developer review routes within 300 feet
considering destination and length of trip; and considering between destinations and meets (approximately V4 mile) from the development site
that the optimum trip length of pedestrians is generally 1/4 the travel needs of cyclists and and, if proportional, make necessary
to 1/2 mile. pedestrians improvements to complete"gaps"
(e) Internal pedestrian circulation within new office parks 18.705.030.E requires walkways
and commercial developments shall be provided through within commercial developments
clustering of buildings, construction of accessways, walkways
and similar techniques.
To support transit in urban areas containing a
population greater than 25,000, where the area is already
served by a public transit system or where a determination has
been made that a public transit system is feasible, local
governments shall adopt land use and subdivision regulations
as provided in (a)-(f) below:
(a) Transit routes and transit facilities shall be designed to SDR standards 18.360.090.11
support transit use through provision of bus stops, pullouts requires development to provide
and shelters, optimum road geometrics, on-road parking transit amenities as required by
Page 4
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
restrictions and similar facilities, as appropriate; tri-met during the development
review (if proportional and
justified)
(b) New retail, office and institutional buildings at or near
major transit stops shall provide for convenient pedestrian
access to transit through the measures listed in (A) and (B)
below.
(A) Walkways shall be provided connecting
building entrances and streets adjoining the site; 18.705.030.f
(B) Pedestrian connections to adjoining properties
shall be provided except where such a connection is 18.810.070—sidewalks
impracticable as provided for in OAR
660-012-0045(3)(b)(E). Pedestrian connections shall
connect the on site circulation system to existing or
proposed streets, walkways, and driveways that abut
the property. Where adjacent properties are
undeveloped or have potential for redevelopment,
streets, accessways and walkways on site shall be laid
out or stubbed to allow for extension to the adjoining
property;
(C) In addition to (A) and (B) above, on sites at
major transit stops provide the following: 18.360.090.11 requires •
(i) Either locate buildings within 20 feet of consideration of transit facility
the transit stop, a transit street or an improvements as part of
intersecting street or provide a development review (which
pedestrian plaza at the transit stop or a covers ii to v). Building
street intersection; placement standards are already
(ii) A reasonably direct pedestrian in place in the Tigard Triangle
connection between the transit stop and and as part of the Washington
building entrances on the site; Square Regional Center.
(iii) A transit passenger landing pad Additional standards for building
Page 5
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
accessible to disabled persons; placement outside of these transit
(iv) An easement or dedication for a oriented areas are not appropriate. _ _
passenger shelter if requested by the
transit provider; and
(v) Lighting at the transit stop.
Airil Local governments may implement 4(b)(A) and(B) While not specifically designated
Wve through the designation of pedestrian districts and pedestrian districts, the Tigard
adoption of appropriate implementing measures regulating Triangle and the Washington
development within pedestrian districts. Pedestrian districts Square Regional Center
must comply with the requirement of 4(b)(C) above; implement the requirements of
4(b) (C)
(d) Designated employee parking areas in new 18.765.030.F required parking
developments shall provide preferential parking for carpools lots in excess of 20 long-term
and vanpools; parking spaces to provide
preferential long-term carpool
and vanpool parking for
employees and other visitors to
the site.
(e) Existing development shall be allowed to redevelop a Not specifically provided for,but
ortion of existing parking areas for transit-oriented uses,
�
would not be disallowed since
luding bus stops and pullouts, bus shelters, park and ride nothing on the code prohibits it.
stations, transit-oriented developments, and similar facilities,
where appropriate;
(f) Road systems for new development shall be provided 18.810 has street standards that
that can be adequately served by transit, including provisions provides for adequate width of
of pedestrian access to existing an identified future transit pavement and turning radius, etc
routes. This shall include, where appropriate, separate that will provide for transit.
accessways to minimize travel distances. Sidewalks are required along all
public streets
Page 6
•
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(g) Along existing or planned transit routes, designation Existing zoning along transit
of types and densities of land uses adequate to support transit. routes is transit supportive—no
changes are needed
(5) In MPO areas, local governments shall adopt land use The Tigard Triangle area,
and subdivision regulations to reduce reliance on the Washington Square Regional
automobile which: Center area and Central Business
(a) Allow transit oriented developments (TODs) on lands District zone have provisions for •
along transit routes; mixed use development and
street and design standards which
(b) Implements a demand management program to meet encourage transit oriented
the measurable standards set in the TSP in response to 660- development
012-0034(4).
(6) In developing a bicycle and pedestrian circulation plan TSP provides bike and pedestrian Proposed amendments specifically require
as required by 660-012-0020(2)(d), local governments shall master plan. The development pedestrian or bike improvements if shown on the
identify improvements to facilitate bicycle and pedestrian code currently requires walkways pedestrian or bikeway plan, if roughly
trips to meet local travel needs in developed areas. and sidewalks, however we need proportional.
Appropriate improvements should provide for more direct, to amend the code to specifically
convenient and safer bicycle or pedestrian travel within and require if shown on the pedestrian
between residential areas and neighborhood activity centers or bikeway plan.
•
(i.e., schools, shopping, transit stops). Specific measures
include, for example, constructing walkways between cul-de-
sacs and adjacent roads, providing walkways between
buildings, and providing direct access between adjacent uses.
(7) Local governments shall establish standards for local Current code required pavement The TSP, which provides the foundation for the
streets and accessways that minimize pavement width and width between 24' and 32' for amendments being proposed, was developed with
total right-of-way consistent with the operational needs of the local streets (actual width the help of a Citizen Task Force and Technical
facility. The intent of this requirement is that local depends on ADT and whether Advisory Committee and involved several public
Page 7
•
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
governments consider and reduce excessive standards for parking is provided on the street) information meetings to gather input and
local streets and accessways in order to reduce the cost of and up to 12 feet per lane for comments and 2 formal public hearings. After the
construction, provide for more efficient use of urban land, arterial streets development and adoption of the TSP, a group of
provide for emergency vehicle access while discouraging City Staff from Planning and Engineering and a
inappropriate traffic volumes and speeds, and which representative from Tualatin Valley Fire and
accommodate convenient pedestrian and bicycle circulation. Rescue met over several months to develop code
mot withstanding subsection (1) or(3) of this section, local language to implement the TSP. The discussions
et standards adopted to meet this requirement need not be included the TPR"skinny street"requirement.
adopted as land use regulations. After review and discussion, it was determined
that the safe harbor widths were acceptable,
provided a traffic flow plan was submitted to
verify that the distribution of driveways, no
parking areas, etc would allow efficient queuing
and traffic flow as the State's "Neighborhood
Streets Design Guidelines" assumed. Additional
assurances were needed to ensure that adequate
off-street parking was provided for streets that had
parking on one side only. It was determined that
the existing width standards would remain for
those that did not want to submit a traffic flow
plan or provide additional assurances for off-street
. parking, but the option to go to narrower streets
would be provided as well. While technically, the
wider street width is the default because no
additional documentation is required, both street
width standards are acceptable and available for
developments on local streets.
Page 8
•
f
• • Exhibit C
PLANNING COMMIS SION
RECOMMENDATION TO THE
CRY OF TIGARD
TIGARD CITY COUNCIL ComrriunityDevelopment
Shapiiig'A Better ,
_ 'Community
SECTION I: APPLICATION SUMMARY
FILE NAME: TRANSPORTATION SYSTEM PLAN
CASES: Zone Ordinance Amendment (ZOA) 2002-00004
PROPOSAL: The proposal is to formally adopt Development Code standards to
fully implement the Transportation System Plan (TSP) that was
adopted in January 2002.
APPLICANT: City of Tigard
13121 SW Hall Boulevard
Tigard, OR 97223
LOCATION: All areas within the City of Tigard.
APPLICABLE
REVIEW
CRITERIA: Oregon's Statewide Planning Goals 1, 2 and 12; Oregon Administrative
Rule 660; Metro Regional Transportation Plan (RTP); Comprehensive
Plan Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3, and
Community Development Code Chapter 18.380.020 and 18.390.060.G. •
SECTION II: PLANNING COMMISSION RECOMMENDATION:
The Planning Commission moved to forward the Development: Code amendments• to
implement the Transportation System Plan (TSP) to the'City Council'as shown irrlExhibit.A-
1 through A-4, and in the summary of proposed changes,;based.on the findings,that all
relevant criteria are satisfied: The TPR compliance matrix. (Exhibit B):. and this.
recommendation report provide the analysis and findings which demonstrate compliance
with all relevant criteria.
STAFF REPORT ZOA 2002-00004 Page 1
• •
SECTION III: BACKGROUND INFORMATION
The City of Tigard began looking at updating the Transportation System Plan (TSP)
several years ago. With the help of a 12 member task force, agencies and staff, a draft
TSP was produced which takes into account the existing traffic conditions in Tigard,
community needs and goals and the anticipated future demands on the transportation
system. The TSP and Comprehensive Plan amendments were adopted by the City
Council in January 2002. An additional step necessary to fully implement the TSP was
developing amendments to the Development Code to reflect changes to the TSP. The
Planning Commission and City Council held work sessions on the proposed Development
Code amendments in June. The proposed changes reflect the comments received at the
work sessions. The Planning Commission held a public hearing on August 5, 2002. No
testimony was offered at the hearing. As an addition to the Planning Commission's motion
to forward the amendments to the City Council, the Commission recommended that staff
provide a presentation to the CIT prior to the Council's public hearing. In accordance with
the Commission's recommendation, a CIT presentation is scheduled for the September 5,
2002 meeting prior to the Council's September 10, 2002 hearing.
SECTION IV. SUMMARY OF APPLICABLE CRITERIA
Chapter 18.380 states that legislative text amendments shall be undertaken by
means of a Type IV procedure, as governed by Section 18.390.060G.
Chapter 18.390.060G states that the recommendation by the Commission and the
decision by the Council shall be based on consideration of the following factors:
A. The Statewide Planning Goals and Guidelines adopted under Oregon Revised
Statutes Chapter 197;
B. Any federal or state statutes or regulations found applicable;
C. Any applicable Metro regulations;
D. Any applicable Comprehensive Plan Policies; and
E. Any applicable provisions of the City's implementing ordinances.
SECTION V: APPLICABLE REVIEW CRITERIA AND FINDINGS
STATEWIDE GOALS
Citizen Involvement: Goal 1 requires a citizen involvement program that ensures the
opportunity for citizens to be involved in the planning process.
Tigard Comprehensive Plan Policy 2.1.1 and Tigard Community Development Code Chapter
18.390 provide for citizen participation and notice. Notice of the Planning Commission and
City Council hearings and opportunity for response was advertised in the local newspaper.
Notice was sent to Department of Land Conservation and Development in accordance with
their notice requirements. This goal is satisfied.
STAFF REPORT ZOA 2002-00004 Page 2
• •
• Land Use Planning: Goal 2 requires, in part, that adopted comprehensive plans be
revised to take into account changing public policies and circumstances.
This goal is met because the City has applied all relevant Statewide Planning Goals, City
Comprehensive Plan policies and Community Development Code requirements in the
review of this proposal as discussed throughout this staff report.
Transportation: Goal 12 requires a safe, convenient and economic transportation
system.
The TSP has been prepared in accordance with the Statewide Planning Goals and
requirements. Oregon Administrative Rule 666, the compliance with which is discussed
further in this report, implements the Statewide Transportation Goal 12. The plan has been
reviewed by ODOT and DLCD.
COMPLIANCE WITH FEDERAL AND STATE STATUTES OR GUIDELINES
Oregon Administrative Rule: Section 660-12-0000 through 0070 is intended to
implement Statewide Planning Goal #12 by providing guidelines for local
governments to demonstrate compliance with Goal #12 through their Transportation
System Plans.
When the TSP was adopted, it was recognized that Development Code amendments were
needed to fully comply with the TPR. Attached as Exhibit B is a chart identifying how each
of the TPR requirements are addressed. Based on the information provided in Exhibit B and
in this section, staff finds that the TSP complies with the state statutes. There are no
specific federal standards that apply.
COMPLIANCE WITH METRO REGULATIONS
Regional Transportation Plan (RTP): The RTP takes the place of Metro Functional Plan
Title 6 (Regional Accessibility), and is consistent with Chapter 2 of the Regional
Framework Plan. The RTP provides a regional framework for transportation systems
and has its own criteria that must be addressed that are in addition to the
Transportation Planning Rule (TPR) requirements.
The TSP is consistent with the RTP and the proposed amendments include all language
required to be adopted by local jurisdictions. The only specific language that needed to be
changed to implement the RTP was the requirement to have local street spacing no less
than 530 feet apart to address connectivity requirements.
COMPLIANCE WITH COMPREHENSIVE PLAN POLICIES
General Policies: Policy 1.1.1(a) requires that legislative changes are consistent with
statewide planning goals and the regional development plan.
The proposal is consistent with statewide planning goals as addressed above under
`Statewide Goals'. The proposal conforms with the applicable portions of the Metro
Functional Plan that was approved for adoption on October 24, 1996 by the Metro Council.
This policy is satisfied.
STAFF REPORT ZOA 2002-00004 Page 3
• •
Citizen Involvement: Policy 2.1.1 states that the City shall maintain an ongoing
citizen involvement program and shall assure that citizens will be provided an
opportunity to be involved in all phases of the planning process. Policy 2.1.2 states
that opportunities for citizen involvement shall be appropriate to the scale of the
planning effort. Policy 2.1.3 states that the City shall ensure that the information on
planning issues is available in an understandable format.
A request for comments was sent to all affected jurisdictions and agencies. The Planning
Commission hearing was legally advertised with notice published in the Tigard Times. The
TSP had extensive notice and opportunities to comment. Because the current proposal is
simply an implementation of a previously adopted plan, the same level of public notice is not
necessary.
Transportation: Transportation Policies 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 were
adopted at the same time the TSP was adopted to incorporate the TSP
recommendations into the Comprehensive Plan. The policies are specifically
addressed below:
8.1.1 — requires the planning of transportation facilities to be done in a way that
enhances livability through the proper location of facilities, encouraging pedestrian
traffic and addressing issues of through traffic and speeding on local residential
streets.
8.1.2 — requires a balanced transportation system that incorporates all modes of
transportation.
8.1.3 — requires the effort be made to develop a safe transportation system through
the street standards and access management policies.
8.1.5 — requires the development of transportation facilities that are accessible to all
citizens and minimize out-of-direction travel.
8.2.3 — provides the minimum improvement level and dedication that should be
required of developers as a precondition of development to ensure that the
community's transportation system functions adequately.
The code amendments provide greater clarification of where bike lanes are required,
requires the identification and removal of gaps in sidewalks (if roughly proportional), has
local street spacing standards that will minimize out-of-direction travel, provide greater
access spacing standards and greater clarification of when transit amenities are required.
The proposed development code amendment changes are directly implementing the TSP
and Comprehensive Plan policies, therefore, the applicable Comprehensive Plan
standards have been satisfied.
COMPLIANCE WITH THE CITY'S IMPLEMENTING ORDINANCES:
The implementing ordinances are contained in the Tigard Community Development Code.
The applicable criteria identified in the Development Code are summarized in Section IV —
STAFF REPORT ZOA 2002-00004 Page 4
• •
Summary of Applicable Criteria and addressed in Section V — Applicable Review Criteria
and Findings. As this staff report demonstrates, all applicable criteria have been satisfied.
SECTION VI: COMMENTS (AGENCY. STAFF AND OTHER)
City of Tigard Engineering, City of Tigard Current Planning Division, City of Tigard
Operations, City of Tigard Public Works, City of Tigard Police, City of Beaverton, City of
Durham, City of King City, Washington County, Tigard-Tualatin School District, and Tri-
met have reviewed the proposal and offered no comments or objections.
Tualatin Valley Fire and Rescue reviewed the proposed amendments and indicated that
they find no conflicts with their interests. The provisions for skinny streets are acceptable
to the Fire District. They also state that the Fire District is currently developing traffic
calming device design criteria that will be submitted upon completion. The general
statement in the Development Code indicates only when they are to be installed. The Fire
District hopes that their criteria will be considered for design details.
DLCD reviewed the proposed amendments and offered comments which are summarized
below:
• They want to make sure that Tigard documents its process used to develop the local
street standards regarding narrow streets;
• They suggested changes which have been incorporated into the proposed
amendments that presents the narrow street option in a way that does not discourage
someone from using that method and as a method that is not favored.
• They provided suggested language which has been incorporated into the proposed
amendments for "Traffic Flow Plan" (formerly referred to as a queuing plan).
. They recommend against changing the block length standard from 1,800 feet to 2,120
feet and provided language that Washington County uses that they suggest we
consider.
Staff response: The change from 1,800 foot block length to 2,120 foot block length was
suggested to be consistent with the street spacing standards, however staff is not
opposed to retaining the original block length concept. Because the measurement system
is being changed from right-of-way line to centerline, the maximum block length dimension
will be 2,000 feet. This will result roughly in the same block length requirement as
currently existing and as recommended by DLCD staff.
Metro reviewed the proposed amendments and generally offered the same comments as
DLCD, specifically, they suggested changes that present the narrow street option in a way
that does not discourage someone from using that method and as a method that is not
favored and they recommend against changing the block length standard from 1,800 feet
to 2,120 feet.
The City of Tigard Urban Forester reviewed the proposed changes and offered the
following comments: "The planter strips should be at least five feet wide so that large trees
can be planted in order to create more tree canopy. I think that planter strips are a good
idea since the trees will be shading much more of the street, thus reducing the heat island
effect too common in this City!"
STAFF REPORT ZOA 2002-00004 Page 5
• • . -
Oregon Department of Transportation (ODOT) reviewed the proposed amendments ,
and offered comments summarized as follows: They appreciate our efforts to clarify when -
a traffic study is required, however a traffic study is not always needed to address ODOT
interests. They suggest changing 18.810.030.AC to state that a traffic study MAY (instead
of shall) be required if a site is within 500 feet of an ODOT facility and/or trip generation
from the development adds 300 or more trips per day to an ODOT facility and/or trip ,
generation from the development adds 50 or more peak hour trips to an ODOT facility.
They request that ODOT be notified of pre-applications to help make the determination of
whether a traffic study is required prior to a formal application being submitted and
deemed complete.
Staff response: The proposed development code language has been amended to include
ODOT's recommended changes
EXHIBITS:
EXHIBIT A-1 through A-11:- Proposed Development Code changes
EXHIBIT B: Chart addressing TPR criteria and Tigard's compliance status
fjPREPA D BY:I4ticiW
ulia Hajduk, DATE
Associate Planner
4(hi " 0,-O9, 0,
SIGNED:
Mark Padgett
Planning Commission Chair DATE
I:Irplan1ulia/TSP/implementation/cc packet/staff report—exhibit C.doc
STAFF REPORT ZOA 2002-00004 Page 6
• •
Attachment 2
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Traffic Flow Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right-of-way, the setback for a
structure must be no less than the required setback plus 1/2 the required right-of-way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on-street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP/DLCD-TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1
(Updated 5-3-02)
A
• •
Added sections requiring street connections to be spaced no less than 530 feet apart to address •
connectivity requirements. (18.810.030.G.1) (TSP/Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul-de-sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the measurement of block length from the right-of-way to centerline and adjusted the
maximum block length perimeter from 1,800 feet to 2,000 feet to accommodate the revised way of
measuring. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of"not possible". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right-of-way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation/POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2
(Updated 5-3-02)
DRAFillt •
CITY OF TIGARD Attachment 3
PLANNING COMMISSION
Meeting Minutes
August 5, 2002
1. CALL TO ORDER
President Padgett called the meeting to order at 7:00 p.m. The meeting was held in
the Tigard Civic Center, Town Hall, at 13125 SW Hall Blvd.
2. ROLL CALL
Commissioners Present: President Padgett; Commissioners Anderson, Buehner,
Mores, Munro, Scolar, Sutton, and Webb
Commissioners Absent: Commissioner Bienerth
Staff Present: Julia Hajduk, Associate Planner; Brian Rager, Development
Review Engineer; Jerree Gaynor, Planning Commission
Secretary
3. PLANNING COMMISSION COMMUNICATIONS
None
4. APPROVE MEETING MINUTES (taken out of order)
Commissioner Buehner moved and Commissioner Webb seconded the motion to
approve the July 15, 2002 meeting minutes as submitted. A voice vote was taken
and the motion passed by a vote of 7-0. Commissioner Sutton abstained.
5. PROCESS FOR MOTIONS - DISCUSSION
Discussion was held on the proper procedure for making motions. President
Padgett advised that Commissioners should "move", not "make a motion", to
approve; approve with changes in conditions (list changes); approve with conditions
listed in the staff report; disapprove; recommend to Council. Commissioners need
to include all the case numbers in the motion. The motion also needs to list the
findings (based on findings in staff report; conditions in staff report and testimony
heard). It was suggested that specific language be on a card for the
Commissioners to read when making motions. President Padgett will forward
suggested language to the secretary.
6. PUBLIC HEARING
6.1 ZONE ORDINANCE AMENDMENT (ZOA) 2002-00004 TIGARD
TRANSPORTATION SYSTEM PLAN IMPLEMENTATION
REQUEST: Amend the Tigard Development Code to reflect the Transportation
System Plan and Comprehensive Plan changes adopted in January 2002. The
proposed amendments also reflect the State of Oregon's Transportation Planning.
Rules (TPR) which include provision of skinny streets. The specific code sections
•
PLANNING COMMISSION MEETING MINUTES -August 5,2002-Page I
• •
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and
18.810. LOCATION: Citywide ZONE: N/A — Citywide APPLICABLE REVIEW
CRITERIA: Statewide Planning Goals 1, 2 and 12; Oregon Administrative Rule •
(OAR) 660, Metro Regional Transportation System Plan; Comprehensive Plan
Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 and Community
Development Code Chapters 18.380.020 and 18.390.060.G.
STAFF REPORT
Julia Hajduk presented the staff report on behalf of the City. She reported that
comments from worksessions with the Planning Commission and City Council
were incorporated into the proposed code amendments. She noted that although
the Planning Commission recommended doing away with setback sidewalks,
Council disagreed. Language was added to clarify cases for properties with
more than one frontage. Hajduk noted that all the proposed code amendments
meet required State goals and policies and are consistent with the Transportation
Planning Rule.
It was recommended that this proposal be presented before the CITs before the
Council public hearing.
PUBLIC TESTIMONY
None
•
PUBLIC HEARING CLOSED
Commissioner Buehner moved the Planning Commission forward to Council, the
amendments of the development code specified as ZOA 2002-00004, based on
the staff report and the public hearing, specifically including Exhibits A-1 through
A-5 and B; and also recommending that a presentation on the pertinent
amendments be made at the CIT meeting prior to the public hearing in front of City
Council. Commissioner Sutton seconded the motion. The motion passed
unanimously.
7. OTHER BUSINESS
At present, there are no meetings scheduled for September.
8. ADJOURNMENT
The meeting adjourned at 7:18 p.m.
Jerree Gaynor, Planning Commission Secretary
ATTEST: President Mark Padgett
PLANNING COMMISSION MEETING MINUTES -August 5,2002-Page 2
•
•
• •
AGENDA ITEM# t-v
FOR AGENDA OF June 18, 2002
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
ISSUE/AGENDA TITLE Development Code amendments to implee c-nt the Transportation System Plan
J /7/PREPAD BY: Julia Hduk DEPT HEAD OK #(Y MGR OK PPPI ISSUE BEFORE THE COUNCIL
Receive an update on the proposed changes to the Development Code to implement the TSP.
STAFF RECOMMENDATION
Review the TSP information, ask questions as needed and provide comment on the proposed changes.
INFORMATION SUMMARY
The Tigard Transportation System Plan (TSP) was adopted in January, 2002 along with Comprehensive Plan
amendments and became effective in February. An additional step that was necessary to fully implement the
TSP was developing amendments to the Development Code to reflect changes to the TSP. The planning staff,
along with staff from the engineering department have completed the review of the Development Code and are
prepared to begin processing the recommended amendments. A meeting with the Planning Commission was
held on June 3, 2002 and any suggestions or comments raised will be presented to the Council at the work
session on June 18, 2002.
The Planning Commission public hearing is tentatively scheduled for August 5, 2002.and the City Council public
hearing is tentatively scheduled for September 10,2002.
OTHER ALTERNATIVES CONSIDERED
N/A
VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEGY
Transportation and Traffic, Goal#2—Improve traffic flow.
•
ATTACHMENT LIST
Attachment: 1 —Summary of changes to implement the TSP
2—Development Code Chapter 18.705 amendments
3 —Development Code Chapter 18.730 amendments
4—Development Code Chapter 18.810 amendments
5 —Additional amendments to portions of Development Code Chapters 18.120, 18.360,
18.520, 18.530 and 18.745.
FISCAL NOTES
N/A
1:Irpin/julia/TSP/6-18-02 TSP worksession.doc
• •
• Attachment 1
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Queuing Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets an d replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right-of-way, the setback for a
structure must be no less than the required setback plus 1/2 the required right-of-way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on-street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP/DLCD-TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
• reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1 of 2
(Updated 5-3-02)
• •
Added sections requiring street connections to be spaced no less than 520 feet apart to address
connectivity requirements. (18.810.030.G.1) (TSP/Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul-de-sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline.radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
•
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the requirement that blocks not exceed 1,800 feet to 2,120 feet to be consistent with Metro
connectivity requirements of streets every 530 feet. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of"not possible". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.13) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right-of-way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation/POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP
(Updated 5-3-02) Page 2 of 2
• •
Attachment 2
Chapter 18.705
ACCESS, EGRESS, AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply.The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures(see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of.Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures,or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title, provided:
Proposed 18.730 Development Code changes to implement the TSP page 1
1111 • •
•
1_ Satisfactory legal evidence shall be presented in the form of deeds; easements, leases or
contracts to establish the joint use; and
2. Copies of the deeds, easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient_
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping, pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes_ Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director,the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety,and general welfare.
Proposed 18.730 Development Code changes to implement the TSP page 2
•
• •
•
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to major collector or arterial streets shall be
considered only if there is no practical alternative way to access the site. If direct access is
permitted by the City,theapplicant will be required to mitigate for any safety_ or neighborhood
traffic management jNTMVILimpacts deemed applicable by the city Engineer, Th.i.a.may_
• include but will not be limited to, the construction of a vehicle turnaround on the_site to
eliminate the need for a vehicle to back out into the roadway.
I In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street,other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
Access Management
. I. An access report shall be submitted with all new development proposals which verifies design
of driveways and streets are safe by meeting adequatestackina needs sight distance and
deceleration standards as set y ODOT. Washington County,the City and AASHTO
. (depending_on jurisd iction of facility.)
2_Driyeways shall nQt_be_.permitted_to.lzeplaced in the influence area of collector or arterial street
intersections Inffuence_area of intersections is that area where queues of traffic commonly_
form on approach to an intersection. The minimum driveway setback from a collector or
arterial street intersection shall be 150 feet,measured from the rig htnf way line of the
intersectin;street to the throat of the proposed driveway. The setback may be greater
depending upon the influence area, as determined from City Engineer review of a traffic impact
resort submitted.by the applicant's traffic engineer. In a case where a project has less than 150
feet of street frontage the applicant_must explore any_option_for shared access with the adjacent
parcel, If shared access is not possible or practical,the driveway shall be placed as far from_the
intersection as possible.
3. The minimum spacing of driveways and streetsalQng a collector shall be 200 feet_ The
minimum spacing_of driveways_andstreets along an arterial shall be 600 feet.
4. The minimunispacing of local streets along a IQcal streetshall be 125 feet_
Minimum access requirements for residential use.
I. Vehicular access and egress for single-family,duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less.than as"provided in Table
18.705.1 and Table 18.705.2;
•
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
I or 2 1 15' 10' -
3-6 1 20' 20'
•
Proposed 18.730 Development Code changes to implement the TSP • page 3
• •'
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI-FAMILY RESIDENTIAL USE _
Dwelling Units Minimum Number of ,Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15' if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24' if two-way
or
2 30' 15' if one-way: Curbs and
5' walkway required
50-100 2 30' 24' Curbs and 5' walkway
required
2. Vehicular access to multi-family structures shall be brought to within 50 feet of the ground
floor entrance.or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts; (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site. _
•
J. Minimum access requirements for commercial and industrial use.
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed 18.730 Development Code changes to implement the TSP page 4
• •
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site, it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets, upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles; or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health,safety,and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties,parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic,access and parking area plans shall provide
efficient sidewalk and/or pathway connections,as feasible, between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
II procedure,as regulated by Section 18.390.040,using criteria contained in Section 18.370.020 C3.
Proposed 18.730 Development Code changes to implement the TSP • page 5
• •
Attachment 3
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
•
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet; provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2-1/2 stories or 35 feet, whichever is less,provided:
Proposed 18.730 Development Code changes to implement the TSP page 1
• •
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
• mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420,Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line;and
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed 18.730 Development Code changes to implement the TSP page 2
• •
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings;and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance with Chapter 18350, Planned Developments, Chapter. 18.430,
Subdivisions,or Chapter 18.420, Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and •
necessary data or narrative which explains how the development conforms to the standards;
2. A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
Proposed 18.730 Development Code changes to implement the TSP page 3
•
• •
A. Additional setback from specified-roadways. . - • . - . . . • , .' , . . • . . .
. . - . D . . . . •� . . .. . .. - ..
. . . - ,
•
•
Street Names Requirement
Arterial Streets.
SW Pacific Highway(within City Limits) 50 feet
• SW Hall Boulevard 95 feet
intersections with Old Scholls.Ferry Road) 50 feet
T •
Upper Boones Ferry) 45 feet
SW Upper Boones Ferry Road 15 feet •
Collector Stfeets-
SW Ash Avenue 30 feet
•
•
SW Atlanta(west of 68th Avenue) 30 feet
SW Beef Bend Road • 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
Hall Boulevard) 30 feet •
SW Franklin Street 30 feet
SW Gaardo Street • 30 feet
SW Grant Avenue 30 feet
SW Grecnburg Road 30 feet
SW Hunziker Road 30 feet
SW Main Street 30 feet
•
SW McDonald Street 30 feet
SW_Murdock Street• 30 feet •
SW North Dakota Avenue 30 feet
SW Oak(west of Hall-Boulevard) 30 feet
Proposed 18.730 Development Code changes to implement the TSP page 4
• •
•
SW Pfaffle Strcct 30 feet
Old Scholls Ferry Road) 30 feet
! •
Street Names Requirement
SW Summerfield Drive 30 feet
SW Tiedeman Avenue 30 feet
SW Tigard Street - 30 feet
SW Walnut Street 30 feet
SW 68th Avenue 30 feet
SW 68th Avenue(south of Pacific Highway) 30 feet
S\V 70th Avenue(south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
S\V 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffio connection 30 feet
•
• •••f • _ • _ . . _ ... -. • ..•
3-.----The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
of-way width less than required by its functional classification on the City's transportation plan map
and, in such case,the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
B. Distance between multi-family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development,the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed.walls facing buildings with a blank wall shall have a 15-foot
separation;
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections;and
Proposed 18.730 Development Code changes to implement the TSP page 5
• •
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
2. Where buildings exceed a horizontal dimedsion of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone,the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots.
B. . When one abutting property has a non-conforming front setback. If there is a dwelling on one
• abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats,trailers, campers, camper bodies,house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
Proposed 18.730 Development Code changes to implement the TSP page 6
•
• •
D. Projections into required yards.
1. Cornices, eaves, belt courses, sills, canopies or,similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
AREA NOT INCLUDED
IN LOT AREA
•
LO ARE
\ \\\\
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.■
Proposed 18.730 Development Code changes to implement the TSP• page.7
• • S .
Attachment 4
• Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190. City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction, reconstruction or repair of streets,
sidewalks,curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal.Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9_ (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed 18.810 Development Code changes to implement the TSP page 1
• • •
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets •
A. Improvements.
1.- No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets;or
f. Additional planning work is required to define.the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6. The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed 18.810 Development Code changes to implement the TSP page 2
• •
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030,E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use;or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards,the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title;and
3. All deeds of dedication shall be in a.form prescribed by the City and shall name"the public,"as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
by deed without full compliance with this title provided such. an easement is the only reasonable
method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.1 and 18.705.0301.
D. Street location,width and grade. Except as noted below, the location,width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed 18.810 Development Code changes to implement the TSP page 3
• 110
planned streets, .to topographic conditions, to public convenience and safety, and in their
appropriate relation.to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas,or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to'existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticipated average daily traffic(ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists, bicyclists, and pedestrians;
k. Access needs for emergency vehicles.
Proposed 18.810 Development Code changes to implement the TSP page 4
• •
• TABLE48404-
Typetof-Steeet :
. • : •.: •1.
Arterial 6O- 0 24
Major ColleGtoc 60-84- 44 2-4
Mmor Qollector 60- 40"".
21.1
a Through street with
-9Les Than 500 ADT ci2.;
2 4,)
"
D•Ltess-Tliaii-L208414-1 24'•
Than 500 ADT
•
4.54
'.7-21.'es"s'thady'206 Apt 42;.-
•
f=1wg1liogliipts).
- 50'radiu radius
47 rhdius 10r thdius
Residential.
•
•
Proposed 18.810 Development Code changes to implement the TSP page 5
. .
. -
Table 18.810.1
Minimum Widths for Street Characteristics -
1 '.9 • 1
1
• 4-4 . j ''
-0 C U.. CU 1.IIII
L..;j °- .
CD (1)
-4j, ..c u"" 4.,
u.
Type of Street ...ii., 'IL inc --4 .c _v ,....k:
: .....,.!
.c 1- 0
• • z E § -I- a § (17 a)
ce . ci• . ci. ...- • Z .
..:.)
. „ . . . . . .
Arterial 6.41:128: Varies 2.: 7 (Refer a N.LA 61.(New_Str_e_ets1 6'._(.R..es....A_In.d...imee.) 5' izill)
to_iae.1
5!_.7.61tEiating_atte_e_ts.) 10L.C.C.om_nl.2pne..a)
Collector 58-96' Varies 2 - 5 (Refer 11: N/A 6' (New Streets) 6' (Res..& Ind,Zones) 12
to TSP) .
• . 51-6' (Existing Streets) 8' (Comm, Zones) . -
Neigh.b.orno.o.d R.o.u.te 50'._77.58' 28'736' 2 10' 8' 5'7_6'. 5',6:( ) '. 5' N/8
L.Q.cat.
Lactotrial/Commemial .o.: . 2 N/A .5'.76'!.2) 5'. NLA
Lapel: R.e.,sicential • NIA
• Under 1500 ADT(3) 541 32' 2 8' (both sides) N/A 5'-6'(2) .
• Under 500 ADT(J) 5S).1 2.8.: - ' i
N/A
2 )
• Under 200 ADT(J3 46.1, 24' • 2 .. NLA
.(ND(one Parkinsdeg)
CLII:de-s_a_c_tuits_in 5.0.: 4Zia.diu.a NLA NLA N/A No
ra_clattlal-Ex rt Legal§ .
cp.mmerciaLzones . .
_Q..t.th.d.t..aa.c.,..411b..$_in 41', • .as___Lal.-§ NLA N/A NLA, .NIA NIA
Re_sideritialzo_n.es • radius
AALeyfiesidential 16..! 161 NLA NIA - NLA N/A NLA
,Alleysin.es_s 2.0: 2...Q! ' N/A N/A NIA N/A NIA
'Medians required for 5 and 7 lane roadways. They are optional for 3 lane roadways.
2Sidewalk widths for these streets shall Jpe 5 ft with jandscaDe strip.',6 ft ifnainst curb (if permitted in accordance with 18.810.070.C),
? kiArly_.S.tr��.elliQ.edwav widths are aermitted rif the,cross section criteria are met. Refer__ L(Figut,e_§ • .
18.810.3, 18.810.4 and 18.810.5) for'details and conditions. • -
. . .
. -
Proposed 18.810 Development Code changes to implement the TSP page 6.
. .
41)
•
Figure 1 8.8 10.1_
Arterials Sample Cro_ss Sectimis
..—
,---Ff__ --' .-7--
LN---ifs 9
,. . _
!! :
r .—
1-11-r. V7
1 •1
. 48-1015.5' to'ne 12' 12' ;6'Elket 5.5'
R/W 64'-68'
2 Lane 641-68'R/W
...-:::----‹ ,----,
,--. -...,,,
..:,'3,''--...---
i4:17-- 0 1...r--
-----
I -• - -,)1 -- t'l( .4-"--=-
1 :;i FJ-= I, slow 1
1‘ „
v......,...2:ig*g,-.2,-....... ;3777..-:--fn.;',.77,.. ---:■■=m,•---- ifri .
5' 12'Median/ 5'
I 18-10'1 5 5':6'Elke I 12'-- Turn Lane , 12' ,6like I 5.5'
I , ---H
RAN 76.-80'
3 Lane 761-80'R/W
,------,1,==:=-, .,_:--"--\-•-:1 4 .••,. _.-
,_ ---,c.-.-,-_,-•
_.• •r.•-•,-------= ;., ri?
.c.--;..:)f -=---qr
, -- .---
-" 1 ii
-.....,
EtgA-4.74
12'Median/
; 8_7.10'1 _6' 18 Bice_4 12' 1 12' laurni_orieIT __I 12' .16' -la__a
R,,,,,,,0,,104'
I 1 .
5 Lane 1001-104'R/14,
,--,
,.---, .
1-.. ..„
..... , ,
• ,....._--
--
12'Median/
8-10' 5.5' 6'Bike .12' . 12' 12' Turn Lane , 12' 12' 12' .Like 6' 5.5' 8-10'
; ; i i ; ; ; ; 1
I
1j_124'-128'
7 Lane 124'-128'R/W
. ,
Proposed 18.810 Development Code changes to implement the TSP page 7
• 0 . ,
Figure 18.81112
Collector Sample Cross Sections
, °
q. r• a �_. u�
' S 6-8',5.5' .6'Bike. ._ 11' —t 11'-- i6'Bleh5.5' 6-8's 5'
R/W 58'-62' ,
2 Lane 58'-62'R/W
% ( i 1�
12'Median/
•5,6-8'15.5',6'Bice I 11' I Turn Lane I 1 1' i 6'Bike 15.5 I6-8'I.5
l-- --- — — WO/70'-74' --- — —I
3 Lane 70'-74'R/W
c'o � y�
MEW I
5' 12'yMedian/ 5'
H 6-8' I 5.5"___1_6'Bice, 11' 11' Turn I ar. _I 11' i 11' i 6'Bike i 5,5' i 6-8' 1
t . — --- R/W 97-96' -- - —!
5 Lane 92'-96'R/W
Proposed 18.810 Development Code changes to implement the TSP page 8
••
•
Figure 18.810.3
Neighborhood Routes
•
Sample Cross Sections
1,
rr"
)
.5'
28' 5.5'. 5' -5'
,
R/W 50' R/W 54'
No Parking on One Side With Parking on Both Sides
.r;
2-0
)94 I I
-445faiWr
•
36'
5' 5.5' 6'Bike
I+ -1 I
RM/58'
With Bike Lanes/No Parking
•
Figure 18.810.4 •
Local Residential Streets-<1 500 vpd
A. Standard(sample) B. Skinny Street Option(criteria)
••›;----s-
2--(.1
I =
.5', 5' 5.5' ra•
I . 32' 5.'
al 5'5' -** --- —
RAN 54'
i; r.am.
• .5. 5. rhaecin, (0..1.11) Plaet1ns: ;
On-street Parking 5=r• ; • 5.*
rftwensont
<1500 vpd *
If parking on both sides,
block length not to exceed 600 feet
Criteria:
• Queuing Plan must be submitted and approved.
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
• development only.
•
Figure 18.810.5 •
Local Residential Streets<5_00 v-p_d
Proposed 18.810 Development Code changes to implement the TSP page 9
0 .
• . • .
A. Standard(sample) B. Skinny Street Option(criteria) •
dill . =
i5. 5' _ 5.5': O 28' t 5.5'� 5' S ® III 0---'t
R/W 50'
T 167
s.s• '._Pariig bawl lam 5.5' f
Residential Local Street/Cul-de-sac "-=' ^'; f' �� '
SiAmall 2s' Sl4.M'
One Side On-street Parking .. •
*V.
<500 vpd .'
Criteria: •
• Queuing Plan must be submitted and approved. .
• Not appropriate for streets serving more than 500 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of(1)off-street parking space for
every 20 feet of restricted street frontage.
•
• Figure 18.810.6 .
. Local Re dent al_Stree <200.vpd •
A. Standard(sample) • B. -Skinny Street Option(criteria)
d Z o 4
<%'wi7 Z E•
7 ie
.5' s.s' L 2dn..a..e ..-5.5• is
5' 5.5' , — 24 i 5.5' i 5' bi ,. ',bay. ...ink..1> .
51.4•x` SH P s14..•
t--- — - RtW 46' —t—
Cul-de-sac/Residential Local Street
w ...e .
<200 vpd .
• (No parking)
F. Future street plan and extension of streets.
_i •
1. A future street plan shall:
•
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall-rnayprepare
a future streets proposal._Costs of the_City preparing a future streets _prsal shall be
Proposed 18.810 Development Code changes to implement the TSP page 10
•
• •
reimbursed folthe_time involved. A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus routes,pullouts or other transit facilities, bicycle routes and
pedestrian facilities on or within 530`feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be cull-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
G. Street spacing and access management. Refer to 18.705.030.1-1.
GR. Street alignment and connections.
1._Full street connections with spacing of no more than 530 feet between connections is required
except where prevented by barriers such as topograp , railroads, freeways, pre-existing
developments, lease_provision_, easements covenants or other restrictions existing_ rior to May
1 1925 which preclude street connections. A full street connectiorrtnay also e exempted due to
a rezulatedwuate_r_feature if regulations would not permit construction.
. -- . « ,. • - - - . . . - . . . .. . .
street, .
23. All local a _neighborhood routes and collector streets which abut a development site
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such as schools, shopping
areas and parks.
4-5_ All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development_ -
Proposed 18.810 Development Code changes to implement the TSP. page 11
• •
141. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection desigrf, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
1J. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
JK. Partial Street Improvements. Partial street improvements resulting in.a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul-de-sac shall be measured from the centerline intersection point of the two
streets to the radius point of the bulb.. • - - • - •• . . - .. . . •• •- - -
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
bM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and as approved by the City
Engineer,.- .
MN. Grades and curves.
__ 1. Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet),and:
—1-2. Centerline radii of curves shall be as determined by the City Engineer.- : ! ! -• •
- ! ! - - ^-! .. .. . - ! ! :•-
and
Proposed 18.810 Development Code changes to implement the TSP page 12
•
• •
percent or less. Landings are that portion of the street within 20 feet of the edge of the
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
I. Concrete curbs and driveway approaches are required;except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards. .
OP.Streets adjacent to railroad right-of-way. Wherever the proposed development contains or is adjacent f
to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the . •
following:
1. A parallel access street along the arterial or major•collector;
2. Lots of suitable depth abutting the arterial or major-collector to provide adequate buffering with
frontage along another street;
3. Screen planting.at the rear or side property line to be contained in a nona ccess reservation along.
the arterial or major collector;or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR. Alleys,public or private.
1. Alleys shall be no less than 20 feet in width.In commercial and industrial districts, alleys shall be
• provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed 18.810 Development Code changes to implement the TSP page 13
• • •
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks, and multi-family residential developments.
TU.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
LTV. Street signs. The City shall install all street signs, relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
WX. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XI. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
VZ.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other I
signs may be required.
ZAA. Street cross-sections. The final lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the •
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development, whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed 18.810 Development Code changes to implement the TSP page 14
• •
. 2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1-1/2 inches in thickness. (Ord.99-22)
AB Traffic Calming. When. in the opinion of the City Engineer, the proposed development will
cr-a e . ne•ative r.ii on•ition on -xi tin• nei• borhood stre-ts such as ex -ssiv- s•eedin• th-
dev-lo•- a •- e•uir-• o •rovide tr.ffic calmi • -asures. These me. re ma be required
within the development and/or offsite as deemed a••ro•riate. As an alternative the develo•er ma
b- -• "red o de•osi funds wi h th- i to he!. •a for traffi calmi • • easur-s tha becom-
necessary once the development is occupied and the City Engineer determines that the additional
traffic fro t e d-vel••men has tri••-r-d the need or traffic calmin• measures. Th- Cit En•inee
will determine the amount of funds required. and will collect said funds from the developer prior to the
issuance of a certificate of occupancy, or in the case of subdivision, prior to the approval of the final
plat. The funds will be held by the_City for a period of five (5) years from the date of issuance of
certificate of occupancy, or in the case of a subdivision. the dateof final plat approval. Any funds not
used by the City within the five-year time period will be refunded to the developer.
AC. A traffic study shall be required_for all new_developments under any of the following
circumstances:
1. when they_generate a l 0% or <ereater increase in existing_traffictolligh collision intersections
identified by Washington County,
2. Trip generations from developmen_o_nto the City_y_street at the point of access and the existing
adtADT fall within the following range
Existing ADT ADT to be added by development
23,000 vpd 2.000 vpd
3.001-6,OQOvpd L.000vpd
>6.000 vpd 500 v_pd or more
3. If any of the following issues become evident to_the City engineer_
a. High ffic_volumesoi_theadjacent roadway that may_affect movement nto or out of the
site,
b. Lack of existing left-turn lanes onto the adjacent roadway at the proposed access drive(s)
c. Inadequate horizontal or vertical sight distance at access points
d. The proximity of the proposed access to other existing drives'or intersections is a potential
hazard
e. The proposal requires a conditional use_permit or involves a drive-through o eeration
.f The proposed development may result in excessive traffic volumes on adjacent local streets.
4. When the site is within 500 feet of an ODOT facility_
18.810.040 Blocks
A. Block Design. The length, width and shape.of blocks shall be designed with due regard to providing
adequate building sites for the use contemplated, consideration of needs for convenient access,
Proposed 18.810 Development Code changes to implement the TSP page 15
• • •
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2J20-1 X800 feet measured along the
centerline of the streets-right of way line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or
b. For blocks adjacent to arterial streets, limited access highways,majer-collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is net-pessibleexempted by 13.1 above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,`or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse,or drainageway,there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development_.shall make arrangements with the
City, the applicable district and each utility franchise .for the'provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated,and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single-family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
Proposed 18.810 Development Code changes to implement the TSP page 16
• •
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation,and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are likely to be
redivided, the Commission may require that the lots be of such size and shape,and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the -
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
A, A. Sidewalks. All industrial streets a nd_privatestreets_shall have sidewalks meeting City standards
along at least one side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development, even if no sidewalk exists on the other side of the street
13. Requirement of developers
1. As part of any development_proposal_or change in use resulting in an additional 1.,000
vehicle trips or more per day_, an applicant shall be required to identify direct, safe(I.25 x the straight line
distanceLpedestrian routes within 112 mile of their site to all transit facilities and Neigh orhood Activity:
Cer te.s (schoots„par cs. libraries etc.). In addition., the developer may be required to participate in the
removal of anyQaps in the pedestrian system off.-site if justified bathe development.__
2. If there is an existing sidewalk,on the same side of the street as the development, within 300
feet of a development site in either direction, the sidewalk shall be extended from the site to meet the
existing sidewalk_subject to rough proportionality (even if the sidewalk does not serve a neighborhood
activity center)
13D.Planter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of any•arteries' a olJccter streets • - - .., • ' .
ache..* to the c- b, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; or it would conflict with
the utilities there are significant natural features (large trees,water features,_etc) that would he
destroyed if the sidewalk were located_as required or where there are existing_structures in close
proximity to the street(l5 feet or less
CD. Sidewalks in central business district. In the central business district,sidewalks shall be 10 feet I
in width, and:
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
Proposed 18.810 Development Code changes to implement the TSP page 17
•
•
EF.Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed, then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property.in question within a
reasonable lengih of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a side walk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
F .Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
_ hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings,commercial buildings or public buildings and/or parks; and
4. A criteria which allowed noncompliance under Section E.l.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord.99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
Proposed 18.810 Development Code changes to implement the TSP page 18
• •
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan' the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas.within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park, playground,
. or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord.99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design- and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within.the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains,or violations of state or federal standards pertaining to
operation of the sewage treatment system.
18.810.100 Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made,and:
I. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
Proposed 18.810 Development Code changes to implement the TSP • page 19
• •
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1_. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream'drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
•
18.810.110 Bikeways and Pedestrian Pathways
A. --Bikeway extension.
1. As a standard, hiike lanes shall be required along_all Arterial and Collector routes and where
identified on the City's adopted bicycle plan in the Transportation System Plan (TSP),
2. Developments adjoining proposed bikeways identified on the City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3. Any new_street improvement project shall include bicycle lanesa_s_muired in this document
and Qn the adopted bicycle plan,
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly.
proportional to the impact of the development.
C. Minimum width.
___Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
_2. Minimum width rnulti=use._paths separated from the road is eight ten
(10)feet._The width may be reduced to eight(_8)feet if there are environmental or other constraints.
3_=Theminimum width for pedestrian only off-street pathsjs five(5)feet.
4. Design standards for bike and_pedestrian-ways shall be determined by the City Engineer,
(Ord. 99 22)
18.810.120 Utilities •
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above, and:
Proposed 18.810 Development Code changes to implement the TSP page 20
• •
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer,shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information,easements for all underground utility facilities,and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval;and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement.
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common, but not the
only,such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities, unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area The fee due from any developer shall be calculated based on a front-foot basis.
Proposed 18.810 Development Code changes to implement the TSP page 21
• •
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area'shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review.
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
•
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City, permit fee paid, and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement ofthese regulations or,at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed.by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction,Oregon
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments)shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
Proposed 18.810 Development Code changes to implement the TSP page 22
• •
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices,and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)■
Proposed 18.810 Development Code changes to implement the TSP page 23
• •
Attachment 5
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions in alphabetical order and renumber the remaining
definitions accordingly:
"Neighborhood Activity Center"— A use such as schools, parks, libraries or pools which
provide recreational or social services for groups of people.
-Queuing Plan" — A plan submitted with a .ro.osal for skinn streets that shows the
potential queuing pattern that will allow for safe and efficient travel of emergency
vehicles,service vehicles and passenger vehicles with minimal disturbance.
•
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B
change the 3`d sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
Additional TSP implementation code amendments Page 1
• • .
18.745.050.C.2.b
change from:
Are permitted up to six feet in height,in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, m collector or collector street.
Additional TSP implementation code amendments Page 2
•
Update : Implementation of
Transportation System Plan
•
Background
• TSP adopted in January 2001 •
• Comprehensive Plan Amendments adopted
• No Development Code amendments
• Planned to come back after review with
Development Code Amendments •
• Internal group developed the proposed
amendments
Proposed amendments
• • Clarify existing language
• Implement TSP recommendations
• Address Department of Land Conservation
and Development (DECD) requirements
• • Address Metro Regional Transportation
Plan (RTP) requirements
P(oon 1,r (i) rst sior) r .Se ss b it4/0/ ,-)-7//ke
Summary of significant changes
• Right of way width •
- Standard
?c, �°� — Skinny street option
Pad/ Sidewalk location
• Sidewalk requirements of developer
• Access management •
• Traffic Calming
Required notice
• • Because the changes do not limit a persons
ability to develop a piece of property, the
City attorney has indicated that Measure 56
notice requirements do not apply.
• Legislative notice published in the Tigard
• Times 20 days prior to each hearing.
• Notice to DLCD 45 days prior to the
Planning Commission hearing.
Next steps
• DLCD notice (45 days prior to first hearing)
• Public notice (20 days prior to first hearing)
• Planning Commission hearing 8-5-02
• City Council hearing 9- 10-02
• Effective 30 days after adoption •
Transportation System Plan
• (TSP) Implementation Update
CIT August 5 , 2002
•
Background
• • TSP adopted in January 2002
• Comprehensive Plan Amendments adopted
• No Development Code amendments
• Planned to come back after review with
• Development Code Amendments
• Internal group developed the proposed
amendments
Proposed amendments
• • Clarify existing language
• Implement TSP recommendations
• Address Department of Land Conservation
and Development (DECD) requirements
• • Address Metro Regional Transportation
Plan (RTP) requirements
Summary of significant changes
• • Right of way width
— Standard
— Skinny street option
• Sidewalk location
• Sidewalk requirements of developer
• • Access management
• Traffic Calming
Right-of-way width
• • In addition to existing street width
standards, narrower street widths (28 feet
for local streets with parking on both sides)
are provided as an option for new
developments.
• • Traffic flow plan must be submitted. (may
include strategic driveway locations, pull-
outs, etc)
Sidewalk location
• • Require, as a standard, that planter strips be
required along all streets.
• Provide specific exemptions under certain
circumstances. Example: if there is
inadequate right of way or curbside
• sidewalks already exist.
Sidewalk requirements of
developers
• • Requires developers to identify gaps in the
sidewalk within 1 /2 mile of the site.
• Developer required to participate in the
removal of gaps if costs can be justified.
•
Access Management
• • Developers required to verify that design of
driveways are safe.
• Detailed guidelines on where driveways
shall be located.
• Sites that do not have enough frontage to
• meet the distance requirements must locate
driveways as far as possible from the
intersection.
Traffic Calming
• • Requires developer to deposit funds towards
traffic calming if project has the potential of
creating a negative impact on existing
neighborhood streets.
•
Additional issues
�
• The Council packet will be available for
viewing by Friday September 6, 2002 on
the City' s web site (www.ci.tigard.or.us)
• The Council packet contains a summary of
the proposed changes, specific proposed
• development code changes, and the staff
report.
Next steps
•
• City Council hearing 9- 10-02
• Effective 30 days after adoption
•
•
/411111,
CITY OF TIGARD
Community Development
Shaping A Better Community
MEMORANDUM
CITY OF TIGARD
TO: Planning Commission members
FROM: Julia Hajduk, Associate Planner
DATE: July 15, 2002
SUBJECT: Development Code Amendments to Implement the Transportation System Plan
(TSP)
As you recall, the Tigard Transportation System Plan (TSP) was adopted in January, 2002
along with Comprehensive Plan amendments and became effective in February. An
additional step necessary to fully implement the TSP was developing amendments to the
Development Code to reflect changes to the TSP. A work session was held with the
Planning Commission on June 3rd and the City Council on June 18th. Based on the
comments received at both work sessions, this memo has been prepared to summarize
additional changes and to respond to questions that were raised.
TPR requirement for narrow streets
There was a lot of discussion of the "skinny street" requirement and what was required. The
Transportation Planning Rule (TPR) interpretation on skinny streets is that 32' streets as a
uniform requirement is too wide. Streets that are 28' with parking on both sides is a safe
harbor regulation. Because the 28' standard was simply a safe harbor, we had the ability to
apply standards that met our own needs, within limits. For that reason, we developed
additional criteria that stated a queuing plan (traffic flow plan) has to be submitted and
approved and off-street parking has to be provided if on-street parking is eliminated.
At the work session, there was a question about whether parking bays or turn-outs could be
required. It is anticipated that this could be an option that a developer could utilize in their
traffic.flow plan and, in definition, we give the option/suggestion for vehicle turn-outs. In
response to additional issues raised on this subject, the "queuing" plan has been re-named
"traffic flow" plan.
The "Neighborhood Street Design Guidelines" provides guidelines for narrow streets and was
developed by consensus with the input from emergency service personnel, public works
department, and transportation engineers. The purpose given for the narrow street
requirements is that they minimize land consumption, are less costly to develop and maintain,
and they reduce the amount of run-off and water quality problems. Narrower streets also
• O J
serve to slow traffic speeds without the need for additional traffic calming devices such as
speed humps.
It should be noted that these standards will apply to NEW local streets only with an ADT of
1000 vehicle trips or less. It only applies to local residential streets.
A concern was raised regarding the possibility to commercial traffic spilling onto these
narrower streets and causing congestion problems. Upon review of the commercial sites in
Tigard, there do not appear to be any undeveloped residential properties adjacent to
commercial uses that would be impacted by the commercial traffic (there are a few instances
where there are larger lots that abut the back of a commercial development, however there is
no access from the commercial site to the larger lot).
Sidewalk planter strips
While the Planning Commission did not recommend the requirement for planter strips, the
• City Council indicated that they were supportive of the idea but wanted some additional
language in the event that the property had more than one frontage and one of the frontages
was a collector or arterial and maintenance responsibility was not obvious. (Durham, for
example). Language has been added to 18.810.070.0 which allows for additional
consideration in situations like that.
Additional comments
There was an issue with the traffic study criteria, however, no suggested changes or specific
concerns have been submitted to date. Specific suggestions for change may be provided at
the Planning Commission public hearing.
There was also a general question raised about the level of service (LOS) standard that the
TSP was adopting. The question was whether LOS F was acceptable. The short answer is
no. The TSP, pages 8-30 through 8-32, identifies key intersections and what the LOS will be
with and without mitigation. With mitigation (improvements and strategies identified in the
adopted TSP) the intersection, while not ideal, remain at or above LOS E. Please refer to
table 8-4 for additional information.
Attached please find the following:
Attachment 1 — Staff Report
Exhibit A:
1 — Summary of changes to implement the TSP
2 — Development Code section 18.705 amendments
3 — Development Code section 18.730 amendments
4 — Development Code section 18.810 amendments
5 —Additional amendments for portions of code sections 18.120,
18.360, 18.520, 18.530 and 18.745.
Exhibit B —Transportation Planning Rule Compliance chart
In the attached documents, the changes being inserted are identified with a double underline
and items deleted are identified with a str-iEethrough.
l:lrpin/julia/TSP/PC adoption hearing memo.doc
• Attachment 1
Agenda Item: 5.1
Hearing Date: August 5.200/ 7:00 PM
�P.,•:,
STAFF' REPORT TO. THE CI Y OF TIGARD
`P LAN N I'NTG�'CO M M I S°S I O N
FOR THE CITY:OF TI;GARD 'OREGON
SECTION I: APPLICATION SUMMARY
FILE NAME: TRANSPORTATION SYSTEM PLAN
CASES: Zone Ordinance Amendment (ZOA) 2002-00004
PROPOSAL: The proposal is to formally adopt Development Code standards to
fully implement the Transportation System Plan (TSP) that was
adopted in January 2002.
APPLICANT: City of Tigard
13121 SW Hall Boulevard
Tigard, OR 97223
LOCATION: All areas within the City of Tigard.
APPLICABLE
REVIEW
CRITERIA: Oregon's Statewide Planning Goals 1, 2 and 12; Oregon Administrative
Rule 660; Metro Regional Transportation Plan (RTP); Comprehensive
Plan Policies 1.1.1(a), 2.1.1, 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3, and
Community Development Code Chapter 18.380.020 and 18.390.060.G.
SECTION II: STAFF RECOMMENDATION:
-Staff r ecom
mends:that at:tie Plannin- Commisso n f
orward°:kfecorrrYerrdation:to atie -Ci
Council for approval-- Of the::. ®evelopment Code;, amendments: to ° implen ent:: the
Transportation System Plan (TSP)'as shown in: Exhibit A=1 through-=/A=S: >;based,_:on the::
finding that all.-relevant cr-iteria are,satisfied
STAFF REPORT ZOA 2002-00004 Page 1
SECTION III: BACKGROUND INFORMATION
The City of Tigard began looking at updating the Transportation System Plan (TSP)
several years ago. With the help of a 12 member task force, agencies and staff, a draft
TSP was produced which takes into account the existing traffic conditions in Tigard,
community needs and goals and the anticipated future demands on the transportation
system. The TSP and Comprehensive Plan amendments were adopted by the City
Council in January 2002. An additional. step necessary to fully implement the TSP was
developing amendments to the Development Code to reflect changes to the TSP. The
Planning Commission and City Council held work sessions on the proposed Development
Code amendments in June. The proposed changes reflect the comments received at the
work sessions.
SECTION IV. SUMMARY OF APPLICABLE CRITERIA
Chapter 18.380 states that legislative text amendments shall be undertaken by
means of a Type IV procedure, as governed by Section 18.390.060G.
•
Chapter 18.390.060G states that the recommendation by the Commission and the
decision by the Council shall be based on consideration of the following factors:
A. The Statewide Planning Goals and Guidelines adopted under Oregon Revised
Statutes Chapter 197;
B. Any federal or state statutes or regulations found applicable;
C. Any applicable Metro regulations;
D. Any applicable Comprehensive Plan Policies; and
E. Any applicable provisions of the City's implementing ordinances.
SECTION V: APPLICABLE REVIEW CRITERIA AND FINDINGS
STATEWIDE GOALS
Citizen Involvement: Goal 1 requires a citizen involvement program that ensures the
opportunity for citizens to be involved in the planning process.
Tigard Comprehensive Plan Policy 2.1.1 and Tigard Community Development Code Chapter
18.390 provide for citizen participation and notice. Notice of the Planning Commission
hearing and opportunity for response was advertised in the local newspaper. Notice was
sent to Department of Land Conservation and Development in accordance with their notice
requirements. This goal is satisfied.
Land Use Planning: Goal 2 requires, in part, that adopted comprehensive plans be
revised to take into account changing public policies and circumstances.
This goal is met because the City has applied all relevant Statewide Planning Goals, City
Comprehensive Plan policies and Community Development. Code requirements in the
review of this proposal as discussed throughout this staff report.
Transportation: Goal 12 requires a safe, convenient and economic transportation
system.
STAFF REPORT ZOA 2002-00004 Page 2
• .
The TSP has been prepared in accordance with the Statewide Planning Goals and
requirements. Oregon Administrative Rule 666, the compliance with which is discussed
further in this report, implements the Statewide Transportation Goal 12. The plan has been
reviewed by ODOT and DLCD.
COMPLIANCE WITH FEDERAL AND STATE STATUTES OR GUIDELINES
Oregon Administrative Rule: Section 660-12-0000 through 0070 is intended to
implement Statewide Planning Goal #12 by providing guidelines for local
governments to demonstrate compliance with Goal #12 through their Transportation
System Plans.
When the TSP was adopted, it was recognized that Development Code amendments were
needed to fully comply with the TPR. Attached as Exhibit.B is a chart identifying how each
of the TPR requirements are addressed. Based on the information provided in Exhibit B and
in this section, staff finds that the TSP complies with the state statutes. There are no
specific federal standards that apply.
COMPLIANCE WITH METRO REGULATIONS
Regional Transportation Plan (RTP): The RTP takes the place of Metro Functional Plan
Title 6 (Regional Accessibility), and is consistent with Chapter 2 of the Regional
Framework Plan. The RTP provides a regional framework for transportation systems
and has its own criteria that must be addressed that are in addition to the
Transportation Planning Rule (TPR) requirements.
The TSP is consistent with the RTP and the proposed amendments include all language
required to be adopted by local jurisdictions. The only specific language that needed to be
changed to implement the RTP was the requirement to have local street spacing no less
than.530 feet apart to address connectivity requirements.
COMPLIANCE WITH COMPREHENSIVE PLAN POLICIES
General Policies: Policy 1.1.1(a) requires that legislative changes are consistent with
statewide planning goals and the regional development plan.
The proposal is consistent with statewide planning goals as addressed above under
`Statewide Goals'. The proposal conforms with the applicable portions of the Metro
Functional Plan that was approved for adoption on October 24, 1996 by the Metro Council.
This policy is satisfied.
Citizen.Involvement: Policy 2.1.1 states that the City shall maintain an ongoing
citizen involvement program and shall assure that citizens will be provided an
opportunity to be involved in all phases of the planning process.- Policy 2.1.2 states
that opportunities for citizen involvement shall be appropriate to the scale of the
planning effort. Policy 2.1.3 states that the City shall ensure that the information on
planning issues is available in an understandable format.
A request for comments was sent to all affected jurisdictions and agencies. The Planning
Commission hearing was legally advertised with notice published in the Tigard Times. The
STAFF REPORT ZOA 2002-00004 Page 3
•
TSP had extensive notice and opportunities to comment. Because the current proposal is
simply an implementation of a previously adopted plan, the same level of public notice is not
necessary.
Transportation: Transportation Policies 8.1.1, 8.1.2, 8.1.3, 8.1.5 and 8.2.3 were
adopted at the same time the TSP was adopted to incorporate the TSP
recommendations into the Comprehensive Plan. The policies are specifically
addressed below:
8.1.1 — requires the planning of transportation facilities to be done in a way that
enhances livability through the proper location of facilities, encouraging pedestrian
traffic and addressing issues of through traffic and speeding on local residential
streets.
8.1.2 — requires a balanced transportation system that incorporates all modes of
transportation.
8.1.3 — requires the effort be made to develop a safe transportation system through
the street standards and access management policies.
8.1.5 — requires the development of transportation facilities that are accessible to all
citizens and minimize out-of-direction travel.
8.2.3 — provides the minimum improvement level and dedication that should be
required of developers as a precondition of development, to ensure that the
communities transportation system functions adequately.
The code amendments provide greater clarification of where bike lanes are required,
requires the identification and removal of gaps in sidewalks (if roughly proportional), has
local street spacing standards that will minimize out-of-direction travel, provide greater
access spacing standards and greater clarification of when transit amenities are required.
The proposed development code amendment changes are directly implementing the TSP
and Comprehensive Plan policies, therefore, the applicable Comprehensive Plan
standards have been satisfied.
COMPLIANCE WITH THE CITY'S IMPLEMENTING ORDINANCES:
The implementing ordinances are contained in the Tigard Community Development Code.
The applicable criteria identified in the Development Code are summarized in Section IV —
Summary of Applicable Criteria and addressed in Section V — Applicable Review Criteria
and Findings. As this staff report demonstrates, all applicable criteria have been satisfied.
STAFF REPORT ZOA 2002-00004 Page 4
•
SECTION VI: COMMENTS (AGENCY, STAFF AND OTHER)
City of Tigard Engineering, City of Tigard Current Planning Division, City of Tigard
Operations, City of Tigard Public Works, City of Tigard Police, City of Beaverton, City of
Durham, City of King City, Washington County, Tigard-Tualatin School District, and Tri-
met. Have reviewed the proposal and offered no comments or objections.
Tualatin Valley Fire and Rescue reviewed the proposed amendments and indicated that
they find no conflicts with their interests. The provisions for skinny streets are acceptable
to the Fire District. They also state that the Fire District is currently developing traffic
calming device design criteria that will be submitted upon completion. The general
statement in the Development Code indicates only when they are to be installed. The Fire
District hopes that their criteria will be considered for design details
DLCD reviewed the proposed amendments and offered comments which are summarized
below:
• They want to make sure that Tigard documents its process used to develop the local
street standards regarding narrow streets;
• They suggested changes which have been incorporated into the proposed
amendments that presents the narrow street option in a way that does not discourage
someone from using that method and as a method that is not favored.
• They provided suggested language which has been incorporated into the. proposed
amendments for "Traffic Flow Plan" (formerly referred to as a queuing plan).
• They recommend against changing the block length standard from 1,800 feet to 2,120
feet and provided language that Washington County uses that they suggest we
consider.
Staff response: The change from 1,800 foot block length to 2,120 foot block length was
suggested to be consistent with the street spacing standards, however staff is not
_ opposed to retaining the original block length concept. Because the measurement system
is being changed from right of way line to centerline, the maximum block length dimension
will be 2,000 feet. This will result roughly in the same block length requirement as
currently existing and as recommended by DLCD staff.
Metro reviewed the proposed amendments and generally offered the same comments as
DLCD, specifically, they suggested changes that presents the narrow street option in a
way that does not discourage someone from using that method and as a method that is
not favored and they recommend against changing the block length standard from 1,800
feet to 2,120 feet.
The City of Tigard Urban Forester reviewed the proposed changes and offered the
following comments: "The planter strips should be at least five feet wide so that large trees
can be planted in order to create more tree canopy. I think that planter strips are a good
idea since the trees will be shading much more of the street, thus reducing the heat island
effect too common in this City!"
Oregon Department of Transportation (ODOT) reviewed the proposed amendments
and offered comments summarized as follows: They appreciate our efforts to clarify when
a traffic study is required, however a traffic study is not always needed to address ODOT
interests. They suggest changing 18.810.030.AC to state that a traffic study,MAY (instead
STAFF REPORT ZOA 2002-00004 Page 5
•
of shall) be required if a site is within 500 feet of an ODOT facility and/or trip generation
from the development adds 300 or more trips per day to an ODOT facility and/or trip
generation from the development adds 50 or more peak hour trips to an ODOT facility.
They request that ODOT be notified of pre-applications to help make the determination of
whether a traffic study is required prior to a formal application being submitted and
deemed complete.
Staff response: The proposed development code language has been amended to include
ODOT's recommended changes
EXHIBITS:
EXHIBIT A-1 through A-5: Proposed Development Code changes
EXHIBIT B: Chart addressing TPR criteria and Tigard's compliance status
•
�2N�4 /1.../eik July 22, 2002
PR ARED BY: Julia Hajduk, •
Associate Planner
NaA1-40
12/1}-e..- July 22. 2002
APPROVED BY: Barbara Shields DATE
Planning Supervisor
I;IrplanrulialrSPlimplemetation/PC Staff report.doc
STAFF REPORT ZOA 2002-00004 Page 6
•
• •
Exhibit A-1
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Traffic Flow Plan (Staff clarification)
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to major collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP) .
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right-of-way, the setback for a
structure must be no less than the required setback plus 1/2 the required right-of-way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810 .
Provided new minimum widths and standards for streets
• Includes lane width, on-street parking, bike lanes, sidewalks, landscape strips and median
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP/DLCD-TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1 of 2
(Updated 5-3-02)
• •
Added sections requiring street connections to be spaced no less than 530 feet apart to address
connectivity requirements. (18.810.030.G.1) (TSP/Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul-de-sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the measurement of block length from the right-of-way to centerline and adjusted the
maximum block length perimeter from 1,800 feet to 2,000 feet to accommodate the revised way of
measuring. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of"not possible". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right-of-way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation/POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2 of 2
(Updated 5-3-02)
• • Exhibit A-2
Chapter 18.705
ACCESS, EGRESS,AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose. The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply.The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures (see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures, or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title,provided:
1. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
Proposed Development Code changes to implement the TSP Page 1
• •
2. Copies of the deeds,easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular access and egress as required in Sections 18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts.Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping, pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes. Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the Director, the access proposed: •
b a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles; or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety, and general welfare.
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to collector or arterial streets shall be considered only
Proposed Development Code changes to implement the TSP Page 2
• •
S . if there is no practical alternative way to access the site. If direct access is permitted byjhe
C':ity, the__applicant__will_ be required to mitigate for_any safety or_neighborhood traffic
management (NTM) impacts deemed applicable by the City_Fngineer. This may includei_hut
will not be limited to, the construction of a vehicle turnaround on the site to eliminate the need
for a vehi_cle_to backt onto_the_roadway
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street, other than an alley. Single-family
•
and duplex dwellings are exempt from this requirement.
H. Access Management
1,___An access teport_shall_be_submitted with all new development proposals which verifies design
of driveways and streets are safe_hy meeting adequate shtdistance distance and
deceleration standards as set by ODO_T,_Washing,ton County_the City and A.A.SIITQ
{depending on turisdiction of facility,)
2. Driveways shall not be permitted to be placed in the influence area of collector or arterial street
intersections. Influence area of intersections is that area where queues of traffic commonly
form on app_ro_ach to.... intcssutim_ithe_minimum driveway_nitback fmni a coll_cctor or
arterial street intersection shall be 150 feet measured from theright-of-wayline of the
intersecting street to the throat of the proposed driveway. The setback may be_greater
dependinpon the influence area as determined from City_Engineer review of a traffic impact
report submitted_by the_applicant's traffic engineer__In a_case where a_project_has_less_than 1_50_
feet of_street frontage. the applicant must
explore any option for shared access with the adjacent
parcel. If shared access is not possible or practical the driveway shall be placed as far from the
intersection as_possible.
3,__The.minimurn spaeing,nt:_drivewaya_and areets_alegg_a_collector snull_be...200
minimum spacing of driveways and streets along arterial shall be 600 feet.
4. The minimum spacings&local streets_aIong a local street shall be 125 feet
Minimum access requirements for residential use.
1. Vehicular access and egress for single-family,duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less than as provided in Table -
18.705.1 and Table 18.7052;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
I or 2 1 15' 10'
3-6 1 20' 20'
Proposed Development Code changes to implement the TSP Page 3
• i
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI-FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15'if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24'if two-way
or
2 30' 15' if one-way: Curbs and
5' walkway required
50-100 2 30' 24' Curbs and 5' walkway
required
2. Vehicular access to multi-family structures shall be brought to within 50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed Development Code changes to implement the TSP Page 4
• •
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site,it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets,upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions;or
b. Provide inadequate access for emergency vehicles;or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health,safety, and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties,parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic,access and parking area plans shall provide
efficient sidewalk and/or pathway connections, as feasible,between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
II procedure, as regulated by Section 18.390.040, using criteria contained in Section 18.370.020 C3
Proposed Development Code changes to implement the TSP Page 5
•
Exhibit A-3
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet; provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition; or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be
2-1/2 stories or 35 feet,whichever is less,provided:
Proposed Development Code changes to implement the TSP Page 6
•
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three.or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
_ 2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420,Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line; and -
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed Development Code changes to implement the TSP Page 7
•
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings;and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
• (2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance with Chapter 18.350, Planned Developments, Chapter 18.430, ,
Subdivisions,or Chapter 18.420,Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
'2. A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
A. Additional setback from speci€ied-roadways. - - . - - . . . , . , . - - .
Proposed Development Code changes to implement the TSP Page 8
•
• •
1. Arterial Streets. The required setback distance for buildings on arterial streets is the setback
TABLE 184M 1
. Street Names Requirement •
Arterial Streets:
SW Pacific Highway(within City Limits) 50 feet
SW Hall Boulevard 45 feet
intersections with Old Scholls Ferry Road) 50 feet
Upper Boones Ferry) 45 feet
SW Upper Boones Ferry Road 45 feet
•
•
Collector Streets:
SW Ash Avenue 30 feet
SW Atlanta Haines (east of 68th Avenue) 30 feet
SW Atlanta(west of 68th Avenue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
SW Cascade Boulevard 30 feet
• SW Durham Road(between Pacific Highway and
Hall Boulevard) 30 feet
SW Franklin Street 30 feet
SW Gaarde Street 30 feet
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
SW Hunziker Road 30 feet
SW Main Street 30 feet
SW McDonald Street 3.0 feet
•
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak(west of Hall Boulevard) 30 feet
•
•
SW Pfaffle Street 30 feet
SW Sattler Street(40 ft pavement between 100th/Hall) 30 feet
Old Scholls Ferry.Road) . 30 feet
Proposed Development Code changes to implement the TSP Page 9
• 410
TABLE 18.730.1 (CON'T)
Street Names Requirement
SW Summerfield Drive 30 feet
SW Tiedeman Avenue 30 feet
SW Tigard.Street 30 feet
SW Walnut Street 30 feet
SW 68th Avenue 30 feet
SW 68th Avenue(south of Pacific Highway) 30 feet
SW 70th Avenue(south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
Planned, SW Hampton to 69th(westerly loop road) 30 feet
3--The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
of-way width less than required by its functional classification on the City's transportation plan map
and, in such case,the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
however, shall not be less than 25 feet plus the yard required by the zone. This provision shall
B. Distance between multi-family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development,the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15-foot
separation;
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections; and
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
•
Proposed Development Code changes to implement the TSP Page 10
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone, the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots.
B. When one abuttin1 property has a non-conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats, trailers, campers, camper bodies,house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
.residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that_one camper, house trailer or
recreational vehicle may be-used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
D. Projections into required yards.
Proposed Development Code changes to implement the TSP Page 11
• •
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
AREA NOT INCLUDED
IN LOT AREA
LO ARE
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots,are satisfied.
Proposed Development Code changes to implement the TSP Page 12
•• •
Exhibit A-4
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections:
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction,reconstruction or repair of streets,
sidewalks, curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land _
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed Development Code changes to implement the TSP Page 13
s •
"public streets"unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets
A. Improvements.
1. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the inability to achieve proper design
standards;
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets; or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6: The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed Development Code changes to implement the TSP Page 14
• •
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use;or
•
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards,the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public,"as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
by deed without full compliance with this title provided such an easement is the only reasonable
method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.H and 18.705.030I.
D. Street location, width and grade. Except as noted below,the location,width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed Development Code changes to implement the TSP Page 15
flo
•
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas, or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticipated average daily traffic(ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists,bicyclists,and pedestrians;
k. Access needs for emergency vehicles.
Proposed Development Code changes to implement the TSP Page 16
•
•
Tiotl4s4.104.
Major coliotAlq• kg94:= 4-7-4
6.044; 4*
Miii4t0,61te.Oof
."" SO 4*.
alTslifii14Watief11
7*4 :
,
tetS.-Thafr,f500-ADT $0; 32 2
Less Than '500--APT 46 28 4-2
Less•Thati.. 290;;A:1)T 441 24!
„
b.- Cul de sac-dead:end. ,
Less g$09 Mg'
Les -Thaii '200 ADT 24= -1=2
50 thdiu 42 mdlu3
-- ••• - -
41"radius 40 radiis
Alley jointi
-16=
•
•
Proposed Development Code changes to implement the TSP Page 17
•
Table 18.810.1
I Minimum Widths for Street Characteristics
. '..1
%N. .. .aw
. 1 14-1— i■ 2 ! il
1 § ,., '. '1, 1.611.
1
Type of Street .5 • "j . -IC ii? .
._, .._ ....
• Z ' . I" ' 3:1 "§", _ . CU C "§" .. a)
Ce" CL • —. Ed,
....1
. „ .
Arterial 5411126: Veriu 2...7.11Refer 1.2: NIA 6L(New at reels) .8L(Re$—Ikl..n.st..Z.Qoe.$) 5_'.. 121F_.( .
-- -
to_ISE')
5.'2_611Etingatreets.) . ,1011CQm_ca,...Zonee)
Collector 58'-96' Varies 2 - 5 (Refer 11 NLA 6' (New Streets) §' (Res. & hid. Zones) S 12'("
to TSP)
5'-6' (Existing Streets) 8' (Comm. Zones)
Neighborhood Route .50'..77_66: 2s:,3.6!. 2 8! 5.'_:16'. 5.z..e. 5 N/A
Local.:.
[ndu.strial/C..o.mmercial. 50.: 3.6.: 2 N/A 5,_6,(2) 5 N/A
.i.,Qc.a1;„..Re_sidenti_al NIA
• Under 1500 ART 54750°) 32'/28" 2 8' (both sides) NIA 5.-6(2) 5!
• Under 500 ADT 50'/46'(3/ 28724433 2 8' (one side) N/A
• Under 200 ADT 46742°) 24720'(33 2 No Parking.) NLA
Cul-de-sac bulbs in 50' 42' radius N/A NIA IlLA NIA
Industrial and radius •
Commercial zones III
Cul-de-sac bulbs in 4Z. 40' radius NLA N.LA NYA tliA NiA
Residential zones radius
Alley: Residential a 16' NIA N/A N/A NLA N/A
Alley: Business 20' 2_()'_ NLA N/A N/A N/A N/A
,1 Megliciatiradix_5_ancillan_e_roaAwaYa—TheyaraDatiOnaLfar31aneroadwayl.
'Sidewalk widths for these streets shall be 5 ft with landscape strip: 6 ft if against curb (if permitted in accordance with 18.810.070.C).
"Skinny Street" roadway widths are permitted where cross section and review criteria are met. Refer to corresponding cross sections
.C.Eigmres_l 8.60-3.. conditions.
Proposed Development Code changes to implement the TSP Page 18
. •
•
Figure 18.810.1
Arterials aarriple_Gross Sections
.1,- .. .."
:.• 1 •,—:,--- ".
. --NI[ -*, ..4.2,•,. ...1111110 '
116.-imilei" •aia'—'
^.-----ki;}•*; -i,-b!e;' ,--—.<-g.'
.518-101 5.5' 16'ne4 12' f 12' :6'Etkei_5_.5' :8-10'1.F
R/W 64'-68'
I
2 Lane 641-68'R/W
---)C..■ 5. '' "
`-7 ---
--,,." '•---- -
-----1 t, ..
1 r, II \ Y
- '-vs; ■••■11111.e.A2...=+.-.......;:, ".'■ww ..... ,,,,A1
'I 12'Median/
I 18-10'i 5.5':&Bike 1 12' I Turn Lane , 12' ;611ke1 5.5' ;8-10'1 i
R/W 76.-80'
I
3 Lane 761-80'R/W
--`.1-- .--:,:c---- --,----...,_
4. .
,. inr---
q
'11
r J " ,...r—.:-., ..2 if L...
—
--
,„-±.....1,,,....-,:_., — ......
- 12'Median/
,__t 8-10_, 6 t6 Mei 12' i_ 12' I liurracine i 12' i 12' 03-10' 45:
R/W 100'1 04' I
5 Lane 100404'RIW
.--_
,_, .,,.... ,.._ _, ,. -,
.. -.------.
').....-A - `"
,. fr`Gi ''---1
-, --
r li ,7 1 r= ) • - - t (
' ... ..rria•
5
12'Median/
8-10' 5.5 6'Bile 12' . 12' 12' :Turn lane i 12' 1 12' 1 12' :Filke6', 5.5' 1 8-10' , 1
I I I I
i_ R/W 124'128' .
7 Lane 124'-128'R/W
•
- ,
Proposed Development Code changes to implement the TSP Page 19
•
•
Figure 18.810.2
Collector Sample Cross Sections
„.-.-. ,...--. ‹.::, -,
._...--‹::ar...:, ...,'
ik 4---g i.
,
5.5' ,6'flike 11'
f-i---:
R/W 58'-62'
• :
2 Lane 581-62'R/W
<-':-:----,. ...-------, -,,
,- - -,..- •. ,----- , -
If .44••■. IA
.1--1.... „4...*.c?,■
--
5 11I 1 1-.,-2'M.77 e.7.7td0-ii'.a":n/
6-8 5.56Bee I 11' Tum Lane
I "11' 6'Eket.P 55'-.r-6-8-'A.-r-.
-- R/VV 7 -74 _5I
I
3 Lane 70=74'RH
2__, -s 4- --„,
---"--
,------ :, ', .,--,7 ,:.7,
a .2,:_...or ,, -
i t '.(117774 C1--.. -; I '!....'. ' -
)1
. -.-a-
a.--,----Jtatit&-.7-ti,
.5' 12 Median/ 5'
hi_6_-8.1 6'Bikel, 11' : 11' Fiurniane_ 11' i 11' 4,6'nel 5.5'
5 Lane 921-96'R/W
..,
Proposed Development Code changes to implement the TSP Page 20
• •
Figure 18.810.3
Neighborhood Routes
Simple Cross Sections
,,—,_ ----,
. ,..1
\:-
L,.....2:a a t a — IT i t t.4_____,,,A ,.. --. .-f i i•0
.5' .'
28' . 5.5', 5' ;5' -,5; 5' , 5.5'10 32' la ; 5'5' I 5' ft
5 I
I— R/W 50'
No Parking on One Side With Parking on Both Sides
,----- ,-----,.
....s, .„
<1r
.1•gr;::11--.--.4
36'
.5 I I
5' 5 6'Bike 12' 12' 6'Bi
5. ' , , .5'
ce, 5. ' '5 i 5 . .
I-: I , 1 I •
R/W 58'
With Bike Lanes/No Parking
Figure 18.810.4
Local Residential Streets-<1,500 vpd
A. Standard(sample) B. Skinny Street Option(criteria)
i .,,,,......./i _ \1,. al ..-;-:.-i,74 . i•-
,n0.1.111_,17.4aliiiii -zez,42Ve-f, ,—, 1 .--,,_Ll
IN
;72. .,...- ..-'..., ti"
32' a55'
-,. 1
I-1 f---5•5'1 Q- i---5L-H.
R/W 7
54' ::i i ; 7 : W ;
---i
5:; 5' (0..1.9) ,---," :y•
.
On-street Parking . %A..5-4, i
28'
614.,i
<1500 vpd *
1,101-of-wa),
If parking on both sides,
block length not to exceed 600 feet Criteria:
-. • Traffic Flow Plan must be submitted and approved.
•,
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only. '
1
1
Proposed Development Code changes to implement the TSP Page 21
S . •
Figure 18.810.5 •
Local Residential Streets<.500 ypd
A. Standard(sample) B. Skinny Street Option(criteria)
G S-7 cc-
,
G;
'14_5' 5' ; 5.5' as 28 __1._5•5'; _5'-5 ® 0 Ili t
50' H T i61T
5.5 c dMj rcrwl 1... s.l•
sue•« !
.Residential Local Street/Cul-de-sac " °; �,. °9
One Side On-street Parking WI.
<500 vpd RigK-a-te
• Criteria:
• Traffic Flow Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd.
•. No parking permitted within 30 feet of an intersection. •
• Appropriate adjacent to single family detached
development only.
• Must provide a minimum of(1)off-street parking space for
,every 20 feet of restricted street frontage.
• Figure 18_810.6
Local Residential Street<200 vpd -
A. Standard(sample) B. Skinny Street Option(criteria)
•
I lit
fin
-mg=
,; !;
5 S.Y ?D'P..e.lers 5.S•
5' 5.5' 24' k 5.5' k 5' { .�•;�,..113« se PLIncine!
i --- — _WW 46'— —-- �
Cul-de-sac/Residential Local Street —wM#-r
<200 vpd Criteria:
• Must provide a minimum of(1)off-street parking space
(No parking) for every 20 feet of restricted street frontage.
• No parking permitted within 30 feet of an intersection.
F. Future street plan and extension of streets.
1. A future street plan shall:
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall-may prepare
a future streets proposal.___ Costs-.of the City preparing__a future streets proposal_shall be
Proposed Development Code changes to implement the TSP Page 22
•
• •
reimbursed for the time_involved. A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus routes, pullouts or other transit facilities, bicycle routes and
pedestrian facilities on or within 530 feet of the site.
2. Where necessary to give access or permit a satisfactory future division of adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
G_Street spaeing_and acce5s_management. Refer to M705.030 H.
GH. Street alignment and connections.
1. Full street connections with spacing of no more than 530 feet between connections is required
excet_t_where prevented by__t arriers._sueh_as_topography..,_ ra lroads,__freeway_s_pre=existing
developments, lease provis ns,ea sementscovenants_or ether restrictions existingprior=to May
I, 1995 which preclude street connections Afull street connection mayalso be exempted due to
a regulated water feature if regulations would not permit construction.
-1-. . , « „ •- - _ . . - . .
street,
23. All local der, neighborhood routes_and collector streets which abut a development site
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this coder A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15%for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such as schools, shopping
areas and parks.
45. All developments.should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed Development Code changes to implement the TSP Page 23 •
• •
I4I. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
IJ. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
JK. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and .
2. The length of the cul-de-sac shall be measured from the centerline point of the two
streets to the radius point of the bulb.: •- - - • •- . -- . -- --
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
bM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and as approved by the City
Engineer..-
MN. Grades and curves.
L Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet), and
—42. Centerline radii of curves shall be as determined by the City Enjneer.not be less than 700 feet on
arterials, 500 feet on major collectors, 350 feet on minor collectors; or 100 feet on other streets;
and
Proposed Development Code changes to implement the TSP Page 24
• •
NO. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required;except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards.
OP_.Streets adjacent to railroad right-of-way. Wherever the proposed development contains or is adjacent
to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major-collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major-collector street, the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the
following:
1. A parallel access street along the arterial or major collector;
2. Lots of suitable depth abutting the arterial or major collector to provide adequate buffering with
frontage along another street;
3. Screen planting at the rear or side property line to be contained in a nonaccess reservation along
the arterial or major collector; or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR. Alleys,public or private.
1. Alleys shall be no less than 20 feet in width. In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
RS.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed Development Code changes to implement the TSP Page 25
• •
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks,and multi-family residential developments.
TU.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
VV. Street signs. The City shall install all street signs,relative to traffic control and street names, as
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
WX. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XY. Street light standards. Street lights shall be installed in accordance with regulations adopted by
the City's direction.
YZ.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
ZAA. Street cross-sections. The fmal lift of asphalt concrete pavement shall be placed on all new
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development, whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed Development Code changes to implement the TSP Page 26
• •
2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
5. No lift shall be less than 1-1/2 inches in thickness. (Ord. 99-22)
AB Traffic Calming. When. in the o.inion of the City Engineer. the proposed development will
c eat- a n-•ative traffic c• .iti.n .n exi fn•_ nei•iborh..d str--t s h , e_ -s 'v- see-e' . the
d-v-le•-r ma be r-• ir-• t. .rovide tr-ffi calmine mea ure Ti- - u-.su e u. •e r-•uires
w' hin th- d-v-loe ent an./or .ffsite -s deem-d a..ro. iate. A an alt-rn.tive th- devel.•-r ma
be required to deposit funds with the City to help pay for traffic calming measures that become
necessary once the development is occusied and the Cit Engineer determines that the additional
tr, is fro th- develo•men ias t '..ere• the need fir tr.ffic calmine me. ur- . Th- Cit Engineer
will determine the amount of funds required. and will collect said funds from the developer prior to the
issuance of a certificate of occupancy or in the case of subdivision, prior to the approval of the final
pal t. The funds will be held by the City for a period of five (5) years from the date Of issuance of
certificate of occupancy-, or in the case of a subdivision. the date of final plat approval. Any funds not
used by the City within the five-year time period will _e refunded to the developeL
AC. Traffic study
1__ A traffic studyshall be required for all new or expanded usesor developments under any of the
following circumstances:
a. when theme_enerate a 10_% or greater increase in existing traffic to high collision intersections
identified by Washington County.
b. Trip generations from development onto the City street at the point of access and the existing
•a4tADT fall within the following ranges:
Existing_ADT ADT to be added by de_velopment
0_3.,00_0 vpd 2_,000 vpd
3001 76,000 vpd 1. 00vpd
>6,000_ypd 500 vpd or more
c. If any of the following i sues_become evideto the City engineer:
(I) 1jjgh traffic volumes on the adjacent roadway that may affect movement into or out of the
site
O Lack of existing left-turn lanes onto the adjacent roadway at the proposed access drive(s)
(31 Inadequate horizontal'or vertical sight distance at access points
(4) The_proxirnityof the proposed access to other existina drives or intersections is a potential
hazard
(5) The proposal requires a conditional use permit or involves a drive-through operation
(()Thenroposed development may result in excessive traffic volumes on adjacent local streets.
2. In addition, a traffic study may be required for all new or expanded uses or developments under
any of the following circumstances:
a,= when the site is within 500 feet of an ODQT facility_and/or
b— trip_generation from a development adds 300 or more vehicle trips per dayto an ODOT facility
Proposed Development Code changes to implement the TSP Page 27
•
•. •
and/or
e.___trip generation from a development adds 50 or more peak hour trips to an ODOT facility.
18.810.040 Blocks
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing
adequate building sites for the use contemplated, consideration of needs for convenient access,
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2,000-4800 feet measured along the
centerline of the streets-right-ef-way-line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or
b. For blocks adjacent to arterial streets, limited access highways,major collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is net-pessibleexempted by B.1 above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse, or drainageway,there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make arrangements with the
City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 1.5 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. „Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated,and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
Proposed Development Code changes to implement the TSP • Page 28
• •
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single-family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation,and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
• which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are likely to be
redivided, the Commission may require that the lots be of such size and shape, and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
A. fir---Sidewalks. All industrial streets and private streets shall have sidewalks meeting City standards
along at least one side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development,even if no sidewalk exists on the other side of the street
B. Requirement of developers
As part of and development proposal_or change in_use_resulting in an additional 1,000
vehicle trips or rnore_per day,an applicant shall be required to identi direct, safe(1.25 x the_straight line
d i s t a n c e f.p e d e s t r i a r i x o u t e s w_i t h_i n 1/2mile of their site to.all transit facilit eland Neighborhood Activi
Centers (schools parks; libraries, etc.). In addition, the developer may. be required to participate in the
removal of anygaps in_thepedestrian system off-site if ilustified jv_the development.
2. If there is an existing sidewalk,on the same side of the street as the development, within 30Q
feet of a development site in either direction, the sidewalk shall be extended from the site to meet the
existing sidewalk. subject to rough proportionality(even if the sidewalk does not serve a neighborhood
activity center)
1-3C:Planter strip requirements. A planter strip separation of at least five feet between the curb and the
sidewalk shall be required in the design of u arterial elector streets • - .. " .
adjacent to the curb, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; OF it would conflict with
the utilities, there are significant natural features (large trees, water features, etcl that would be
destroyed if the sidewalk were located as required_or where there are existing structures in close
proximity to the street (15 feet or less]-Additional consideration for exempting_the planter strip
requirement may be_given on a case by case basis if a property abuts more than one street frontage.
•
Proposed Development Code changes to implement the TSP Page 29
• •
CD. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
in width, and:
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
E.F.Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed, then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property in question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
EQ.Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings, commercial buildings or public buildings and/or parks; and
Proposed Development Code changes to implement the TSP Page 30
• •
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord. 99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park,playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord. 99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
operation of the sewage treatment system.
•
18.810.100 Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
Proposed Development Code changes to implement the TSP Page 31
• •
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
18.810.110 Bikeways and Pedestrian Pathways
A. A. Bikeway extension.
1. Aga_standard bike lanes shall be required along all Arterial and Collector routes and where
identified on the_City_s adopted bicycle plan in the Transportation System Plan (TSP)_
•
2. Developments adjoining proposed bikeways identified on the City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3. Any new street improvement project sail include bicycle lanes as required in this document
and on the adopted bicycle plan.
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and'other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
1. Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
2._Minimum width • multi-use paths separated from the road is eight ten
(tQ)_feet_The width maybe reduced to eight_(81feet if there are environmental or other constraints.
3. The minimum width_forpede_strianonly offmfreet paths is five (5)feet_
4. Design standards for bike_andoedestrian-ways shall be determined by the City Engineer.
Proposed Development Code changes to implement the TSP Page 32
• •
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above, and:
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer, shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information,easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement.
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common,but not the
only,such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
• undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
Proposed Development Code changes to implement the TSP Page 33
• •
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities, unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front-foot basis.
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually:
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City,permit fee'paid,and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Proposed Development Code changes to implement the TSP Page 34
111/ •
•
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments)shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices, and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)
Proposed Development Code changes to implement the TSP Page 35
• •
Exhibit A-5
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions in alphabetical order and renumber the remaining
definitions accordingly:
"Neighborhood Activity Center"—A use such as schools,parks, l.ibraries,_shoppintr areas
employment_centers or pools which provide recreational or social services_for groups of
people. ---- ----- ---
"Traffic Flow Plan" — A plan submitted with a proposal for skinny streets that shows the
potential queuing_pattem that will allow for safe and ,efficient travel_ of emergency
vehicles, service vehicles and passenger vehicles with minimal disturbance. This may
include a combination of strategic driveway locations, turnouts or other mechanisms
which will foster safe and efficient travel.
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B
change the 3rd sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more Major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
Additional TSP implementation code amendments Page
• •
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
18.745.050.C.2.b
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or miner-collector street.
Additional TSP implementation code amendments Page 2
Exhibit B
Attached are the TPR requirements with an explanation of how they are addressed in the existing City of Tigard
Development Code and in the proposed amendments.
(Where there is a dashed line- it indicates that there is not a standard to be addressed,just an intro in to the
standards.)
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
Local governments shall adopt land use or subdivision
regulations for urban areas and rural communities as set forth
below. The purposes of this section are to provide for safe and
convenient pedestrian, bicycle and vehicular circulation
consistent with access management standards and the function
of affected streets, to ensure that new development provides
on-site streets and accessways that provide reasonably direct
routes for pedestrian and bicycle travel in areas where
pedestrian and bicycle travel is likely if connections are
provided, and which avoids wherever possible levels of
automobile traffic which might interfere with or discourage
pedestrian or bicycle travel.
Bicycle parking facilities as part of new multi-family 18.765.050.E states the minimum
eidential developments of four units or more, new retail, parking requirements for all use
office and institutional developments, and all transit transfer types. This is required as part of
stations and park-and-ride lots; any land use review.
(b) On-site facilities shall be provided which 18.765.050 provides bike parking 18.810.070 is being amended to include a
accommodate safe and convenient pedestrian and bicycle design standards requirement of the developer to show connections
access from within new subdivisions, multi-family to neighborhood activity centers within V2 mile of
developments, planned developments, shopping centers, and 18.705.030.E (Access, Egress and development and require consideration of
commercial districts to adjacent residential areas and transit Circulation—required walkway improvement requirements depending on
stops, and to neighborhood activity centers within one-half location) addresses walkway proportionality. The amendment also required the
requirements for multi-family, removal of gaps in the sidewalk within 300 feet on
Page 1 of 8
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
mile of the development. Single-family residential industrial or commercial the same side of the street as a development
developments shall generally include streets and accessways. development. 0 (subject to rough proportionality).
Pedestrian circulation through parking lots should generally
be provided in the form of accessways. 18.810.040 (Street and Utility
Improvement Standards—Blocks)
addresses pedestrian connections
when full street connections are
not possible •
18.810.070 (sidewalks)requires
all public streets to have
sidewalks
(A) "Neighborhood activity centers" includes, but 18.120.030 is being amended to include a
is not limited to, existing or planned schools, parks, definition of Neighborhood Activity Center.
shopping areas, transit stops or employment centers;
(B) Bikeways shall be required along arterials and Sidewalks currently are required 18.810.110.A is amended to include the
major collectors. Sidewalks shall be required along along all public streets. requirement that bike lanes be located on all
arterials, collectors and most local streets in urban areas, Development code does not have arterials and collectors and any additional routes
except that sidewalks are not required along controlled a bike lane requirement but refers identified in the TSP for any new construction or
access roadways, such as freeways; to the City's comprehensive plan. improvement project.
(C) Cul-de-sacs and other dead-end streets may be 18.810.030.K regulated cul-de-
used as part of a development plan, consistent with the sacs and states that they can't be •
purposes set forth in this section; more than 200 feet long. IF a
variance is granted and the cul-
de-sac is greater than 300 feet,
pedestrian connections are
required. This is in addition to
the block length standards which
may also require additional
pedestrian connections through a
block.
Page 2 of 8
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(D) Local governments shall establish their own 18.810 establishes standards that There are amendments which address street
standards or criteria for providing streets and accessways regulate street spacing and block spacing and block lengths, however, they continue
consistent with the purposes of this section. Such lengths intending on limiting out to limit out-of-direction travel and provide greater
measures may include but are not limited to: standards for of direction travel. clarification to increase efficiency and safety.
spacing of streets or accessways; and standards for
excessive out-of-direction travel;
• (E) Streets and accessways need not be required where 18.810.040—Block length
one or more of the following conditions exist: standards provide for this
(i) Physical or topographic conditions make a exception in the standard.
street or accessway connection impracticable.
Such conditions include but are not limited to
freeways, railroads, steep slopes,wetlands or
other bodies of water where a connection could
not reasonably be provided;
(ii) Buildings or other existing development on
adjacent lands physically preclude a
connection now or in the future considering the
potential for redevelopment; or
(iii) Where streets or accessways would violate
provisions of leases, easements, covenants,
restrictions or other agreements existing as of
May 1, 1995 which preclude a required street
or accessway connection.
(c) Where off-site road improvements are otherwise Any road is required to be
required as a condition of development approval, they shall constructed to the standards
include facilities accommodating convenient pedestrian and called for in our code. As shown
bicycle travel, including bicycle ways along arterials and within this matrix, the code
major collectors; requires sidewalks but additional
amendments have been made to
Page 3 of 8
660-12-0045 - How Addressed in current code Proposed amendments
TPR Requirement
define required bikeway
locations.
(d) For purposes of subsection(b) "safe and convenient"
means bicycle and pedestrian routes, facilities and
improvements which:
(A) Are reasonably free from hazards, particularly The City's Municipal code
types or levels of automobile traffic which would interfere prohibits obstructions on public
with or discourage pedestrian or cycle travel for short sidewalks •
trips;
(B) Provide a reasonably direct route of travel The access standards, block
between destinations such as between a transit stop and a length standards and requirement
store; and for sidewalks provides a In addition, an amendment is proposed to have the
(C) Meet travel needs of cyclists and pedestrians reasonably direct route of travel developer review routes within 300 feet
considering destination and length of trip; and considering between destinations and meets (approximately Y4 mile) from the development site
that the optimum trip length of pedestrians is generally 1/4 the travel needs of cyclists and and, if proportional, make necessary
to 1/2 mile. pedestrians improvements to complete "gaps"
(e) Internal pedestrian circulation within new office parks 18.705.030.E requires walkways
•
and commercial developments shall be provided through within commercial developments
clustering of buildings, construction of accessways, walkways
and similar techniques.
(4) To support transit in urban areas containing a
•
population greater than 25,000, where the area is already
served by a public transit system or where a determination has
been made that a public transit system is feasible, local
governments shall adopt land use and subdivision regulations
as provided in (a)-(f)below:
(a) Transit routes and transit facilities shall be designed to SDR standards 18.360.090.11
support transit use through provision of bus stops, pullouts requires development to provide
and shelters, optimum road geometries, on-road parking transit amenities as'required by
Page 4 of 8
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
restrictions and similar facilities, as appropriate; tri-met during the development
review (if proportional and
justified)
(b) New retail, office and institutional buildings at or near
major transit stops shall provide for convenient pedestrian
access to transit through the measures listed in(A) and (B)
Glow.
(A) Walkways shall be provided connecting
building entrances and streets adjoining the site; 18.705.030.f
(B) Pedestrian connections to adjoining properties
shall be provided except where such a connection is 18.810.070—sidewalks
impracticable as provided for in OAR
660-012-0045(3)(b)(E). Pedestrian connections shall
connect the on site circulation system to existing or
proposed streets, walkways, and driveways that abut ,
the property. Where adjacent properties are •
undeveloped or have potential for redevelopment, •
streets, accessways and walkways on site shall be laid
out or stubbed to allow for extension to the adjoining
property;
(C) In addition to (A) and (B) above, on sites at
major transit stops provide the following: 18.360.090.11 requires
(i) Either locate buildings within 20 feet of consideration of transit facility
the transit stop, a transit street or an improvements as part of
intersecting street or provide a development review (which
pedestrian plaza at the transit stop or a covers ii to v). Building
street intersection; placement standards are already
(ii) A reasonably direct pedestrian in place in the Tigard Triangle
connection between the transit stop and and as part of the Washington
building entrances on the site; Square Regional Center.
(iii) A transit passenger landing pad Additional standards for building
Page 5 of 8
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
accessible to disabled persons; placement outside of these transit
(iv) An easement or dedication for a oriented areas are not appropriate.
passenger shelter if requested by the
transit provider; and
(v) Lighting at the transit stop.
(c) Local governments may implement 4(b)(A) and (B) While not specifically designated •
above through the designation of pedestrian districts and pedestrian districts, the Tigard
adoption of appropriate implementing measures regulating Triangle and the Washington
development within pedestrian districts. Pedestrian districts Square Regional Center
must comply with the requirement of 4(b)(C) above; implement the requirements of
4(b) (C)
(d) Designated employee parking areas in new 18.765.030.F required parking
developments shall provide preferential parking for carpools lots in excess of 20 long-term
and vanpools; parking spaces to provide
preferential long-term carpool •
and vanpool parking for
employees and other visitors to
the site.
(e) Existing development shall be allowed to redevelop a Not specifically provided for, but
portion of existing parking areas for transit-oriented uses, would not be disallowed since
including bus stops and pullouts, bus shelters,park and ride nothing on the code prohibits it.
stations, transit-oriented developments, and similar facilities,
where appropriate;
(f) Road systems for new development shall be provided 18.810 has street standards that
that can be adequately served by transit, including provisions provides for adequate width of
of pedestrian access to existing an identified future transit pavement and turning radius, etc
routes. This shall include,where appropriate, separate that will provide for transit.
accessways to minimize travel distances. Sidewalks are required along all
public streets
Page6of8
660-12-0045 How Addressed in current code Proposed amendments
TPR Requirement
(g) Along existing or planned transit routes, designation Existing zoning-along transit
of types and densities of land uses adequate to support transit. routes is transit supportive—no
changes are needed
(5) In MPO areas, local governments shall adopt land use The Tigard Triangle area,
and subdivision regulations to reduce reliance on the Washington Square Regional
iiiitomobile which: Center area and Central Business
Allow transit oriented developments (TODs) on lands District zone have provisions for
along transit routes; mixed use development and
street and design standards which
(b) Implements a demand management program to meet encourage transit oriented
the measurable standards set in the TSP in response to 660- development
012-0034(4).
(6) In developing a bicycle and pedestrian circulation plan TSP provides bike and pedestrian Proposed amendments specifically require
as required by 660-012-0020(2)(d), local governments shall master plan. The development pedestrian or bike improvements if shown on the
identify improvements to facilitate bicycle and pedestrian code currently requires walkways pedestrian or bikeway plan, if roughly
trips to meet local travel needs in developed areas. and sidewalks, however we need proportional.
Appropriate improvements should provide for more direct, to amend the code to specifically
convenient and safer bicycle or pedestrian travel within and require if shown on the pedestrian
een residential areas and neighborhood activity centers or bikeway plan.
.e., schools, shopping, transit stops). Specific measures
include, for example, constructing walkways between cul-de-
sacs and adjacent roads, providing walkways between
buildings, and providing direct access between adjacent uses.
(7) Local governments shall establish standards for local Current code required pavement The TSP, which provides the foundation for the
streets and accessways that minimize pavement width and width between 24' and 32' for amendments being proposed, was developed with
total right-of-way consistent with the operational needs of the local streets (actual width the help of a Citizen Task Force and Technical
facility. The intent of this requirement is that local depends on ADT and whether Advisory Committee and involved several public
Page 7 of 8
660-12-0045 � How Addressed in current code Proposed amendments
TPR Requirement
governments consider and reduce excessive standards for parking is provided on the street) information meetings to gather input and
local streets and accessways in order to reduce the cost of and up to 12 feet per lane for comments and 2 formal public hearings. After the
construction, provide for more efficient use of urban land, arterial streets development and adoption of the TSP, a group of
provide for emergency vehicle access while discouraging City Staff from Planning and Engineering and a
inappropriate traffic volumes and speeds, and which representative from Tualatin Valley Fire and
accommodate convenient pedestrian and bicycle circulation. Rescue met over several months to develop code
Not withstanding subsection(1) or(3) of this section, local language to implement the TSP. The discussions
street standards adopted to meet this requirement need not be included the TPR"skinny street"requirement.
adopted as land use regulations. After review and discussion, it was determined ill
•
that the safe harbor widths were acceptable,
•
provided a traffic flow plan was submitted to
verify that the distribution of driveways, no
parking areas, etc would allow efficient queuing
and traffic flow as the State's "Neighborhood
Streets Design Guidelines" assumed. Additional
assurances were needed to ensure that adequate
off-street parking was provided for streets that had
parking on one side only. It was determined that
the existing width standards would remain for
those that did not want to submit a traffic flow
plan or provide additional assurances for off-street
parking, but the option to go to narrower streets
would be provided as well. While technically, t�
wider street width is the default because no
additional documentation is required, both street
width standards are acceptable and available for
developments on local streets.
Page 8 of 8
y • •
FAX TRANSMITTAL
1 I
Date July 8, 2002
Number of pages including cover sheet 1
To: Sylvia Makinster From: Jerree Gaynor
Co: Community Newspapers Co: City of Tigard
Fax #: 503-620-3433 Fax#: 503-684-7297
Ph #: (503) 639-4171, Ext. 323
SUBJECT: Legal Ad
MESSAGE:
The following legal notice was e-mailed to you today:
Document Title: , TSP ad.doc
Paper to publish: Tigard Times
Date of publication: July 18, 2002
Contact name: see above
I:IENGIFAX.DOT
97/08/2002 13: 38 5035460725 COMMUNITY NE4JPERS PAGE 01
• 0•
COO
NEWSPAPERS
M.rm Wq m..•QolooCwyrr.r•mlomar Woo•macaw UM•w Mom row•1oai Wow rr..m.
aborroCulok•laiwOurea Woo.lake0o**in•awn al ma.Abet res•Simi
Comma rlwawr.4mspaowwww•a.olB*%IOW•wrrrmlmelod OM*Minos
FAX COVER SHEET
. .
ATTN. • 6 '
COMPANY: Y�
FAX #: ?s/— 7a1-5'
We have received your Public Notice information
w
!
Re: i 6& Z9/} 0044
/ "®
Publication Date(s): /8, ° o��
You will receive a notarized affidavit, with tear sheet attached, after the last publication
date.
Thank you for publishing with Community Newspapers,Inc., and please feel free to call
if you have questions.
Sincer , jez4:0,
•
Sylvi akinster, Adv. Asst. &Legals
Phone: 503-546-0779 Fax: 503-620-3433
Y47 Date: 7/51°2-Time: No. Pages: 1
(including cover)
Please direct this transmittal. If you do not receive all pages, please call. Thank You.
P.O. Box 370 •.Beaverton, OR 97075 • (503) 684-0360 • Fax: (503) 620-3433
"r
1
CITY OF TIGARD
PLANNING COMMISSION
Meeting Minutes
June 3, 2002
1. CALL TO ORDER
President Padgett called the meeting to order at 7:00 p.m. The meeting was held
in the Tigard Civic Center, Red Rock Creek Conference Room, at 13125 SW Hall
Blvd.
2. ROLL CALL
Commissioners Present: President Padgett; Commissioners Anderson,
Buehner, Mores, Munro, Sutton, and Webb
Commissioners Absent: Commissioners Bienerth and Scolar
Staff Present: Julia Hajduk, Associate Planner; Brian Rager, Development
Review Engineer; Jerree Gaynor, Planning Commission
Secretary
3. PLANNING COMMISSION COMMUNICATIONS
a) Alternate Commissioner Tom Wolch resigned 5/21/02.
b) Next meeting will be 6/17/02.
4. APPROVE MEETING MINUTES
Commissioner Anderson moved and Commissioner Webb seconded the motion
to approve the May 20, 2002, meeting minutes as submitted. The motion passed
by a vote of 5-0. Commissioners Buehner & Sutton abstained.
5. WORKSHOP ON IMPLEMENTATION OF TRANSPORTATION SYSTEM PLAN
Associate Planner Julia Hajduk provided explanation and details on the proposed
changes to the Development Code that are necessary to implement the
Transportation System Plan (TSP) adopted in January 2001. See Memorandum
to Planning Commission members from Ms. Hajduk dated May 23, 2002.
Discussion items:
➢ City's authority to require sidewalks on private streets — Any development
must comply with City standards, which include requirements for street width
and sidewalks. Requirements for sidewalks have to do with access and
pedestrian circulation, which ties back to the Transportation Planning Rule
and Metro requirements.
PLANNING COMMISSION MEETING MINUTES — June 3,2002 — Page 1
• •
➢ Bike lanes on arterials and collectors — requirements based on Transportation
Planning Rule and Regional Transportation Plan. There is a proposal to
change this in the Washington County plan.
➢ Staff will report back to the Commission on whether or not the Regional
Transportation Plan F standard for arterials was adopted as part of the TSP.
It is unlikely the Tigard TSP will require more than the Regional
Transportation Plan.
➢ Staff will request Planning Commission recommendation to City Council for
landscape strips with setback sidewalks, except under circumstances set
forth in Code Section 18.810 for curb-tight sidewalks. Exceptions can also be
determined by the Commission and PUD in specific situations. Appropriate
improvements, such as trees and sprinkler systems, as well as maintenance
of sidewalk landscape strips, are issues of concern and should be considered
as part of any recommendation to City Council. If sidewalk landscape strips
are not required, it is unlikely that they would be included in any new
development because it allows for less right-of-way. There are pros and cons
to the issue. One component in the street utility fee proposal is a right of way
maintenance fee to provide for City maintenance of the strips. The majority of
the Commission objected to requiring landscape strips.
➢ Skinny streets — there are two standards due to DLCD/TPR requirements for
28-foot minimum standard; normal standard is for 32-foot street width.
Specific standards for "skinny streets" require approval of a queuing plan (i.e.,
location/staggering of driveways), traffic of less than 1,000 trips per day, only
available for single-family detached homes, etc. Sidewalk landscape strips
discussed above will also be required. Although skinny streets are
predominantly in residential areas, parking in areas adjacent to commercial
development may become an issue to be considered. Parking, bus routes,
and emergency vehicle access were also discussed.
6. OTHER BUSINESS
None
7. ADJOURNMENT
The meeting adjourned at 8:30 p.m.
Jerree Gaynor, Planning Commission Secretary
ATTEST: President Mark Padgett
PLANNING COMMISSION MEETING MINUTES — June 3, 2002 — Page 2
•
• /qp,d, s._
_ J
" CITY OF TIGARD
Community Development
Shaping A Better Community
MEMORANDUM
CITY OF TIGARD
TO: Planning Commission members
FROM: Julia Hajduk, Associate Planner
DATE: (May 23, 2002
SUBJECT: Development Code amendments to implement the
Transportation System Plan (TSP)
As you recall, the Tigard Transportation System Plan (TSP) was adopted in
January, 2001 along with Comprehensive Plan amendments and became
effective in February. An additional step that was necessary to fully
implement the TSP was developing amendments to the Development Code to
reflect changes to the TSP. The planning staff, along with staff from the
engineering department have completed the review of the Development Code
and are prepared to begin processing the recommended amendments. At the
June 3, 2002 work session, we plan to discuss the proposed changes to the
Development Code needed to fully implement the TSP and address any
comments and questions you may have. Attached please find the following:
Attachment 1 — Summary of changes to implement the TSP
Attachment 2 — Development Code section 18.705 amendments
Attachment 3 — Development Code section 18.730 amendments
Attachment 4 — Development Code section 18.810 amendments
Attachment 5 —Additional amendments for portions of code sections 18.120,
18.360, 18.520, 18.530 and 18.745.
In the attached documents, the changes being inserted are identified with a
double underline and items deleted are identified with a .
The Planning Commission public hearing is tentatively scheduled for August
5th and the City Council public hearing is tentatively scheduled for September
10,2002.
1:Irpin/julia/TSP/PC worksession memo.doc
•
•
• •
Attachment 1
Summary of changes to implement the TSP
The following is a summary of changes proposed to implement the TSP adopted in January 2002.
After a brief explanation of the change is the code section location for quick reference. Because the
changes are made for several reasons, the impetus for the change is also identified (TSP, staff, Metro
or DLCD)
18.120
Added the following definitions:
• Neighborhood Activity Center
• Queuing Plan (Staff clarification)
•
18.360
Amended 18.360.090.11.a to define adjacent as being within 500 feet of a transit route. (TSP)
18.520
Amended 18.520.020.B to remove reference to maior collector streets and replaced with reference to
collector street. (Staff clarification/TSP)
18.530
Amended 18.530.050.A.2 to remove reference to major collector streets and replaced with reference
to collector street. (Staff clarification/TSP)
18.705
Identified that if direct access is permitted onto an arterial or collector street, an application may be
required to mitigate any safety or neighborhood traffic management impacts. (18.705.030.G.2) (TSP)
Provided access management requirements (18.705.030.H)
• Verify that design of driveways are safe
• Regulate driveway locations from intersections
• Moved spacing of driveways and streets from 18.810 (TSP)
18.730
Removed reference to specific roadways in the additional setbacks section. The reason for this was
that the entire list was very outdated. In addition, the intent could be met by retaining the existing
requirement that in the event a street had less than the required right-of-way, the setback for a
structure must be no less than the required setback plus 1/2 the required right-of-way width measured
from centerline.(18.730.040.A) (Staff clarification)
18.745
Amended 18.745.050.C.2.b to remove reference to major and minor collector streets and replaced
with reference to collector street. (Staff clarification/TSP)
18.810
Provided new minimum widths and standards for streets
• Includes lane width, on-street parking, bike lanes, sidewalks, landscape strips and median •
requirements. (Table 18.810.1 and figures 18.810.1 through 18.810.6) (TSP/DLCD-TPR)
Clarified that if the city prepares a future streets plan for an applicant, costs for time involved shall be
reimbursed by the applicant (18.810.030.F) (Staff clarification)
Summary of changes to implement the TSP Page 1 of 2
(Updated 5-3-02)
• • •
Added sections requiring street connections to be spaced no less than 520 feet apart to address
connectivity requirements. (18.810.030.G.1) (TSP/Metro)
Moved spacing of streets to 18.705.030.H (Staff clarification)
Clarified how cul-de-sac length is measured (18.810.030.K.2) (Staff clarification)
Provide the City engineer with a say in approving street names(18.810.030.L) (Staff clarification)
Removed standards that are conflicting with the Engineering Departments Design and Construction
standards and that would need to be amended anyway to reflect the removal of minor and major
collector references. Standard now says that centerline.radii curves shall be as determined by the
City Engineer. (18.810.030.N) (Staff clarification/TSP)
Added traffic calming provisions requiring a developer to deposit funds towards traffic calming if the
City Engineer determines that a development has the potential of creating a negative impact on
existing neighborhood streets in regards to excessive speeding, etc. The funds would be kept for up
to 5 years and if after that time it is determined that traffic calming measures are not warranted, the
funds would be returned. (18.810.030.AB) (TSP)
Provided parameters for when a traffic study is required (18.810.030.AC) (Staff clarification)
Changed the requirement that blocks not exceed 1,800 feet to 2,120 feet to be consistent with Metro
connectivity requirements of streets every 530 feet. (18.810.040.B.1) (Staff clarification)
Clarified that bike and pedestrian connections shall be provided when full street connections are
exempted, instead of"not possible". (18.810.040.B.2) (Staff clarification)
Formalize existing policy by stating that private streets shall be required to have sidewalks along at
least one side of the street. (18.810.070.A) (Staff clarification)
Required developments to identify gaps in sidewalks and participate in the removal of gaps if the
costs can be justified. (18.810.070.B) (TSP)
Changed policy that planter strips are required along arterial and collector streets to require planter
strips adjacent to all streets except under specific conditions. (The specific conditions are: there is
inadequate right-of-way, the curbside sidewalks already exist on predominant portions of the street, it
would conflict with utilities, there are natural features which could otherwise be protected, or there are
existing structures within 15 feet of the right of way). (18.810.070.C) (Staff recommendation/POLICY
DECISION NEEDED)
Required bike lanes along all arterial and collector routes and where identified on the adopted bike
plan in the TSP. Identify the minimum widths various types of pedestrian and bicycle paths
(18.810.110) (TSP)
Summary of changes to implement the TSP Page 2 of 2
(Updated 5-3-02)
• • Attachment 2
Chapter 18.705
ACCESS,EGRESS,AND CIRCULATION
Sections:
18.705.010 Purpose
18.705.020 Applicability of Provisions
18.705.030 General Provisions
18.705.010 Purpose
A. Purpose: The purpose of this chapter is to establish standards and regulations for safe and efficient
vehicle access and egress on a site and for general circulation within the site.
18.705.020 Applicability of Provisions
A. When provisions apply. The provisions of this chapter shall apply to all development including the
construction of new structures, the remodeling of existing structures(see Section 18.360.050), and
to a change of use which increases the on-site parking or loading requirements or which changes
the access requirements.
B. Change or enlargement of use. Should the owner or occupant of a lot or building change or enlarge
the use to which the lot or building is put, thereby increasing access and egress requirements, it is
unlawful and is a violation of this title to begin or maintain such altered use until the provisions of
this chapter have been met if required or until the appropriate approval authority has approved the
change.
C. When site design review is not required. Where the provisions of Chapter 18.360, Site
Development Review, do not apply, the Director shall approve, approve with conditions, or deny
an access plan submitted under the provisions of this chapter in conjunction with another permit or
land use action.
D. Conflict with subdivision requirements. The requirements and standards of this chapter shall not
apply where they conflict with the subdivision rules and standards of this title.
18.705.030 General Provisions
A. Continuing obligation of property owner. The provisions and maintenance of access and egress
stipulated in this title are continuing requirements for the use of any structure or parcel of real
property in the City.
B. Access plan requirements. No building or other permit shall be issued until scaled plans are
presented and approved as provided by this chapter that show how access, egress and circulation
requirements are to be fulfilled. The applicant shall submit a site plan. The Director shall provide
the applicant with detailed information about this submission requirement.
C. Joint access. Owners of two or more uses, structures,or parcels of land may agree to utilize jointly
the same access and egress when the combined access and egress of both uses, structures, or
parcels of land satisfies the combined requirements as designated in this title, provided:
Proposed 18.730 Development Code changes to implement the TSP page 1
• •
1. Satisfactory legal evidence shall be presented in the form of deeds, easements, leases or
contracts to establish the joint use; and
2. Copies of the deeds, easements, leases or contracts are placed on permanent file with the City.
D. Public street access. All vehicular.access and egress as required in Sections'18.705.030H and
18.705.030I shall connect directly with a public or private street approved by the City for public
use and shall be maintained at the required standards on a continuous basis.
E. Curb cuts. Curb cuts shall be in accordance with Section 18.810.030N.
F. Required walkway location. On-site pedestrian walkways shall comply with the following
standards:
1. Walkways shall extend from the ground floor entrances or from the ground floor landing of
stairs, ramps, or elevators of all commercial, institutional, and industrial uses, to the streets
which provide the required access and egress. Walkways shall provide convenient_
connections between buildings in multi-building commercial, institutional, and industrial
complexes. Unless impractical, walkways shall be constructed between new and existing
developments and neighboring developments;
2. Within all attached housing (except two-family dwellings) and multi-family developments,
each residential dwelling shall be connected by walkway to the vehicular parking area, and
common open space and recreation facilities;
3. Wherever required walkways cross vehicle access driveways or parking lots, such crossings
shall be designed and located for pedestrian safety. Required walkways shall be physically
separated from motor vehicle traffic and parking by either a minimum 6-inch vertical
separation (curbed) or a minimum 3-foot horizontal separation, except that pedestrian
crossings of traffic aisles are permitted for distances no greater than 36 feet if appropriate
landscaping, pavement markings, or contrasting pavement materials are used. Walkways shall
be a minimum of four feet in width, exclusive of vehicle overhangs and obstructions such as
mailboxes, benches, bicycle racks, and sign posts, and shall be in compliance with ADA
standards;
4. Required walkways shall be paved with hard surfaced materials such as concrete, asphalt,
stone, brick, etc. Walkways may be required to be lighted and/or signed as needed for safety
purposes. Soft-surfaced public use pathways may be provided only if such pathways are
provided in addition to required pathways.
G. Inadequate or hazardous access.
1. Applications for building permits shall be referred to the Commission for review when, in the
opinion of the'Director,the access proposed:
a. Would cause or increase existing hazardous traffic conditions; or
b. Would provide inadequate access for emergency vehicles;or
c. Would in any other way cause hazardous conditions to exist which would constitute a
clear and present danger to the public health, safety,and general welfare.
Proposed 18.730 Development Code changes to implement the TSP page 2
• IP
2. Direct individual access to arterial or collector streets from single-family dwellings and duplex
lots shall be discouraged. Direct access to major collector or arterial streets shall be
considered only if there is no practical alternative way to access the site. If clireot access is
permitted by the City the applicantwill_be required to IniAlgatc.tor arw_safety or neighborh.00d
traffic__mananment (NIM impadeemed applicable _by_the__Gitvr__,Engineer,____This _may
include; but_willnot_be Inniled_10-11.te eo_ns_truction of_a vehicle turnaround On OWL_Site_ tO.
eliminate the need for a vehicle to back out the roadway.
3. In no case shall the design of the service drive or drives require or facilitate the backward
movement or other maneuvering of a vehicle within a street,other than an alley. Single-family
and duplex dwellings are exempt from this requirement.
1-1„__ _Access Management
1_. An_access reLmmt bessibmitted with allnew development_grop_o_s_als which verifies design
of drivewaysand_streets are safe by_rnee_titp?adestuate stacking_needs_sight distance and
deceleration standards as set by___ODOT, Washington_County_,the Cif_ and_AASI-IT0
(depending on jurisdiction_offaciliq7A
2. Driveways shall not_bepermitted to,be placed_inthe influence area of collector or arterial street
intersections—lanencearea_of intersections_is thatarea where_quettes_of traffic coat J319111y
fOr111_01-1 ap_p_r_o_ach_ito anintersection„ The inininnUn driVQNYOY setback_from asollootor
arterial street interseetion feet_measured from the right:of-way line of the
intersection-street to the throat of the proposed driveway. The setback may_be_greater
depending upon the influence area,as determined from City Engineer review of a traffic impact
report submitted by the ap_plicant's traffic engineer._In a case where aproject has less than 150
_feetof greet frontag_e appficantmust_explore any option for shared access 3.vith the_adjacnt
parcel, If share_d a_cc_es_s_is not_possib le orpracticat_the driveway shall be placed as far from_the
i n ters_ection aa_)Q.S_S ible.
minimum_spacing of driveways_andstreets_along a_collecior shall_be 200 feet„_The
minimum spacing of driveway_s_and streets_along an arterial_shall be 00feet.
4, Therninimum spacin(Y_of local_streets alo_ng a local greet_shall be 125 feet.
Minimum access requirements for residential use.
1. Vehicular access and egress for single-family, duplex or attached single-family dwelling units
on individual lots and multi-family residential uses shall not be less than as provided in Table
18.705.1 and Table 18.705.2;
TABLE 18.705.1
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
RESIDENTIAL USE(6 OR FEWER UNITS)
Number Dwelling Minimum Number of Minimum Access Width Minimum Pavement
Unit/Lots Driveways Required Width
1 or 2 1 15' 10'
3-6 1 20' 20'
Proposed 18.730 Development Code changes to implement the TSP page 3
• •
TABLE 18.705.2
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
MULTI-FAMILY RESIDENTIAL USE
Dwelling Units Minimum Number of Minimum Access Minimum Pavement
Driveways Required Required Sidewalks,Etc.
1-2 1 15' 10'
3-19 1 30' 24' if two-way, 15' if
one-way: Curbs and 5'
walkway required
20-49 1 30' 24' if two-way
or
2 30' 15' if one-way: Curbs and
5' walkway required
50-100 .2 30' 24' Curbs and 5'walkway
required
2. Vehicular access to multi-family structures shall be brought to within 50 feet of the ground
floor entrance or the ground floor landing of a stairway, ramp, or elevator leading to the
dwelling units;
3. Private residential access drives shall be provided and maintained in accordance with the
provisions of the Uniform Fire Code;
4. Access drives in excess of 150 feet in length shall be provided with approved provisions for
the turning around of fire apparatus by one of the following:
a. A circular, paved surface having a minimum turn radius measured from center point to
outside edge of 35 feet;
b. A hammerhead-configured, paved surface with each leg of the hammerhead having a
minimum depth of 40 feet and a minimum width of 20 feet;.
c. The maximum cross slope of a required turnaround is 5%.
5. Vehicle turnouts, (providing a minimum total driveway width of 24 feet for a distance of at
least 30 feet), may be required so as to reduce the need for excessive vehicular backing
motions in situations where two vehicles traveling in opposite directions meet on driveways in
excess of 200 feet in length;
6. Where permitted, minimum width for driveway approaches to arterials or collector streets
shall be no less than 20 feet so as to avoid traffic turning from the street having to wait for
traffic exiting the site.
J. Minimum access requirements for commercial and industrial use.
1. Vehicle access, egress and circulation for commercial and industrial use shall not be less than
21 as provided in Table 18.705.3;
Proposed 18.730 Development Code changes to implement the TSP page 4
• •
•
TABLE 18.705.3
VEHICULAR ACCESS/EGRESS REQUIREMENTS:
COMMERCIAL AND INDUSTRIAL USES
Required Parking Minimum Number of Minimum Access Minimum Pavement
Spaces Driveways Required Width
0-99 1 30' 24' curbs required
100+ 2 30' , 24' curbs required
or
1 50' 40' curbs required
2. Vehicular access shall be provided to commercial or industrial uses, and shall be located to
within 50 feet of the primary ground floor entrances;
3. Additional requirements for truck traffic may be placed as conditions of site development
review.
K. One-way,vehicular access points. Where a proposed parking facility indicates only one-way
traffic flow on the site, it shall be accommodated by a specific driveway serving the facility; the
entrance drive shall be situated closest to oncoming traffic and the exit drive shall be situated
farthest from oncoming traffic.
L. Director's authority to restrict access. The Director has the authority to restrict access when the
need to do so is dictated by one or more of the following conditions:
1. To provide for increased traffic movement on congested streets and to eliminate turning
movement problems,the Director may restrict the location of driveways on streets and require
the location of driveways be placed on adjacent streets, upon the finding that the proposed
access would:
a. Cause or increase existing hazardous traffic conditions; or
b. Provide inadequate access for emergency vehicles;or
c. Cause hazardous conditions to exist which would constitute a clear and present danger to
the public health, safety, and general welfare.
2. To eliminate the need to use public streets for movements between commercial or industrial
properties, parking areas shall be designed to connect with parking areas on adjacent
properties unless not feasible. The Director shall require access easements between properties
where necessary to provide for parking area connections;
3. To facilitate pedestrian and bicycle traffic, access and parking area plans shall provide
efficient sidewalk and/or pathway connections, as feasible,between neighboring developments
or land uses;
4. A decision by the Director per 18.705.030 K.1.-3. above may be appealed by means of a Type
I1 procedure, as regulated by Section 18.390.040,using criteria contained in Section 18.370.020 C3.
Proposed 18.730 Development Code changes to implement the TSP page 5
• •
Attachment 3
Chapter 18.730
EXCEPTIONS TO DEVELOPMENT STANDARDS
Sections:
18.730.010 Purpose
18.730.020 Exceptions to Building Height Limitations
18.730.030 Zero Lot Line Setback Standards
18.730.040 Additional Setback Requirements
18.730.050 Miscellaneous Requirements and Exceptions
18.730.010 Purpose
A. Purpose. The purpose of this chapter is to present exceptions to the height and setback standards
which apply in various zoning districts as detailed in Chapters 18.510, 18.520 and 18.530.
Flexible and/or more stringent setback standards are designed to allow for the maximum use of
land and to allow for a varied building layout pattern while ensuring there will be adequate open
space, light, air and distance between buildings to protect public health and safety.
18.730.020 Exceptions to Building Height Limitations
A. Projections not used for human habitation. Projections such as chimneys, spires, domes, elevator
shaft housings, towers excluding TV dish receivers, aerials, flag poles, and other similar objects
not used for human occupancy, are not subject to the building height limitations of this title.
B. Building height exceptions. Any building located in a non-residential zone may be built to a
maximum height of 75 feet; provided:
1. The total floor area of the building does not exceed 1-1/2 times the area of the site;
2. The yard dimensions in each case are equal to at least 1/2 of the building height of the primary
structure; and
3. The structure is not abutting a residential zoning district.
C. Building heights and flag lots.
1. Limitations on the placement of residential structures on flag lots apply when any of the
following exist:
a. A flag lot was created prior to April 15, 1985;
b. A flag lot is created after April 15, 1985 by an approved partition;or
c. A flag lot is created by the approval of a subdivision and the flag lot is located on the
periphery of the subdivision so that the lot adjoins other residentially-zoned land.
2. The maximum height for an attached or detached single-family, duplex, or multiple-family
residential structure on a flag lot or a lot having sole access from an accessway, private drive or
easement is 1-1/2 stories or 25 feet, whichever is less, except that the maximum height may be-
2-1/2 stories or 35 feet, whichever is less,provided:
Proposed 18.730 Development Code changes to implement the TSP page 1
•
•
a. The proposed dwelling otherwise complies with the applicable dimensional requirements of
the zoning district;
b. A 10 feet side yard will be preserved;
c. A residential structure on any abutting lot either is located 50 feet or more from the nearest
point of the subject dwelling, or the residential structure exceeds 1-1/2 stories or 25 feet in
height on any abutting lot; and
d. Windows 15 feet or more above grade shall not face dwelling unit windows or patios on
any abutting lot unless the proposal includes an agreement to plant trees capable of
mitigating direct views, or that such trees exist and will be preserved.
3. Where an agreement is made to plant trees capable of mitigating direct views, the agreement
shall be deemed a condition of approval under the provisions of Section 18.390.030 D.
4. The tree planting agreement shall be a condition of Chapter 18.360, Site Development Review,
for three or more attached units or a multiple-family residential structure, or, at the time of
issuance of building permits, for single detached units, one duplex or two attached residential
units.
18.730.030 Zero Lot Line Setback Standards
A. Applicability and limitations. The provisions of this chapter apply to the R-4.5 and R-7 zoning
districts and are limited to single-family detached dwelling units. The provisions of this chapter
shall be applied in conjunction with:
1. An application for planned development approval under the provisions of Chapter 18.350,
Planned Development;
2. An application for subdivision approval under the provisions of Chapter 18.430, Subdivision;
or
3. An application for partitioning approval under the provisions of Chapter 18.420, Partition.
B. Approval criteria and conditions.
1. The approval authority shall approve, approve with conditions or deny an application for a zero
lot line development based on findings that:
a. There shall be a 10-foot separation between each residential dwelling structure or garage;
b. No residential dwelling shall be placed on a lot line which is common to a lot line which is
not a part of the overall development;
c. No structure shall be placed on a lot line which is common to a public or private road right-
of-way or easement line; and
d. A five-foot non-exclusive maintenance easement shall be delineated on the plan for each lot
having a zero setback area:
Proposed 18.730 Development Code changes to implement the TSP page 2
• •
(1) The easement shall be on the adjacent lot and shall describe the maintenance
requirements for the zero lot line wall, or deed restrictions must be submitted with the
preliminary plat which addresses the maintenance requirements for the zero setback
wall of the detached dwellings; and
(2) The easement shall be recorded with Washington County and submitted to the City
with the recorded final plat prior to the issuance of any building permits within the
development.
2. The approval authority requires the following conditions to be satisfied:
a. Deed restrictions shall be recorded with Washington County which ensure that:
(1) The 10-foot separation between the residential structures shall remain in perpetuity;
and
(2) The 10-foot separation between the residential structures shall be maintained free from
any obstructions other than:
(a) The eaves of the structure;
(b) A chimney which may encroach into the setback area by not more than two feet;
(c) A swimming pool;
(d) Normal landscaping; or
(e) A garden wall or fence equipped with a gate for emergency access and
maintenance purposes.
b. Easements shall be granted where any portion of the structure or architectural feature
projects over a property line; and
c. The maximum lot coverage for zero lot line shall not exceed the maximum lot coverage for
the base zone.
C. Application submission requirements. All applications shall be made on forms provided by the
Director in accordance with Chapter 18:350, Planned Developments, Chapter 18.430,
Subdivisions,or Chapter 18.420, Partitions, and shall be accompanied by:
1. Copies of the plat plan indicating building and easement location and dimensions, and
necessary data or narrative which explains how the development conforms to the standards;
2. A list of names and addresses of all property owners of record immediately abutting the site;
3. All other requirements of Chapters 18.350, 18.430 and 18.420 shall apply.
18.730.040 Additional Setback Requirements
Proposed 18.730 Development Code changes to implement the TSP page 3
•
A. Additional setback from sppecifed-roadways. To ensure improved light, air, and sight distance and
centerline or general extension of the street right of way: •
. . a •
centerline of the street as contained in Table 18.730.1.
2. Collector Streets. The required setback distance for buildings on the following collector streets
of the street as contained in Table 18.730.1.
TABLE 15.730.1 •
. . • . •
Street Names Requirement
Arterial Streets:
SW Pacific Highway (within City Limits) 50 feet
SW Hall Boulevard 15 feet
SW Scholls Ferry Road (except between its
intersections with Old Scholls Ferry Road) 50 feet
- • S
Upper Boones Ferry) 15 feet
SW Upper Boones Ferry Road 45 feet
•
Collector Streets:
SW Ash Avenue 30 feet
SW Atlanta Haines (east of 68th Avenue) 30 feet
SW Atlanta(west of 68th Avenue) 30 feet
SW Beef Bend Road 30 feet
SW Bonita Road 30 feet
SW Bull Mountain Road 30 feet
SW Burnham Street 30 feet
SW Cascade Boulevard 30 feet
SW Commercial Street 30 feet
SW Durham Road (between Pacific Highway and
Hall Boulevard) 30 feet
• SW Franklin Street 30 feet
SW Gaarde Street 30 feet
•
SW Grant Avenue 30 feet
SW Greenburg Road 30 feet
SW Hunziker Road 30 feet
SW Main Street 30 feet
SW McDonald Street 30 feet
SW Murdock Street 30 feet
SW North Dakota Avenue 30 feet
SW Oak(west of Hall Boulevard) 30 feet
Proposed 18.730 Development Code changes to implement the TSP page 4
• •
SW Pfaffle Street 30 feet
SW Sa#lei-Street(10 ft pavement between 100th/flail) 30 feet
Old Scholls Ferry Road) 30 feet
TABLE 18.730.1 (CON'T)
. 11 • . • . . e . . • � ��
Street Names Requirement
SW Summerfield Drive 30 feet .
SW Tiedeman Avenue 30 feet
SW Tigard Street 30 feet
SW Walnut Street 30 feet •
SW 68th Avenue 30 feet
SW 68th Avenue(south of Pacific Highway) 30 feet
SW 70th Avenue(south of Pacific Highway) 30 feet
SW 72nd Avenue 30 feet
SW 97th Avenue 30 feet
SW 98th Avenue 30 feet
SW 110th Avenue 30 feet
SW 121st Avenue 30 feet
Planned, SW Dartmouth to Pfaffle connection 30 feet
Planned, SW Hampton to 69th(westerly loop road) 30 feet
3. The minimum yard requirement shall be increased in the event a yard abuts a street having a right-
of-way width less than required by its functional classification on the City's transportation plan map
and, in such case,the setback shall be not less than the setback required by the zone plus one-half of the
projected road width as shown on the transportation map.
1. The minimum distance from the wall of any structure to the centerline of an abutting street,
however, shall not be less than 25 feet plus the yard required by the zone. This provision shall
•
B. Distance between multi-family residential structure and other structures on site.
1. To provide privacy, light, air, and access to the multiple and attached residential dwellings
within a development,the following separations shall apply:
a. Buildings with windowed walls facing buildings with windowed walls shall have a 25-foot
separation;
b. Buildings with windowed walls facing buildings with a blank wall shall have a 15-foot
separation;
c. Buildings with opposing blank walls shall have a 10-foot separation;
d. Building separation shall also apply to buildings having projections such as balconies, bay
windows and room projections;and
Proposed 18.730 Development Code changes to implement the TSP page 5
•
•
e. Buildings with courtyards to maintain separation of opposing walls as listed in Subsections
1-3 above for walls in separate buildings.
2. Where buildings exceed a horizontal dimension of 60 feet or exceed 30 feet in height, the
minimum wall separation shall be one foot for each 15 feet of building length over 50 feet and
two feet for each 10 feet of building height over 30 feet.
3. Driveways, parking lots, and common or public walkways shall maintain the following
separation for dwelling units within eight feet of the ground level:
a. Driveways and parking lots shall be separated from windowed walls by at least eight feet;
walkways running parallel to the face of the structures shall be separated by at least five
feet; and
b. Driveways and parking lots shall be separated from living room windows by at least 10
feet; walkways running parallel to the face of the structure shall be separated by at least
seven feet.
C. When no yard setback is required. In zoning districts where a side yard or a rear yard setback is
not required, a structure which is not to be built on the property line shall be set back from the
property line by a distance in accordance with the Uniform Building Code requirements.
18.730.050 Miscellaneous Requirements and Exceptions
A. When abutting properties have non-conforming front setbacks. If there are dwellings on both
abutting lots with front yard depths less than the required depth for the zone, the depth of the front
yard for the intervening lot need not exceed the average depth of the front yards of the abutting
lots. .
B. . When one abutting property has a non-conforming front setback. If there is a dwelling on one
abutting lot with a front yard of less depth than the required depth for the zone, the front yard for
the lot need not exceed a depth one-half way between the depth of the abutting lot and the required
front yard depth.
C. Storage in front yard. Boats,trailers, campers, camper bodies, house trailers, recreation vehicles or
commercial vehicles in excess of 3/4 ton capacity may be stored in a required front yard in a
residential zone subject to the following:
1. No such unit shall be parked in a visual clearance area of a corner lot or in the visual clearance
area of a driveway which would obstruct vision from an adjacent driveway or street;
2. No such unit shall be used for dwelling purposes except that one camper, house trailer or
recreational vehicle may be used for sleeping purposes only by friends, relatives or visitors on
land entirely owned by or leased to the host person for a period not to exceed 14 days in one
calendar year, provided that such unit shall not be connected to any utility, other than
temporary electricity hookups and provided that the host person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shall have current state license plates or registration and
must be kept in mobile condition.
Proposed 18.730 Development Code changes to implement the TSP page 6
•
• •
D. Projections into required yards.
1. Cornices, eaves, belt courses, sills, canopies or similar architectural features may extend or
project into a required yard not more than 36 inches provided the width of such yard is not
reduced to less than three feet;
2. Fireplace chimneys may project into a required front, side or rear yard not more than three feet
provided the width or such yard is not reduced to less than three feet;
3. Open porches, decks or balconies not more than 36 inches in height and not covered by a roof
or canopy, may extend or project into a required rear or side yard provided such natural yard
area is not reduced to less than three feet and the deck is screened from abutting properties.
Porches may extend into a required front yard not more than 36 inches;
4. Unroofed landings and stairs may project into required front or rear yards only.
E. Lot area for flag lots.
1. The lot area for a flag lot shall comply with the lot area requirements of the applicable zoning
district;
2. The lot area shall be provided entirely within the building site area exclusive of any accessway
(see figure following).
< AREA NOT INCLUDED
• IN LOT AREA
•
LO ARE
F. Front yard determination. The owner or developer of a flag lot may determine the location of the
front yard, provided no side yard setback area is less than 10 feet and provided the requirements
of Section 18.730.010C, Building Heights and Flag Lots, are satisfied.■
Proposed 18.730 Development Code changes to implement the TSP page 7
• ,•
Attachment 4
Chapter 18.810
STREET AND UTILITY IMPROVEMENT STANDARDS
Sections: -
18.810.010 Purpose
18.810.020 General Provisions
18.810.030 Streets
18.810.040 Blocks
18.810.050 Easements
18.810.060 Lots
18.810.070 Sidewalks
18.810.080 Public Use Areas
18.810.090 Sanitary Sewers
18.810.100 Storm Drainage
18.810.110 Bikeways and Pedestrian Pathways
18.810.120 Utilities
18.810.130 Cash or Bond Required
18.810.140 Monuments
18.810.150 Installation Prerequisite
18.810.160 Installation Conformation
18.810.170 Plan Check
18.810.180 Notice to City
18.810.190 City Inspection
18.810.200 Engineer's Certification
18.810.210 Completion Requirements
18.810.010 Purpose
A. Purpose. The purpose of this chapter is to provide construction standards for the implementation of
public and private facilities and utilities such as streets, sewers, and drainage.
18.810.020 General Provisions
A. When standards apply. Unless otherwise provided, construction, reconstruction or repair of streets,
sidewalks, curbs and other public improvements shall occur in accordance with the standards of this
title. No development may occur and no land use application may be approved unless the public
facilities related to development comply with the public facility requirements established in this
section and adequate public facilities are available. Applicants may be required to dedicate land
and build required public improvements only when the required exaction is directly related to and
roughly proportional to the impact of the development.
B. Standard specifications. The City Engineer shall establish standard specifications consistent with
the application of engineering principles.
C. Section 7.40 applies. The provision of Section 7.40 of the Tigard Municipal Code shall apply to
this chapter.
D. Adjustments. Adjustments to the provisions in this chapter related to street improvements may be
granted by means of a Type II procedure, as governed by Section 18.390.040, using approval
criteria in Section 18.370.030 C9. (Ord. 99-22)
E. Except as provided in Section 18.810.030S, as used in this chapter, the term "streets" shall mean
Proposed 18.810 Development Code changes to implement the TSP page 1
• •
"public streets" unless an adjustment under Section 18.810.020.D is allowed. (Ord. 99-22)
18.810.030 Streets
A. Improvements.
1.. No development shall occur unless the development has frontage or approved access to a public
street.
2. No development shall occur unless streets within the development meet the standards of this
chapter.
3. No development shall occur unless the streets adjacent to the development meet the standards
of this chapter, provided, however, that a development may be approved if the adjacent street
does not meet the standards but half-street improvements meeting the standards of this title are
constructed adjacent to the development.
4 Any new street or additional street width planned as a portion of an existing street shall meet
the standards of this chapter;
5. If the City could and would otherwise require the applicant to provide street improvements, the
City Engineer may accept a future improvements guarantee in lieu of street improvements if
one or more of the following conditions exist:
a. A partial improvement is not feasible due to the 'inability to achieve proper design
standards;
•
b. A partial improvement may create a potential safety hazard to motorists or pedestrians;
c. Due to the nature of existing development on adjacent properties it is unlikely that street
improvements would be extended in the foreseeable future and the improvement associated
with the project under review does not, by itself, provide a significant improvement to
street safety or capacity;
d. The improvement would be in conflict with an adopted capital improvement plan;
e. The improvement is associated with an approved land partition on property zoned
residential and the proposed land partition does not create any new streets;or
f. Additional planning work is required to define the appropriate design standards for the
street and the application is for a project which would contribute only a minor portion of
the anticipated future traffic on the street.
6. The standards of this chapter include the standard specifications adopted by the City Engineer
pursuant to Section 18.810.020.B.
7. The approval authority may approve adjustments to the standards of this chapter if compliance
with the standards would result in an adverse impact on natural features such as wetlands, steep
slopes, or existing mature trees. The approval authority may also approve adjustments to the
standards of this chapter if compliance with the standards would have a substantial adverse
impact on existing development or would preclude development on the property where the
development is proposed. In approving an adjustment to the standards, the approval authority
Proposed 18.810 Development Code changes to implement the TSP page 2
• •
shall balance the benefit of the adjustment with the impact on the public interest represented by
the standards. In evaluating the impact on the public interest, the approval authority shall
consider the criteria listed in Section 18.810.030 E.1. An adjustment to the standards may not
be granted if the adjustment would risk public safety.
B. Creation of rights-of-way for streets and related purposes. Rights-of-way shall be created through
the approval of a final subdivision plat or major partition; however, the Council may approve the
creation of a street by acceptance of a deed, provided that such street is deemed essential by the
Council for the purpose of general traffic circulation:
1. The Council may approve the creation of a street by deed of dedication without full compliance
with the regulations applicable to subdivisions or major partitions if any one or more of the
following conditions are found by the Council to be present:
a. Establishment of a street is initiated by the Council and is found to be essential for the
purpose of general traffic circulation, and partitioning or subdivision of land has an
incidental effect rather than being the primary objective in establishing the road or street for
public use; or
b. The tract in which the road or street is to be dedicated is an isolated ownership of one acre
or less and such dedication is recommended by the Commission to the Council based on a
finding that the proposal is not an attempt to evade the provisions of this title governing the
control of subdivisions or major partitions.
2. With each application for approval of a road or street right-of-way not in full compliance with
the regulations applicable to the standards,the proposed dedication shall be made a condition of
subdivision and major partition approval:
a. The applicant shall submit such additional information and justification as may be
necessary to enable the Commission in its review to determine whether or not a
recommendation for approval by the Council shall be made;
b. The recommendation, if any, shall be based upon a finding that the proposal is not in
conflict with the purpose of this title;
c. The Commission in submitting the proposal with a recommendation to the Council may
attach conditions which are necessary to preserve the standards of this title; and
3. All deeds of dedication shall be in a form prescribed by the City and shall name "the public,"as
grantee.
C. Creation of access easements. The approval authority may approve an access easement established
by deed without full compliance with this title provided such an easement is the only reasonable
method by which a lot large enough to develop can be created:
1. Access easements shall be provided and maintained in accordance with the Uniform Fire Code
Section 10.207;
2. Access shall be in accordance with Sections 18.705.030.H and 18.705.030I.
D. Street location, width and grade. Except as noted below, the location,width and grade of all streets
shall conform to an approved street plan and shall be considered in their relation to existing and
Proposed 18.810 Development Code changes to implement the TSP page 3
• •
planned streets, to topographic conditions, to public convenience and safety, and in their
appropriate relation to the proposed use of the land to be served by such streets:
1. Street grades shall be approved by the City Engineer in accordance with Subsection M below;
and
2. Where the location of a street is not shown in an approved street plan, the arrangement of
streets in a development shall either:
a. Provide for the continuation or appropriate projection of existing streets in the surrounding
areas, or
b. Conform to a plan adopted by the Commission, if it is impractical to conform to existing
street patterns because of particular topographical or other existing conditions of the land.
Such a plan shall be based on the type of land use to be served, the volume of traffic, the
capacity of adjoining streets and the need for public convenience and safety.
E. Minimum rights-of-way and street widths. Unless otherwise indicated on an approved street plan,
or as needed to continue an existing improved street, street right-of-way and roadway widths shall
not be less than the minimum width described below. Where a range is indicated, the width shall
be determined by the decision-making authority based upon anticipated average daily traffic (ADT)
on the new street segment. (The City Council may adopt by resolution, design standards for street
construction and other public improvements. The design standards will provide guidance for
determining improvement requirements within the specified ranges.) These are presented in Table
18.810.1.
1. The decision-making body shall make its decision about desired right-of-way width and
pavement width of the various street types within the subdivision or development after
consideration of the following:
a. The type of road as set forth in the Comprehensive Plan Transportation Chapter -
Functional Street Classification;
b. Anticipated traffic generation;
c. On-street parking needs;
d. Sidewalk and bikeway requirements;
e. Requirements for placement of utilities;
f. Street lighting;
g. Drainage and slope impacts;
h. Street tree location;
i. Planting and landscape areas;
j. Safety and comfort for motorists,bicyclists, and pedestrians;
k. Access needs for emergency vehicles.
Proposed 18.810 Development Code changes to implement the TSP page 4
• •
*0;14=0404
411L 1 • 1 - . _
type-OfStreet
Arterial 60;794,4 12 fkthé 24
Major-C-ollec-teF 24
141nor-C-ellestof 2 3
50' 344
a. Through street With:
4ess:Than 1500 ADT 50
:Less Than 500 ADT 461
Thess Than 200 ADT 422
h. Cu! de sac dead end streets
ELess Than 500 ADT 44
Less Than 200 ADT 42-1
-14
2-,; .-2 •: ••: •.•
dwelling its)
50 radnIs l2 radius
47' radius 40 radius
Alley: Residential
20-
Proposed 18.810 Development Code changes to implement the TSP page 5
•
Table 18.810.1
Minimum Widths for Street Characteristics
a) *, 3 I' "42
Type of Street �_ ' 3 c � . _ �• .1 . % 14
•a a 3 a ` . . .03 . . . .
Arterial 64- _28' Varies 2-7 (Refer 12 NIA 6L(_N.ew Streets.) 8'(Rees&Ind,._Z.on.es) 5' . 2'c2
to TSP)
5'..-.6'.(Existng_Streets) 1.01_(_Eomm,_, ones).
Collector 58'-96' Varies 2 -5 (Refer 11' WA 6' (New Streets) 6' (Res..& Ind. Zones) 5' 1241,
to TSP)
5'-6' (Existing Streets) 8' (Comm. Zones) .
Neighborhood Romte 50=58' 28:7_36' . 2 1 ' 8 5-6' S'-6'(2) 5' N/A
Local
'milks_teal/C4rnmm�rcial 5Q 36 . 2 N/A 5=6'(2) 5' N/A
Local:_Residentiiai N/A
• Under 1500 ADT(3) ,L4' 321 2 8' (both sides) NA 5'-6'(2)
• Under 500 ADT"1 50' 2$ 2 N/A
Under 200 ADT`33 46' 24 2 8 (one side)
• N/A
_ .(No Parking
CuI-d_e:_sac buttes Jn 50' 42' radius NA N/A N/A
II
Industrial and radius -
_C_ommer._ciaLz e.3.
CAL-de a ulps in � 40' radius N/A N/A N/A N/A N/A
Resdential..zon.es ' radius •
Alley: Re.Si_d.enti.a.l • 1.6 16' N/A N/A N/A N/A N/A
Alleyy....I3u.si.ne.ss 2.0' ZA'. N/A NIA N/A N/A N/A
' Medians required for 5 and 7 lane roadways. They are optional for 3 lane roadways.
3 Sidewalk widths for these streets shall be 5 ft with landscape strip; 6 ft if against curb (if permitted in accordance with 18.810.070.C).
"Skinny Street" roadway widths are permitted only if the cross section criteria are met. Refer to corresponding cross sections (Figures
18.810.3, 18.810.4 and 18.810.5) for details and conditions.
Proposed 18.810 Development Code changes to implement the TSP page 6
• •
Figure_18,810.1_
Arterials Sample Cross Section_s
— ----.,
...---.%■;- ,.., ::=4.,,,,,,p5-......_
.5'8-10 55' 6'Bfle 12' 12' ,6'Bike 5.5' 8-10'.5.
I i I I I
R/W 64-68'
I
2 Lane 641-68'RIW
--.
--,:„ ,, „
--
-., •> ..-•... ,
-...•, ,-,-. .•,- - •:.
..,...-- ,L: „....,
- D------
C ,
,:„..:_,--- -----vt:. -,•-•”
;V,.. t .. ;:
•''-'i■
41111■„ -
'I 1 . ._ IL 121,11.-r''.... '
,,.. ,,....... ,'.
ll ,I•i.:..., 1,-.... .s..,,,,:.,.....A■mmi..•...ft-411•1111
5'
12'MediaN 5'
8-10', 5 5',6'Fike 12' i Turn Lane . 12' +6kef5.5'43-10:,H
HI , , —i-
RAiv 78-80'
I. I
3 Lane 768O'PA'/
-i• - ...,-. „.•:-, .:-.
• •,.--:::-.-- _., ,,.,•,,,,------
.0, _....
AIM, 4-2--<)7'
t.4 .r.! 2.0.- .-. ■ ..,,za-ix.
[1. ',/:'2 Z.s.,`;.:■ ' '...,:-:.#27 .--,...,-i .---t-...- --iimmon,
12'Median/
.5'8-10'. 6' 613ke 12' . i 12' I Turn Lone i 12' 1 12' i 6'Bike
,-.- f i-
R/W 100I-104'
I I
5 Lane 1001-104'RAN
..„:::24,t:',.,1`.f.. ---,-- ‘-I "'".•---:-4,.. .;E' ,•:,:-g-r-Z,..
•r::. ‹ •
.........._
12'MediaN .5'
.5' 8-10' 5.5' •6'Bike 12' , 12' 12' , Turn I I Lane 12' 12' 12' •Ilke 6'I 5,5' 8-10'
I I I I I I 1
R/W 124-128'
I--
7 Lane 124=128'R/W
----------------- ----------
Proposed 18.810 Development Code changes to implement the TSP page 7
• •
•
Figure 18.810.2
Collector Sample Cross Sections
„--,
.....
r 44:
.5' 6-8' 5.5' .6ke 1V 11' 6'Bke 5 5' 6-8'
I-i--
R/W 58'-62'
2 Lane 58'-62'R/W
*5'
41111111. '
iv,
12'Median/
'5.6-8' 5 5' 6'Bke 11' 4 Turn Lane 11' .6'Bike.5.5' 6-8'
R/W 7CY-74'
3 Lane 701-74'R/W
•
6,40 .3s id
MEI*
.5' 12'Median/
6 '.78 5..5' ,.,6'Bike 11' 11' Turn Lane 11 11' 1.6'Bikei. 5.5' 1_<?n,"_
R/W - - -- - ;
5 Lane 92'-96'R/W
•
•
•
Proposed 18.810 Development Code changes to implement the TSP page 8
• •
. .
gure 18.810.3
Neighborhood Routes
Sample Cross Sections
-N:
aim
I›wjalarx
[1.11.1-1e;:&,, 1 4■111
.5'
28' , 5.5'. 5' .5' . 55„5'ia____3 ..±_5' f'
R/W 50' kyy 54'
1
No Parking on One Side With Parking on Both Sides
,----
..-..,,--•-,5..: . .....n -=-
,-::.
-, /.1 v
Alki ••: ---Nj
Tr . ./..1,. . 0144 I 1
/1.11111.1111t.''t;1,;
36'
I.* 5LI 5.5 1 6 Bike:
R/W 58'
With Bike Lanes/No Parking
Figure 18.810.4
Local Residential_Streets-<1.2500ypd
A. Standard(sample) B. Skinny Street Option(criteria)
.,-;,----. ,>-----TA-.
',S L''',.-• --'-
4,,, ,:-..---Lq 1 •(.>'---- :‘
— :-.... . II 415IL
—
r ,
,--1 ,■ : 5 5. l'Perting Trend Lane Parkine.g 5 5' : i!
•' ,*----
• .5, 5. Plantlna (0.A.9) Pt.;;—aetane: 5. 5.
On-street Parking skkwak 5'F ■ 20'
r_ .: s, — --
: 544reallt
Pavement
<1500 vpd *
Ripen-al-way' :
If parking on both sides, .
block length not to exceed 600 feet
7 Iv 19 1'1
Criteria: ,-rrqrrie-- rlo
• Quetiag-P.lan must be submitted and approved.
• Not appropriate for streets serving more than 1,000 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
development only. A
• CO/Siddr-- AL:re.N d kfoi kitn-, ./61.40/Y/114911
Figure_18,310.5
Local Residential Streets<500 vpd
Proposed 18.810 Development Code changes to implement the TSP page 9
• . . ,
• .
Iiik .
I
A. Standard(sample) B. Skinny Street Option(criteria)
''A.,,,,, Aliki .
ftrlrrlE !,'
` t. 5' 5.5'; 0 28' i 5.5': 5' 15 ® IiIl !"' — 4
i RM/50' T ,s-,T
!_5' i PA.k g Trawl faro 5.5'
•
' '=�` ""s '46 .5
Residential Local Street/Cul-de-sac su..ait 5l"v u P 74 rd:
One Side On-street Parking . "'a.^'.s
<500 vpd Right-of,a,:
Criteria:/
• Qucu ng Plan must be submitted and approved.
• Not appropriate for streets serving more than 500 vpd.
• No parking permitted within 30 feet of an intersection.
• Appropriate adjacent to single family detached
• development only.
• Must provide a minimum of(1)off-street parking space for
every 20 feet of restricted street frontage.
Figure 18_810.6 .
Local Residential_Street:_<200.vpd
•
A. . Standard(sample) B. Skinny Street Option(criteria)
J V--'1- ti it
L
Ii
JI 1. ' _ it
. li
t
.5' 5' ' NY ISrend� 5.5' i
.,•:
::.._ 5 . 5.5 24' 5.5 5' 'i - : 5.6F , €.s_:...•
Cul-de-sac/Residential Local Street .0°=°.=-7
<200 vpd .
. (No parking)
.\/F. Future street plan and extension of streets.
•
A' re-4 s
1. A future street plan shall:
a. Be filed by the applicant in conjunction with an application for a subdivision or partition.
The plan shall show the pattern of existing and proposed future streets from the boundaries of
the proposed land division and shall include other parcels within 530 feet surrounding and
adjacent to the proposed land division. At the applicant's request, the City shall may prepare
a future streets proposal._ Costs of the_Cit`'_preparing_a future_streets_proposal shall be
•
Proposed 18.810 Development Code changes to implement the TSP page 10
• •
reimbursed for the_time_involved. A street proposal may be modified when subsequent
subdivision proposals are submitted.
b. Identify existing or proposed bus • - . louts or other transit facilities, bicycle routes and
pedestrian facilities on or wit t feet of the 'te. 664917, ,), ,L4 ,Soro
2. Where necessary to give access or perms a satisfactory future division off adjoining land, streets
shall be extended to the boundary lines of the tract to be developed, and
a. These extended streets or street stubs to adjoining properties are not considered to be culs-de-
sac since they are intended to continue as through streets at such time as the adjoining
property is developed.
b. A barricade shall be constructed at the end of the street by the property owners which shall
not be removed until authorized by the City Engineer, the cost of which shall be included in
the street construction cost.
c. Temporary hammerhead turnouts or temporary cul-de-sac bulbs shall be constructed for stub
street in excess of 150 feet in length.
(1._.__Sti_eet_spac ng._a d acc:ess.management_Refer to_1t3.705.030..1:1..
GH. Street alignment and connections.
_1, Full street connections with spacing of no_mere than 50 feet bet}been.connections_is__required
except_where_prevented by barriers such as topography___railroads, _freeways__p►e existing
devel_cments_lease_prov_isions easements? covenants or other restrictions exisfin _prio_to May
1,_1995 which preclude_street connections. A full street connection may also be exempted due to
a regulatedwater-featmre if regulations w not permit conStructi_Q_n.
-1-. _ - • - • « " •• . - - . : . - '.
street:
23. All local ar, neighborhood routes and collector streets which abut a development site
shall be extended within the site to provide through circulation when not precluded by
environmental or topographical constraints, existing development patterns or strict adherence to
other standards in this code. A street connection or extension is considered precluded when it is
not possible to redesign or reconfigure the street pattern to provide required extensions. Land is
considered topographically constrained if the slope is greater than 15% for a distance of 250 feet
or more. In the case of environmental or topographical constraints, the mere presence of a
constraint is not sufficient to show that-a street connection is not possible. The applicant must
show why the constraint precludes some reasonable street connection.
34. Proposed street or street extensions shall be located to provide direct access to existing or planned
transit stops, commercial services, and other neighborhood facilities, such as schools, shopping
areas and parks.
•
4-S. All developments should provide an internal network of connecting streets that provide short,
direct travel routes and minimize travel distances within the development.
Proposed 18.810 Development Code changes to implement the TSP page 11
•
141. Intersection angles. Streets shall be laid out so as to intersect at an angle as near to a right angle as
practicable, except where topography requires a lesser angle, but in no case shall the angle be less
than 75°unless there is special intersection design, and:
1. Streets shall have at least 25 feet of tangent adjacent to the right-of-way intersection unless
topography requires a lesser distance;
2. Intersections which are not at right angles shall have a minimum corner radius of 20 feet along
the right-of-way lines of the acute angle; and
3. Right-of-way lines at intersection with arterial streets shall have a corner radius of not less than
20 feet.
1J. Existing rights-of-way. Whenever existing rights-of-way adjacent to or within a tract are of less than
standard width, additional rights-of-way shall be provided at the time of subdivision or development.
JK. Partial Street Improvements. Partial street improvements resulting in a pavement width of less than
20 feet; while generally not acceptable, may be approved where essential to reasonable development
when in conformity with the other requirements of these regulations, and when it will be practical to
require the improvement of the other half when the adjoining property developed.
KL.Culs-de-sacs. A cul-de-sac shall be no more than 200 feet long shall not provide access to greater
than 20 dwelling units, and shall only be used when environmental or topographical constraints,
existing development pattern, or strict adherence to other standards in this code preclude street
extension and through circulation:
1. All culs-de-sac shall terminate with a turnaround. Use of turnaround configurations other than
circular, shall be approved by the City Engineer; and
2. The length of the cul-de-sac shall be measured from the centerline intersection point_of the two
streets to the radius point of the_bulb.. :•. •- -• - ••• - •- - . •- . . •-
3. If a cul-de-sac is more than 300 feet long, a lighted direct pathway to an adjacent street may be
required to be provided and dedicated to the City.
bM. Street names. No street name shall be used which will duplicate or be confused with the names
of existing streets in Washington County, except for extensions of existing streets. Street names and
numbers shall conform to the established pattern in the surrounding area and as approved_by the City
Engineer...-
MN. Grades and curves.
_..._ -1-._-___Grades shall not exceed ten percent on arterials, 12% on collector streets, or 12% on any other
street (except that local or residential access streets may have segments with grades up to 15% for
distances of no greater than 250 feet), and:
—42. Centerline radii of curves shall be_as_-determined hy.the City Engineer..-: •. 1e
arterials, 500 feet on major collectors, 350 feet on minor collectors, or 100 feet on other streets;
and
. - . b • - - . . - -
Proposed 18.810 Development Code changes to implement the TSP page 12
• •
percent or less. Landings are that portion of the street within 20 feet of the edge of the
•
NO_. Curbs, curb cuts, ramps, and driveway approaches. Concrete curbs, curb cuts, wheelchair,
bicycle ramps and driveway approaches shall be constructed in accordance with standards specified in
this chapter and Section 15.04.080; and:
1. Concrete curbs and driveway approaches are required; except
2. Where no sidewalk is planned, an asphalt approach may be constructed with City Engineer
approval; and
3. Asphalt and concrete driveway approaches to the property line shall be built to City configuration
standards. .
OP.Streets adjacent to railroad right-of-way. Wherever the proposed development contains or is adjacent
to a railroad right-of-way, provision shall be made for a street approximately parallel to and on each
side of such right-of-way at a distance suitable for the appropriate use of the land. The distance shall
be determined with due consideration at cross streets or the minimum distance required for approach
grades and to provide sufficient depth to allow screen planting along the railroad right-of-way in
nonindustrial areas.
PQ.Access to arterials and major collectors. Where a development abuts or is traversed by an existing or
proposed arterial or major collector street; the development design shall provide adequate protection
for residential properties and shall separate residential access and through traffic, or if separation is
not feasible, the design shall minimize the traffic conflicts. The design shall include any of the
following:
1. A parallel access street along the arterial or major collector;
2. Lots of suitable depth abutting the arterial or major collector to provide adequate buffering with
frontage along another street;
3. Screen planting.at the rear or side property line to be contained in a nonaccess reservation along
the arterial or collector; or
4. Other treatment suitable to meet the objectives of this subsection;
5. If a lot has access to two streets with different classifications, primary access should be from the
lower classification street.
QR. Alleys,public or private.
I. Alleys shall be no less than 20 feet in width.In commercial and industrial districts, alleys shall be
provided unless other permanent provisions for access to off-street parking and loading facilities
are made.
2. While alley intersections and sharp changes in alignment shall be avoided, the corners of
necessary alley intersections shall have a radius of not less than 12 feet.
14S.Survey monuments. Upon completion of a street improvement and prior to acceptance by the City, it
Proposed 18.810 Development Code changes to implement the TSP page 13
• •
shall be the responsibility of the developer's registered professional land surveyor to provide
certification to the City that all boundary and interior monuments shall be reestablished and protected.
ST.Private Streets.
1. Design standards for private streets shall be established by the City Engineer; and
2. The City shall require legal assurances for the continued maintenance of private streets, such as a
recorded maintenance agreement.
3. Private streets serving more than six dwelling units are permitted only within planned
developments, mobile home parks, and multi-family residential developments.
TU.Railroad crossings. Where an adjacent development results in a need to install or improve a railroad I
crossing, the cost for such improvements may be a condition of development approval, or another
equitable means of cost distribution shall be determined by the public works Director and approved
by the Commission.
UV.. Street signs. The City shall install all street signs, relative to traffic control and street names, as I
specified by the City Engineer for any development. The cost of signs shall be the responsibility of
the developer.
VW. Mailboxes. Joint mailbox facilities shall be provided in all residential developments, with each I
joint mailbox serving at least two dwelling units.
1. Joint mailbox structures shall be placed adjacent to roadway curbs;
2. Proposed locations of joint mailboxes shall be designated on a copy of the preliminary plat or
development plan, and shall be approved by the City Engineer/US Post Office prior to final plan
approval; and
3. Plans for the joint mailbox structures to be used shall be submitted for approval by the City
Engineer/US Post Office prior to final approval.
WX. Traffic signals. The location of traffic signals shall be noted on approved street plans. Where a I
proposed street intersection will result in an immediate need for a traffic signal, a signal meeting
approved specifications shall be installed. The cost shall be included as a condition of development.
XY. Street light standards. Street lights shall be installed in accordance with regulations adopted by I
the City's direction.
V-Z.Street name signs. Street name signs shall be installed at all street intersections. Stop signs and other
signs may be required.
ZA_A. Street cross-sections. The final lift of asphalt concrete pavement shall be placed on all new I
constructed public roadways prior to final City acceptance of the roadway and within one year of the
conditional acceptance of the roadway unless otherwise approved by the City Engineer. The final lift
shall also be placed no later than when 90% of the structures in the new development are completed
or three years from the commencement of initial construction of the development, whichever is less.
1. Sub-base and leveling course shall be of select crushed rock;
Proposed 18.810 Development Code changes to implement the TSP page 14
• •
. 2. Surface material shall be of Class C or B asphaltic concrete;
3. The final lift shall be placed on all new construction roadways prior to City final acceptance of
the roadway; however, not before 90% of the structures in the new development are completed
unless three years have elapsed since initiation of construction in the development;
4. The final lift shall be Class C asphaltic concrete as defined by A.P.W.A. standard specifications;
and
•
5. No lift shall be less than 1-1/2 inches in thickness. (Ord. 99-22)
AB_ Traffic Calming. When, in the opinion of the City Engineer, the proposed development will
create a negative traffic condition on existing neighborhood streets. such as excessive speeding, the
developer may be required to provide traffic calming measures. These measures may be required
within the development and/or offsite as deemed appropriate. As an alternative, the developer may
be required to deposit funds with the Cit _to help pay for traffic calming_ measures that become
necessary once the development is occupied and the City Engineer determines that the additional
traffic from the development has triggered_the-n_e_ed for traffic calming measures. The City_Engineer
will determine the amount of funds required. and will collect said funds from the developer prior to the
issU_ance of a ce—rtificate_of occu_ ancy, or in the case of subdivision,._prior to the epproveLgf the final
plat. The funds will be held by the_City for_a period of five_5)_years from the_date of issuance of
eertificete oLoc ttpancy,_or in the_ ase of aaubdivision_,_the date of final..plat approval __Any funds not
u_eed lakthe CitY.within the five-year time_period will be refunded to._the developer,
• AC. _A traffic study shall be required__for_all__new_developments under any_of the__following
circumstances:
1_:__. vhen_the _generate a..__U%or._o„mater_i»crease..=_i.n_e st n_...tt_affc...to_.It..h..c.U...11ision..._intersect obis
identified_by_Washii gtonCounty.
2_Tripgererations from_developmentt onto=_the._C ty_street_atrhe=point ofaccess and..the existing
adtADT fall within the.following ranges:
. Existing ADT_to be added development •
9—_3_.,000 ypd. ?_000.ypd.
1431OI_6,000=y0 14000v_•pd.
>6,000 ypd 51)_0 vpd<Lrnore
any of thefollowing_issnes beeeme_evident-to_te City engineer •
a .____High tratf c Y_olunics on the-ad3acent roadway that_ nay affect movementinto or out of the
site
b, Lackaf existing left-turn lanes onto the adjacent roadway at the proposed acce.ssdrive(s)
c. _Inadequate horizontal or vertical_sight distance at access points
d. _The_proximi _of the__proposed_access to.other existing drives_or_intersections_is_apotential
hazard
e. The rp Oposal re_ck_mires a conditional use permit-or involves a drive—t through o_peration
The.proposed development may result_in excesswe traffic volum.es on adjacent local streets,
4.—When the_site is within 500 feet awl QDQT facility.
•
18.810.040 Blocks
•
A. Block Design. The length, width and shape of blocks shall be designed with due regard to providing
adequate building sites for the use contemplated, consideration of needs for convenient access,
Proposed 18.810 Development Code changes to implement the TSP page 15
•
circulation, control and safety of street traffic and recognition of limitations and opportunities of
topography.
B. Sizes.
1. The perimeter of blocks formed by streets shall not exceed 2,.1201400 feet measured along the
center]ine of the streets right of way line except:
a. Where street location is precluded by natural topography, wetlands or other bodies of water,
or pre-existing development; or
b. For blocks adjacent to arterial streets, limited access highways,major collectors or railroads.
c. For non-residential blocks in which internal public circulation provides equivalent access.
2. Bicycle and pedestrian connections on public easements or right-of-ways shall be provided when
full street connection is not—possi-bleexempted hy_ X3.1 above. Spacing between connections shall
be no more than 330 feet, except where precluded by environmental or topographical constraints,
existing development patterns,or strict adherence to other standards in the code.
18.810.050 Easements
A. Easements. Easements for sewers, drainage, water mains, electric lines or other public utilities shall
be either dedicated or provided for in the deed restrictions, and where a development traversed by a
watercourse, or drainageway,there shall be provided a storm water easement or drainage right-of-way
conforming substantially with the lines of the watercourse.
B. Utility easements. A property owner proposing a development shall make arrangements with the
City, the applicable district and each utility franchise for the provision and dedication of utility
easements necessary to provide full services to the development. The City's standard width for
public main line utility easements shall be 15 feet unless otherwise specified by the utility company,
applicable district, or City Engineer.
18.810.060 Lots
A. Size and shape. Lot size, width, shape and orientation shall be appropriate for the location of the
development and for the type of use contemplated, and:
1. No lot shall contain part of an existing or proposed public right-of-way within its dimensions;
2. The depth of all lots shall not exceed 2-1/2 times the average width, unless the parcel is less than
1-1/2 times the minimum lot size of the applicable zoning district;
3. Depth and width of properties zoned for commercial and industrial purposes shall be adequate to
provide for the off-street parking and service facilities required by the type of use proposed.
B. Lot frontage. Each lot shall abut upon a public or private street, other than an alley, for a width of at
least 25 feet unless the lot is created through a minor land partition in which case Subsection
18.162.050 (C) applies, or unless the lot is for an attached single-family dwelling unit, in which case
the lot frontage shall be at least 15 feet.
C. Through lots. Through lots shall be avoided except where they are essential to provide separation of
Proposed 18.810 Development Code changes to implement the TSP page 16
•
•
• •
residential development from major traffic arterials or to overcome specific disadvantages of
topography and orientation, and:
1. A planting buffer at least ten feet wide is required abutting the arterial rights-of-way; and
2. All through lots shall provide the required front yard setback on each street.
D. Lot side lines. The side lines of lots, as far as practicable, shall be at right angles to the street upon
which the lots front.
E. Large lots. In dividing tracts into large lots or parcels which at some future time are likely to be
redivided, the Commission may require that the lots be of such size and shape,and be so divided into
building sites, and contain such site restrictions as will provide for the extension and opening of
streets at intervals which will permit a subsequent division of any tract into lots or parcels of smaller
size. The land division shall be denied if the proposed large development lot does not provide for the
future division of the lots and future extension of public facilities.
18.810.070 Sidewalks
A_: —Sidewalks. All industrial streets and_prvate_streets shall have sidewalks meeting City standards
along at_least_.one side of the street. All other streets shall have sidewalks meeting City standards
along both sides of the street. A development may be approved if an adjoining street has sidewalks
on the side adjoining the development, even if no sidewalk exists on the other side of the street
Q.___Requirement of developers
=__As_part ofanv develQpment_proposal_or_change_ in use resulting_ in_ an addiaortal. MO
vehicle trips or more edgy, an_ap_llrcant shall be required to identify direct safe (1 2.5 x the straight fine
distance)pe_d_estrian routes within_1/2 mile of their site to all transit facilities and Neig_hborhood Activity
Centers (schoQls= parks Irbrar�es, etc. . ln-addition., the developer may be_re i ed_to_partieipate in the
removal of__any gaps in_the pedestrian system off-site if justified by the dev_elopntent_-
2_ Ifthere is an existing sidewalk,on the same side of the street as the development,_within 300
feet_of_a_dev elopment_site_iii_eithzr_direction, the_sidewalk shall_be_extended_from the_site to meet the
existing_-sidewalk. subject to roughproportionality (evep_if the sidewalk does_not serve a neighborhood
acti_y._itycenter
( 13C_ .Planter strip requirements. A planter strip separation of at least five feet between the curb and the
(J``\ , sidewalk shall be required in the design of. - - - streets • - •• • - - • -
adjacent t,. the curb, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; Of it would conflict with
the utilities, there are significant natural_ features (large trees, water features, _dc) that would be
destro_yed_if the sidewalk were located_as required, or where there are existing structures in close
p roximi_ty to the_s_treet 01..5 feet or_1_ess)-
CD. Sidewalks in central business district. In the central business district, sidewalks shall be 10 feet
in width, and:
1. All sidewalks shall provide a continuous unobstructed path; and
2. The width of curbside sidewalks shall be measured from the back of the curb.
DE.Maintenance. Maintenance of sidewalks, curbs, and planter strips is the continuing obligation of the
adjacent property owner.
Proposed 18.810 Development Code changes to implement the TSP page 17
EF.Application for permit and inspection. If the construction of a sidewalk is not included in a
performance bond of an approved subdivision or the performance bond has lapsed,then every person,
firm or corporation desiring to construct sidewalks as provided by this chapter, shall, before entering
upon the work or improvement, apply for a street opening permit to the Engineering department to so
build or construct:
1. An occupancy permit shall not be issued for a development until the provisions of this section are
satisfied.
2. The City Engineer may issue a permit and certificate allowing temporary noncompliance with the
provisions of this section to the owner, builder or contractor when, in his opinion, the
construction of the sidewalk is impractical for one or more of the following reasons:
a. Sidewalk grades have not and cannot be established for the property question within a
reasonable length of time;
b. Forthcoming installation of public utilities or street paving would be likely to cause severe
damage to the new sidewalk;
c. Street right-of-way is insufficient to accommodate a sidewalk on one or both sides of the
street; or
d. Topography or elevation of the sidewalk base area makes construction of a sidewalk
impractical or economically infeasible; and
3. The City Engineer shall inspect the construction of sidewalks for compliance with the provision
set forth in the standard specifications manual.
EC.Council initiation of construction. In the event one or more of the following situations are found by
the Council to exist, the Council may adopt a resolution to initiate construction of a sidewalk in
accordance with City ordinances:
1. A safety hazard exists for children walking to or from school and sidewalks are necessary to
eliminate the hazard;
2. A safety hazard exists for pedestrians walking to or from a public building, commercial area,
place of assembly or other general pedestrian traffic, and sidewalks are necessary to eliminate the
hazard;
3. 50% or more of the area in a given block has been improved by the construction of dwellings,
multiple dwellings, commercial buildings or public buildings and/or parks; and
4. A criteria which allowed noncompliance under Section E.1.b above no longer exists and a
sidewalk could be constructed in conformance with City standards. (Ord. 99-22)
18.810.080 Public Use Areas
A. Dedication requirements.
1. Where a proposed park, playground or other public use shown in a development plan adopted by
the City is located in whole or in part in a subdivision, the Commission may require the
Proposed 18.810 Development Code changes to implement the TSP page 18
• •
dedication or reservation of such area within the subdivision, provided that the reservation or
dedication is roughly proportional to the impact of the subdivision on the park system.
2. Where considered desirable by the Commission in accordance with adopted comprehensive plan
policies, and where a development plan of the City does not indicate proposed public use areas,
the Commission may require the dedication or reservation of areas within the subdivision or sites
of a character, extent and location suitable for the development of parks or other public use,
provided that the reservation or dedication is roughly proportional to the impact of the
subdivision on the park system.
B. Acquisition by public agency. If the developer is required to reserve land area for a park, playground,
or other public use, such land shall be acquired by the appropriate public agency within 18 months
following plat approval, at a price agreed upon prior to approval of the plat, or such reservation shall
be released to the subdivider. (Ord.99-22)
18.810.090 Sanitary Sewers
A. Sewers required. Sanitary sewers shall be installed to serve each new development and to connect
developments to existing mains in accordance with the provisions set forth in Design, and
Construction Standards for Sanitary and Surface Water Management (as adopted by the Unified
Sewerage Agency in 1996 .and including any future revisions or amendments) and the adopted
policies of the comprehensive plan.
B. Sewer plan approval. The City Engineer shall approve all sanitary sewer plans and proposed systems
prior to issuance of development permits involving sewer service.
C. Over-sizing. Proposed sewer systems shall include consideration of additional development within
the area as projected by the Comprehensive Plan.
D. Permits denied. Development permits may be restricted by the Commission or Hearings Officer
where a deficiency exists in the existing sewer system or portion thereof which cannot be rectified
within the development and which if not rectified will result in a threat to public
health or safety, surcharging of existing mains, or violations of state or federal standards pertaining to
operation of the sewage treatment system.
18.810.100 Storm Drainage
A. General provisions. The Director and City Engineer shall issue a development permit only where
adequate provisions for storm water and flood water runoff have been made, and:
1. The storm water drainage system shall be separate and independent of any sanitary sewerage
system;
2. Where possible, inlets shall be provided so surface water is not carried across any intersection or
allowed to flood any street; and
3. Surface water drainage patterns shall be shown on every development proposal plan.
B. Easements. Where a development is traversed by a watercourse, drainageway, channel or stream,
there shall be provided a storm water easement or drainage right-of-way conforming substantially
with the lines of such watercourse and such further width as will be adequate for conveyance and
maintenance.
Proposed 18.810 Development Code changes to implement the TSP page 19
• •
C. Accommodation of upstream drainage. A culvert or other drainage facility shall be large enough to
accommodate potential runoff from its entire upstream drainage area, whether inside or outside the
development, and:
1. The City Engineer shall approve the necessary size of the facility, based on the provisions of
Design and Construction Standards for Sanitary and Surface Water Management (as adopted by
the Unified Sewerage Agency in 1996 and including any future revisions or amendments).
D. Effect on downstream drainage. Where it is anticipated by the City Engineer that the additional
runoff resulting from the development will overload an existing drainage facility, the Director and
Engineer shall withhold approval of the development until provisions have been made for
improvement of the potential condition or until provisions have been made for storage of additional
runoff caused by the development in accordance with the Design and Construction Standards for
Sanitary and Surface Water Management (as adopted by the Unified Sewerage Agency in 1996 and
including any future revisions or amendments).
18.810.110 Bikeways and Pedestrian Pathways
Bikeway extension.
1...,__.._As astandard, bike lanes_hall.._he rewired_alono_all Arterial and_Collector routes and where
ident.fie_d..on the City's_adopted biex_c_le plan in the Transportation Svstem Plan n(T$ .
?._-..._Developments adjoining proposed bikeways identified on the City's adopted
pedestrian/bikeway plan shall include provisions for the future extension of such bikeways
through the dedication of easements or rights-of-way, provided such dedication is directly
related to and roughly proportional to the impact of the development.
3__Any._new._street._m ro_v._enient_, ro'ectshall..include_bic._cle lanes._as required_in this locumennt
and onthe_adopted_bicycle.plaii.
B. Cost of construction. Development permits issued for planned unit developments, conditional use
permits, subdivisions and other developments which will principally benefit from such bikeways shall
be conditioned to include the cost or construction of bikeway improvements in an amount roughly
proportional to the impact of the development.
C. Minimum width.
1.____Minimum width for bikeways within the roadway is five feet per bicycle travel lane.
Minimum width multi.:u_se__paths separated from the road is eight-ten
(101 feet._The_width may reduced to eight(8)feet if there are environmental or other constraints.
___... min imum_widtb for pedestr an_only_off-street_ aths_is fve(5)feet_
4._—Design standards for bike and__pedestrian-ways_shall be determinedly} the City__Engineer.
(Ord. 99 22)
18.810.120 Utilities
A. Underground utilities. All utility lines including, but not limited to those required for electric,
communication, lighting and cable television services and related facilities shall be placed
underground, except for surface mounted transformers, surface mounted connection boxes and meter
cabinets which may be placed above ground, temporary utility service facilities during construction,
high capacity electric lines operating at 50,000 volts or above,and:
Proposed 18.810 Development Code changes to implement the TSP page 20
•
• •
1. The developer shall make all necessary arrangements with the serving utility to provide the
underground services;
2. The City reserves the right to approve location of all surface mounted facilities;
3. All underground utilities, including sanitary sewers and storm drains installed in streets by the
developer, shall be constructed prior to the surfacing of the streets; and
4. Stubs for service connections shall be long enough to avoid disturbing the street improvements
when service connections are made.
B. Information on development plans. The applicant for a development shall show on the development
plan or in the explanatory information, easements for all underground utility facilities, and:
1. Plans showing the location of all underground facilities as described herein shall be submitted to
the City Engineer for review and approval; and
2. Care shall be taken in all cases to ensure that above ground equipment does not obstruct vision
clearance areas for vehicular traffic.
C. Exception to under-grounding requirement.
1. The developer shall pay a fee in-lieu of under-grounding costs when the development is proposed
to take place on a street where existing utilities which are not underground will serve the
development and the approval authority determines that the cost and technical difficulty of
under-grounding the utilities outweighs the benefit of undergrounding in conjunction with the
development. The determination shall be on a case-by-case basis. The most common, but not the
only, such situation is a short frontage development for which undergrounding would result in the
placement of additional poles,rather than the removal of above-ground utilities facilities.
2. An applicant for a development which is served by utilities which are not underground and which
are located across a public right-of-way from the applicant's property shall pay the fee in-lieu of
undergrounding.
3. Properties within the CBD zoning district shall be exempt from the requirements for
undergrounding of utility lines and from the fee in-lieu of undergrounding.
4. The exceptions in Subsections 1 through 3 of this section shall apply only to existing utility lines.
All new utility lines shall be placed underground.
D. Fee in-lieu of undergrounding.
1. The City Engineer shall establish utility service areas in the City. All development which occurs
within a utility service area shall pay a fee in-lieu of undergrounding for utilities if the
development does not provide underground utilities, unless exempted by this code.
2. The City Engineer shall establish the fee by utility service area which shall be determined based
upon the estimated cost to underground utilities within each service area. The total estimated cost
for undergrounding in a service area shall be allocated on a front-foot basis to each party within
the service area. The fee due from any developer shall be calculated based on a front-foot basis.
Proposed X18.810 Development Code changes to implement the TSP -page 21
• •
3. A developer shall receive a credit against the fee for costs incurred in the undergrounding of
existing overhead utilities. The City Engineer shall determine the amount of the credit, after
review of cost information submitted by the applicant with the request for credit.
4. The funds collected in each service area shall be used for undergrounding utilities within the City
at large. The City Engineer shall prepare and maintain a list of proposed undergrounding projects
which may be funded with the fees collected by the City. The list shall indicate the estimated
timing and cost of each project. The list shall be submitted to the City Council for their review
and approval annually.
18.810.130 Cash or Bond Required
A. Guarantee. All improvements installed by the developer shall be guaranteed as to workmanship and
material for a period of one year following acceptance by the City Council.
B. Cash deposit or bond. Such guarantee shall be secured by cash deposit or bond in the amount of the
value of the improvements as set by the City Engineer.
C. Compliance requirements. The cash or bond shall comply with the terms and conditions of Section
18.430.090.
18.810.140 Monuments
A. Replacement required. Any monuments that are disturbed before all improvements are completed by
the subdivider shall be replaced prior to final acceptance of the improvements.
18.810.150 Installation Prerequisite
A. Approval required. No public improvements, including sanitary sewers, storm sewers, streets,
sidewalks, curbs, lighting or other requirements shall be undertaken except after the plans have been
approved by the City, permit fee paid, and permit issued.
B. Permit fee. The permit fee is required to defray the cost and expenses incurred by the City for
construction and other services in connection with the improvement. The permit fee shall be set by
Council resolution.
18.810.160 Installation Conformation
A. Conformance required. In addition to other requirements, improvements installed by the developer
either as a requirement of these regulations or at his own option, shall conform to the requirements of
this chapter and to improvement standards and specifications followed by the City.
B. Adopted installation standards. The Standard Specifications for Public Works Construction, Oregon
Chapter A.P.W.A., and Design and Construction Standards for Sanitary and Surface Water
Management(as adopted by the Unified Sewerage Agency in 1996 and including any future revisions
or amendments) shall be a part of the City's adopted installation standard(s); other standards may also
be required upon recommendation of the City Engineer.
18.810.170 Plan Check
A. Submittal requirements. Work shall not begin until construction plans and construction estimates
have been submitted and checked for adequacy and approved by the City Engineer in writing. The
Proposed 18.810 Development Code changes to implement the TSP page 22
• •
developer can obtain detailed information about submittal requirements from the City Engineer.
B. Compliance. All such plans shall be prepared in accordance with requirements of the City.
18.810.180 Notice to City
A. Commencement. Work shall not begin until the City has been notified in advance.
B. Resumption. If work is discontinued for any reason, it shall not be resumed until the City is notified.
18.810.190 City Inspection
A. Inspection of improvements. Improvements shall be constructed under the inspection and to the
satisfaction of the City. The City may require changes in typical sections and details if unusual
conditions arising during construction warrant such changes in the public interest.
18.810.200 Engineer's Certification
A. Written certification required. The developer's engineer shall provide written certification of a form
provided by the City that all improvements, workmanship and materials are in accord with current
and standard engineering and construction practices,and are of high grade,prior to City acceptance of
the subdivision's improvements or any portion thereof for operation and maintenance.
18.810.210 Completion Requirements(To be completed.)■
Proposed 18.810 Development Code changes to implement the TSP page 23
•
Attachment 5
ADDITIONAL AMENDMENTS
18.120.030
Add the following definitions in alphabetical order and renumber the remaining
definitions accordingly:
_Neighborhood Activity Center"— A use such as schools,�arks libraries. or pools which
provide recreational or social services for groups of people.
•
``Queuing Plan" — A plan submitted with a proposal for skinny streets that shows the
potential queuing pattern that will allow for safe and efficient travel of emergency
vehicles service vehicles and passenger vehicles with minimal disturbance.
•
18.360.090.A.11.a
change from:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to existing or proposed transit route
change to:
Provisions within the plan shall be included for providing for transit if the development
proposal is adjacent to or within 500 feet of existing or proposed transit route
18.520.020.B
change the 3`d sentence from:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
change to:
Separated from other commercially-zoned areas by at least one-half mile, community
commercial centers are intended to serve several residential neighborhoods, ideally at
the intersection of two or more major collector streets
18.530.050.A.2
change from:
The site shall have access to be approved by the City Engineer to an arterial or major
collectors street.....
change to:
The site shall have access to be approved by the City Engineer to an arterial or major
collector street.....
Additional TSP implementation code amendments Page 1
18.745.050.C.2.b
change from:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, major collector or minor collector street.
change to:
Are permitted up to six feet in height in front yards adjacent to any designated
arterial, m "°ctor or minor collector street.
•
Additional TSP implementation code amendments Page 2
•
U.S. Postal Service
CERTIFIED MAIL RECEIPT
(Domestic Mail Only;No Insurance Coverage Provided)
u�-,
a-
\eV et, 20 - 2002 - 00004
Postage $
•
� 7
Certified Fee
r` f�L • `y Postmark ece Return
- (Endor.5emeneRequirred) p Here
1
p Restricted Delivery Fee c�\
p (Endorsement Required) \.�• ,
O Total Postage&Fees $ d
O `
Recipient's Name(Please Print Clearly)(to be completed by mailer)
m _ -
Street PLAN AMENDMENT SPECIALIST, DLCD
635 CAPITAL ST. NE, SUITE 150
I city,si' SALEM, OR 97301-2540
r—
PS Form 3800,February 2000 See Reverse for Instructions
---
SENDER: COMPLETE THIS SECTION COMPLETE THIS SECTION ON DELIVERY 11
• Complete items 1,2,and 3.Also complete A. Received by(Please Print Clea y) B. Date of Deli ery
item 4 if Restricted Delivery is desired. 20
• Print your name and address on the reverse C. Signature ��J�
so that we can return the card to you. 0
• Attach this card to the back of the mailpiece, +V A 1 0-Agent
or on the front if space permits. i:rr� '°J-A-'"'-- ❑Addressee
D.-is delivery address different from item 1? ❑Yes
1. Article Addressed to: i f YES,enter delivery address below: ,❑ No
^— — — — — ,t
PLAN AMENDMENT SPECIALIST
DLCD 1 •
635 CAPITAL ST. NE, SUITE 150
SALEM, OR 97301-2540 3. Service Type
0 Certified Mail ❑ Express Mail
❑ Registered ❑ Return Receipt for Merchandise
❑ Insured Mail ❑C.O.D.
4. Restricted Delivery?(Extra Fee) ❑Yes
2. Article Number(Copy from service label)
7099 3'100 00 5. 775 s/y?
PS Form 3811,July 1999' Domestic Return Receipt 102595-00-M-0952
Form 1 • C
DLCD NOTICE OF PROPOSED AMENDMENT
This form must be received by DLCD at least 45 days prior to the first evidentiary hearing
per ORS 197.610, OAR Chapter 660 - Division 18
and Senate Bill 543 and effective on June 30, 1999
(See reverse side for submittal requirements)
Jurisdiction: City of Tigard Local File No.: ZOA 2002-00004
(If no number,use none)
Date of First Evidentiary Hearing: August 5, 2002 Date of Final Hearing:set for 9/10/02
(Must be filled in) (Must be filled in)
Date this proposal was sent or mailed: (47 days)
(Date mailed or sent to DLCD)
Has this proposal been submitted to DLCD? Yes X No Date:
Comprehensive Plan Text Amendment _ Comprehensive Plan Map Amendment
X Land Use Regulation Amendment _ Zoning Map Amendment
New Land Use Regulation _ Other:
(Please Specify Type of Action)
Briefly summarize the proposal. Do not use technical terms. Do not write "See Attached."
Amend the Tigard Development Code to reflect the Transportation System Plan and
Comprehensive Plan changes adopted in January 2002. The proposed amendments also reflect
the State of Oregon's Transportation Planning Rules (TPR) which include provision of skinny
streets. The specific Tigard Development Code sections meeting amended include: 18.120
(definitions), 18.360 (Site Development Review), 18.520 (Commercial zoning), 18.530 (Industrial
zoning), 18.705 (Access Egress and Circulation), 18.745 (Landscaping and screening) and
18.810 (Street and Utility Improvement Standards).
Plan Map Change from: N/A to N/A'
Zone Map Change from: N/A to N/A
Location: City wide Acres Involved:
Specified change in Density: Current: N/A Proposed:
Applicable Statewide Planning Goals: 1, 2 and 12
Is an Exception proposed?_Yes X No
Affected State or Federal Agencies, Local Governments or Special Districts: DLCD, Metro
•
Local Contact: Julia Hajduk Area Code + Phone Number: 503-639-4171 x 336
Address: 13125 SW Hall Blvd
City: Tigard, OR Zip Code + 4: 97223
DLCD No.:
Form 1 1111
SUBMITTAL REQUIREMENTS
This form must be received by DLCD at least 45 days prior to the first evidentiary hearing
per ORS 197.610, OAR Chapter 660-Division 18
and Senate Bill 543 and effective on June 30, 1999.
1. Send this Form and Two (2) Copies of the Proposed Amendment to:
ATTENTION: PLAN AMENDMENT SPECIALIST
DEPARTMENT OF LAND CONSERVATION AND DEVELOPMENT
635 CAPITAL STREET NE, SUITE 150
SALEM, OREGON 97301-2540
COPIES TO:
Metro Land Use & Planning
600 NE Grand Avenue
Portland, OR 97232-2736
ODOT—Region 1, District 2-A
Jane Estes, Permit Specialist
5440 SW Westgate Drive, Suite 350
Portland, OR 97221-2414
2. Unless exempt by ORS 197.610 (2), proposed amendments must be received at the
DLCD's SALEM OFFICE at least FORTY-FIVE (45) before the first evidentiary
hearing on the proposal. The first evidentiary hearing is usually the first public
hearing held by the jurisdiction's planning commission on the proposal.
3. Submittal of proposed amendments shall include the text of the amendment and any
other information the local government believes is necessary to advise DLCD of the
proposal. "Text" means the specific language being added to or deleted from the
acknowledged plan or land use regulations. A general description of the proposal is
not adequate.
4. Submittal of proposed "map" amendments must include a map of the affected area
showing existing and proposed plan and zone designations. The map should be on
8 1/2 x 11 inch paper. A legal description, tax account number, address or general
description is not adequate.
5. Submittal of proposed amendments which involve a goal exception must include the
proposed language of the exception.
6. Need More Copies? You can copy this form on to 8-1/2x11 green paper only8-1/2x11 •
green parer only; or call the DLCD Office at (503) 373-0050; or Fax your request to:
(503) 378-5518; or email your request to Larry.French(a)state.or.us — ATTENTION:
PLAN AMENDMENT SPECIALIST.
05/07/2002 15:25 5036203433 COMMUNITY NEWSPAPERS PAGE 01
•
COMMUNITY-
11114.:_64TEwsrEmER.s._
•
rk
F_���] X COVER. SHEET
ATTN:1 1: i�'
COMPANY (i
FAX : „rip
— � . - -
We have rec.-ivc4 your Public Notice inforzaatiort
h 404.040:470 cer.m.444.zdae.e);:■
Re: y�
PiPer(s):
Publication Date(s): iey /6j cleOcil'--
You will t .-ivc a nota.*;z;� a.Mdavit, with leis shc.c at[ach..�a., aetcr the last pubiic=.Lion
date
• Thank you for publishing with Community NcwspaQc.x, tr c., and pleas: fc-1 two to c2-1.1
if you havc oucstions.
FROM: SyLV,A fr /N$7e� Le .s
PHONE: .503- .Sfl6- 0779FAX: 5-0 3 - 354-3 3
Date: 5-77/i�ca Time: • ' No. Panes: /
(including cover)
Picric direct this transtnitt.l. If you do-not receive all pages, please call. Thank You.
P.O. Box 370 -.Beaverton, OR 97075.;.(503) 624-0360 • Fax: (503) 620-3433
•
EO€Sr FpR QffiMhtEAJI5
.f
Ill Ill
f
0 0
F
,, 1.**.f. ,71,
� o �� �� Department of Transportation
F r :z Region 1
John A.Kitzhaber,M.D.,Governor 123 NW Flanders
s 9� Portland,OR 97209-4037
(503)731-8200
FAX (503)731-8259
FILE CODE:
July 16, 2002
PLA9-2A-
ODOT Case No: 1579 1 all
City of Tigard ,J ' 1,
Planning Division dd1,.
g a59/ 5.
13125 SW Hall Blvd. Can ir4 r,y'"� 54tr
Tigard, OR 97223 ci''�" 1y/ 02
Attn: Julia Hajduk
Subject: ZOA2002-00004: Tigard TSP Implementation Ordinance
Dear Julia,
I appreciate the City's efforts to address the policies of the Oregon Highway Plan and
the requirements.'of the Transportation Planning Rule (OAR660-012) in drafting
implementation ordinance_language for your Transportation System Plan. Applications
for plan and land use regulation amendments must address OAR 660-012-0060 and
Oregon Highway Plan Policy 1 F:Highway Mobility Standards. Therefore, we request the
City incorporate these requirements into your implementation ordinances.
To view text for OAR 660-012-0060 Plan and Land Use Regulation Amendments use
this link to the Transportation Planning Rule:
http://arcweb.sos.state.or.us/rules/OARS 600/OAR 660/660 012.html
Oregon Highway Plan Policy 1F actions 1F.2 and 1F.4 apply directly to plan and land
use regulation amendments. To view the entire text of Policy 1F: Highway Mobility
Standards, including tables 6 and 7 referenced in action 1 F.4, use this link to highway
plan policies and scroll to page 59.
•
http://www.odot.state.or.us/tdb/planning/highway/documents/goal1.doc
Action 1F.2
When evaluating highway mobility for amendments to transportation system plans,
acknowledged comprehensive plans and land use regulations, use the planning horizons
in adopted local and regional transportation system plans or a planning horizon of 15
years from the proposed date of amendment adoption, whichever is greater. To
determine the effect an amendment to a transportation system plan, acknowledged
comprehensive plan or land use regulation has on a state facility, the capacity analysis
Form 734-1850(1/98) as
City of Tigard;ZOA2002-00004,Tigard TSP Implementation 2
ODOT RESPONSE • • 7/16/2002
shall include the forecasted growth of traffic on the state highway due to regional and
intercity travel and to full development according to the applicable acknowledged
comprehensive plan over the planning period.
Action 1F.6
For purposes of evaluating amendments to transportation system plans, acknowledged
comprehensive plans and land use regulations subject to OAR 660-12-060, in situations
where the volume to capacity ratio for a highway segment, intersection or interchange is
above the standards in Table 6 or Table 7, or those otherwise approved by the
Commission, and transportation improvements are not planned within the planning
horizon to bring performance to standard, the performance standard is to avoid further
degradation. If an amendment to a transportation system plan, acknowledged
comprehensive plan or land use regulation increases the volume to capacity ratio
further, it will significantly affect the facility.
Thank you for your attention to these issues. If you have questions regarding this matter,
I can be reached at 503-731-8258. Please forward a copy of the Decision with Final
Findings when it has been issued.
Sincerely,
Marah Danielson
Development Review
C: Darci Rudzinski, DLCD
�iv�° re on Department of Transportation
0 - 0 • •
i.�'• z Region 1• John A.Knzhaber,M.D.,Governor 123 NW Flanders
is 5 9 Portland,OR 97209-4037
(503) 731-8200
FAX (503) 731-8259
RECEIVED PLANNING
J U L 01 2002 FILE CODE:
June 28, 2002
CITY OF TIGARD PLA9-2A-
ODOT Case No: 1479
City of Tigard
Planning Division
13125 SW Hall Blvd.
Tigard, OR 97223
Attn: Julia Hajduk, Associate Planner -.
Subject: ZOA2002-00004: TSP Implementation Ordinance Amendments
Traffic Study Requirement
Dear Ms. Hajduk,
We appreciate the City's efforts to address ODOT interest to ensure the safe and efficient
operation of state highway facilities through the TSP implementation ordinance
amendments. Staff clarification of 18.810.030.AC provides parameters for when a traffic
study is required, "A traffic study shall be^required for all new developments under any of
the following circumstances: 4. When the site is within 500 feet of an ODOT facility."
A traffic study is not always necessary to address ODOT interests. Therefore, we
recommend 18.810.030AC be subdivided into two sections. Section 1 would include
criteria for when a traffic study shall be required and section 2 would include criteria for
when a traffic study may be required. We request the following language for subsection 2
to more clearly define the parameters for when a traffic study may be needed to address
ODOT /irfilfrAi°-
A traffic study may be required for all new developments under any of the following
circumstances:
a. When a site is within 500 feet of an ODOT facility and/or
b. trip generation from development adds 300 or more vehicle trips per day to an
ODOT facility and/or
c. trip generation from development adds 50 or more peak hour trips to an ODOT
facility.
In order to make a determination whether or not a traffic study is required to address
ODOT interests, we request the, City send ODOT notification of all pre-applications that
meet the above criteria. This will allow ODOT to make a recommendation as to whether or
not a traffic study is needed to address ODOT interests prior to a Formal Application being
deemed complete.
Form 734-1850(1/98)
City of Tigard;ZOA2002-000TSP Implementation • 2
ODOT RESPONSE 6/28/2002
If you have any questions regarding these comments, please contact John Bosket, Sr
Transportation Analyst, at 503-731-3427. Thank you for providing notice of the TSP
implementation ordinance amendments. Please send us a copy of the adopted language.
I can be reached at 503-731-8258.
Sincerely,
Mara 'anielson
Development Review
C: John Bosket, ODOT Region 1 Traffic
•
V 0.
6 0 0 NO E A S T T G R A N D A V E N U E P O R T L A N D, O R E G O N 7 2 3 2 2 7 3 6
TEL 503 797 1 700 I FAX 503 797 1797
METRO
July 12,2002
Julia Hajduk
Associate Planner
City of Tigard
13125 SE Hall Boulevard
Tigard,Oregon 97223
Re: City of Tigard,Code Amendments to Adopt the Transportation System Plan
Local File No: ZOA 2002-00004
Dear Julia:
Thank.you:for the opportunity to review and comment on the latest set of,code
amendments proposed by staff to implement the Tigard Transportation System Plan
(TSP) adopted in January 2002. Based on Metro staff review of the proposed
amendments,we offer the following comments related to the updated residential street
standards and block standards to ensure consistency with the Regional Transportation
Plan(RTP).
Narrow Residential Street Standards
The city proposes to implement Transportation Planning Rule (TPR)and RTP provisions
to reduce residential street right-of-way and pavement width through provisions in
section 18.810.030 of the code (e.g., "skinny streets"). As proposed,the requirements in
Table 18.810.1 and the associated figures might discourage a developer from pursuing
narrower residential streets where appropriate. We suggest that footnote#3 to Table
18.810.1 be revised to more clearly encourage narrower residential streets. For example,
the footnote could read, "Narrower residential streets are encouraged where cross
section and review criteria are met."
Block Standards
Tigard staff proposes a change to Section 18.810.040.B.1 dealing with maximum block
standards. Metro recommends that the city retain the existing maximum perimeter
standard of 1,800 feet to ensure that.overall block development in these areas facilitates
pedestrian=scale development. While the difference between the existing standard and
the proposed new standard is only 120 feet per block, this cart make an important
difference over the course of a new development.
Recycled Paper
www metro-region org
T D D 7 9 7 1 8 0 4
City of Tigard • •
July 12,2002
Page 2
Thank you for the opportunity to review and comment on the proposed code
amendments. I hope you find these comments helpful as you continue to finalize the
City's code to implement the transportation plan. If you have any questions,please call
me at(503)797-1617 or email me at whitek@metro.dst.or.us.
Sincer-ly,
Kim White,AI 4
Senior Transportation Planner
• cc: Darci Rudzinski, DLCD
Lidwien Rahman, ODOT
O p • •
pgi ' Department of Land Conservation & Development
w,T4 ' IIregon 800 NE Oregon St.#18
•may Portland,OR 97232
John A.Kitzhaber,M.D.,Governor . (503) 731-4065
FAX(503) 731-4068
REC'D JUL 12 2002
July 10, 2002
Julia Hajduk
Associate Planner
City of Tigard
13125 SE Hall Boulevard
Tigard, Oregon 97223
Re: City of Tigard, Code Amendments to Adopt the Transportation System Plan
Local File No: ZOA 2002-0004; DLCD File No: 004-02
Dear Julia:
We have reviewed the latest set of code amendments proposed by staff to implement the Tigard
Transportation System Plan (TSP) adopted in January 2002. Here are brief comments on two
elements of the proposal—residential street standards and block standards.
Narrow Residential Street Standards
As we have discussed on several occasions, the department is interested in assuring that local
code provisions to carry out aspects of the Transportation Planning Rule(TPR) are as clear as
possible.
A very important aspect of adopting these proposed amendments is to document the process
Tigard used to develop its local street standards consistent with OAR 660-012-0045(7). Such an
explanation is not evident in the TSP itself; it should be documented as part of the City's action
on these implementing measures.
The city proposes to implement TPR(and local TSP) provisions to reduce residential street right-
of-way and pavement width ("skinny streets") through provisions in section 18.810.030 of the
code. Requirements in Table 18.810.1 and the associated figures essentially provide two options
for a developer seeking to develop residential streets. We recommend that the code present the
options in a manner that does not discourage someone from pursuing narrower residential streets
where appropriate. To this end, we offer the following suggestions:
• In Table 18.810.1, provide the dimension for the "standard" street and the"skinny" street
option in the table. As written, the table and its footnotes give the strong (and wrong)
*.
•
City of Tigard,TSP •
DLCD File No.: 004-02
7/10/02
Page 2 of 3
impression that a narrower street option is not favored in Tigard. For example a footnote
might read "Narrower residential streets are encouraged where cross section and review
criteria are met."
• In Figures 18.810.4 and 18.810.5, we recommend that the approval criteria specify who
approves a"Queuing Plan" and provide guidance about the purpose and contents of the plan.
Since"Queuing Plan"is only relevant to these sections of the code, one idea would be to add
the definition from Section 18.120.030 to the text explaining the figures. We also would
suggest this definition:
"Queuing Plan"—A plan showing how a proposed residential street narrower than the
"standard"residential street enables safe passage of emergency, service, and passenger
vehicles in the unlikely event of two vehicles meeting on a residential street. Emergency
service providers typically request approximately 20 feet of unobstructed passage
accomplished by placement of driveways and on-street parking.
Block Standards
We note that staff proposes a change to Section 18.810.040.B.1 dealing with maximum block
standards. We recommend that the city retain the existing maximum perimeter standard of 1,800
feet,but perhaps modify the standard to assure that the Tigard code is consistent with the Metro
functional plan requirements for street spacing. A good model is the language (below)used by
Washington County.
408-6.2 For residential, office, retail and institutional development, on-site streets shall be
provide which meet the following:
A. Block lengths for local streets and collectors shall not exceed 530 feet between
through streets, measured along the nearside right-of-way line of the through
street. . .
B. The total length of a perimeter of a block for local and collector streets shall not
exceed eighteen hundred(1,800)feet between through streets, measured along the
nearside right-of-way. . .
These standards assure that streets are not excessively spaced, consistent with Metro standards,
and also assure that overall block development facilitates pedestrian-scale development. The
difference between the proposed standard and the Washington County example is not large (120
feet per block), but this can make an important difference over the course of an entire
development.
Thank you for your attention to these issues. We appreciate your efforts to improve upon the
city's TSP and bring it into conformance with state and regional standards through this
implementation process. Please enter this letter into the record or proceedings. We would also
City of Tigard,TSP • •
DLCD File No.: 004-02
7/10/02
Page 3 of 3
appreciate a copy of any additional changes to the proposed amendment and a copy of the final
decision. If you have any questions regarding the content of this letter, please contact me at 731-
4065 ext. 25.
Sincerely,
Darci E. A. Rudzinski
Portland Metro Area Regional Representative
c: Sonya Kazen, ODOT Region 1
Lidwein Rahman, ODOT Region 1
Kim White, Metro
Distribution: Cansler, Cortright, Oulman
TUALATIN VALLEY FIRE & RESCU . SOUTH DIVISION
COMMUNITY SERVICES • OPERATIONS • FIRE PREVENTION
Tualatin Valley
Fire & Rescue
July 8, 2002
Julia Hajduk, Associate Planner
City of Tigard
13125 SW Hall Blvd
Tigard, OR 97223
Re: Tigard Development Code Amendments
Dear Julia,
I have reviewed the above name document and find no conflicts with our interests. The provisions for
skinny streets are acceptable to the Fire District.
The Fire District is currently developing traffic calming device design criteria that will be submitted upon
completion. The general statement in the Development Code indicates only when they are to be
installed. The Fire District hopes that our criteria will be considered for design details.
Please contact me at(503)612-7010 with any additional questions.
Sincerely,
Eric T. McMullen
Eric T. McMullen
Deputy Fire Marshal
7401 SW Washo Court,Suite 101 •Tualatin,Oregon 97062•Tel.(503)612-7000•Fax(503)612-7003•www.tvfr.com
•
REQUEST FOR COMMENTS CITY OF TIiGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: ohn Roy, Public Works, COT
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Hajduk, Associate Planner
Phone: (503) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5. 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWING ITEMS THAT APPLY:
We have reviewed the proposal and have no objections to it.
_ Please contact of our office.
_ Please refer to the enclosed letter.
Written comments provided below:
(Please provide the following information) Name of Person(s) Commenting:
I Phone Number(s): I
Sent By: CITY OF DURHAM; 5035988595; Jun- -02 12:40; Page 1 /1
REQUEST FOR COMMENTS C. TIGARD
Community Development
Shaping A Better Community
DATE: June 21. 2002
TO: City Manager, City of Durham
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Ha'duk Associate Planner JUN 2 0 ?(10?_
Phone: (503) 639-4171 Fax: (503) 684-7297 11 _
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP ImplementationQ
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5, 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWtNG.ITI=MS THAT APPLY:
We have reviewed the proposal and have no objections to it.
Please contact
of our office.
Please refer to the enclosed letter.
Written comments provided below:
(Please provide the following information) Name of Person(s) Commenting: aqD�L Lomb 6�vr5?-
'Phone Number(s): 50 3 , 3/. Os-/ I
0 •
't A
III
REQUEST FOR COMMENTS CITY OF TIGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: Dennis Koellermeier, Public Works, COT
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Ha duk, Associate Planner
Phone: (503 ) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5. 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWING ITEMS THAT APPLY:
I/ We have reviewed the proposal and have no objections to it.
— Please contact of our office.
— Please refer to the enclosed letter.
Written comments provided below:
(Please provide the following information) Name of Person(s) Commenting:% Qy
'Phone Number(s): ‘..5? 4/./7/ I' g 4 .
• •
REQUEST FOR COMMENTS CITY OF TIIGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: Matt Stine, Urban Forester, COT
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Ha'duk, Associate Planner
Phone: (503) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5, 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWING ITEMS THAT APPLY:
We have reviewed the proposal and have no objections to it.
_ Please contact of our office.
Please refer to the enclosed letter.
X Written comments provided below:
N-E pal-Are-A_ STRA Ps 5 -o u,Lo a E T- t_e A-Sr .� of l D E SO
Tk EeS cAnj g.E P L-A-A!i t iAt O1 ER. 70 c_kE-0- Nlo Gtr 712x( cA-A10 SPY_
Mt r(HA fit- 1 2 srye-PS AkE i9- 400A (1 C.-ft 5(,VC
rye ire$ IA 1 3e- sl•4-)4-6i;1r4 MR1-4 Alt lee of
TcrkAs c,AI r. FFec/ 700 C6 MAIM, /n/ t-wiS
Cur
fr1i-rrSrf,v
(Please provide the following information) Name of Person(s) Commenting:
I Phone Number(s): I
• •
REQUEST FOR COMMENTS CITY OF TIIGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: Jim Wolf, Police Department, COT
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Hajduk, Associate Planner
Phone: (503) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5, 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PL ASE CHECK THE FOLLOWING ITEMS THAT APPLY:
We have reviewed the ro osal and have no objections to it.
P P objections
_ Please contact of our office.
_ Please refer to the enclosed letter.
•
Written comments provided below:
(Please provide the following information) Name of Person(s) Commenting: d.\NIDvT
'Phone Number(s): *I.SA I
REQUEST FOR COMMENTS CI OF TIGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: Current Planning, COT
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Hajduk, Associate Planner
Phone: (503) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR.
COMMENTS BACK BY: July 5. 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWING ITEMS THAT APPLY:
We have reviewed the proposal and have no objections to it.
_ Please contact of our office.
_ Please refer to the enclosed letter.
Written comments provided below:
•
•
(Please provide the following information) Name of Person(s) Commenting:
I Phone Number(s): I
• • A
REQUEST FOR COMMENTS CITY of TIGARD
Community Development
Shaping A Better Community
DATE: June 21, 2002
TO: PER ATTACHED
FROM: City of Tigard Planning Division
STAFF CONTACT: Julia Hajduk, Associate Planner
Phone: (503) 639-4171 Fax: (503) 684-7297
ZONE ORDINANCE AMENDMENT (ZOA) FILE #2002-00004
>TSP Implementation<
Amend the Tigard Development Code to reflect the Transportation System Plan and Comprehensive Plan
changes adopted in January 2002. The proposed amendments also reflect the State of Oregon's
Transportation Planning Rules (TPR) which include provision of skinny streets. The specific code sections
meeting amended include: 18.120, 18.360, 18.520, 18.530, 18.705, 18.745 and 18.810. Attached are the
"DRAFT" proposed amendments for your review. From information supplied by various departments and agencies
and from other information available to our staff, a report and recommendation will be prepared and a decision will be
rendered on the proposal in the near future. If you wish to comment on this application, WE NEED YOUR
COMMENTS BACK BY: July 5, 2002. You may use the space provided below or attach a separate letter to return
your comments. If you are unable to respond by the above date, please phone the staff contact noted above with
your comments and confirm your comments in writing as soon as possible. If you have any questions, contact the
Tigard Planning Division, 13125 SW Hall Boulevard, Tigard, OR 97223.
PLEASE CHECK THE FOLLOWING ITEMS THAT APPLY:
We have reviewed the proposal and have no objections to it.
_ Please contact of our office.
_ Please refer to the enclosed letter.
Written comments provided below:
(Please provide the following information) Name of Persontsl Commenting:
Phone Humberto]:
• CITY. TIGARD REQUEST FOR COIENTS
NOTIFICATION LISt FOR LAND USE & COMMUNITY DEVELOPMENT APPLICATIONS
•
FILE NOS.: 104 ZODa.- Dao`f FILE NAME: 7 P.' /070/ 11�
. CITIuEN"INVOLVEMENT TEAMS•" •: ,. - ' .
14-DAY PENDING APPLICATION NOTICE TO CIT AREA: ❑Central DEast ❑South ['West ElProposal.Descrip.in Library CIT Book
. _.._
. . .
CITY OFFICES " t: .'
Cw�c4 f
VLONG-RANGE PLANNING/Barbara Shields,Planning Mgr. ✓COMMUNITY DVLPMNT.DEPT/Planning-Engineering Techs. } POLICE DEPTJJim Wolf,Crime Prevention Officer
_ E
BUILDING DIVISION/Gary Lampella,Building Official NGINEERING DEPTJBrian Rager,Ovlpmnt.Review Engineer✓WATER DEPTJDennis Koellermeier,Operations Mgr.
CITY ADMINISTRATION/Cathy Wheatley,City Recorder _PUBLIC WORKS/John Roy,Property Manager ."-PUBLIC WORKS/Matt Stine,Urban Forester
I PLANNER-POST PROJECT SITE IF A PUBLIC HEARING ITEM-10 BUSINESS DAYS PRIOR TO THE PUBLIC HEARING! _C.DJSherman Casper,Permit Coord.(sowcup re:TIF)
SPECIAL DISTRICTS. .: : . : -:
_ TUAL.HILLS PARK&REC.DIST.*VTUALATIN VALLEY FIRE&RESCUE* _ TUALATIN VALLEY WATER DISTRICT* _ CLEANWATER SERVICES*
Planning Manager Fire Marshall Administrative Office Lee Walker/SWM Program
15707 SW Walker Road Washington County Fire District PO Box 745 155 N.First Avenue
Beaverton,OR 97006 (place in pick-up box) Beaverton,OR 97075 Hillsboro,OR 97124
LOCAL AND_STATE JURISDICTIONS - :`
,CITY OF BEAVERTON* ✓CITY OF TUALATIN* _OR.DEPT.OF FISH&WILDLIFE _OR.DIV.OF STATE LANDS
_ Planning Manager Planning Manager 2501 SW First Avenue Jennifer Goodridge
Irish Bunnell,Development Services PO Box 369 PO Box 59 775 Summer Street NE
PO Box 4755 Tualatin,OR 97062 Portland,OR 97207 Salem,OR 97301-1279
Beaverton,OR 97076
OR.PUB.UTILITIES COMM.
METRO-LAND USE&PLANNING * _OR.DEPT.OF GEO.&MINERAL IND. 550 Capitol Street NE
'CITY OF DURHAM* 600 NE Grand Avenue 800 NE Oregon Street,Suite 5 Salem,OR 97310-1380
City Manager Portland,OR 97232-2736 Portland,OR 97232
PO Box 23483 Bob Knight,Data Resource Center(ZCA) � _US ARMY CORPS.OF ENG.
Durham,OR 97281-3483 Paulette Allen,Growth Management Coordinator ✓OR.DEPT.OF LAND CONSERV.&DVLP Kathryn Harris
_ Mel Huie,Greenspaces Coordinator(CPA20A) Larry French(Comp.Plan Amendments Only) Routing CENWP-OP-G
i.ITY OF KING CITY* _ Jennifer Budhabhatti,Regional Planner(Wetlands) 635 Capitol Street NE,Suite 150 PO Box 2946
City Manager _ C.D.Manager,Growth Management Services „Salem,OR 97301-2540 Portland,OR 97208-2946
15300 SW 116th Avenue bsrc'Rye ts10
King City,OR 97224 WASHINGTON COUNTY
. _ OR.DEPT.OF ENERGY(Powerlines in Area) _OREGON DEPT.OF TRANS.(ODOT) Dept.of Land Use&Transp.
Bonneville Power Administration Aeronautics Division(Monopole Towers) 155 N.First Avenue
t1 CITY OF LAKE OSWEGO* Routing TTRC-Attn: Renae Ferrera Tom Highland,Planning Suite 350,MS 13
Planning Director PO Box 3621 3040 25th Street,SE Hillsboro,OR 97124
PO Box 369 Portland,OR 97208-3621 Salem,OR 97310 _Brent Curtis(CPA)
Lake Oswego,OR 97034 _Gregg Leion(CPA)
_ OR.DEPT.OF ENVIRON.QUALITY(DEQ) 9DOT,REGION 1 _Anne LaMountain(IGNORE)
_CITY OF PORTLAND (Notify for Wetlands and Potential Environmental Impacts) vSonya Kazen,Development Review Coordinator _Phil Healy(IGANRB)
David Knowles,Planning Bureau Dir. Regional Administrator _Carl Toland, Right-of-Way Section(vacations) _Steve Conway(General Apps.)
Portland Building 106,Rm. 1002 2020 SW Fourth Avenue,Suite 400 123 NW Flanders _Sr.Cartographer(cPArzcA)M S 14
1120 SW Fifth Avenue Portland,OR 97201-4987 Portland,OR 97209-4037 _Jim Nims(ZCA)MS 15
Portland,OR 97204 Doria Mateja(ZCA)MS 14
WCCCA(911)(Monopole Towers) �ODOT,REGION 1 -DISTRICT 2A �� y/R,C/ 7qUif- ,
Dave Austin Jane Estes,Permit Specialist
17911 NW Evergreen Parkway 5440 SW Westgate Drive,Suite 350
Beaverton,OR 97006 Portland,OR 97221-2414
:r : -.
. UTILITY PROVIDERSAND : ',:_• : ;"' - ," : 7 `=.
_PORTLAND WESTERN R/R,BURLINGTON NORTHERN/SANTA FE R/R,OREGON ELECTRIC R/R(Burlington Northem/Santa Fe R/R Predecessor)
Robert I.Melbo,President&General Manager
' 110 W.10th Avenue
Albany,OR 97321 •
—SOUTHERN PACIFIC TRANS.CO.R/R _METRO AREA COMMUNICATIONS _AT&T CABLE �RI-MET TRANSIT DVLPMT.
Clifford C.Cabe,Construction Engineer Debra Palmer(Annexations Only) Pat McGann (If Project is wdhin V.Mile of A Transit Route)
5424 SE McLoughlin Boulevard Twin Oaks Technology Center 14200 SW Brigadoon Court Ben Baldwin,Project Planner
Portland,OR 97232 1815 NW 169th Place,S-6020 Beaverton,OR 97005 710 NE Holladay Street
Beaverton,OR 97006-4886 Portland,OR 97232
_PORTLAND GENERAL ELECTRIC
—NW NATURAL GAS COMPANY —VERIZON _ QWEST COMMUNICATIONS
Jim VanKleek,Svc.Design Consultant Scott Palmer,Engineering Coord. Ken Perdue,Engineering Jeri Cella,Engineering
9480 SW Boeckman Road 220 NW Second Avenue PO Box 1100 8021 SW Capitol Hill Rd,Rm 110
Wilsonville,OR 97070 Portland,OR 97209-3991 Beaverton,OR 97075-1100 Portland,OR 97219
—TIGARD/TUALATIN SCHOOL DIST.#23J_BEAVERTON SCHOOL DIST.#48 _ AT&T CABLE(Apps"Edl r.n
Marsha Butler,Administrative Offices Jan Youngquist,Demographics&Planning Dept. Diana Carpenter
6960 SW Sandburg Street 16550 SW Merlo Road 3500 SW Bond Street
Tigard,OR 97223-8039 Beaverton,OR 97006-5152 Portland,OR 97232
)If INDICATES AUTOMATIC NOTIFICATION IN COMPLIANCE WITH INTERGOVERNMENTAL AGREEMENT IF WITHIN 500' OF THE SUBJECT PROPERTY FOR ANY/ALL
CITY PROJECTS(Project Planner Is Responsible For Indicating Parties To Notify). • h:tpattyvnasters\Request For Comments Notification List 2.doc (Revised: 8-Mar-02)