Highway Performance Monitoring System (HPMS)

3.0 Best or Most Common Practices used by States

3.1 Introduction

The purpose of this chapter is to describe the various practices that address the issues and challenges associated with data collection, processing, and reporting for high traffic-volume routes. Table 3.1 aligns the issues to the practices adopted by states to overcome or mitigate them. The practices are grouped into four major categories: (A) general (the issues apply to all categories), (B) data collection equipment, (C) data collection, and (D) data processing, quality control, and quality assurance.

The descriptions are based on the information gathered through the interviews of sample states and supplemented by information from the published literature. The practice areas are illustrated with examples of use by states. Additional sources of information relevant to the practices are also identified. Furthermore, additional documentation for each practice area is included on an accompanying CD. Where possible, hyperlinks to these documents are provided. The documents on the CD include traffic monitoring guidelines, HPMS field guides, contractor specifications, training materials, equipment evaluations and specifications, and data quality assessments.

Table 3.1: Best or Most Common Practices used by States Category Practice Issues Addressed Examples

Category	Practice	Issues Addressed	Examples
A. General	A1. Training and Guidelines	Safety to field crew Equipment installation, calibration, & maintenance Data quality control and assurance Institutional issues	DOT's Traffic Monitoring Handbook Pennsylvania HPMS Quality Review NYSDOT Annual Training Workshop Indiana DOT's assessment of traffic monitoring program
B. Data Collection Equipment	B1. Equipment Selection, Calibration and Maintenance	Technological limitations of detection equipment safety of field crew on high-volume routes Equipment failures and damage High quality data on high-volume routes	DOT's pocket guide to installing road-tubes TxDOT, WsDOT, Georgia DOT and Michigan DOT equipment testing TI and Vehicle Detector Clearinghouse evaluation of equipment
	B2. Use of Non-Intrusive Equipment	Safety of field crew on high-volume routes Installation and maintenance costs Equipment damage – loops and sensors Congested and stop-and-go traffic conditions construction and incidents	Microwave detection use in New York, Ohio, California, and Virginia California Microwave Specifications TTI, Vehicle Detector Clearinghouse evaluations of equipment
C. Data Collection	C1. Use of Safety Strategies	Safety of field crew on high-volume routes Data collection on high-volume routes Congested and stop-and-go traffic conditions	WsDOT Safety Zones Florida DOT Safety Guidelines
	C2. Ramp Balancing	Safety of field crew on high-volume routes Data collection on high-volume routes Congested and stop-and-go traffic conditions	Ramp Balancing in California, Georgia, Texas, and Washington
	C3. Use of Innovative contractual Practices	Improved data quality situational issues, e.g., funding lack of interagency cooperation	Maryland Contractor Specifications NYSDOT Contractor Specifications Ohio DOT Task-Order Contract for Maintenance Virginia DOT's performance based service agreements
	C4. Use of ITS Data	Safety of field crew on high-volume routes Limited coverage of traffic monitoring program Congested and stop-and-go traffic conditions Construction and incidents	California's Detector Isolation Assembly California PeMS database ODOT's use of ARTIMIS data Michigan DOT's use of MITS data Illinois DOT's use of CATS data WsDOT use of ITS data in Spokane
D. Data Processing and Quality Control	D1. Data Processing and Quality Control Procedures	Raw data analysis and AADT estimation Assumptions and business rules Data quality control and assurance issues	California Validity Criteria Virginia Quality Edits
	D2. Adjustment Factors and Growth Factors	Raw data analysis and AADT estimation Assumptions and business rules	California's Adjustment Factor calculation WsDOT short count guidelines

3.2 Best or Most Common Practices

A1. Training and Guidelines for Traffic Monitoring Personnel

Issues Addressed

• Safety to field crew
• Equipment installation, calibration, and maintenance
• Data quality control and assurance
• Institutional issues

Description

Improving HPMS data collection on high-volume roads is often pursued by training and providing guidelines to personnel and agencies, since high-volume routes have special requirements with regards to placement of equipment and data quality verification. Several agencies provide focused training to the staff involved in data collection and processing.

Examples of Use by States

1. Staff training was identified as an important element to ensure that good quality and reliable traffic data are collected. For example, Virginia DOT (VDOT) conducts annual program meetings, quarterly reviews, and other equipment-related training to enhance the skills and experience of the field staff and contractors. VDOT also publishes a pocket guide for conducting traffic counts, including guidance on best practices for installation and site selection (Guide to Installing Road-Tubes in Virginia [CD]). On-going training helps field personnel in selecting areas with the best characteristics needed to collect accurate traffic data.
2. New York State DOT (NYSDOT) trains county personnel, contractors, and state personnel on traffic monitoring in an annual workshop. The workshop is open to all and serves as a valuable forum for all the parties involved with traffic monitoring in the state to meet and discuss concerns, opportunities, and emerging approaches.
3. Florida follows certain guidelines for multilane facilities as laid out in the Traffic Monitoring Handbook [CD] . These guidelines are used by the Central and District Offices as well as their consultants and contractors performing traffic surveys for FDOT use. It may also be used by local governments and other agencies. Guidelines are presented in a multimedia-rich format with audio-visual presentations and accompanying text. The guidelines incorporate site selection, safety procedures, type of counts and durations for short-counts. Similar details are offered for permanent weigh-in-motion (WIM), classification, and volume stations. The guidelines also document adjustment factor calculations, factor development, and AADT estimation
4. Maryland and Virginia have detailed specifications for short-term counts performed by a contractor, including quality levels, installation, and data collection procedures. Maryland has detailed specifications and requirements for contractors to follow, including a review of data by a professional engineer. If short-term counts are found to be in error, the agency requires contractors to recount the section.
5. Pennsylvania DOT (PennDOT) assesses HPMS data and publishes an annual quality review report. The main objectives of the quality report are to ascertain the current state of HPMS data quality and ensure that errors found are corrected, determine if any common problems areas exist and identify training needs, and determine if any organizational or procedural changes to HPMS program are warranted. To this end, random HPMS field views of randomly selected sample sections in several counties are checked. Approximately one third of the data-collecting agencies in Pennsylvania are reviewed each year (Heltebridle, 2002). Some of the improvements attributed to the quality reviews include development of the PennDOT HPMS Data Collection Guide, HPMS conferences, yearly quarterly review reports, and invitations to MPOs and city officials to attend conferences. However, it is not clear if AADT values are checked as a part of the quality reviews.
6. Indiana DOT (IDOT) conducted a detailed assessment and update of its traffic monitoring system to ensure that IDOT is in agreement with the new traffic-monitoring guide requirements (Labi and Fricker, 1998). The assessment focused on the management systems, the continuous counts, coverage counts, vehicle classifications, database systems, office factoring, and field procedures used by IDOT. The document also discusses the HPMS program, involvement of MPOs in traffic data collection, and traffic-monitoring activities of other states.

