My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
3 - CUP2018-02_2000 W ALTON AVE
Clerk
>
Agenda Packets / Staff Reports
>
Planning Commission (2002-Present)
>
2018
>
03-12-2018
>
3 - CUP2018-02_2000 W ALTON AVE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/13/2018 10:07:19 AM
Creation date
9/13/2018 10:05:01 AM
Metadata
Fields
Template:
PBA
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
114
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
T RAFFIC I MPACT A NALYSIS <br />S EPTEMBER 2017 <br />C HRIST O UR S AVIOR C ATHOLIC P ARISH <br />S ANTA A NA , O RANGE C OUNTY , C ALIFORNIA <br /> <br />P:\DOM1701\doc\Traffic Impact Analysis.docx «09/20/17» 3 <br />Access to the project site is currently provided via a driveway off the south leg of Raitt Street/Alton <br />Avenue and a gated right-in/right-out driveway on Alton Avenue. The project will reconstruct the <br />intersection of the main entry driveway with Raitt Street to provide more turn-around space. The <br />project proposes to add a gate to the Church side of the access. The project will maintain the <br />existing right-in/right-out driveway and gate from Alton Avenue. An additional driveway and gate <br />with a Knox-Box is proposed at the northern terminus of Jaguar Way. The project will also construct <br />a fire lane off this southern driveway, which will be accessible from Jaguar Way without interference <br />from the gate. Figure 2 shows the project site plan. <br />METHODOLOGY <br />This TIA is prepared consistent with the objectives and requirements of the City’s Capacity <br />Calculations and Level of Service Standards and applicable CEQA provisions. <br />City staff reviewed the scope of work for this traffic analysis. Figure 3 illustrates the locations of the <br />intersections included in the study area. Figure 4 provides the existing geometrics and traffic control <br />at each study area intersection. The study area analyzed in this report includes the following <br />intersections: <br />Study Area Intersections <br />1. Raitt Street/Alton Avenue <br />2. Jaguar Way/Project Driveway (unsignalized) <br />3. Jaguar Way/Proposed Residential Driveway (unsignalized) <br />4. Raitt Street-Jaguar Way/MacArthur Boulevard <br />5. Project Driveway/Alton Avenue (unsignalized) <br />Intersection Level of Service Methodology <br />Traffix Version 8.0 computer software was used to determine the level of service (LOS) at signalized <br />intersections based on the intersection capacity utilization (ICU) methodology, while Synchro <br />Version 9.1 computer software was used at the unsignalized project driveway using the Highway <br />Capacity Manual (HCM) methodology. The ICU methodology was used to determine the LOS for the <br />signalized study area intersections consistent with City requirements, including 5 percent loss time, <br />1,700 vehicle per lane per hour capacity for through lanes, and 1,600 vehicle per lane per hour <br />capacity for turn lanes. The ICU methodology compares the volume-to-capacity (v/c) ratios of <br />conflicting turn movements at an intersection, sums up these critical conflicting v/c ratios for each <br />intersection approach, and determines the overall ICU. The HCM methodology calculates the delay <br />experienced by vehicles passing through the intersection. <br />The resulting ICU or delay is expressed in terms of LOS, where LOS A represents free-flow activity <br />and LOS F represents overcapacity operation. LOS is a qualitative assessment of the quantitative <br />effects of such factors as traffic volume, roadway geometrics, speed, delay, and maneuverability on <br />roadway and intersection operations. LOS criteria for intersections are described in detail below. <br />3-54
The URL can be used to link to this page
Your browser does not support the video tag.