My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ORANGE COUNTY TRANSPORTATION AUTHORITY (5) - 2013
Clerk
>
Contracts / Agreements
>
O
>
ORANGE COUNTY TRANSPORTATION AUTHORITY (OCTA)
>
ORANGE COUNTY TRANSPORTATION AUTHORITY (5) - 2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/31/2021 10:14:57 AM
Creation date
2/27/2013 10:42:57 AM
Metadata
Fields
Template:
Contracts
Company Name
ORANGE COUNTY TRANSPORTATION AUTHORITY
Contract #
A-2013-021
Agency
PUBLIC WORKS
Council Approval Date
1/22/2013
Destruction Year
0
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
80
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
COOPERATIVE AGREEMENT NO. C-2-2030 <br />ATTACHMENT A <br />8. All electronic data produced for this project shall be provided on CD-R. <br />Task 2: Data Collection <br />CONSULTANT shall collect the following data necessary to thoroughly understand <br />existing traffic conditions in the study area and be able to develop optimal time -of -day <br />traffic signal coordination plans, if applicable. <br />From the involved AGENCIES and or Authority, CONSULTANT shall collect existing <br />timing charts/sheets, existing coordination plans, traffic as -built drawings, aerial <br />photos, maps, traffic collision data as available, and collision diagrams for the study <br />intersections, if available. CONSULTANT shall also collect any off the shelf plans <br />(PS & E) for construction of any and all traffic signal coordination/synchronization <br />related plans, specifications and estimates for the corridor. CONSULTANT, if <br />requested by the involved AGENCY, will provide their own staff to review available <br />records/plans and request copies of needed records/plans with a minimum of <br />disruption to the involved AGENCY. <br />2. From the involved AGENCIES, CONSULTANT shall collect signal timing and signal <br />priority preferences, including, but not limited to, those related to pedestrian and <br />bicycle timing, phase sequence modifications and preferences, and special <br />operations such as conditional service, coordination preferred phase re — service, <br />and ring — barrier logic, as well as the timing optimization software preference. <br />3. CONSULTANT shall conduct seven-day 24-hour machine counts along each 1 mile <br />segment of PROJECT. Additionally, CONSULTANT will collect 24-hour vehicle <br />classification counts using a machine at four (4) locations on PROJECT to determine <br />heavy vehicle (truck) percentage information. Data obtained from Saturday and <br />Sunday counts will determine the necessity of weekend signal timing. <br />4. CONSULTANT shall conduct weekday and weekend peak period turning movement <br />counts (TMC) at each and every of the PROJECT signalized intersections, including <br />pedestrian and bicycle counts. No other types of TMC classification shall be <br />necessary. Weekday counts shall be conducted for two hours of each peak period <br />(AM, mid -day, and PM). If needed, after analyzing the seven-day 24-hour machine <br />counts, weekend counts shall be conducted at each and every of the PROJECT <br />signalized intersections for a single two hour Saturday mid -day peak period. For <br />intersections with more than 2 through lanes in any of the approaches, a minimum of <br />2 people per intersection is required. <br />a. CONSULTANT, APM, and Local AGENCIES shall determine locations for <br />special video recording of bicycle and pedestrian activity for specific data <br />collection in support of upcoming changes to the CA MUTCD. Video <br />recording and data reduction shall be required at minimum 6 locations. <br />b. CONSULTANT and designated sub consulting Traffic Counting Firm shall be <br />L, <br />
The URL can be used to link to this page
Your browser does not support the video tag.