Additional Information on CD

• Heltebridle, L., Pennsylvania Department of Transportation, PennDOT Quality Reviews, Presentation at HPMS Issues Workshop, Chicago, August, 2002.
• Florida Department of Transportation, Transportation Statistics Office, Traffic Monitoring Handbook, October 2002
• Virginia Department of Transportation, Guide to Installing Road-Tubes in Virginia

B1. Equipment Selection, Calibration, and Maintenance

Issues Addressed

• Technological limitations of vehicle detection equipment
• Safety of field crew on high-volume routes
• Equipment failures and damage
• High quality data on high-volume routes

Description

Agencies are trying to maximize performance of existing technologies such as axle and volume traffic counters using road tubes or inductive loops. Improving performance of these detectors is primarily achieved through a combination of installation, calibration, and maintenance practices as well as through technical improvements.

Examples of Use in States

Accuracy of Counters

The accuracy of counters declines in high-volume conditions, especially using pneumatic road tubes. The accuracy of classifiers also declines in congested or especially in stop-and-go conditions. The following are potential solutions to the problem and illustrated by examples.

1. Make sure local practice complies with standards for installing pneumatic tubes for roadway traffic counters and classifiers (See ASTM E1957, "Standard Practice for Using Pneumatic Tubing for Roadway Traffic Counters and Classifiers").
2. Tests conducted by Texas Transportation Institute (TTI) on Peek ADR-6000 demonstrated that it can accurately classify vehicles in stop-and-go conditions and even when vehicles change lanes over the detectors.
3. Washington state DOT (WSDOT) conducts coverage counts by pneumatic road tubes using Peek ADR-1000 equipment. The software includes tailgate logic to improve classification accuracy in cases where vehicles are close together and might otherwise be classified as a single vehicle (truck) instead of two cars.
4. Florida DOT (FDOT) discourages the use of pneumatic road tubes and recommends installation of permanent sensors as part of construction projects on multilane facilities.
5. California DOT (Caltrans) has a battery of quality checks for equipment and data. It also recommends hiring quality staff to ensure high-quality data.
6. VDOT uses tight classification tables and requires vendors to use the same. Field personnel are experts with the equipment.
7. Illinois DOT (ILDOT) had great success with Hi-Star Numetric sensors in collecting traffic volume and classification data on highways carrying traffic less than 75,000 AADT. These sensors are easy to install and are excellent for volume data and fairly good for vehicle classification.

Maintenance, Calibration, and Testing

Pneumatic tubes are a stable technology and are the mainstay of short-term equipment in many states. States interviewed are comfortable in using this technology, while recognizing its limitations. In order to increase the efficiency of road tubes, states require staff and contractors to select appropriate locations to minimize some common problems (e.g., stop-and-go traffic, parking on road tubes, pavement surface deterioration), secure the tubes to the roadway, and check the settings on the counter.

The use of high-quality surge suppressors and adequate equipment ground on-site minimizes the risk of damage to pneumatic road tubes due to lightening. Also, the use of gas-discharge tubes for primary protection of phone lines.

In order to reduce the risk of premature loop failure due to pavement rutting or other pavement factors, avoid the use of inductive loops in thin pavements (less than 4 inches thick) or in pavements that need rehabilitation. Their installation in such pavements will often induce even more problems. Improve pavement maintenance and use deeper saw cuts to allow milling as needed. The use of high quality loop detector wire with a thick PE or PVC tube such as IMSA Spec 51-5 and twist loop lead-in wire at least 6 turns per foot to reduce cross talk is recommended.

1. VDOT provides a Pocket Guide ("Guide to Installing Road-Tubes in Virginia") [CD] to their field staff to aid in road-tube installation. The guide provides guidance on installation techniques based on traffic conditions and some general best practices. As such, VDOT routinely uses methods like "blocker" and "independent arrays" to separate the vehicle actuations in adjacent lanes in order to successfully gather traffic data in high-volume routes using pneumatic tubes. An example installation of an independent array using two tubes, two traffic counters, and blockers in the middle of the lane is shown in Figure 3.1. Further details can be found in, Lane Array and Road Tube Best Practice Guidelines, (VDOT, 2002).

Figure 3.1: Independent Array Installation of Road-tubes (Virginia DOT)

2. In Ohio, data collection crews are instructed to review data prior to submitting to central office for processing. The crew is instructed to check for high volume, multiple hours of zeros, and to reset the counters if necessary. The existing count contract includes a reset clause. When Ohio DOT (ODOT) determines that there is an error with the count, the contractor is required to make a reset. If reset is within a given range of the original count, ODOT pays the contractor for the two counts. If a difference in the count is significant, ODOT pays for one count. All new equipment is tested for accuracy and calibrated before installation. ODOT is currently initiating a research project to create a piezo-weigh-in-motion (WIM) bench tester.

3. Texas DOT (TxDOT) tests axle counters annually using a test highway section and ground truth measurements, including manual and video counts that are then corroborated with axle counters. In Washington, tube counters are set and validated prior to every count. A manual count (100 axles or 5 minutes of traffic, whichever comes first) is performed and compared to the data from the traffic counters. Similarly, each of the continuous count sites is validated once a year by a manual traffic count (three hours in duration)

4. Michigan DOT (MDOT) tests short-count equipment set-up for accuracy prior to data collection. ATR data are downloaded daily and reviewed in week-long chunks. Any abnormalities in the data are identified by the reviewer, and the maintenance staff is sent to check the device. In addition, ATRs are also polled daily to test for communication problems. MDOT tries to schedule counts either before or after construction when possible during the traffic-counting season (Mid-April to Mid November).

5. Caltrans inspects ATRs only if unable to poll the ATR or if the data are erroneous. However, extreme care is taken in installation and calibration. Extensive calibration is performed before accepting any new equipment. In Virginia, trained operators check equipment for accuracy during the initial setup operation in all cases. All equipment currently in use has a visual display with real-time results. Each new count setup requires an evaluation of performance before continuing on to the next count. Road-tubes are checked before each setup and replaced as needed. Advanced loop logic functions provide information when piezo-sensors begin to fail so that preventive maintenance can be planned. Equipment performance is continuously reviewed, and hardware and firmware upgrades are added as needed. In-house software is used to examine all data collected to determine the performance of equipment and sensors. New rules and parameters are added to the review process as needed. Any performance issues are addressed by making calibration changes to the detectors setup. Any changes in performance are addressed immediately. Locations with extreme stop and- go traffic are avoided.

