Traffic Data Collection Sample Clauses
The Traffic Data Collection clause establishes the terms under which data related to the flow and volume of traffic is gathered and managed. Typically, this clause outlines the types of data to be collected, such as vehicle counts, speed, or congestion levels, and may specify the methods or technologies used, like sensors or cameras. Its core practical function is to ensure that accurate and relevant traffic information is systematically obtained, which supports effective planning, monitoring, and decision-making for transportation management.
POPULAR SAMPLE Copied 1 times
Traffic Data Collection. Coordinate with City staff on available turning movement volume data and supplement with data collection. Overall, the following locations would be collected during the AM and PM peak periods, pending available data: o 93rd Avenue at ▇▇▇▇▇▇▇ Industrial Road o 93rd Avenue at I-5 SB Ramps o 93rd Avenue at I-5 NB Ramps o 93rd Avenue at Pilot Driveway o 93rd Avenue at West Ace ▇▇▇▇▇▇▇ Driveway o 93rd Avenue at East Ace ▇▇▇▇▇▇▇ Driveway o 93rd Avenue at Kimmie Street • Collect the most recent five-year crash data. sort and identify key problems with severity and bicycle/pedestrian crashes. • Collect any approved development traffic studies that would add traffic to the study corridor and coordinate with City staff on any additional development activity that may be in process. • Coordinate with TRPC to collect: o Existing 2018 travel demand model volumes for AM and PM peak hours o Future 2045 travel demand model volumes for AM and PM peak hours o Land use growth by TAZ for the surrounding area influencing the study corridor • Collect/verify the specific intersection and corridor channelization, control, and pedestrian facilities.
Traffic Data Collection. The Engineer shall collect or identify required traffic data to supplement the data provided by TxDOT, including:
a) Classification Turning Movement Counts collected from previous studies.
b) Origin Destination Data collected from previous studies.
c) Historical Crash Data: Historical crash data
Traffic Data Collection. The Engineer shall be responsible for field review of the project, inventory and cataloging of existing available data. The State shall provide recent counts that were relevant to the study area. Based on review of available existing data, additional data needs will be identified, and data collection efforts will be conducted. Prior to field traffic data collection, the Engineer shall develop a data collection plan and provide to State for approval. The Engineer shall conduct a field review concurrent to the data collection.
Traffic Data Collection. CONSULTANT shall obtain one (1) day, two (2) hour standard A.M. and P.M. peak hour turning movement counts (TMCs) for up to two (2) intersections. CONSULTANT shall obtain five (5) day, twenty- four (24) hour bi-directional traffic counts for up to two (2) locations. It is not anticipated that traffic data collection will be required as part of the study beyond the scope of services provided herein. If deemed necessary, any additional traffic data collection required by the COUNTY or LCDOT staff will be covered in Task 9 Additional Services as authorized by COUNTY.
Traffic Data Collection. The scope of work includes collection, verification, and preparation of traffic counts to support the traffic studies including, but not limited to the following: • Travel time study (T2) • Engineering & Traffic Speed Surveys (T3) • Stop Warrants • Traffic Signal Warrants • Left-Turn Phasing Warrants • Crossing Guard Warrants • ITAM traffic forecasting and HCM traffic operational models (T4) • Count data collection for intersections (AM, PM, mid-day) and roadway segments (ADT) Consultant shall be expected to deliver completed and approved traffic counts on or ahead of approved schedules. All counts shall be prepared and submitted in a manner that ensures a consistent format approved by City staff. Consultant must be proactive and knowledgeable of all regulations required for data collection. Consultant shall be an advisor, advocate, and produce a product with the best interest intended for the City within the required schedule and project budget. Consultant shall attend project related meetings, be responsive to project issues and maintain communication between City staff, project applicants, community members and interested parties. All work shall be done in conformance with applicable City, State and Federal laws, and any coordination with neighboring jurisdictions such as Caltrans or County will require consultant to conform to their policies and standards unless directed otherwise.
Traffic Data Collection. Engineer will subcontract with The Traffic Group to perform data collection at the following locations: • ▇▇ ▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇ Road and ▇▇ ▇▇▇▇▇ Road • Mo Route 350 SB on ramp and off ramp • Mo Route 350 NB on ramp and off ramp. • ▇▇ ▇▇▇▇▇▇▇ Road and NW Blue Parkway • ▇▇ ▇▇▇▇▇▇▇ Road and NW Blue Parkway/Unity Way • ▇▇ ▇▇▇▇▇▇▇ Road and N Main Street • NW Main Street and NW Victoria Drive • ▇▇ ▇▇▇▇▇▇▇ Road and NE ▇▇▇▇▇▇▇ Street • NE ▇▇▇▇▇▇▇ Street and WB I-470 on ramp and off ramp • NE ▇▇▇▇▇▇▇ Street and EB I-470 on ramp and off ramp • NE ▇▇▇▇▇▇▇ Street and NE Mulberry Street • NE ▇▇▇▇▇▇▇ Street and NE Victoria Drive The traffic data collection will include 24-hour video turning movement counts at the above intersections with truck classifications and pedestrian crossings included. The collection will occur shortly after Notice to Proceed and will be conducted when conditions are above freezing, while school is in session, and avoiding holiday influences.
Traffic Data Collection. The ENGINEER shall collect traffic data when school is in session and will include 24‐hour average daily traffic (ADT) volume counts at each of the three intersection approaches, 2‐hour peak period turning movement counts (TMC) during the morning, school, and evening peak periods, 24‐hour vehicle classification data at each of the three intersection approaches and intersection geometric sketches.
Traffic Data Collection. The CONSULTANT shall perform all effort required for traffic data collection, including crash reports, 24 hr. machine counts, 8 hr. turning movement counts, 7 day machine counts, and speed & delay studies.
Traffic Data Collection. The Contractor shall collect all traffic volume data necessary to re-time the traffic signals identified in Section C-05. The Contractor shall manually collect AM, Midday, and PM peak hour turning movement counts from 7:00AM to 9:00AM, 11:00AM to 1:00PM, and 4:00 PM to 6:00 PM respectively, in 15- minute units. 24-hour bi-directional tube counts shall be collected at key segments in each corridor. Weekday traffic counts shall be performed on a Tuesday, Wednesday or Thursday only. No weekend traffic counts are allowed as part of this project. In addition, no traffic data collection shall occur during holidays or holiday weekends, days following or preceding holidays, school breaks, construction activities or unfavorable weather conditions such as drizzle, rain, hail, or snow. Field observations during each peak period for each intersection must be performed to verify lane geometry, identify saturation flow rate, pedestrian activities, percentage of heavy vehicles, oversaturated vehicle movements, to evaluate any breakdown of an existing signal system and to setup the appropriate limits of Time-of-Day plans. Upon collection of the field observation data and Before Study data the Contractor shall notify the City immediately of traffic patterns that may require special attention during the development of the traffic signal timing plans. The Contractor should also note locations where special features of the traffic signal controller should be considered for implementation to improve the operations of the subject intersection or corridor.
Traffic Data Collection. In order to improve the ability to analyze potential solutions within the corridors, traffic data shall be collected by the ENGINEER. These include traffic counts at various locations within the corridor, including main lanes, frontage roads, ramps, and intersections. Traffic Counts – The ENGINEER shall conduct traffic counts on segments of the corridor − 24 hour vehicle classification counts for a maximum of 75 locations along the main lanes, frontage roads, and arterials − A.M. and P.M. peak-hour Turning Movement Counts (TMC’S) for a maximum of 100 intersections will be provided from the STATE and the City that can be utilized for operational analysis Origin-Destination (O-D) Surveys using Bluetooth Data– The ENGINEER shall conduct Bluetooth surveys to identify the OD patterns along the corridor. These surveys shall be supplemented by outside data purchased from other resources (Streetlight or Airsage) to identify O-D patterns by mode. Travel Speed – The ENGINEER shall obtain travel speed data information from INRIX/Google to calibrate Travel Demand and Micro-Simulation Models. The ENGINEER shall evaluate the traffic count database available through the Statewide Traffic Analysis and Reporting System (STARS) ▇▇▇▇://▇▇▇▇▇.▇▇▇▇▇▇▇.▇▇▇/tcds/▇▇▇▇▇▇▇.▇▇▇?loc=Txdot&mod= Traffic Count Locations (ArcGIS Shapefile) Traffic Counts (Microsoft Excel tables) O-D matrices (Microsoft Excel table)