My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CDS_Ordinance_2023 NonDocket Amendments_KCC
>
Meetings
>
2023
>
06. June
>
2023-06-20 10:00 AM - Commissioners' Agenda
>
CDS_Ordinance_2023 NonDocket Amendments_KCC
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/15/2023 2:23:18 PM
Creation date
6/15/2023 1:54:53 PM
Metadata
Fields
Template:
Meeting
Date
6/20/2023
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Item
Request to Approve an Ordinance Adopting the 2023 Non-Docket Docket Amendments to Kittitas County Code
Order
3
Placement
Consent Agenda
Row ID
104780
Type
Ordinance
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
274
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
D. The TIA shall be prepared by and/or under the supervision of a registered engineer in <br />the State of Washington. <br />E. To establish the scope of the TIA, the developer shall follow the Public Works <br />Department TIA guidelines and shall provide a preliminary, limited scope analysis <br />documenting the estimated trip generation and distribution for the proposed <br />development application. The director or his designee will review and adjust, if <br />necessary, this information for use in establishing the analysis locations for the TIA for <br />the concurrency evaluation. The TIA shall, at a minimum, provide the following <br />information for the identified concurrency locations: <br />a. Number of peak hour trips generated by the development according to the <br />ITE trip generation manual or other method approved by the director; <br />b. Anticipated trip distribution; <br />c. The current calculated level of service of all impacted transportation <br />facilities; <br />d. The future calculated level of service of all impacted transportation facilities, <br />as identified by the county, incorporating traffic volumes from the <br />proposed development; <br />e. Any proposed mitigation; and <br />f. The future calculated level of service of all impacted transportation facilities <br />with the incorporation of proposed development traffic volumes and any <br />proposed mitigation. <br />g. Any adverse effects or safety hazards that are created or worsened by trips <br />generated by the development and the effect these trips may have on the <br />structural integrity of the transportation facilities. <br />F The TIA shall be based on traffic counts obtained within twelve (12) months of the fully <br />complete date of the development application as determined under Section 15A.03.040. <br />The traffic counts shall reflect representative traffic conditions within transportation <br />corridors and at intersections. <br />G. The Public Works director reserves the right to require a developer to provide data <br />and/or analysis as part of a particular TIA, where the Public Works director determines <br />that additional information or analysis is required to implement the standards and <br />requirements contained in this section. <br />H. The concurrency evaluation and determination shall be completed prior to: <br />a. Issuance of administrative approval/denial of the project permit if SEPA <br />review is not a requirement of the project; or <br />b. Issuance of the DNS, MDNS or IDS if SEPA review is a requirement of the <br />project; or <br />c. Issuance of the staff report to the hearings examiner if there is a hearing <br />before the hearings examiner and SEPA review is not a requirement of the <br />project. <br />Development permits for phased developments shall have the concurrency evaluation <br />completed for the entire project. A developer may elect to have the concurrency <br />evaluation undertaken for less than the entire project if and only if: <br />a. The director agrees to such limited evaluation; and <br />b. Each phase shall include all of the infrastructure to service that phase; and <br />
The URL can be used to link to this page
Your browser does not support the video tag.