6. Georgia DOT (GDOT) randomly tests ATRs for accuracy using video logs that are then compared to the collected data. GDOT has a tolerance level of 5 percent variance from the ground truth and only equipment that meets this threshold is used. Adjustment factors for AADTs can be estimated better if ATRs are accurate and installed properly.

   For short-term counts, historical trend analysis is used with a tolerance level. GDOT also requires crews to report on conditions in the field, including changes from the previous count cycle.

7. New Jersey regularly recalibrates WIM sensors. Regular crack sealing is done at piezoelectric axle sensors. Most service involves the communication link, such as resetting or reprogramming modems, replacing surge suppressors, or cleaning the cabinet interior. Occasionally, unexplained problems require replacing circuit boards or the equipment (e.g., communication boards, loop detector boards, or other ancillary boards).

8. Massachusetts reported that equipment is checked on an ongoing basis, performing testing throughout the year. The DOT emphasizes operational instructions to field staff on a continuous basis. Staff are required to wait after equipment is installed to ensure it is working before leaving the site, and to check if it is still working accurately before shutting it off and picking it up at the conclusion of the count.

Technology Improvements

1. Maryland uses two road-tube-based products from Progressive Engineering Technologies (i.e., PET Switch, Road Ramp) for traffic monitoring on high-volume roads. The PET Switch System uses an intelligent road tube that is configured to distinguish between lanes and allows the collection of speed, axle classification, and volume data simultaneously in up to four lanes. RoadRamp, a portable axle-sensing system with a separate axle sensor in each lane, guarantees more accurate lane classification and reliable traffic counts on busy, multi-lane sites.

2. VDOT has specified that all traffic-counting equipment include a visual display component that enables the field personnel to check visually if the equipment is set-up, calibrated, and working correctly. VDOT also works closely with vendors to develop a tight classification table and requires vendors to use this table for their classification algorithms. Any vehicle that registers as an unclassifiable (Class 15) will be reported back to the center and reviewed. VDOT also works with the vendors (e.g., PEEK) to develop a tailgating logic especially for high-volume roads with close headways to better classify vehicles (e.g., determining whether four counted axles represent two cars or one truck). VDOT uses in-house software to cross check set-up parameters in counters to ensure that manufacturers correctly code in the required information.

3. NYSDOT has specifications describing the requirements for portable microprocessor based ATR to be furnished to NYSDOT, and other governmental units within New York State for use with loop-piezo-based sensors. Technical requirements include construction, materials, hardware, software, environment, vehicle detection, and operations.

One of the breakthroughs, which enhance vehicle detector output by utilizing inductive loop signatures, is now available in the Peek ADR-6000. The software enhancement techniques involve several algorithms designed for use in roadside vehicle detection equipment and which may apply to vehicle classification, toll applications, and incident detection. Recent tests by the TTI indicated that the Peek ADR-6000 was very accurate as a classifier, counter, and speed detection device and as a generator of simultaneous contact closure output. However, its recent introduction into the U.S. market and being adapted from a toll application are factors in its need for further refinement. The classification result for a data set of 1,923 vehicles indicated only 21 errors and resulted in a classification accuracy of 99 percent (ignoring Class 2 and 3 discrepancies). This data sample occurred during a peak period and included some stop-and-go traffic. For count accuracy, the Peek in this same data set only missed one vehicle (it accurately accounts for vehicles changing lanes) (Middleton and Parker, 2002).

Additional Information on CD

• NYSDOT, Highway Data Services Bureau, Loop/Piezo Automatic Traffic Recorder Specification, September 2001.
• Virginia DOT, Lane Array and Road Tube Best Practice Guidelines, December 2002
• FHWA, Traffic Detector Handbook- Chapter 6 Draft – Sensor Maintenance
• Florida Department of Transportation, Standardization of Count and Classification equipment set-up and configuration process, prepared by PB Farradyne, 1995
• New Jersey Department of Transportation , Traffic Monitoring Standards, January 2000
• Ohio Department of Transportation, Service, Acceptance and Warranty Requirements

B2. Use of Non-Intrusive Equipment

Issues Addressed

• Safety of field crew on high-volume routes
• Installation and maintenance costs
• Equipment damage – loops and sensors
• Congested and stop-and-go traffic conditions
• Construction and incidents

Description

Non-intrusive sensors require less exposure of workers to traffic hazards and are sufficiently accurate for traffic volume monitoring applications except in very congested and stop and go conditions. The use of non-intrusive data collection equipment for traffic data collection has been investigated by various states primarily to realize two major advantages: relative ease of installation and improved safety of traffic personnel. Non-intrusive traffic detection technologies include infrared-, microwave-, laser-, acoustic-, and video-based sensors.

Examples of Use by States

While some of the states are experimenting and testing some types of non-intrusive equipment, other states are now beginning to review that option. The following sections summarize state practices and experiences with non-intrusive equipment.

