City Council Packet - 06/18/20023 ,stir 1 Jk 4`p"~~~~j~~ 1 M.-Ill4'f ~~Tj t ~t yg~q
5 t c ~ti ~r3x rd7.eyF1 s a ~ r ~ ~ a i o T~'~; ~ Ea
s fe ~~1y,-tt t ar ,d't' w~o tv x
,r k •.a ~A l `F r'1.a. , 'f,S`-'~.~ 45 v + ~.rr~ [c ?
: e3Gr t„ K.t i t4xe~ x y b
~-~.h 14•t-°• r ~~i ~r! h~'~"4' t~~`~~at ~ ~ t1~' 1~,~~9~~~ ~
lL N, ` r 4 ^b~ f t / t .f ~ '~k t~;t a4 4 M
. t ~ t 4. e J1•C nl )~~'L+ a 7tiF K ^y.y+ r r o
1 _ at kr Wr~St~x e,~~~r~2y.,~j t'f }.u5',, 5 Syr u'i {9
l Rt ? $r ti'+i+~a~7 ~'~`ti~~0.T }a'~a rS~.~'~~~~
Aif g`f
{'f~ s+'tx rr f~, t~ y °f Iac1T'
ty < r~~ y t s} a sr s'ngbk'"w+,`r~~~F{~'~.~ t~7~.r
, _ -n ~ o ,Yhd °'1% `TJ.7' ~~'~,i7r~~"~¢•+a:13z~i S w~y ~~'~kv,
r r n r i i yrDi~~~i"~~k' ~ ii 3r Y r t x ~r:• ~ 5
P; g<r, 'V i
r~ t; t r~, , t' t r
7 ~~1~ lr Ala A
~ Cpl TCn"' Ik
R"f
l j t F L
r`rfRY ~{y4~S iv.j
5
t
t F
i ~pPp
Q no
tl l ~ "29
t
- t
"j`• ~f a' xNr
r,
i..ss d g S~
t{p5
` 7 ' l SX ~ l3 ;A n
' I l y', Y / b r.l': t~~tl ~l Ml1R
I i e s~ r
:oi
H.tjsanntaldc►cslcapld2
+a Ld f
~ x~d~ br P°t R~
..ars
n
t~
Y ~r Il I t j. cry t a3 ~Y ~I
S~
f
y~ Yn^ +7
31 f
tt - ~
n
t s
t; l ; l
;I1 t
t >
t
~e
PUBLIC NOTICE:
CITY OF TIGARD
OREGON
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. 309 (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 date by calling:
503-639-4171, x309 (voice) or 503-684-2772 (TDD - Telecommunications Devices for
the Deaf).
SEE ATTACHED AGENDA
COUNCIL AGENDA - dune 18, 2002 page 1
AGENDA
TIGARD CITY COUNCIL WORKSHOP MEETING
June 18, 2002
X5:30 PM
1. WORKSHOP MEETING
1.1 Call to Order - City Council
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. DISCUSS WATER RATE ADJUSTMENT - THREE-YEAR PLAN
C Staff Report: Public Works Department
3. UPDATE ON TIGARD WATER SUPPLY OPTIONS
® Staff Report: Public Works Department
4. DISCUSS WASHINGTON COUNTY/CITY OF TIGARD COOPERATIVE
PROJECTS WITH WASHINGTON COUNTY LAND USE AND
TRANSPORTATION DIRECTOR KATHY LEHTOLA
Y Staff Report: Administration Department
5. UPDATE ON DOWNTOWN/COMMUTER RAIL MEETING
• Staff Report: Community Development Department
6. UPDATE ON COMMUNITY DEVELOPMENT CODE AMENDMENTS TO
IMPLEMENT THE TRANSPORTATION SYSTEM PLAN
9 Staff Report: Community Development Department
7. COUNCIL LIAISON REPORTS
Qw
8. NON-AGENDA ITEMS
COUNCIL AGENDA - June 18, 2002 page 2
9. 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.
10. ADJOURNMENT
1AADMICATHY\CCM020818P.D0C
COUNCIL AGENDA - June 18, 2002 page 3
Agenda Item No. 15Meeting of 7- 9 - o 2-
COUNCIL MINUTES
TIGARD CITY COUNCIL MEETING
June 18, 2002
1. WORKSHOP MEETING
1.1 Council President Moore called the meeting to order at 6: 30 p.m.
1.2 Council Present: Council President Moore; Councilors Dirksen, Patton, and
Scheckla.
1.3 Pledge of Allegiance
1.4 Council Communications ar Liaison Reports: None
1.5 Call to Council and Staff for Non Agenda Items: None
> Skateboard Park Update
Parks Manager Dan Plaza and Skateboard Park Task Force Chair Rich Carlson reported
on a potential skateboard park location next to Fowler Middle School, which appears
to fir the established location criteria quite well. Both the School District staff and
School Board have given a preliminary "ok" to pursue this possibility. The site can also
accommodate some playground equipment, with future expansion potential. There is
a mobile home structure on the site; there was discussion that this might be a good
community policing location. Council consensus was to add this property to the list of
properties to be considered for a skateboard park. Council stressed the importance of
notifying adjacent property owners about the proposal. Noise mitigation options need
to be identified early on.
2. DISCUSS WATER RATE ADJUSTMENT - THREE-YEAR PLAN
Public Works Director Ed Wegner introduced this item. Assistant Public Works
Director Dennis Koellermeir and Finance Manager Tom Imdieke were also present to
update the Council on water rate adjustments. Staff reviewed a three-year rate
schedule with the City Council. A rate-adjustment resolution will be before the City
Council on June 25, 2002. Staff is recommending a three-year rate plan that will
adjust rates, beginning October 1, 2002, by 10%, then 6% each of the following
two years.
3. UPDATE ON TIGARD WATER SUPPLY OPTIONS
Public Works Director Wegner updated the Council on the status of securing water
supply options for the Tigard water service area. Two options are being studied:
a) Joint Water Commission - Tigard continues to purchase surplus water as
allowed through the memorandum of understanding. The Tualatin Basin
COUNCIL MINUTES - June 18, 2002 page 1
Feasibility Study work has been focusing on source options. A preliminary
report will be coming out this fall for Council review.
b) Proposed Bull Run Regional Drinking Water Agency - A consulting team has
been working with 13 participating agencies. Work has been divided into four
groups:
1. Engineering - what would be supply assets of new agency
2. Financial - a rate model is being developed to determine the cost
scenarios for participants
3. Governance/Legal (see notes below)
4. Public Involvement - keeping the citizenry of the Metro area aware of
the progress of this project
Mr. Wegner reviewed with the City Council governance options along with a
comparison of criteria relating to governance options that was prepared by the Policy
Steering Committee. After Council review and discussion, the consensus was that the
ORS 190 Organization was the preferred governance option of the Tigard City
Council. Mr. Wegner distributed a chart outlining the key characteristics of an ORS
190 organization.
It was noted that Portland Commissioner Erik Sten is no longer representing Portland
on water issues. Commissioner Dan Saltzman is now the head of the Portland Water
Bureau. It has been reported that Commissioner Saltzman is supportive of the study
concerning the Bull Run Regional Drinking Water Agency.
4. DISCUSS WASHINGTON COUNTY/CITY OF TIGARD COOPERATIVE
PROJECTS WITH WASHINGTON COUNTY LAND USE AND
TRANSPORTATION DIRECTOR KATHY LEHTOLA
Land Use and Transportation Director Kathy Lehtola visited with the City Council and
visited briefly about some of the various projects that the City and County are
undertaking cooperatively. Ms. Lehtola was appointed to the Director position last
month and shared with Council that she has a masters degree in geology, has worked
in the public works field for 29 years with experience as the "regulated" and the
"regulator." She referred to the importance of maintaining good interpersonal
relationships with staff and elected officials and said she enjoys the close association
that has been established among the Washington County cities and the County.
She responded to a question about the status of the Washington Square Regional Plan
implementation. Washington County is doing work on this project and the Board
action (ordinance) is on its 2003 agenda schedule. Community Development
Director Hendryx explained that the City of Tigard had primary responsibility to meet
COUNCIL MINUTES - June 18, 2002
page 2
a Metro deadline and Tigard needed to complete its work on this Plan before
Beaverton and Washington County could finish their process.
Councilor Dirksen noted his appreciation for Ms. Lehtola's Involvement in the
commuter rail project in downtown Tigard.
Ms. Lehtola commented on urban growth boundary expansion issues. Two-thirds of
the growth is anticipated to be occurring in Clackamas County in the foreseeable
future. She noted the need to balance out growth patterns to protect each area's
economy and livability.
5. UPDATE ON DOWNTOWN/COMMUTER RAIL MEETING
Community Development Director Hendryx introduced this agenda item. He
reviewed a chart with the City Council outlining the planning needed for infrastructure
and economic/business Improvements in the downtown due to the coming commuter
rail station. A meeting was held on May 13 and 18 people attended to learn more
about the commuter rail station in the downtown. For the most part, the response
was positive but there are concerns about parking and traffic circulation.
Councilor Dirksen is the Council representative on this project. He noted the
importance of communicating to the business and property owners what the City can
provide and what will be their responsibility with regard to business development.
The next meeting is on June 27, 6:30 - 8 p.m., in Town Hall.
The County has the lead on the project and Tri Met is also involved. Tigard will need
to give input with regard to station design and planning for the park-and-ride lot.
Council meeting recessed: 8:12 p.m.
Council meeting reconvened: 8:16 p.m.
6. UPDATE ON COMMUNITY DEVELOPMENT CODE AMENDMENTS TO
IMPLEMENT THE TRANSPORTATION SYSTEM PLAN (TSP)
Associate Planner Julia Hajduk presented the staff report. She gave background
information on the TSP, which was adopted in January 2002. The proposed
amendments to the Community Development Code are intended to clarify existing
language, implement TSP recommendations, address Department of Land
Conservation and Development (DLCD) requirements, and address Metro Regional
Transportation Plan Requirements.
Ms. Hajduk reviewed the significant changes proposed. The following were discussed:
Right of way width: standard and the skinny street option
COUNCIL MINUTES - June 18, 2002 page 3
Sidewalk location (The Planning Commission indicated it did not like
the sidewalk location requirements with regard to the requirement of
landscaping strips because of lack of maintenance problems and
personal liability issues. Council discussed this briefly and consensus was
to defer to staff's recommendation on sidewalk location; the Council
cited the pedestrian safety element. In addition, the Council will soon
be reviewing the possibility of implementing a street maintenance fee,
which may alleviate concerns about maintenance.)
Sidewalk requirements of developer
Access Management
Traffic calming
Ms. Hajduk reviewed the required notice to process the Development Code
amendments. Planning Commission is scheduled to conduct a public hearing on the
amendments on August 5, 2002, with the Council hearing scheduled for September
10, 2002.
7. COUNCIL LIAISON REPORTS: None
8. NON-AGENDA ITEMS:
> Update on Visitors from Indonesia: City Manager Monahan reported that
progress on the work plan with the Indonesian delegation from Samarinda City,
Kutai County has been going well. Sessions on citizen involvement have been
conducted. The work plan also specifies that training will be provided in
double-entry accounting, fee adjustments, and recycling. The group has
toured Intel and other tours to water treatment facilities and a landfill are
planned. The delegates visited the Tigard Library and were very interested in
learning more about how our library system works.
The delegation will attend a portion of the June 25, 2002, City Council
meeting.
9. EXECUTIVE SESSION: Not held
10. ADJOURNMENT: 9:05 p.m.
Attest:
Ma or, o ' i
Da e: a~ o
1AADM\CAT CCM\02061B.DOC
~-Lc GCS
Catherine Wheatley, City Recorder
4W
COUNCIL MINUTES - June 18, 2002 page 4
AGENDA ITEM #
FOR AGENDA OF June 18, 2002
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
ISSUE/AGENDA TITLE Water Rate Adjustment - 3 Year Plan
PREPARED BY: Dennis Koellermeier DEPT HEAD OK C CITY MGR OK
ISSUE BEFORE THE COUNCIL
Shall the City Council amend the current water rate schedule and adopt a 3-year rate schedule that reflects the
increases in costs associated with providing water service?
STAFF RECOMMENDATION
City Council approves the attached Resolution that amends current water rates.
INFORMATION SUMMARY
Chapter 12.10.130 of the Tigard Municipal Code provides that fees and charges for water and water related services
be established by Resolution of the City Council
The City commissioned a water rate study in 1999 at the request of the Intergovernmental Water Board (IVdB). The
results of that study indicated that significant increases in water rates were necessary to pay all capital, operational,
maintenance, and administrative costs of the water system. The rate study recommended significant rate increases
to meet anticipated expenses. The increases, beginning in FY 2000/01, were to be annual increases of 10%, 12%,
12%, 8% and 8%. Due to the proposed Taxpayers Protection Initiative on the November, 2000 ballot, Rates were
increased 3% in 2000. In 2001 rates were adjusted 15.5%. Thus, by July 1, 2002, the City finds itself approximately
3.5% behind its recommended schedule, and facing 28% worth of increases in the coming 3 years.
The Public Works and Finance Department staff have reviewed the financial plan and the major factors or imputs
to the rate model. We have concluded that the original model recommendations remain valid and should be
accomplished. The major factor driving the revenue needs for the Water Fund, continue to be increasing unit costs
and volumes needed of wholesale water purchased and funding our $40.7 Million Capital Improvement Plan.
An additional and currently non-resolved issue is the impacts of the successful Tigard/Tualatin School District
Bond Levy and the timing of the construction of certain Water capital improvement projects. Specifically, the
School District has granted the City permission to construct a buried water reservoir (550-foot Reservoir #2) on the
site of the proposed Alberta Rider School property located on Bull Mountain Road. This reservoir needs to be
permitted and built in conjunction with the school project, to avoid safety and operational issues at the school. If
this school is built soon, the City will need to re-prioritize it's CIP and construct a group of projects estimated to
cost $8.84 million dollars. To accomplish this the City will need to issue water revenue bonds, probably within the
next 12 months. The impacts of this bond sale could cause the need for an additional rate adjustment.
In an effort to minimize the impacts of these rate increases on our customers we are proposing two strategies. The
first strategy is to move the effective date for water rate increases to the fall, after the heavy consumption periods of
summer have ended. The second strategy is to adopt a three year rate plan that moves us back onto the rate model
schedule over a longer time period. We are recommending a 3 year rate plan that will adjust rates, beginning this
October 1, 2002 by 10%, then 6% each the following two years.
Water rate charges, including customer charges and booster charges, are as follows:
Current Rate
2001/02
Proposed Rate
Increase 10%
2002/03
Proposed Rate
Increase 6%
2003/04
Proposed Rate
Increase 6%
2004/05
Customer Charge
$4.00/billing period
$4.40/billing period
$4.661billin period
$4.94/billing period
Booster Charge
$3.54/billing period
$3.89/billing period
$4.12/billing period
$4.37/billing period
Residential
$1.56 per CCF
$1.71 per CCF
$1.81 per CCF
$1.92 per CCF
Multi-Family
$1.54 per CCF
$1.69 per CCF
$2.04 per CCF
$2.16 per CCF
Commercial
$1.81 per CCF
$1.99 per CCF
$2.11 per CCF
$2.24 per CCf
Industrial
$1.50 per CCF
$1.65 per CCF
$1.75 per CCF
$1.86 per CCF
Irrigation
$1.93 per CCF
$2.12 er CCF
$2.25 per CCF
$2.39 per CCF
OTHER ALTERNATIVES CONSIDERED
• Do not increase rates, which will cause a depletion of capital reserves
• Increase rates greater than the recommended 10%, 6%, 6% recommendation
VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEG
The current update process for "Tigard beyond Tomorrow Urban and Public Services, Water and stormwater
Goal lists a specific strategy of funding the first five years of construction projects identified in the Water
Distribution System Hydraulic Study at an estimated cost of $7.6 million dollars. These projects include both
System Development fee funding as well as water rate revenue.
N/A
FISCAL NOTES
The proposed rate increases are consistent with revenue projections anticipated in the recently adopted FY
2002/03 budget.
AGENDA ITEM # 3
FOR AGENDA OF June 18 022
ISSUE/AGENDA TITLE
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
PREPARED BY: Ed Wegner DEPT HEAD OK Ge CITY MGR OK
ISSUE BEFORE THE COUNCIL
Public Works staff will update the City Council on the progress of source options for the City of Tigard and
our summer supply status.
STAFF RECOMMENDATION
Staff recommends continuing to work on these water projections until completion or until such time as
sufficient data is available to make a decision by Tigard and it's Intergovernmental Water Board partners.
INFORMATION SUMMARY
The Public Works staff has been studying two long term water supply source options. The following outline
and attached documents will be reviewed in detail during the workshop session.
Joint Water Commission
0
0
Through our memo of understanding, we continue to purchase surplus water. Presently we are averaging
less than 1 mgd.
Tualatin Basin Water Supply Feasibility Study
® Work has been focusing on the source options
® The hydrologic modeling has been started with the collection of the stream flows and other related
information
0 Work continues on the Sain Creek Tunnel element
Proposed Bull Run Regional Drinking Water Agency
a A consulting team is working with the 13 participating agencies
® Work is divided into four groups
Engineering - What would be supply assets of a new agency
Financial - A rate model is being developed to determine the cost scenarios for participants
Governance/Legal - Please review the attachments as our discussion will focus on this area
Public Involvement - Keeping the citizenry of the Metro area aware of the progress of this project
Public Works has been involved in other water supply projects, which we will also discuss
• Aquifier Storage and Recovery (ASR) we will review the injection process, discuss a couple of turbidty
events and what are the next steps
Beaverton Intertie - We will review the status of this project, which could enable us to get another two 25
mgd from the JWC, if water is available
0 Summer purchasing and conservation - What we will be doing to ensure a summer capacity and highlight
our summer conservation program.
OTHER ALTERNATIVES CONSIDERED
We are currently looking at all of the alternatives known to staff, with the exception of the Willamette
Water supply.
VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEGY
Securing a long term water supply is both a City Council and Vision Task Force Goal.
ATTACHMENT LIST
1. Criteria for formation of a Bull Run Regional Drinking Water Agency
2. Alternatives Governance models
3. Comparison of PSC criteria to governance options.
Each water supply option has it's own financial impact on the ratepayer of the water service area. We are
not far enough along on any of these options to develop projected costs.
All water capital projects are budgeted for in the Water Fund.
J
CRITERIA FOR THE FORMATION OF A BULL RUN
REGIONAL DRINKING WATER AGENCY
Approved by the Policy Steering Committee
April 25, 2002
In Phase I of this study (May-December 2001), there were 17 suggested criteria to
take into consideration in studying the creation of a regional drinking water agency.
Those criteria can be found in the Phase I report titled "Progress Report Regional
Drinking Water Supply Initiative, December 12, 2001. (This report can be found on the
Portland Water Bureau's web site at www.water.ci.portland.or.us then click on "What's
New".)
In this current phase of study and development (February-September, 2002) the
Technical Advisory Committee reviewed those 17 criteria and suggested the elimination
of one and modifications to others. The draft criteria were then recommended to the
Policy Steering Committee to be used when reviewing and weighing governance and
financial options that will be developed as part of this phase. The Steering Committee
review and discussed these criteria, took public input, made a few changes and approved
the criteria at their meeting on April 25, 2002. The criteria are as follows:
1. The proposed Bull Run Regional Drinking Water Agency will have responsibility
to provide Bull Run and Columbia South Shore Wellfield water to its members in
the amount requested. Others may join the agency after the implementation plan
is complete.
2. The proposed Bull Run Regional Drinking Water Agency will develop and
protect the Bull Run and Columbia South Shore Wellfield.
3. The proposed Bull Run Regional Drinking Water Agency will have a reliable
supply of water to meet current and future needs, with backup supplies to meet
seasonal and/or emergency needs.
4. The proposed Bull Run Regional Drinking Water Agency will plan for and build
capital improvements to meet the amount of supply and transmission needs of its
members as requested.
5. The proposed Bull Run Regional Drinking Water Agency will be responsible for
meeting all applicable State and Federal laws and compliance with drinking water
regulations to the point of delivery.
6. The proposed Bull Run Regional Drinking Water Agency may contract for the
sale of water to non-member agencies.
7. The proposed Bull Run Regional Drinking Water Agency will have the authority
to provide any water related services, including distribution, as agreed to by
individual members.
02
Adopted by PSC on 4/25/2002
, .6
8. The proposed Bull Run Regional Drinking Water Agency will be created under
Oregon law to have the full and usual municipal powers provided under Oregon
law, including but not limited to the ability to set rates and charges, collect
revenues, issue debt, hire staff, and enter into agreements.
9. The proposed Bull Run Regional Drinking Water Agency will be created under
existing Oregon law.
10. The proposed Bull Run Regional Drinking Water Agency will make the most
efficient and effective use of its water sources to meet the needs of its members,
consistent with sustainable development, best management practices, and
integrated resource management strategies.
11. The proposed Bull Run Regional Drinking Water Agency will be an enterprise
utility, obtaining its revenues from rates, charges, and issuance of debt related to
the sale and delivery of water.
12. Each member will have representation by elected officials on the board of the
proposed Bull Run Regional Drinking Water Agency.
13. Individual customers receiving water from the proposed Bull Run Regional
Drinking Water Agency will have direct access to the agency's Board of Directors
and to the elected public officials of the members.
14. The proposed Bull Run Regional Drinking Water Agency is intended to be
organized and operated to minimize duplication or inefficiency.
15. The proposed Bull Run Regional Drinking Water Agency will participate in the
programs and activities within the Bull Run and Columbia South Shore Wellfield
watersheds.
16. Creation of the proposed Bull Run Regional Drinking Water Agency will not
result in increased overall costs for water by virtue of combining infrastructure
and operations.
02 2
Adopted by PSC on 4/25/2002
- i •
V
i
a
RJi ~
a
G
L
Z mro
p j9
y~ s
o ar
NN
m
c p
0 0
-d u
L~ a2J •O N
4! ar
.
! N
Vf L L
m ro 0
" 'OO ro w
E
d
-c- C O
O Ld
m
p
M
o _
E
c
E
~i mri
T
°
y~
tO a~
a °
c
:D N
N
ro c ar
o
3
0cLU
.
o•E
FF `a $
~ioymG
G
a,
E
a~i c-p o a~
t Nno3m~E
c x
~°c>oL~
~
•
cc -0
'
3
cF L
b)
v >.ow
n
'a u ° -
X E ro
q'
2-0
m
LA
3N r- u
o='o 9
E
•
'
5~
'
'c
O
0 600
o >
€
~
`O3
o~ccQaL~
rom0 Lao
~o°n.oaj
c o
c
47 0
c
j; 3. c
(b
> =v ei u
t v a u u
L
~
L m~s 1
-0 7
u
> C ,p 7
V `V vii N
y
N
d
N 'U OC
o
'u'~~
O
<
> ~a°a
i5 Oo~$
<
ZA~or~vro
w0 3
:E
0
a,o
o O .0
-
O
V
w~10 ua
O
~
g
3
°
to
N
ro
:
-
~
m
Z
.O 0. A o
I,
o
~
)
o 0. A
O R
t
O
C r4
c
p n-n 6o
o$~
°a0
c
m
«
L°c>' _ 3~ c
E
f
~:u cc
C.6
3
. ro U ~
a 40
5
°i 2 a
E
c
0
c
t
° o
r
o
~a
n c L
c
o' ° ai
2
3 o
o
r
$ N
c o w_ 3
r.- v
a3imu
~o
U•0
L0
CL
12
:3
°
R(5
° ZE
w
m
=
r-
a'rorooom
~orfuum
0
CL
~'~c'
c
°1
b
ri~ a1
O
u
c
to H
E•
m Z. C
I
o
m
n
0
v -C
V
c
;
°
v
°
;aim
o
o E
,a
0 m
'
o
cd
°a~
N~:N
g'i
y
o
> o
3 -z
u c
m
-2 O
w v
c
« a E X
, w
m 'C'
c >
E'
n
o
.
CL= c
19 c~-0
~Ey
E
w (U
:2
pU
n
3c
La w
?
E
E N E '
LoN
1= 4
y n °v c
L
.
E
rv 'a$~
T
di
> E~o
A
L°
=boo
wt 27
S 3 °
:3 c
C.t-. '
o
0 °
v
v ro
LL` c
°
t
o
.
_p
-
3
N>
E E
3
v x V :
A.E
CL
cu a
0
0r- cu
°
i
a
O w p
y
~
c
o
O
c
a'
a x oi
o
c 19 E
c
p
D
an d
o~
vo
v
'C O '
t
o
o
p
y
s
j_ N V ~
p is p f
u
>
o
> > t; an
i a;
E,,
-2 c °j
A orv
t0
c
'ci o a: f
~L° °mro
0
0
vC
- -Z
0 ~ o E
0
i
3
o
ro
c in '
c
R
NooL
p
O~° 3Z
0
0 Q
-8 a0
a
12 C4 o w
EFn~ -'u V
CL
ro
Z
c
°
E 0
3
d c ro
rv° o y
- ~'3 a
d, v v
4
L tO a
v~
3
°
p
0 u0 n
N
ro
p F
c to
O cu
O r 0
Y
O O
n1
0
E ro
0
0
~
c
o
L' v m C
ro a o
o
v
oa a~ t0 'O v
m ~
v
O
12
rn•
ac o
ja
i
Y
E =
'C ~
v~
o c o
v 3No
>
0 rn°$
v>_c
yam, ~i'u
:fro
S.°uaNi
E E c o
L
c
>
.n ~s
c
N
w ~O 3
AA'u
i j
a
~A
Ey°p
.0 7 O
m°m o.
2
E y w to
EE va' E
t A
V OCD
c 3mc°
c
C N
Lac ` r,
~+mo
L° ,ma
~
gg~ c r
3 c
E u L° w
V d-0 ° -0 E
mro g>
-
m `U ° n> °
O v c~' Er n~
c
~
O ro lj C u
-0 c v°b'
5 t ~a c
'
s w
r
Q c
E Q m° , E u 4
i
`
c c° c v
°
c
b° ° 0 'n
; o EE
'
N
O
. `
O p
~
v 5 a
m y o T'G -
>.'c y 3 c
ro O
C N
« tu.. b m
N r>a
00
Q1 C E Q€
O C N A
B
ir
O c r'
n t
°
'
^
C
12 C
C in 3;
`
_
`7 -0p
n a/
L
Z
? o a
'
° c°
o• o C
_
_
_
n'
b d° v
y
e r 3> ~2
° 'a
a) .
> e en E °N'
ro
a
c
D ow
-0 ro ; d"
Q roro n Y
O o.
d N c, n
O-0 -0 nro
3 co N
T O
c o n S E~
3 o V 0'
o u u 3 0
N
O
N
N
N
O
O
Q
Z
W
y~ {Y O N O-
C C dJ L
3 p Q co 7 Aa .5
p
Bo Cc;
r 15 4) -a 102
o" L
, _ ro c
E ~
c -oo c v
u ro o m o~ o> 3 c ffi 0 0 - 0
cow rot: cooeo cc CL to 0tv'3 } Ecru 7c
> o
'2 M CL CL CL CU
19 ~J EL ro p E o ro 'P > b °u ? o
co r t!
n c a < a E ew b oL m° a m ou E 'u aCi ~B o0 0
° v L''u m-6 3 0 v.c C7 75 4 0 5
~
v~ c C o7 N 2 3~ N rya d •0 c 0 2 7 'c.. > LL` ,-Yn a; .a w u 0
o °uv a i- E o °3S o 3 f or _°;v°1i°v;U oe A@ A
0
7 !J
a a~
-O v
a C 3> ro a
t a ' T
N' 25
ILI, .x'
00:6a cQ v~o~
00a
f ` CL -8
o
m 7 coo cvaj s0.c
~y. o c aZ ' A >U n0 i~ > o
4.; c r G. O 7 7 J .G •D
C I f9.! p m q p -•pn > .~1 D Cl ty
7•i'j ~•i''• U o .V Z' 07 E
bo 7 7 C! C •p• lOJ ~j c E
CL -M
Z'O 2E cu LU
C
O 2 w
O C - t N ° N •D d
a.R. c0c c C~ a 3E ° ma
Ac *
7o E L 0 3 w c o V y N L°
CL .8
v
m 2i
0o p n c c .n O c a
IZ ti•:f r. ~ c 'C a' c m o o > •D O a di Y• v J o
j3 -0 -0
IOU n m
B -r EL m x 3 D 0 co
Q, ma m m Em-9 N 0i w ma 0 C~ cJ E
v o = o O> Or- B
d; -8
r. a v
L > V N y `
c o c ro n m m v N
°u S'0 a O U E 2 m~ 3 E J vOi Ln U oL 'v
:r. n71w
G'
O
l.i+'C v n c° 0 D m o N 3 0 V. 15
G; C m y o r N a,
v arEi c 0 •c ° c m> On v 'u 'm c c>
Ln 0 c 0 a 3 .L rv a E Y a~ > ro m
CCPL -0 0 CL
xo2.60 .8c
0) L. °0c~>c
K CL)
O -o
O. O 0.~~ a c 0 E 0v 3 0 5 7 Ln ms
U m V W 7 c+ .n is N 0 C
E > -r- x c m _ v> 0 3 D c o
•?vaa EOV_°caci }i-0'~ a°
0 m c o r y .c a ar o 2 E E ~ a
f~ co pop a~ 7t ~EQ Q ~o A~ O e"i c J Ea
M 'O •C d O r0 " C d O l^ N od
V N
.id. m x V L 7° N 7 C' O CL 0 X of d c'
O n a m E E o b C.4Z - o m m > of J .n ~n U
Q
c c o a`i •a o 0 w rv C A o m vx d au`i `o E .mn l~
O.O m O V N E E- 0ClDA~ 7 7 A r, m S~}' o/
tko 0
c x n m •n C c L 0 c'iq a w c 0 E E :cd E 7
00 a0im °LL0°cicc<e.m-~cc72waci > Ld ° H
c 0 0
m o. .a F ° u° >~i E } a' c ON
c o f ? c E 3 c.j 7r Sis > aE Ea+ d oovc } E 3 E L o
U
0i 0 c c O o
E 3: z:- L
A o c y w y° ° ami a c E N CL b D a La ~ 0;~ Eci n Q~y
°~.5n a ~a~OT ~E~~°r`L`0 ccgocoJ
>o'= >aci EPEE>acicawv0ivwiU EYv
_8 0
0= w n a ~r ° c c° Z ro o A 0 c c a m 3 N w Cie
io'u~~,o c~.2ccc E ~ymo~ooa Oar ~Scv B
i > C7 = N E c z
n7 .C E ° c v 'E 9t E 6' E C o c r+ ac T]
r~ c 7 C C m 7 a 0 E > v N m
0 0? E ai ~ c at c tp' aociy r O N> E'er = u r~ o N as (u uu c
(U ;q ME c° ° 'O ruo ? x < G a s.. m o ia..? a = is oC U n ~J
W
D.
1
Es,
{t
~y}~r1;ri~j i ~ ! r I
r
O bi o 4) Sj y9 c
`~E 1 ~ 1 -0
N
mo ::o
c ro f o
FF < c~ n r~t+ 00
o
?i3 a& 5 3 E n71°-a70 m
cri°~
CcC tom oOC
yy
roro ~1 C .N 00
i' N La
61
0 7, U w C N G
G
a. N
ro- c o b
c V L n l.b u ~ w c-
r:
b Ea0uW0g N c,0 o E. t oa
3ro $2 E.S~Su 0E of-a.Ow > o
c
t L^ Ou v
~ c b ~ c a
7 0.2 ..0..0
~i
.C L 61 N C O ro } N V
C E C C O y d C
Eo 9'T E T c b c 0} }
` LS O! •i0 -pd 4
Q O O O O L y C D o wCL " '^E o~aui~i c
bo cu
L c W 7 L+J ro V C O
q'O N A C C N b C.O gy1 y O.O
3 L 0 O. w E d F CL O W > O
~ ~ CCO a.. C
O O
y 3 rJ •O ~ w E
D
_0 m c ° o
M c o > i
ro C C C N
c c aE N v
o a r-
'0 ° c"o N .n a 1 m
> C 61 N C O
}
c 1
v E?+ v~ c
EE -u ro r' I a
7 V E d c o
~ ~0 cu = (U o Y, a' 1 A
E c to E v a V ro m c
,v_ u c o
A to
3~ v.5 ro O E a~a0w >
0
E
v N y o i>F, e0
O N ~ y'D > v~ T C
~ v •e~ mN
o> 0L O ~
v
0 e? E-
ID
5v.;2c E rvac
m -
< c } a a/ 3 O
cc ~j6 3 8 N a
c y o0
E r co,
v o
E a t5 S w A `a v y c} 1 1 E
c 7 'v t 1 0°b o c
c ci
y c $ v
v a c ~i E b ~`a 3 y c. °u 1 0 ie
CL c 7pc
O m aim `da0/Lm CJ~o°1c2
ri C
C 7 'C d 7 y E o %J 7 ro u J u C 0 O N
0 o c r o y L aNi u 2 c -0C 13 y`' r+ N E E
CL o
c °C ` Q1 O
< °v a8 ° o ° o E' a1°-- ? V
en
N
O
N
N
Lf
O
D
ae
B
Z
ua
ed
a
O a N
O 3
°
d D
U
cu M
q
iv
c 3 u a~ c - E'E o E
ro c Ear c ar
« ffi
~N~i
w ~
~
c
°
o
c_
i
u_
12 '1
0
0'~O 0
O~•d-` o•n &
O n~-v `a~Oyy OC
C C C N
°
A
0 c D o E CL 's o c c L o
c ~ H p 3 a' 3 x
c o N ° c > ° ~i .003 _ c - L0 ro o y
E~vEc°'~o•;Ecocv3roeL+•cu, Eo 00ia
u u aroi n w= € cr `t 3 u E
E E
€ ° E >'u d
_
.
i
0
15 Evoi~dV u0i<
o33a3o0`ow'ac,V)
U1-0 on w° u:3mM
3 c ~i
aci
c ro
O o q n E aci u
y 5 n ro c - P g 0
0
E
0 E
3 0«
.
Lu
w Ln O u C O N' C is 3 O. n
ro w
C
E `p N
C
C '
y t
C
N
01
L L ai
U W
C C
ro 3
v~i
°
C O
b
C
O
N
> > _
a
~
N
'
o
g,
y
,
° 3 x
a M
N ~
°
o
: a c o
.
moo
X o
v
-
X
o
w~ AY
~o of c
~
o n
,
wc
Y
uo. c aia
°
v
c
a wU0 vi
< 0 3 °
3 o
n u
it
O
w a
sa
> p
y' j,• C V •1
0 3
y Cl ro
o c c c v 2i 3pp N ° n E m av
aJ y n'W C H O 4? M 0-0 'C
L
N
E °c r- E
3 0-5 w
_
N u 00 o W L. a^' a s ~ o 0 o m
o
>
n
Q c - _
0 c
d
°
a 0, N
P
odo L; co u o
CU
m z c A 3 o
0 CL
p CL 0
O C i
C
E X
V
o .0
ci
L
, V°
a c r- N
O
C
00
O N C
c 7 0
A A u O OO •r-, co=
C >
j C O O
0 3
6x1
w Ld ro o
N
_
i
oU.-oc 0NC3g~Lic° m
E o L' E c° E. f c o c
~ ~ d x~ M% L
X
pv a,o
-c E a d
,E Y y
.
o E> o v E L« c_
o _ = W= E c c
A
c
" O
~
~ 3 °uQ! E~
W
N V
C
E in a v Q 0 3
U U L 'O n w u M
_0 -
o
0 0
i
O 0 0
c
c
c c
cu ar
ro u
~
E Z'
N n d 0= C c 0 L 'O
r~ c 0 O 3 O
o w 3 00
c
'
O C d r
O
o u
d
° c
0 r- 0 H d
3
«bb Tv nn E ~i n v v o a
v C b C O C 1 C E-
C •O
°
c E
O E
a~civi o
M
~I oti `y `No rooOeL'ar- ro O c
3 ly-'-..
V (U
dS°°`o c?a o"EE0Z
E
aL~«~
E
" ono 00
0 c •N c 0
0 0 € a`~
o u c 3 °=i
_ •N 3 a Z ° c s° n". o - y
>
v`°
m 8
; ro c a L
r, E vc°
E
oQ._+N
~O'>>o
^'3
0 ~
'c
- L
°
LacCc
w
a
v u E u v
O
u u
ro~ g
o E c
o
, o `ro v
w O u"i L x C L O
l
1
v ai.
u
U nU CL=
•
=j
Z ro
0
W V U N C 1'O Q W n 3 p W d v`
• • • • • • o •
3 W O W C C
• •
C ai o
v
c v ar ° °o~ c o
2
°
r
C
ro N 0
C
L >
«,I
o j J,
~i v c
fC
' E N
u c tO
'
,v
of c o J
U
~
E o E E= 2 u S o .y V o
c ro u 0
n = y
a
'5 a) Lo -0 V, Go
u ro ~
0 0 a' > ° n c o E~ c > 0
« a`, v y ° y ~La ai ° ae a a
n c v
i9 t E ~
r9
6
0
u3>
E
O
ry c
-0 u
O 00c ~p N 0 O O C 3 p 0C: G" N N L O
n > 0 o a~ Lp n 00 = c ° 15
o V
'
r o E •D
P
a' E no ~
~ a`i ai s v' «
c
`
E
a
i > ,
r
v (
M
10 E y E
n 0> ro- 3 E=' c r ar c a ar
s W w z m E V A 12 ro 3 d O 3« J
`
`ff
o
°
t ro
.D N E
L W
g; 1
06 ul W
r0
~ cue
ro o ~
E
o~ E
° ro o
-0
ai L^ 07
c
c E y
a~
E o
N w C
_
D C
Id d
u
El ro
E v 0o
e.c
> u
O
T
a
N
ai y~ ro
C
u
j
O
E
C
~
o ~ ro
°
o
a,
3~«
G
O
° -0
o
..u
67 T V
O n C
ro y y O
i~ k)
" O
n
L
.G
o c E ro
w Lj
m ro
W N
~ • •pa C
ro a 0 v
ENE-O
0 ; 0
a
L'
0
ca/
0
N L
~
L0 0 a,0
oai
o E
C 0 r
c a
Li N
E'
O
'
0 0
°
0 C O
c a~
E N 0;9 B N
y
CL OJ N a N C
od
C
q
m
n« a
Svva,EhN
c
va'c« AO
y~i°u yEE3
E g E m c z
Eo OcL+
:E W.2 w E
rx 0-9
« O
M
to
r
a
f
z
a
W
0
o F
O
N
H
Q W
F
F
~ U
~ 1zN~
1~1
W
^^W
U
z
0
a
O
U
°
V
a
t
~
Z
Z
o4p
o
;
Z
H
N y
-45
°
"
o
~
y
o
b
O
pp c
y
p
p
p
v
3~0
d
as
c
u
y a
s
~w o
U o~ oz Lq
o
z;a
0
z
0
z
s
" r7 g U to
~/1 cVa
O
o w a~ 1) 41 > k
°
a+
a
O N ,y
H
°
a~
a
b0 a~
i
bA a~
i
c
3
•
p
~ Er.
v p
'n
°
yo
y° ~
0 1=
y
O y O pQ gN
O ccp~
~
v' O
~
A
C Y•
a0
° b 4"
p,
id~ ~
N
~y a U
bA
~i
o I
~~~ooo
rA ID
° 5 w> q (Q a
Fr 'd
Z
z
Y
w!
b 3 , 4 O aNi ewe q vi
-0
v y
g O
O O y"
0
>
IV
a Sow
ao4° o >
o
o
o.o
,
U w °¢Q oA.0 3 oQ ra.
zb
z-a
u o ;,•o
a~ a~ a
~
a~ V]
p ~ ~ T
~ a ~
~
y
ca
~o
a ° o
am
;
~~J
oU
"pad
o
"
b ;y .d a'i O
cd V .14
W
Q ~
4. 4.
A
a
M
0.0
0
a
w
w
O
C7
O
N ~
O
N
w
t
~,4 U
O w
H
A ~
O
z v
z
a.7
w
w
a H
U
Ae
O
O
rO
N
b
q
+
+
u
a+
p
U
p
U
~
t~
z
z
¢
H
z
z
U N
U N
~
U U
z~
z~
¢
H
z
z~
C
C
~
C
~q
b
a.
~a
•
'
vf 4N
Vl W
N
H
y N
zb
za
¢
z
z
U
U
.d
'Q,
U
~°E
d0 E!
3
~a
E
•
In 4)
N U
~
N
F
ar
y
zb
z
a
z
z;a
20
ti
co
00
°
a
a
a
~
°
n~
a
i
dq a
a
i
a
i . w CC3 o
° on
Q
a
i
zv
Z;
Q
U avU.n a
z
z~s
am, a~
O
°
b b
vl
o n. a $ oA
o°0
°
° u [
y
C's
cqs
„
w
1
,
0
O N
y .~i
N O
w N a a Y H
'k
~
4,08
0
Q '
er p A, ~
-0
U
H .`R w ~ :n
t° f0
-
l0 y
p
'C
ed 'C Oq ~n 7
'ti
°
•D •O
p
~
y b d
~
~
~ ~
a
~ N g~ U
9 u
N~ G1~ N
"
N
is
E) y a~ N
y o U
~
a~
`
o
3
u
w y .n v
V CO
0
0
,r .
i
°
d
Ai
o
S
:
v
v~ h
~
a
o
U
~
a
v u v a
5
a4
A
1--1
a
z
O
1-0
O
u
N ~
N
t
® W
w
a ~a
w
V
a
a
O
O
5
V
O
Q
W
ed
U
id
O
~p
•
bbAA
'q ca
~
y
y ~
z~a
y
z
y
z
'.y 1
.
~
z°a
z
z
.
°
q ao'
U
•U" U
~
U
U
~
t~
'
U
tL
" U
.
V
"•Oq,•A p
N
N •fi
d~D N
:F•i
e0
U U
'C! CC
s
a
~
z
z
zap
z~
za
.
z
y
.fir
H
13
a
° U
y
U
U
C
'
U
U y
4i U
~
C U
3
bbO U y
.
w
'
N
•7 N
y y
0
y U to
0.
N
N
;
.
+7
3
a
z~a
z
z
z
a
z
z
.
y
Li Q
U. U
cs
yw ~
w,;=
~
~
a
wpm
a
w~
~
~
b
'y ~
O C
O
a
i
N y F+
O W 6)
i
Eoa
•tn C.~,,
O 4.i
;
a
~o
y ~
O.
~
Iii
O O U
a
zb
z
zb
z
a
zb
z a.
CC
c
a~
g
•y ~
a a~
3
y
CO
u _
U
t.., U y
V;
H" U
w v
bA O U
0
L
o w
a
o a°'i a
o
b
o w
zb
o o
z-a S
zb
zb a co
z
-
~
0C4
b
_
Y ~
.
> r.. U
O
Ca O
-o a~
~bo
y
CO
a0i ayi cOi Z3
a~i a
° o cOe
p G
°
O c
C's
~
5 g
•5
U U V
w.
q o
U a~
7
b o.
O ,
Iq
Ei .o
o
?
.o
'o o b „
pq.
dD p
o w 'Z:
O.w
a> 3
'
z H
o
"i c. c
boo
o
Cq ~
3
u o
~ U 3
a
~c o o
u u 0
=
Q
@ C.cl 19(o2 C.61vy-,C;
Key Characteristics of ORS 190 Organization
Characteristic
Explanation
1. The parties will have a high
The agency is formed by a written agreement that is negotiated before
degree of certainty what the
agency formation. (Since other governance models involve election
agency will do, how it will
of independent board members, ultimately only the Board members
operate and how costs will be
can determine how the agency will operate.)
allocated before the entity
starts.
2. The parties control
The parties will directly appoint board members (Other governance
membership on the agency
models have directly elected Board members)
Board
3. Clearly assures maintaining
An ORS 190 agency by its nature is the legal creature created by
the existence of existing water
agreement among the parties. (Other governance models derive their
supply entities
power from statute and statute may dictate that some existing water
supply entities will need to dissolve; or the agency may choose to
take some of them over
4. The parties can dissolve the
An ORS 190 agency by its nature is the legal creature of an
agency relatively easily
agreement among the parties, so they can dissolve it. (Other
governance models derive existence from statute and are very
difficult to dissolve.
5. Agency can be limited to
The agreement forming the agency will dictate its scope of activities,
dealing with drinking water
which can limit it in almost any way the parties agree. (Other
issues
governance models derive their scope of power from the underlying
statutes. Some, such as a PUD, could operate electrical utilities and
others could operate stormwater and wastewater utilities.
6. Citizen-passed limitations on
The ORS 190 agreement cannot change local laws. (In other
local governments obtaining
governance models, the entity may override or ignore such initiatives)
water from the Willamette
will continue in force
7. Does not foreclose
The agreement can provide for the agency to transition to one of the
opportunity to transition later
other governance models. (Other governance models do not
to another governance model
inherently provide for transition, or make such transitions easy.)
8. The parties can be the owners
This can be negotiated in the agreement. (In other governance
of the assets of the agency
models the agency 'owns' the assets.
9. The agency's ability to act
The ORS 190 agreement cannot negotiate away powers that are
may be constrained partially
reserved by law to the respective governing bodies of the parties.
by the underlying charters of
Existing agreements have found ways to accommodate this issue
its members
'`trough procedures adopted in the ORS 190 agreement. (Other
oN ernance models do not need to conform to the charters of the
existing entities because they are independent units of local
_
government operating under state law.
10. The parties remain liable foi
This is inherent in the law that allows ORS 190 entities to be formed.
the debts of the agency
In other governance models the agency itself is responsible for debt.
1 Note: A Metro MERC-like entity can have some of the characteristics of an ORS 190 entity, but,
ultimately, it is under the power of the Metro Council. The details of how such an entity might be formed
have not been analyzed.
L) - -
AGENDA ITEM #
FOR AGENDA OF June 18, 2002
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
ISSUE/AGENDA TITLE Discuss Washington County/Ci of Tigard Cooperative Projects with Washington
County Land Use and Transportation Director Kathy Lehtola
PREPARED BY: Cathy Wheatlgy DEPT HEAD OK (Ze& CITY MGR OK Gu'~
ISSUE BEFORE THE COUNCIL
Discuss Washington County/City of Tigard Cooperative Projects with Washington County Land Use and
Transportation Director Kathy Lehtola.
STAFF RECOMMENDATION
N/A
INFORMATION SUMMARY
Kathy Lehtola is the newly appointed Director of Land Use and Transportation for Washington County.
Ms.Lehtola will be present at this meeting to give the Council an update on the status of various projects that the
City and County and are undertaking cooperatively. Those projects include:
1. Commuter Rail-Tigard has a great interest in this project where the potential benefits to our
transportation system as well as the benefits which will be brought by rail stations locating in the
downtown and Washington Square.
2. Washington Square Implementation
3. Continuation of the Intergovernmental Agreement between the county and city for planning and
building services in Bull Mountain.
4. Annexation potential for the Bull Mountain area-Tigard is considering going to the voters in
November 2003 for an annexation plan for Bull Mountain.
5. Urban Growth Boundary expansion issues.
6. Goal 5 coordination by the county and the cities of Washington County.
OTHER ALTERNATIVES CONSIDERED
N/A
VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEGY
N/A
ATTACHMENT LIST
None.
FISCAL NOTES
N/A
AGENDA ITEM #
FOR AGENDA OF 6/18/02
ISSUE/AGENDA TITLE
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
PREPARED BY: Beth St. Arnand DEPT HEAD OK
MGR OK
ISSUE BEFORE THE COUNCII.
An update on the May 23, 2002, meeting with Downtown property and business owners regarding Commuter Rail,
and upcoming joint efforts to prepare for the station.
STAFF RECOMMENDATION
No action necessary.
INFORMATION SUNIlVIARY
Washington County-along with Tigard, Beaverton, Tualatin, Wilsonville and other regional partners- is
planning a Commuter Rail train system that would carry commuters from Wilsonville to Beaverton beginning
in 2005. As part of those plans, downtown Tigard would have its own station.
On Thursday, May 23, 2002, the City held a meeting with Downtown property and business owners to discuss the
Commuter Rail project and how it could benefit Downtown. Councilor Dirksen facilitated the meeting. The 16
attendees heard presentations from Washington County, City and Tri-Met staff and were able to ask questions.
At the meeting's close, the attendees indicated that they supported further meetings. Plans are now being made
to meet over the next six months to provide the County with refinements for the station plan elements and park-
and-ride traffic circulation. The timeline reflects the County's need for this information before final engineering
takes place. These meetings will also examine possible infrastructure improvements, including pedestrian and
vehicular circulation.
OTHER ALTERNATIVES CONSIDERED
N/A
VISION TASK FORCE GOAL AND ACTION COMMITTEE STRATEGY
Community Character and Quality of Life/Central Business District Goal #1, Provide opportunities to work
proactively with Tigard Central Business District Association (TCBDA) businesses and property owners and
citizens of Tigard to set the course for the future of the central business district.
ATTACHMENT LIST
Attachment 1: May 23, 2002, Meeting Agenda
FISCAL NOTES
N/A at this time.
\\TIG333\USR\DEPTS\LRPLN\beth\Downtown\Council 6 18 02 ais.doc
Attachment 1
Agenda
1.
Welcome and Introductions
Craig Dirksen
6:30-6:40
2.
Overview of Commuter Rail
Washington County
6:40-6:55
3.
Downtown Station
Tri-Met/ City Staff
6:55-7:10
• Park and Ride Location
4.
Virtual Tour of Rail Site
City Staff
7:10-7:20
5.
Refreshment Break/ Review Station Drawings
7:20-7:30
6.
Commuter Rail Discussion:
7:30-7:50
• What opportunities will it bring to Downtown?
7.
What's Next
Craig Dirksen
7:50-8:00
m
Lm
CD
0
Q
Lo
N
C
Q
E
6
a.
O
•
pd
O
a
d
WWI'
@c
co
~
.
c
0)
a
to
n
r
c
o
c
0
L.
M a
W
m
LU
e
o
0
W
o
CL
®
E
-s
C
®
'M
V R
d
4)
d i
c
L
®
c
Id
+a°
fi!
d
'C ®
C2
Mc
C)
®
d
N
.aC m
c6
L.
M
M
L-
d
-0
IL
,
c~
E
E
O
CL
C
tr,
C
CL
I--
M
e~
U
AGENDA ITEM # w
FOR AGENDA OF June 18, 2002
CITY OF TIGARD, OREGON
COUNCIL AGENDA ITEM SUMMARY
ISSUE/AGENDA TITLE Development Code amendments to unplenwnt the Transportation wstem rian
PREPARED BY: Julia Haiduk DEPT HEAD OK ITY MGR OK
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:1rp1n/ju1ia/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.13 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 maior 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 clarifecation/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.x.2) (Staff clarification)
Provide the City engineer with a say in approving street names (18.810.0301) (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.6.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.8) (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:
8.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 I
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.0301 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 froth 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. der -collector or arterial streets shall be
considered only if there is no practical alternative way to access the site.:__1f.d_irnc__cces-~s
pertnitfes! _tthTy Cty.Shupp) icant xllCl~e refired lo_m.iti ate fQr agy__salety Qc_il.igh¢arl~ood
traffic-Allan a 'r,emcnt__ M M_ impacts.- deemcsi_. is ble._ A4c_ Cjty_.-E.n~' or-1bis_ma .
ixtcl_t~do -~ut_will noS be lirttited to the co~strstction~of a ~eiticle tuntarottnd oa~he site~o
eli Wn,ate._1be_t&Qd_fbr-a veh.ic.le_ta_I►ack_ouLontQ the_r_oadw,~x
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. N-4. - etn__cat
An~cs~es~report~halLbe_st~~aniSSesi_rvit_I~all_n~vsievelo~ztueat_p~p9sal~vvtiichveciFe~e~igt~
o~drive vys'tY~and stzeets_are safe bYa►eetinQ ad~au~te.~tas;kin~L~esl~ sight distaac~actd
deceleration standards as set by ODOT-Washington Cou : the City and AASI-ITO
(debending on jurisdiction of facility.)
2.__Dr_ivowaxs-shalLnot be_germRued_-t_o_he placed_in_tl~e.inlltaence._area ~£cQllectQx_ot_arte~iaLslxe_e_t
intetseciiat~s,__influettce.re pf_ante.csectlatis is thaLnFea where slee~ae Qt~raff c_catnmQnly
fszrm_~pnrsza_clt,t~_an_i~tler~ccti_c~n_. T'l~le-mi.pimp)u~lriv~Yv_a_v_s?tl?.acl~_fro~u_a~s~lLects?r~r
arterial~Sre~S_intersec~tiott ~liall-he_.1.SQ~eei._c>Ile~su~~cl_frQantla_e~i~h3~f_-~vaylin~ofthe
interse jng street to the throat of the nrownd drjveway. The setback maybe greater
s noi~d'g upon the_influence area as determined from. City Tgineer revview of a traffic imn S
r~s ubmitted_by_tile applicant's traffic engineer. In a c;se where a pm_ mt has less than-l5-0
ieeQf_sireet_fxQntage~tLie apc~t_nausS_x _Lore_a~lY~pti9~_f-_uslaar_e~ acpess witlltlle~~liasnl
ap rcel_[.f~hare~Lacce~s is_nat ~sibao oLpcaciical, the drive<vaY_~I~all~_e_RLaee_d.as_f~r_ftonttlLe
_i~tterse_ctiQ~as_nossible.
~'Ite_rrtinitiJUtn sti~eirt~ QCdri_tie.vay_s aid_~tre_ets_al_eng~_c4lLectstr~ha1.Lt?e_2.2Q1'e~t Tape
minimum Etza f; of driveways and streets alana an arterial shall be 600 feet
4._ The_ma~ittatista_s_p~cing_Qf14.eal_Streets_a_louQ_al~cs~l_sixe~t~li~ll_be=.L?5 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
Unit/Lots
Minimum Number of
Driveways Re wired
Minimum Access Width
Minimum Pavement
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:
A.l711"" v. A&411.V DR4ZIDEN TIAi. III. R,
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
2049
I
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
I
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
Spaces
Minimum Number of
Driveways Required
Minimum Access
Width
Minimum Pavement
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 authoritv 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 T.SP 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 l
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 R4.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 sPeeif+ed-roadways
er3tfee
WheF he st
~.z.~--ens , angles the measutemem shall be made at Fight -r e...
b..
..tedi « „i extension Pat. t ' ay '
distanee regUiFed by the a «t. t the f ll a distanees ' f owe
a
ADDITIONAL TABLE 18.730.1
SW Nei& 1IighA'e' ( ithiR GitTLjnht:s) 50 feet
SW Hall Beule'ard 43- ee
-SW Se ells .r-et ' Read (exeept between its
nteFseeiiotts with Old Sehells lien), .Read) 50 feet
tt+~la+rl FiAa<l lall u,'e «a a•
1~er-l3oe+le~ l~er ~ -43-€eet
&W-lei-- 3 nes-Ferr -4I ead 45 feet
Eo44eetep&re,ets:
SW Ash-Ayeffue 30 feet
SM, Atiatlta-ll iiies-{eastt~€-f~~'3t11-A-venLie` 30 feet
SW ~t--~st-ef-"fli-Avelitie) 30 fe +
Beef fBertd-Read 30 fbet
Pon Road 30 feet
&W-Ru4W-au stain-Dead €eet
S1"U1rnhaf"treet 30 f t
c`asEtlde Boole and 30 feel
t+eet 39 -feet
SNV-Dtir¢tags4oa")eEweetrP--acWte4lighNN -a)- and
Hall-Bettlevard` 30 c e
&W rank-4in-,Stl-eet 30 fee!
SW-Gaar-de-Stfee; 30 feet
S-W-Grant-A-venue-- - 30 feet
.o SN"reetibur-l,-R-oadi 30 oet
S-l4=l-ltttt ikei Road- 30 feet
S ant}-Street 30 feet
SNV-W-Doiiald-Street 30 P et
S W-MtwdeO Cc ' eai 3() T-t
e fee 30 ~-ea4~-Ewest-ef ##a.l l~3eaie~~ard` 30Teet
Proposed 18.730 Development Code changes to implement the TSP page 4
C~fnf;Te-l" eet -30 feet
ctiefls With
Old Sehells 1eF*, Read) 30 fee
TABLE 18.730.1 (GON'T)
SW -Sumer-f la n
SW Ti
d
A
30 feet.
30 feet
venue
e
eman
d S
S4':I'i
30 feet
gar
treet-
Iv
W
I
S
90 feet
tfeet
S
a
l,Ut
,
68th A enue
30 feet
SW 68t1 A
th f D,.
i€
Hi
SW 68
h
0 - veer
hwa
)
e
e
(sou
g
{se~~
t
.
y
3
30 feet
SW 72
d
30 feet
Beni a
n
SW 97tm
30 feet
h A
SW 98
30 feet
t
venue
SW 11ntt A
20 feet
SW 121
A
~n fee:
st
venue
th t Df ffl
SM' n
d
D~
HI3
t
e6t • 30 feet
c E~
~il( r~
ar
cmrrc
,
r'r~-v
Planned, SW Hampten to 69th (wester
n
lyle9p read) 30 r et
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.
ff shall not be less than y
not _50 feet OF gFeater 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
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.
15.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 hosi person shall receive no compensation
for such occupancy or use;
3. Any such unit parked in the front yard shail 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
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.z
Proposed M 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 I
"public streets" unless an adjustment under Section 18.810.020.13 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.13.
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 precis.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-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
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
Type ofRrei
IRA"
}
n
Proposed 18.810 Development Code changes to Implement the TSP page 5
T
O
T
00
O
T
_a)
.Q
9
i
i
z
~
(4:1) 1144PIM
z
dpls
Cl
~ I
N
aue-1 9)119
*61
co x
!Lj
co La
I
c
ZO.
CL
la~7~~-/~4'ttr~B-'im
1 ca:A
aue
~-II
III
~-I
Jo joqwnN
1-
11
N
N
NI NI NI
•
i
4_
ar
IIvil
I
I
Qil
z
2
-J • s •
1
, -
~-I
~I
Q
Q
1.0
a
a
h
d
a
obi
d
r
v
a
u
b
V
v
0
o~
A
O
00
d
0
0
4
Eip,muw.-1U10.1
Ariexial.~ ~anlnl~~r_QSS~r~tiolls
v~.V ~Y} tt
S Z.
• 8-10'5.5' 6'8&e 12'- 12' b'E~ce 55' 8-10' S'
RAN 64168'
2 Lane 64 =68' RW
.a
-
_
5 8-10~ 5.5',6-Me,
12' MediaN
12' Lurn Lane f 17
~619te,5.5' r8-10•,
R/W 76'-80'
3 Lane 76 =80' RiW
Proposed 18.810 Development Code changes to Implement the TSP
page 7
5. 8 ]0 - nneaaN
I6~~--12'- iz
RAN 100'-104'
5 Lane 100 '104' R/W
71n
124 =128' R/W
Figure 18.810.2
Collector Sample Cross Sections
s
L
6 8', 5.5' i6like.-• 11' 11i6'Bkef5.5' 6-9 f 5•
RhV 58'-62'
2 Lane 58 '62' R/W
12' Melon/
66-8', 5_5',6'Bke, 11' TumLone 1 WERe_ 5 6-8
R/W 70'-74'
3 Lane 70t.74' M
Proposed 18.810 Development Code changes to implement the TSP page 8
i RM 92-96'
5 Lane 92 =96' R/W
Eieure18.$10-3
Neighborhoo-d-Routes
SamRle_Cross--Sections
4
~vC•'` ..gyn.
1
5 5.5'. P~ 28' .'5.5'. '
F RAN 50' 1
No Parldng on One Side
2
32' ~5.5'
R/W
I-- - - 54' i
With Parking on Both Sides
L r ~ T • t`
36'
.121_.,__
2 -t6' Bacei_ 5.5' 5'
R/W 58'
With Bike Lanes /No Parking
Fiiaure 18.810.4
Local Residentisal Slr ets_<1.j00 vpd
A. Standard (sample)
32'-f 5 5 5- 5~
On-street Parking
ea o.
If parking on both sides,
block length not to exceed 600 feet
B. Skinny Street Option (criteria)
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.
Eig-unz-1-U&J-0,5
Loc;il -Res.i.dential_Slreet~_<<_ 5.0-o_vna
Proposed 18.810 Development Code changes to implement the TSP page 9
A. Standard (sample)
5'~5
'S 5' S=5 r~ 28'•--i-5-5
R/W 50'
i
Residential Local street/Cul-de-sac
One Side On-street Poildng
wII
1lsure 18.8 U6
Local-Rcsidettsial 51trceS < 2QQ vnd
A. Standard (sample)
..r
Al
S' 5.5' . 24'
5 5' S' 5.
Cul-de-sac/Residential Local Street
E./
(No parking)
F. Future street plan and extension of streets
1. A future street plan shall:
B. Skinny Street Option (criteria)
® b
N• !
' R1,Ndrq`
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.
B. . Skinny Street Option (criteria)
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 fee. surrounding and
adjacent to the proposed land division. At the applicant's request, the City shaWmavprepare
I
a future streets proposal Costs of the-Cit. __-preparinv a future stregt rooc~sal shallshall b___l~~
Proposed 18.810 Development Code changes to Implement the TSP page 10
re.i.rabu.r5ed_-for tlae.__tirneJnv_nlyesi,. 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 cuts-de-
sac since they are hoended 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._Stre-el_spacing...aiW-aegea.rzu.nageit&ut~~ e£e1~o1 ~ZQ5 U Q 1L
GL1. Street alignment and connections.
1. Full street connections with spac*n,g of no more than 530 feet between connections is required
eocevher_e -vNed_ _y=axrierstaelL_a~epogr_aRlava~ailr~_freaxs.._axeait~xlg
cig_vglopnicn1s_._lease_ _r_civisi_Qns,_easennetlts~o9 miants_ar~ther~estcieiio~s~xi tinQ~xiar_tQ__Ll1x
1.t 25_whiela _Iz eplude str~e ~o~neesis~as.~~ _fttl.l_str_eet cs~inle~ ionana _ ~ie~.xem o-duc to
a_r~gulaied_water_~eafitre._if_~e~ula.4io~a~utlsi_uot_t~ermit_~ansxci~EtiQn.
4-. Staggering of streets making "T" inteEseetiens at eelleeteFs and aFtefials shall not be designed so
street:
23. All local aiid
,a;eigltborltQS~d_19utes atad 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.
43. 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 bnplement floe 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:
s
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.
I.I. 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 tile twQ
streets to the radius point of the bulb.
tersesting tfe
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.
LdM. 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 Citv
EU " _r.:
#1N. Grades and curves.
-Grades shall n,)t 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: .
--12. Centerline radii of curves shall b_~ _as__d terntfned_Uy,..the_Ctay.a _gm ear
feet en maJOF rs, 358 feet eii minor- , streets;
of 100 feet en etheF and
Proposed 18.810 Development Code changes to implement the TSP page 12
pe .
a
NQ. 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.
9P. 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.
P-Q.Access to arterials and ffiftier-collectors. Where a development abuts or is traversed by an existing or
proposed arterial or majer-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 nuger-collector; I
2. Lots of suitable depth abutting the arterial or teajoi-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 I
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 st'reet..
Qg. 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 comers of
necessary alley intersections shall have a radius of not less than 12 feet.
IBS. 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.
$T. 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.
T~U.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.
t_y_. 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.
Nom!. 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
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.
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.
XX. 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.
ZE A. 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 1&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
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
AQ A trafti study shall be required for all new der meats under anv of the-following
circumstances:
.l_._~h~u_-th.~~~,ex~crat~a__~.9°/9__oL.;-.'realer=itt.czcaSe__n e~isling-Staf~c toJti.~h_colLisior~inte~sec~~QUs
idcz~t.i_tied~y ~'_a~hitt~t-Qn Gounty__.
T geecr_atioi>s f no !Lc-xeiQptx It_QntQ_the Citr'~- t alhc-P--ojnt_of acc ss-and xhe a stin~~
~~sfa]L~+ithl~ the~o_l_Lo~inQ.~an>;es:-
E~ci_sti~.t~D:l' Ap~:lo_~e.~dded~ d=e~lop~nQ.nl
Q-3,0_QO 2..9Q0 vpd.
3-00L-6.00 y~_d 1 O LOMA
>CM9 .d. 50_0 v. - wringre
3::=1f_ n -of_llw-fiblbo i i.n~ue~ l,~come ev~denl_1Q-tl~e.~ ty enJgi~~ecrx
a~~[i .1_ttlfl;aG vQluJJle_S_Qt]-tI1G_ndJ3Cerlt.XOs~4i}Y~~Ilal=tila~! ~1'fe~1JI1QYCI17e~1Llttto_(~o111 QT~~I.o
mite,
h--Lack-of 1_S i }n.l_efl lUrn _I2rt S2Ltlo_ tFles 4 agent roadwaY_at the-StIonaw-d sirn~SddyeU)
diet ace at acce pint
c___ Inadequate horizorltaLor vertical
d. I roxi of thepspssedccess to._other- existing dries or intersections is iaJntial
haz c
e._--, 'h .pxopasal_rgguaces__ ._co„dittQn l._rtsc_porm.it-o~ iXo-Les.a_driv_e:sltcougb_Qpgrat _
1__-. M2. mpn-EA vq opiiig _anay._. resuUn_excessiyg traffic x_olum s on_H-djpj utlo~; -aLslLcels~
.within. .5QO_feet_ofan_0QQT-facililY.
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.1.241,590 feet measured along the
Cnigrllrie i~fllc__slCegts ® 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, 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 notpcassi ile~ccinpted_by a.l 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 and-pr_i-yate-strcets-shalI have sidewalks meeting City standards
along ai lcast 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 devW_Qp_ers
att of-any_de~r_e_j01)nl~nl _ rp Q S I,_or Eha~ige_kujs __r_ew tinu__irt ,m__a ima1J_,494
hislc_traD_armor.Qer_slys-a.IzulistlzalLb~~esu~ice~tQid~nii_fysli ct-safk-(1,5._x~hetr?.i6t~ine
distARN&. _pe e tzianso~.te.~t ithin.=llM itttle o~3la~it~iic~2~ll~raalsii~as~ilities ud_Llei J tt &IMly
~t~crs CSGbs?ols~parks,J.ibr_arrie_s, e~~~.~~c~djtiQn._S]]e d~y~loS~Lt]1~Y~2.~LeCllr-1Le~t~~lLti~JAs1t~~ILtll~
re~novaLcf ar v gaR i[tthe Aede~triatL~Y~terxt o iuslifd-bvAhc-dev 14ttut~nt•=
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
exigiag sidewalk ~&ect to rough psoportionalit,,leveu if the sidewalk does not serve a neighborhood
aeti_vi ~cn~er .
BC.Pianter 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 ai4er-ial or- aelleeteF streets-wheFepad ing is prohibited
adfaeent-te-the euFb, except where the following conditions exist: there is inadequate right-of-way;
the curbside sidewalks already exist on predominant portions of the street; er it would conflict with
the utilities,- there- am i ant natural features (lare~r~_ water features, etc that would be
destray_ed the=sidew ll~ -r-eeQF~tesl_a a-q~i esi ~r w~ere~he ar exi~ tin shsi tr~r~ ~ns1 -if
pr_ox.i.rro_ty_to_the-street ~.l_ et9 ii -
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.
D.E.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
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.
F-G. 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
.s 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
A,,==A-.Bikeway extension.
_Ls_a staad~rsi hilse~an~s ~ha1L ~~stnire al~tnal.LArtr~al~nd1Lecl~~xc~uxea~clb_~
istentalieci4~~~CaIY'_s~dQpt~FYC1~p1atLitLthg Tr_a.r~Sn~r~tiQtLSx~1~~1~a1TS:P),
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.
a..~~y__ne~v_ss~ee~ltl]pxa~emeu.t~r91~CLsJ.~ILi~EI~d_.e_f?.icvcl_e_1T~c~~s re~ui_c~dan~lii~o~~~meant
ansl 2tLthe~d4~~ bi_c~'~lg flan.
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 €e multi-u.se.--pats separated from the road is eight-p.
Meet. The width may be reduced to eiht (8) feet if there are environmental or other constraints.
___3.._ _'flte._; ~naanum ~v~~th ~Q_c~edes~riann o~tl~a_~_s~r~et_p_atk~s i~~ive_ .~fee_h
__.._____4.._Desig~l_standar~s._fQ~ bike _and._R~ciestrian-~Yays~hull__b~ ~Letcrsxti~~c( by the G~Zv ~n ig_ve~r
m.rOa nn~ 12)
C°
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.
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 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.)a
Proposed M810 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:
"~tei b i hid tivjt ~nigr" - A use such as schools narks librarjes Qr pools which
Provide recreational or social services for groin us of people
"Queuing Plan" - APan submitted with a proposal for skinny streets that shows the
potential queuing pattern that will allow for safe and efficient travel of emerges
vehicles. service vehi Ic es and passenger vehide2 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.13
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 majer 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 i
collector street.....
Additional TSP Implementation code amendments Page l
18.745d650.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- eelleeter-or miner collector street.
Additional TSP implementation code amendments . Page 2
r-L
i~
CD
P-A
CD
lw~
CD
CD
CD
r-L
c~
e~
0
C~
0
e~
CD
n
O
ty
n
~C
cv
C
CD
5
z
0
C~
c
0
0
CD
0
C®
tv-+ •
CD
lo-d
BCD
r~
E
V 1
CD
r-L
h.0a •
0
i~
td
C7
Cdr
1-0
~d o
CD
5
CD
V1
cn
cn
4
o
a
C®
CD
0
CD
d
r
CD
cn
0
C®
Vi
CD
9
CD
C7
CD
PP~~
4f ~
0
CD
OM.A e
P=A e
uq
CD
O
O
CD
I=L
CD
® ® 0 ® 0
C®
k0-d
CD
t:~,
O
fI4
C7
Cd4
CD
O
OWN&
0
0
CD
CD
lo~
cn,