TRAFFIC COUNT DATA Clause Samples

The TRAFFIC COUNT DATA clause establishes requirements for collecting, reporting, and sharing data on the volume and flow of traffic at specified locations. Typically, this clause outlines the methods for data collection, such as manual counts or automated sensors, and sets standards for the frequency, duration, and format of reporting. Its core practical function is to ensure that accurate and consistent traffic information is available for planning, analysis, or compliance purposes, thereby supporting informed decision-making and effective management of transportation systems.
TRAFFIC COUNT DATA. Upon completion of the work, submit all traffic count data in electronic format to the Bureau of Transportation Data Development. The data can be submitted in any form except binary data. If the traffic count collection time range is 48 hours or longer, comply with the requirements of the guidelines described in the FHWA Traffic Monitoring Guide.
TRAFFIC COUNT DATA. Existing weekday morning and afternoon peak hour vehicle, bicycle, and pedestrian traffic volume counts will be obtained from the Cheyenne MPO as available and/or conducted at the 10 intersections identified. These existing traffic volumes will be evaluated to determine operational level of service for existing conditions. Intersection and roadway improvements will be recommended based on existing traffic volumes.  Future Traffic Conditions. Future traffic projections will be obtained from the Cheyenne MPO and identified based on the proposed development plan for the area. This traffic will be assigned to the street network and intersections. A 20- 25 year horizon traffic analysis will be conducted for these future traffic volume forecasts to determine possible capacity needs and level of service criteria requirements. Roadway and intersection improvements (possible traffic signals or roundabouts) will be identified for these ten intersections and the overall 12-Apr-18 Parsley Boulevard corridor. In addition, driveway access realignments or turning movement restrictions will be proposed and recommended. The study will include an evaluation of the previous two proposed Parsley Boulevard alignments at the intersection with College Drive as identified in the ▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇ 10% Design Plan. As identified, traffic signal warrants will also be evaluated at this intersection.  Draft and Final Report. A draft report will be prepared to document the analysis performed in the study. The report will be provided to AVI for inclusion in the project report. Comments received on the draft report will be incorporated into the final report.  Cost Estimate. K-H shall only provide cost estimate assistance for traffic signal installations, if required.  Meetings. ▇▇▇▇▇▇-▇▇▇▇ will attend two (2) steering committee meetings and (1) Public Meeting. One (1) meeting will be attended in person and the other meetings via conference call. Additionally, (2) two one hour conference calls are also included in this task.
TRAFFIC COUNT DATA. The Contractor will conduct a site visit to determine the existing lane configurations and traffic control for the following intersections: · Main Street and US 95A · Newlands Road and US 95A · ▇▇▇▇▇▇▇ Trail/Fremont Street and US 95A · Roundabout at Main Street and Farm District Road The Contractor will collect peak hour morning and evening turning movement data at the study intersections listed above. This scope includes traffic counts, or bicycle and pedestrian counts, or a site-specific evaluation for up to two additional intersections. As an optional service, at the discretion and upon approval of the City, the Contractor will collect additional peak hour morning and evening turning movement data for up to five intersections. The locations of additional data collection will be coordinated between the Contractor and the City.
TRAFFIC COUNT DATA. The CONSULTANT is responsible for all traffic count data necessary to validate/calibrate the 2013 Base Year Model. Extensive traffic count data has been collected by the MPO and SDDOT and will be made available to the CONSULTANT. The CONSULTANT will review the traffic count data/locations for adequacy and shall adjust the counts to average weekday peak season counts. Seasonal adjustment factors for local roads developed by the MPO will be used where appropriate.
TRAFFIC COUNT DATA. Engineer will derive a data collection plan with PCCA staff to gather baseline information needed to assess existing operations and to support traffic volume forecasts. As an initial assumption, the following data collection is proposed: a. Daily Traffic Classification Counts – These would consist of hourly classification counts of bi-directional movements at two (2) strategic locations along the ▇▇▇ ▇▇▇▇▇▇ International Trade Corridor (JFITC) across 24 hours of the day for a seven-day period, repeated during two different seasons of the year (Spring and Summer). b. Daily Traffic Classification and Speed Counts – These would consist of hourly classification counts and automated speed measurements of bi-directional movements at four (4) strategic locations along ▇▇▇ ▇▇▇▇▇▇ across the core hours of the day for a seven-day period, repeated during two different seasons of the year. c. Intersection Turning Movement Counts – These would consist of directional counts of traffic passing left, through, and right across up to five (5) strategic intersections using automated counting techniques across a 24-hour period, repeated on up to four different days, which would be informed by insights from the seven-day counts.

Related to TRAFFIC COUNT DATA

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Third Party Websites The Service may contain or reference links to websites operated by third parties ("Third Party Websites"). These links are provided as a convenience only. Such Third Party Websites are not under our control. We are not responsible for the content of any Third Party Website or any link contained in a Third Party Website. We do not review, approve, monitor, endorse, warrant, or make any representations with respect to Third Party Websites, and the inclusion of any link in the Service, Debit Rewards Offers or any other services provided in connection with them is not and does not imply an affiliation, sponsorship, endorsement, approval, investigation, verification or monitoring by us of any information contained in any Third Party Website. In no event will we be responsible for the information contained in such Third Party Website or for your use of or inability to use such website. Access to any Third Party Website is at your own risk, and you acknowledge and understand that linked Third Party Websites may contain terms and privacy policies that are different from ours. We are not responsible for such provisions, and expressly disclaim any liability for them.