Traffic Monitoring Guide

Traffic Monitoring Guide

NOTICE
The U.S. Government does not endorse products of manufacturers. Trademarks or manufacturers’ names appear in this report only because they are considered essential to the objective of the document.

QUALITY ASSURANCE STATEMENT
The Federal Highway Administration (FHWA) provides high-quality information to serve Government, industry, and the public in a manner that promotes public understanding. Standards and policies are used to ensure and maximize the quality, objectivity, utility, and integrity of ITS information. FHWA periodically reviews quality issues and adjusts ITS programs and processes for continuous quality improvement.

PDF Version (9.5 mb)

TMG Executive Summary

• TMG Executive Summary
  • ES.1 Background
  • ES.2 Scope
  • ES.3 Users
  • ES.4 Manual Organization
• Chapter 1 Traffic Monitoring Theory, Technology and Concepts
  • 1.1 Introduction
  • 1.2 Terminology
  • 1.3 Detection Theory
  • 1.4 Detection Technology
  • 1.5 Variation of Traffic Data
• Chapter 2 Traffic Monitoring Program – Business Planning and Design
  • 2.1 Introduction
  • 2.2 Program Design
  • 2.3 Program Evaluation
  • 2.4 Coordinating Count Programs and Sharing Data
  • 2.5 Traffic Monitoring Calibration, Processing, and Compliance Reviews
  • 2.6 Quality Assurance – Starts with The Data Quality Act (DQA) Requirements
  • 2.7 Documentation and Metadata
• Chapter 3 Traffic Monitoring Methodologies
  • 3.1 Introduction
  • 3.2 Continuous Data Program
  • 3.3 Short Duration Data Program
  • 3.4 Calculations and Computations for End Of Year Processing
• Chapter 4 Traffic Monitoring for Non-Motorized Traffic
  • 4.1 Introduction
  • 4.2 Non-Motorized Traffic Monitoring Technology
  • 4.3 Variability and Traffic Monitoring Concepts
  • 4.4 Permanent Data Program
  • 4.5 Short Duration Data Program
• Chapter 5 Transportation Management and Operations
  • 5.1 Introduction
  • 5.2 Traffic Management and Operations
  • 5.3 Special Monitoring for Evacuations/Emergency/Planned Events
  • 5.4 Commercial Vehicle Enforcement
  • 5.5 Safety
  • 5.6 Planning
• Chapter 6 HPMS Requirements for Traffic Data
  • 6.1 Introduction
  • 6.2 HPMS Requirements
  • 6.3 Guidelines for Collecting Traffic Data to Support HPMS
  • 6.4 Calculation of Data Items
• Chapter 7 Traffic Monitoring Formats
  • 7.1 Introduction
  • 7.2 Station Description Data Format
  • 7.3 Traffic Volume Data Format
  • 7.4 Speed Data Format
  • 7.5 Vehicle Classification Data Format
  • 7.6 Weight Data Format
  • 7.7 Detailed Per Vehicle Data Format (PVF)
  • 7.8 Data Submittal Frequency
  • 7.9 Non-Motorized Count Station Description Data Format
  • 7.10 Non-Motorized Count Data Format
• Appendix A. Glossary of Terms
• Appendix B. Acronyms
• Appendix C. Vehicle Types
• Appendix D. Compendium of Designing Statewide Traffic
  • D.1 Case Study #1: Designing a Statewide Traffic Monitoring Program - Texas Department of
  • D.2 Case Study #2: Designing a Statewide Traffic Monitoring Program - Idaho Transportation Department (ITD)
  • D.3 Case Study #3: State Data Sharing – Colorado DOT (CDOT)
  • D.4 Case Study #4 (Part 1): Local Agency Data Sharing Delaware Valley
  • D.5 Case Study #4 (Part 2): State Data Sharing – Pennsylvania DOT (PennDOT)
  • D.6 Case Study #5: Alabama
  • D.7 Case Study #6: Connecticut
• Appendix E. Compendium of Data Quality Control Criteria
  • E.1 Case Study #1: Innovations in Data Quality QA/QC Systems for Traffic Data
  • E.2 Case Study #2: QA/QC Systems for Traffic Data
  • E.3 Case Study #3: PennDOT – QA/QC Systems for Traffic Data
  • E.4 Case Study #4: QA/QC Systems for Traffic Data - Washington State Department of Transportation (WSDOT)
  • E.5 Case Study #5: New York State DOT (NYSDOT) QA/QC Systems for Traffic Data
• Appendix F. Compendium of Equipment Calibration Procedures, Current Practices, and New Procedures
  • F.1 Case Study #1: Washington State Department of Transportation (WSDOT), Statewide Travel and Collision Data Office (STCDO)
  • F.2 Case Study #2: New York State DOT
  • F.3 Case Study #3: Alaska Department of Transportation and Public Facilities (ADOT&PF)
  • F.4 Case Study #4: Private Sector Contracting for Quality Installations and Data-Site Select, Install, Calibrate and Maintain
  • F.5 Case Study #5: NCHRP and AASHTO Recommendations
• Appendix G. North Carolina Department of Transportation Clustering Methodology for NC Traffic Data Inputs for MEPDG
  • G.1 Introduction
  • G.2 Factors Affecting Clustering Requirements
  • G.3 Sensitivity of Models to North Carolina Traffic Data
  • G.4 Hourly Distribution Factor Input
  • G.5 Monthly Adjustment Factor Input
  • G.6 Vehicle Class Distribution Input
  • G.7 Vehicle Class Seasonal Factor Groups
  • G.8 Axle Load Distribution Factor Input
  • G.9 Summary
  • G.10 References
• Appendix H. Traffic Data for Pavement Design
  • H.1 Background
  • H.2 Vehicle Related Terminologies
  • H.3 Traffic Data Associated with ESAL
  • H.4 Traffic Data Associated with Mechanistic and Empirical
  • H.5 Summary
• Appendix I. Frequently Asked Questions (FAQs)
• Appendix J. TMAS 2.0 Quality Control Checks
• Appendix K. Length Based Class Memo
• Appendix L. Additional State Traffic Monitoring Program Examples
  • L.1 Alaska Department of Transportation and Public Facilities
  • L.2 Georgia Department of Transportation (GDOT)
  • L.3 Colorado Department of Transportation (CDOT)
• Appendix M. References
• Appendix N. Index