1. ODOT uses Electronic Integrated Systems (EIS) Remote Traffic Microwave Sensor RTMS (http://www.rtms-by-eis.com) units in five locations to collect traffic volume data. ODOT has also tested video (Autoscope) and acoustic sensors. ODOT observes that the main disadvantages are that set-up is difficult and that RTMS only reports two vehicle classifications: long vehicles (trucks) and all others.

2. VDOT is actively researching several non-intrusive technology devices. To date, only the RTMS sidefire radar has been approved for use. It can be used as a portable detector and has the required accuracy. VDOT has reviewed other non-intrusive products but none has met their current needs.

3. Caltrans tested RTMS extensively but did not obtain favorable results, citing long set-up times and occlusion problems. Caltrans recognizes that these technologies have improved since and has developed guidelines/requirements for non-intrusive detectors. The draft guidelines are intended to help California personnel to make an educated estimate of whether microwave sensors can fulfill their requirements. The document contains checklists of requirements that must be met, test results of various microwave models, technology descriptions, and installation overviews. The Detector Evaluation and Testing Team (DETT) of the California Department of Transportation has recently tested two non-intrusive detectors, RTMS and Wavetronix SmartSensor. Results indicate that overall count accuracy was almost always within 95 percent of true counts and within 98 percent on some lanes. Speeds were also within 95 percent. One difference between the Wavetronix and the RTMS X3 detectors was the difficulty of setup and calibration. The Wavetronix only required 15 to 20 minutes total to set up, whereas the factory representative took about one hour per lane for the RTMS (Middleton et al., 2004).

4. ILDOT is a strong proponent of length-based classification and has worked with FHWA to report length-based classification for HPMS. The use of length-based classifications encourages the use of non-intrusive detectors. Often the inability of such devices to classify vehicles into 13 vehicle categories is mentioned as a major impediment to their increased use. ILDOT tested various non-intrusive equipment including microwave and acoustic sensors.

5. NYSDOT tested 3M Microloops for bridge deck applications. NYSDOT also tested SAS-1 acoustic sensors for their low-power requirements and low cost advantages. The main advantage stated by New York is the safety of traffic personnel. The Traffic Monitoring Unit of the NYSDOT has successfully developed a permanent acoustic traffic monitoring site. This site was developed in-house to support nonintrusive sensor technology with applications in data collection and ITS activities. Further details are presented in Chapter 4 of this report. In addition to using the acoustic sensors as permanent stations, NYSDOT also has four mobile platforms equipped with the sensor for portable counts including coverage counts, special counts, and some ITS design applications. Each is used to collect volume data on high-speed, high-volume, multi-lane facilities where typical collection methods cannot be used due to safety concerns or equipment limitations.

6. New Jersey DOT (NJDOT) indicated the following non-intrusive equipment use and research:

   • Peek-Vision pole-mounted video data collection was installed. Institutional considerations required the mounting to be roadside rather than in the median. Pole height was limited by available service equipment. Communication was via land line rather than the fiber-optic network originally planned. Staff constraints precluded sufficient evaluation or implementation.
   • 3M Microloop system was installed and operated satisfactorily. The Detector/ Recorder system could not be set to record data on the hour; it was always plus or minus several minutes although 60-minute intervals could be recorded. Initially, there seemed to be interference from nearby power lines. The manufacturer adjusted the system's frequency to alleviate the problem. Staff constraints precluded followup with the manufacturer to rectify the recording time or further implementation.
   • Although RTMS sensors have been installed as part of ITS incident management initiatives, NJDOT does not use count data from these sensors yet.
   • The New Jersey Highway Authority tested an acoustic detector. NJDOT was never advised of the results.

Sources of further information

The Vehicle Detection Clearinghouse, a multi-state, pooled-fund project managed by the Southwest Technology Development Institute (SWTDI) at New Mexico State University (NMSU) and sponsored in cooperation with the U.S. DOT FHWA, is a valuable resource for o documentation about technology, evaluation and testing results, and details on use of technologies by states. On the Internet, the clearinghouse is located at www.nmsu.edu/~traffic.

FHWA sponsored Field Test of Monitoring of Urban Vehicle Operations Using Non-Intrusive Technologies (FHWA-PL-97-018). The final report of the evaluation is available in html format at http://www.dot.state.mn.us/guidestar/nitfinal/about.htm

Additional Information on CD

• California Department of Transportation, Traffic Operations, Microwave Vehicle Detection Systems (MVDS) Guidelines, DRAFT, 2003
• U.S. DOT, Federal Highway Administration, A Summary of Vehicle Detection and Surveillance Technologies used in Intelligent Transportation Systems, produced by the Vehicle Detector Clearinghouse (VDC) for FHWA ITS Joint Program Office, Fall 2000
• Peter Martin et al, Detector Technology Evaluation, November 2003
• New York State Department of Transportation, Permanent and Mobile Platform Acoustic Site Summaries.

C1. Use of Safety Strategies

Issues Addressed

• Safety of field crew on high-volume routes
• Data collection on high-volume routes
• Congested and stop-and-go traffic conditions

Description

A primary concern in the monitoring of high-volume routes is the safety of data collection crews. Various states have developed strategies/guidelines to ensure safety of the agency personnel and the traveling public. Some of the strategies include setting of safety zones, training, and guidelines for field personnel.

Examples of Use by States

1. Washington State identified different zones for data collection. These zones were not identified strictly based on traffic volume but a combination of traffic and roadway characteristics (Figure 3.2).

Source: Interviews with WsDOT, 2003

Figure 3.2: Washington DOT Zones for Data Collection

2. FDOT has the following safety procedures in their traffic monitoring handbook (Florida DOT, 2002):

   • All traffic-count personnel must be provided a minimum of two weeks of training by accompanying an experienced field technician who is collecting traffic data. All personnel must be provided training in first-aid techniques and be familiar with safety procedures before they are allowed in the field.

   • All vehicles used for traffic data collection will be equipped with the minimum equipment specified. All traffic count personnel shall adhere to the following procedures:

     • Seat belts shall be worn during operation of vehicles.

     • Orange safety vests and UL-approved safety glasses or safety prescription glasses shall be worn during field operations.

     • Reflective safety vests shall be worn during low-visibility situations.

     • Vehicle lights shall be used in the following manner:

       • Turn signal and yellow roof mounted strobe lights shall be activated as the traffic count vehicle approaches the work site, usually five hundred to one thousand feet (500' – 1000') in advance of the site.

       • Four-way flashers shall be activated at the work site and the flashers and strobe lights shall remain activated until the proper turn signal is activated to leave the work site.

       • Strobe lights shall be turned off after the vehicle safely re-enters traffic flow.

   • All traffic count personnel shall conform to Occupational Safety and Health Administration (OSHA) Rules & Regulations.

   • vehicles shall be parked where there is adequate space to park the vehicle safely. The vehicle should be parked a minimum of four feet from the edge of the pavement. All traffic count personnel shall exercise extreme caution when entering the roadway to set or retrieve traffic sensors.

   • Under no circumstances shall traffic sensors be placed in the roadway when it is raining or foggy.

   • All traffic count personnel have the right to request that their supervisor assign additional help to assist them if they deem there is a need for a two-person crew to set equipment safely.

   • Only state vehicles are authorized to cross the Interstate medians. All other vehicles are subject to moving violations

   • Night work should be done only when traffic flow dictates it to be necessary, and then only with two or more technicians. One person should spot while the other is working near the pavement. Reflective vests must be worn at all times when working at night.

     These procedures are also reinforced through a video about safety included in the handbook.

3. New Jersey emphasizes installation safety on high-volume roads. The necessity of obtaining vehicle-type classification data by visual/manual methods rather than automatic vehicle classification (AVC) technology also requires special emphasis on safety for high-volume roads. Special consideration is usually given to volumes over 15,000 per lane per day. Typically classification using AVCs is not undertaken where more than one lane cannot be monitored by one machine. Also, if the state or the contractor determines that lane closures are needed to safely install and remove traffic monitoring sensors, the contractor is required to submit a "request for police assistance" to the appropriate state police coordinator and procure the services of a New Jersey DOT-approved Maintenance and Protection of Traffic contractor.

4. According to ILDOT, data collection staff cannot safely install data collection equipment on high-volume roads (AADT greater than 70,000). Road segments with traffic volumes greater than 100,000 AADT are in the Chicago area. In these areas traffic data are collected with loops and at toll way facilities by the toll way authorities and Chicago Area Transportation Study (CATS). When it is determined that a road carries sufficiently high traffic volume to preclude the safe installation of data collection equipment, manual count is used. However, manual counts are not a recommended practice because it noted to be expensive and could potentially suffer from accuracy and reliability problems. Similarly, Texas and New Jersey also perform manual classification counts where it is not possible to install traffic data collection equipment either because of safety considerations or because of equipment limitations.

5. Massachusetts employs safety procedures to protect DOT staff and the general public. Installation of inductive loops on high-volume routes are coordinated with pavement construction and maintenance programs.

Additional Information on CD

• Washington Department of Transportation, Safety Zones for Traffic Monitoring, Regions: Eastern, North Central, North Western, South Central, South Western, Olympia
• Florida Department of Transportation, Transportation Statistics Office, Traffic Monitoring Handbook, October 2002.
• Florida Department of Transportation, Safety Video for Field Personnel, included in Traffic Monitoring Handbook, October 2002.

C2. Ramp Balancing

Issues Addressed

• Safety of field crew on high-volume routes
• Data collection on high-volume routes
• Congested and stop-and-go traffic conditions

Description

Ramp balancing using counts on on/off ramps combined with control counts on the main line are used in locations with high traffic volumes where it is not possible to conduct mainline counts safely. The TMG defines ramp counting as the process of counting traffic volumes on all entrance/exit ramps between two established mainline counters, such as permanent ATRs or other installations, and then reconciling the count data to estimate mainline AADT. A limitation of the ramp-counting approach to estimate mainline volume is that, travel-lane volumes cannot be estimated because traffic entering the road cannot be allocated to lanes. This limitation is not a concern for data collected to meet the specifications of the HPMS, but it may have implications for other programs that depend on lane-specific traffic volume information.

Examples of Use in States

California, Florida, Georgia, Michigan, Ohio, Texas, and Washington use ramp-balancing approaches that were developed based on the guidelines and recommendations of the TMG.

1. California uses ramp balancing extensively on high-volume roads where there are no permanent counters and crew cannot safely install portable counters. Caltrans has an Excel spreadsheet that contains formulae to calculate AADT volumes based on daily ramp counts. Instructions to complete the worksheet are also provided to the field staff and are shown in Figure 3.3.
2. MDOT uses a ramp-counting program in S.E. Michigan (Detroit area). State personnel count at ramp entry and exit locations instead of counting mainline segments. These are then used in combination with the ITS detectors and the loops on the mainline to obtain the AADTs for the segments between two entry and access points. The ramp-counting program is conducted according to the TMG guidelines.
3. Georgia DOT was one of the first state agencies to use step-down (ramp balancing) approaches to counting traffic on mainlines of limited access highways.
4. In Texas a database system (STARS) is expected to automate the ramp-balancing process. The ramp-balancing programs are being set up based on the TMG guidelines.
5. Washington DOT calculates adjustment factors differently for the ramp balancing and has a quality check of less than five percent variation from the control points and estimated counts as recommended by TMG guidelines.

Additional Information on CD

• U.S. Department of Transportation, Office of Policy, Traffic Monitoring Guide, 2001 Section 3, Chapter 4.
• Caltrans Ramp Balancing Process Worksheet, Blank Computational Worksheet, from Joe Avis, Chief, Traffic Data and Photolog Unit, Division of Traffic Operations

Source: Joe Avis, Caltrans, "Ramp Balancing Process, Computational Spreadsheet."

Figure 3.3: California Ramp Balancing Guidelines

C3. Use of Innovative Contracting Practices

Issues Addressed

• Improved data quality
• Institutional issues (e.g., lack of funding and availability of personnel)
• Lack of interagency cooperation and data sharing

Description

A noticeable trend in traffic monitoring is contracting data collection activities to private contractors or other agencies. Under such arrangements, private contractors are responsible for data collection activities, with the DOT playing a supervisory role. Performance criteria is increasingly becoming popular with state DOTs as a means of ensuring data quality from the contractors. There also has been an increased interest in using county and local personnel in traffic-counting programs by providing county and local agencies equipment and training to collect and report data to the state DOTs.

Examples of Use in States

Maintenance and Performance Contracts

1. Maryland State Highway Administration (MDSHA) contracts traffic data collection. SHA provides the specifications and data collection templates for the contractors on their websites.

2. VDOT's Mobility Management Section (traditional data collection) leases its traffic counters and modems from Digital Traffic Systems (DTS). However, VDOT owns the sensors such as inductive loops and piezoelectric sensors. Since 1996, VDOT has contracted the data collection activity and leased data collection equipment. The current maintenance agreement with DTS is carefully written to assign responsibilities and minimize "finger pointing." There are cases where difficulties might otherwise arise, such as with traffic counters that did not work due to faulty piezoelectric sensors. A state inspector checks the equipment once a year, but if there are substantial errors in the data, the contractor has to re-collect the data (Fekpe et al. 2003).

   VDOT has established performance-based lease criteria for payment of data collection services. Contractor compensation is based on the amount of acceptable data being submitted by the contractor. Furthermore, VDOT requires a certain quantity of acceptable data from each site to be able to use that site for traffic factor creation. The list below summarizes some key elements of the agreement:³

   • There will be full payment for all Automatic Traffic Recorders (ATRs) and modems at sites with 25 or more days of useable classification and volume data (for factor creation) during a calendar month.
   • There will be 75 percent payment for 15 or more days and lesser payment for fewer days of acceptable data except that monthly payment will not be made for sites that have fewer than 15 days of volume data only available during a calendar month.
   • For service calls for maintenance purposes, the contractor will not be reimbursed a separate charge (pay item) for the service calls related to ATR/modem equipment problems, telephone line problems, or failed sensors, as costs associated with the service calls are included in the price of the monthly lease charge.
   • The contractor is given seven calendar days to investigate, make site visits, make repairs and respond back to VDOT after notification/receipt of a service call.

3. ODOT's Office of Technical Services, Traffic Monitoring Section, is considering the use of task-order maintenance contracts. In the past, ODOT has used small personnel service contracts to maintain pavement sensors. Now, ODOT is in the process of executing a task-order-type contract for maintenance to have contractors on board for anticipated and unanticipated maintenance requirements of the traditional data collection equipment statewide. The contract is expected to begin in the near future and will cover a time period of two years. ODOT is issuing a task-order-type maintenance contract to repair equipment including loops, piezo-sensors, and WIM sites. Other states also have expressed interest in task-order-based maintenance contracts including Texas, Florida, and Maryland (Fekpe et al. 2003).

4. NYSDOT expressed satisfaction with the performance-based maintenance contracts that are used in the state. NYSDOT uses three contractors for the state of New York whose contracts are renewed annually. Tasks include performing regular maintenance of equipment, on-call duties, and installation of new sites. The scope of work includes ontime requirements, turnaround times, and site inspection / preventive maintenance and repair visits consisting of ⁴:

   • Repair of sensor epoxy
   • Repair of sensor lead-in epoxy
   • Battery condition check
   • Power system condition check
   • Communication system condition and operation check
   • Surge protection equipment condition check
   • Clean cabinet and solar panel
   • Repair conduit-sealing material
   • Manual traffic count to verify ATR performance and data collection accuracy in all lanes⁴

Use of Counties to Collect Data (Resource Sharing)

1. California is considering partnering with MPOs for data collection activities. The partnership would entail MPOs conducting traffic counts with their contractors and providing the data to Caltrans.
2. NYSDOT has a formal practice to obtain data from counties. Counties are loaned equipment by NYSDOT and required to provide 10 counts per counter to the state DOT annually as part of the program. Joining the program is voluntary for the counties. NYSDOT provides training to county personnel in the use of traffic counters, and the reporting and processing systems. The county personnel are also invited to the regional traffic monitoring workshops organized by NYSDOT. It was also noted the Pennsylvania also has used county agencies extensively for data collection. Similarly, the Delaware Valley Regional Planning Commission, the MPO for the Philadelphia region, collects traffic data in four New Jersey counties for NJDOT.

Additional Information on CD

• Maryland State Highway Administration, Specification for Consulting Services for the collection of Manual Traffic and Portable Machine Counts and On-Site Traffic Engineering and Highway Engineering Assistance, 09/2004.
• New York State Department of Transportation, Highway Data Services Bureau, Zone 3 contractor specifications, June 15 2003.

C4. Use of ITS Data for Traffic Data Monitoring

Issues Addressed

• Safety of field crew on high-volume routes
• Limited coverage of traffic monitoring program
• Congested and stop-and-go traffic conditions
• Construction and incidents

Description

The use of ITS data for traffic operation applications has the advantages of non-intrusion, continuous counts, and wider coverage. It also minimizes safety concerns associated with data collection on high-volume routes. Traffic data from ITS sources is of great interest to traffic monitoring programs and HPMS in particular. As stated earlier, the bulk of HPMS volume data is from short counts of 24 to 48 hours in duration. ITS sensors, while still not capable of serving as permanent counters, can efficiently provide at least a day's or two worth of data.

Examples of Use in States

FHWA conducted a survey to assess the use of ITS detectors for HPMS data reporting (Gillmann, 2002). Some of the findings from the 43 respondents were:

• In all, 70 percent of the States have ITS traffic detectors available and almost one-half of these States are currently using some of them for HPMS reporting purposes.
• One-third of these States are using some ITS traffic detectors to supply HPMS traffic data. Several noted that the number of ITS detectors available was currently limited but was expected to increase in the future.
• Other answers were that the data quality was poor or that it is still under consideration.
• Thirty percent of these States currently have no ITS traffic detectors.
• Several said they were willing to use them or expected to have them in the future.

On the question of whether ITS data can be used for AADT reporting, most states responded with a "qualified" yes except New Jersey, which said no. The three main concerns with the use of ITS-generated data are (i) validation of data, (ii) requirements of 24-hour continuous hourly data on all lanes, and (iii) vehicle classification data.

Some of the major initiatives and successes with the use ITS data by state DOTs are described below:

1. Caltrans is in the process of developing sensor-sharing technology to use the existing infrastructure of loops, cabinets and power supplies to collect planning data. Caltrans developed a "detector isolation assembly (DIA)" device that could provide total isolation between the traffic recording and the traffic control functions. The DIA device is housed in the same cabinet as the traffic controller and senses the electronic switch closure produced by the detector and passes the signal to the traffic recorder. This technology offers great potential for using existing infrastructure to obtain planning data and is of immediate use at high-volume locations with traffic controllers and ITS detectors (Triplett & Avis, 2002). California does not use ITS data yet for HPMS reporting. However, the state DOT counting program has about 219 locations where detector infrastructure on signals and ramps are shared. Ohio DOT, working on the same principle of detector sharing, uses loops currently not used for operational analysis by the ITS groups for its traffic data collection.

2. Caltrans has a Performance Measurement System (PeMS) for the inductive loops in California. PeMS obtains 30-second loop detector data in real time from each Caltrans District Transportation Management Center (TMC). The data are transferred through the Caltrans wide area network (WAN) to which all districts are connected. Users can access PeMS over the Internet through a Web browser. The PeMS software architecture is modular and open. It uses commercial-off-the-shelf products for communication and computation. Caltrans is working with the PeMS project team to enable transfer/sharing of data between the PeMS databases and the state highway counting program. The PeMS project team will aim to provide loop detector data aggregated at one-hour intervals in TMG format. The use of PeMS data will provide the state highway traffic-counting HPMS AADT for program with a wealth of detectors that can function either as permanent detectors or control points. Data sharing and use of PeMS data are currently being considered, and it is expected that the full potential of PeMS to state highway traffic monitoring will be realized in a few years.

3. ODOT uses ITS data from ARTIMIS that provides the data in TMG format to ODOT. ODOT also gets information from certain unused loops installed by Columbus TMC by obtaining loop outputs for a period of time using a contact closure card. ODOT installed 44 new Roadway Weather Information Systems (RWIS) that will collect traffic data in TMG format and provide real-time weather information.

4. ITS data from Detroit freeways are extensively used for AADT reporting in Michigan. Michigan ITS (MITS) is responsible for collecting and summarizing traffic data into hourly intervals. The data are provided to MDOT once a month. MITS is responsible for the quality checks on the raw data. This is a relationship that has grown and been in place for the past 12 years. The ITS data also provide more control points to the ramp counting program.

5. FDOT has conducted research to utilize archived ITS data for HPMS and transportation planning purposes. The project is completed in District 5 (I-4 in the Orlando area). FDOT has developed a software system to mine ITS data from the I-4 region in Orlando. The software is used to convert the data obtained from TMC to a format usable by the quality control software (Survey Processing Software). The plan is to expand it to other TMCs. Coordination between various agencies is essential for this to succeed. FDOT indicated that as a first step, data from ITS sources have to be available in an archive. There should be an emphasis to collect data from all lanes of traffic. Metadata, including the use of active/inactive/malfunctioning tags, sample sizes, and editing procedures used, are very helpful in making ITS data more useful to planning and traditional traffic monitoring groups.

6. Illinois uses data from toll way authorities and CATS in the Chicago area collected using a combination of loops, toll plazas etc to collect data on these high-volume roads. IDOT would like to have 365 days of hourly data from ITS data which would be beneficial. This then can be then used for k-factor calculation. This would require current ITS sensors to aggregate and store large amounts of data

7. TxDOT is exploring the use of ITS data from their loops in Houston (TranStar) and Dallas. Various options, formats, and institutional arrangements are being considered. TxDOT does not want data from all detectors from the ITS groups but strategic locations would be very valuable.

8. WSDOT uses ITS data in the Northwest (Seattle) region and plans to use data from new detectors for a TMC in Spokane.

9. VDOT does not currently use ITS data sources but are progressing toward use for HPMS reporting. The ITS TMCs are beginning to report the data to a central archive (Smartravel Lab) and ongoing research is directed at using the data for various purposes.

Sources of further information:

• Triplett, R. and Avis, J. Sensor Sharing Among Applications. 2002 NATMEC, Orlando, Florida. Available from NATMEC 2002 Proceedings CD

Additional Information on CD

• Gillmann, R., Status of ITS Data for HPMS, Memo for FHWA, 2002
• Choe, T., Skabordonis, A., Variya, P., Freeway Performance Measurement System (PeMS): An operational analysis tool, for presentation and publication in the 81st TRB Annual Meeting, 2002

D1. Data Processing and Quality Control Procedures

Issues Addressed

• Raw data analysis and AADT estimation
• Assumptions and business rules
• Data quality control and assurance issues

Description

Data processing to assess accuracy, completeness, and validity of traffic data from continuous count stations is carried out using either in-house software packages or legacy mainframe programs. Typically, a software package is used to flag potentially erroneous data for further review. Similarly, data from short-term counts are processed with in-house software packages or one supplied with the equipment. Data validity and completeness are checked using a combination of business rules and criteria.

Examples of Use by States

Processing Software Validity Rules

1. All states interviewed use software to flag potentially erroneous data for further review by DOT personnel who have extensive local knowledge and experience. Most of the states DOTs interviewed do not use data processing software to process short-term count data except in cases where vendor-provided software is used to download data from the device. Some states have in-house software packages to process short-count data (e.g., Florida uses a software product called "Survey Processing Software"; Washington State uses an in-house program; New Jersey uses TRADAS, a commercially available system and legacy mainframe software that was developed in-house).
2. Several states are in the process of developing a comprehensive database system to store, process, and query all their traffic data. These database systems are also expected to have rigorous quality control and assessment procedures. For example, Texas is developing the Statewide Traffic and Recording System (STARS), Ohio is developing Traffic Keeper-Ohio (TKO), and Georgia is updating their QC/QA system. California is already using a relational database system called the Transportation Systems Network (TSN).
3. All states interviewed use validity criteria or data processing rules to assess the quality of the data. Data processing rules used by the states interviewed are based on AASHTO and TMG guidelines and included range checks, completeness of data, and lane-distribution splits. Figure 3.4 below is an example of the checklist for editing traffic counts in California.

Figure 3.4: California's Checklist for Editing Traffic Counts⁵

4. Virginia uses a detailed quality assessment procedure that includes six different categories of quality as shown in Figure 3.5. Data from ATRs are processed and determined to fit into six quality groups ranging from data not acceptable to VDOT to data acceptable for all purposes. Some error messages from the automated count processing system used to process data at VDOT are also shown in Figure 3.5.

Figure 3.5: Virginia's Quality Flags and Error Messages from the Information System⁶

5. FHWA initiated a pooled fund study with Minnesota, Wisconsin, South Dakota, Indiana, New York, Connecticut, North Carolina, South Carolina, Georgia, Florida, New Mexico, California, Idaho, and Montana to develop a system for consistent traffic data quality edits. Although concluded before all its intended objectives were met, the study compiled a list of all data-screening tools used by one or more of the participating states as they are applied to short or continuous volume, vehicle classification, and/or WIM data for the selected data products. The report included a set of logically consistent, state-of-the-practice rules for traffic-data screening derived from five, multiple-day knowledge-engineering sessions attended by more than 60 traffic-data screening experts. The report also included traffic-data screening algorithms, definitions, and pseudo-code statements to support the development of rule-based testing software (MnDOT, 1997).

Sources of further information

• Triplett, R. and Avis, J. Sensor Sharing Among Applications. NATMEC, Orlando, Florida, 2002. Available from NATMEC Proceedings CD

Additional Information on CD

• Fekpe et al., Traffic Data Quality Workshop and Action Plan, Report to FHWA, 2003
• Ohio Department of Transportation, Traffic Keeper-Ohio (TKO) Traffic Edit Guidelines, Service, Acceptance and Warranty Requirements
• New York State Department of Transportation, Highway Data Services Bureau, Traffic Count Editor: User Manual and System Documentation, February 2003
• Florida Department of Transportation, Survey Processing Software (SPS) User Manual, June 2001.

D2. Adjustment Factors and Growth Factors Calculation

Issues Addressed

• Raw data analysis and AADT estimation
• Assumptions and business rules
• Data quality control and assurance issues

Description

Adjustment factors are used to convert short-term volume counts to AADT. These factors include seasonal factors which account for daily, monthly, weekly variations in data; axle correction factors use when axles instead of vehicles are counted; and growth factors when counts are not available. Most states interviewed indicated that estimating these adjustment factors are based on the recommendations of the TMG. Some states have detailed documentation of the methods used to calculate these factors. It was observed what while adjustment factors were calculated based on factor groups, these groups were mostly determined by functional classifications rather than by traffic volumes. There is no difference in the procedures for calculating the adjustment factors based on traffic volumes.

Examples of Use by States

1. ODOT uses a total of 84 factors (12 months * 7 days) which are generated using 3 year rolling averages from ATRs for each functional class. These factors are calculated using a mainframe program. These are updated yearly.

2. FDOT calculates two traffic adjustment factors using proprietary TranStat database software and can be accessed through the DOT Infobase under IMS from the Traffic Characteristics Inventory (TCI) databases. TCI contains both current and historical information. The continuous counts and the seasonal classification counts provide the necessary information to establish traffic adjustment factors. In the absence of any continuous counts within a county, TranStat borrows seasonal factors from adjacent county sites and assign seasonal factors for these sites. These adjustment factors are later applied to the short-term counts to estimate AADT, K30, D30, and T. Details are available in FDOT's "Project Traffic Forecasting Handbook" [CD]. FDOT also has a video on AADT estimation procedures in their traffic monitoring handbook

3. TxDOT uses seasonal factors from ATRs and truck factors from classification stations. 12-month rolling summaries are used to generate adjustment factors. TxDOT plans to move towards calendar year based averages.

4. California has a slightly different approach to adjustment factor calculation. During any 12-month period there are consistent variations in traffic volume by month, day, and hour. The changes that may occur in this consistent pattern for a specific count location are attributable to normal growth in traffic volume and random incidents affecting the site. Given these consistent variations, factors can be developed for any day of the week, month of the year, and season fluctuation to be used in estimating AADT. These factors are defined below⁷.

   The L factor measures the level of traffic by the day of the week. The seven-day average equals 1.00. The factors typically range from 0.80 to 1.20. The daily traffic volumes are related to AADT by L (level) factor. The L factor is calculated by the following formula:

   L =	(Annual average daily count for one day of the week ----------------------------------------------------------- 7-day annual average daily traffic (AADT)

   Where: 7- day counts are taken for 4, 8, or 12 months on a symmetrical basis in a year. The R factor measures the Range of fluctuation between average summer and average winter traffic. This factor is calculated by day of week as well as a 7- day average. The factors typically vary from 0.00 to 0.70. For a few control stations that have higher traffic in the winter than in the summer, the factor is negative. There are a few control stations with extreme summer/winter fluctuations causing the factor to be higher than 0.70. The R factor is calculated by the following formula:

   R =	(Ave. Summer months) – (Ave. Winter months) ------------------------------------------------------------------- 0.5N * AADT
   Where: N = the number of months counted. 7-day counts are taken for 4, 8, or 12 months on a symmetrical basis in a year.

   The I factor measures the Incremental changes in the R factor from month to month in the fluctuation from summer to winter. The factors typically vary from 0.00 to +/- 10.00. If the R factor is very close to 0.00 the I factor is larger. How much a month is "R" differs from the Average "R". This is needed to adjust the specific day profile counts R factor. The I factor is calculated by the following formula:

   I =

   V – A ------------ AR

   Where: V = Monthly average daily traffic A= Annual average daily traffic. R = 7-day R factor.

   These factors are recomputed every year. The station AADT is then calculated by dividing Profile Count Volumes (counts for which one day of complete data is available) by the average L factor for back and ahead traffic stations (ATRs) for the same day of week, plus average R factor for back and ahead ATRs for the same day of week, multiplied by the incremental regional factor, I, for back traffic station.

   AADT =

   Profile Count Volumes ----------------------------- L+ (R*I)

5. WsDOT has developed a short count Factoring Guide [CD] document available from the WsDOT website. The document contains information on the sensors used, the types of counts and the adjustment factors used. Adjustment factors are updated every year. A preliminary factor is applied to short term counts during the year and re-factored based on data from ATRs at the end of the year. The Factoring Guide discusses how WsDOT calculates and applies seasonal, day of week, and axle-correction factors. It does not discuss the fact that WsDOT creates expansion factors for application to manual count traffic data in order to estimate daily traffic from manual counts (which are conducted for less that 24 hours). These factors are based on short-duration classification count and annual traffic report data.

6. Michigan calculates adjustment factors from 2 year rolling averages of Permanent Traffic Recorders (PTR) data. Factors are calculated for 3 patterns of traffic (Urban to Recreational). These factors are calculated and adjusted every year.

7. ILDOT uses a 4-year rolling average from ATR counts for seasonal factors (monthly factors) calculated from ATR data for five categories – urban interstate, urban noninterstate, rural non-interstate and recreational roads. No Day-of-Week (DOW) factor is used as IDOT schedules only 24 hour counts on a weekday and does not count on weekend and holidays. The Chicago area does not have different adjustment factors as of date but IDOT is working towards developing a new set of factors for the Chicago area. To this end, IDOT has added 38 new ATRs in the Chicago region between 1998 and 2000.

8. Virginia uses ATRs to determine the adjustment factors (7 days (DOW) × 12 months). The factors are computed yearly. Axle correction factors are also calculated. ATRs are also used to develop growth factors for AADT estimates created from short-term counts not being counted in the current year of the three-year cycle.

9. In Massachusetts, seasonal adjustment factors are developed from the permanent inductive loop/piezo cable stations. The axle correction factors are developed from the TMG/HPMS required 300 vehicle classification stations (100/year on a 3 year cycle). The factors are developed and updated each year. They are entered into a MS Excel spreadsheet by group for seasonal adjustment factors and functional classification for axle correction (truck) factors, and then analyzed to develop the listed adjustment factors.

10. In New Jersey, pattern factors (Seasonal Adjustment Factors) are computed by grouping continuous monitoring stations into broad functional class groups (i.e., rural interstate, other rural, urban interstate, other urban, and recreational). For each station, the monthly average weekday is compared to the AADT, as is done for the group as a whole. Stations at which three or more months deviate from the group average by more than 20 percent are rejected from the group and considered as recreational pattern. The stations in each group are then analyzed and it the variation exceeds 20 percent, the station is considered ungrouped. This process is iterated until the stations within each group conform to the group pattern. Axle Correction Factors are computed by grouping all available vehicle type classification data by functional classification. The sum of vehicles by type is divided by total vehicles to determine percentage of vehicles by type. By using axles per vehicle type, average axles per vehicle is determined, and when divided into 2, the Axle Correction Factors are determined. These are averaged for three years of classification data to provide a three-year moving average. The pattern factors (Seasonal Adjustment Factors) are updated annually. The Axle Correction Factors are updated annually based on a three-year moving average.

Additional Information on CD

• U.S. Department of Transportation, Office of Policy, Traffic Monitoring Guide, 2001 Section 3, Chapter 4
• Washington Department of Transportation, Short Count Factoring Guide, June 2004
• Florida DOT, Project Forecasting Handbook, June 2000, Chapter 2
• Florida DOT, AADT Estimation Video, Traffic Monitoring Handbook, 2002

________________
³Interview with Tom Schinkel, Virginia Department of Transportation for FHWA's Traffic Data Quality Workshop project, October 1, 2002.
⁴NYSDOT, Zone 3 Contractor Specifications, June 2003.
⁵California Department of Transportation (Caltrans), Guide for Staff to review traffic data, from Joe Avis, Chief, Traffic Data and Photolog Unit, Division of Traffic Operations.
⁶Virginia DOT, Average Daily Traffic volumes on Interstate, Arterial and Primary Routes, Glossary of Terms, 2001, available at http://www.virginiadot.org/projects/resources/(IAP)AADT.pdf
⁷Information provided by Joe Avis, Caltrans.

<< Previous

Contents

Next >>