Traffic Data Collection Sample Clauses

Traffic Data Collection. The Engineer shall collect or identify required traffic data to supplement the data provided by TxDOT, including:
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
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.
Sample 1
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. Task 2: Field Observation 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.
Sample 1
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) xxxx://xxxxx.xx0xxxx.xxx/tcds/xxxxxxx.xxx?loc=Txdot&mod= Deliverables:  Traffic Count Locations (ArcGIS Shapefile)  Traffic Counts (Microsoft Excel tables)  O-D matrices (Microsoft Excel table)
Sample 1
Traffic Data Collection. The CONSULTANT may be required to conduct traffic counts at various locations throughout the District for Concept Development projects, PD&E studies and Design projects. The type of counts may be vehicle classification, bi-directional, or turning movement counts for any duration (period of time) required by the DEPARTMENT. The CONSULTANT may be expected to document the field conditions at the time of the counts. Field documentation may include counter location and geometric measurements such as number of lanes, length of storage and taper for turn/merge lanes, type of traffic control, and the location and/or presence of signal boxes and loop detectors. In addition, the Consultant may be required to collect and analyze existing data which may include but not be limited to accident data, land use data, access features, highway characteristics, transit service, freight management, signalization information and environmental features. The CONSULTANT may be required to fully document the data collection effort and provide this documentation and collected data in Excel, Nuance, and PDF format.
Sample 1
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.
Sample 1
Traffic Data Collection. The CONSULTANT will be required to conduct traffic counts at various locations throughout the District for Traffic Studies. The type of counts may be vehicle classification, bi-directional or turning movement and for any duration (period of time) required by the DEPARTMENT. The CONSULTANT may be expected to document the field condition at the time of the counts. Field documentation may include counter location and geometric measurements such as number of lanes, length of storage and taper for turn/merge lanes, type of traffic control, and the location and/or presence of signal boxes and loop detectors. The CONSULTANT will be required to fully document the data collection effort and provide this documentation and collected data in PDF format.
Sample 1
AutoNDA by SimpleDocs

Related to Traffic Data Collection

  • Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.

  • Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.

  • Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE)when reporting on beds utilized at the Hospital.

  • Information Collection Information collection activities performed under this award are the responsibility of the awardee, and NSF support of the project does not constitute NSF approval of the survey design, questionnaire content or information collection procedures. The awardee shall not represent to respondents that such information is being collected for or in association with the National Science Foundation or any other Government agency without the specific written approval of such information collection plan or device by the Foundation. This requirement, however, is not intended to preclude mention of NSF support of the project in response to an inquiry or acknowledgment of such support in any publication of this information.

  • Data Collection and Usage The Company and the Employer collect, process and use certain personal information about the Participant, including, but not limited to, the Participant’s name, home address and telephone number, email address, date of birth, social insurance, passport or other identification number, salary, nationality, job title, any Shares or directorships held in the Company, details of all restricted stock units or any other entitlement to Shares or equivalent benefits awarded, canceled, exercised, vested, unvested or outstanding in the Participant’s favor (“Data”), for the legitimate purpose of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is the Participant’s consent.

  • Billing and Collection The Originating party shall xxxx and collect such information service charges and shall remit the amounts collected to the Terminating Party less:

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Local Line’s data from BellSouth’s data, the following shall apply:

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.

  • Information We Collect When You request Goods or Services We may collect Personal Information supplied by You when You complete an online form in order to facilitate the purchase of Goods and/or Services. Such information will enable Us to process Your transactions efficiently, analyse our Website services and enable Us to provide a higher level of customer service (which may include informative or promotional activities). We may also collect the following information/tracking data for statistical purposes and to help Us understand how to make Our Website more available and user friendly for You and to measure the success of any advertising activities We may under take:

Time is Money Join Law Insider Premium to draft better contracts faster.