National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

Rights & Permissions

topleft topright

TCRP Synthesis 77: Passenger Counting Systems (2009)
Transit Cooperative Research Program Synthesis Program (TCRPSYNTH)

Citation Manager

Boyle, Daniel K, Transportation Research Board. "Summary." TCRP Synthesis 77: Passenger Counting Systems. Washington, DC: The National Academies Press, 2009.

Please select a format:

BibTeX EndNote RefMan


Page
26
bottomleft bottomright
Page
26
Front Matter (R1-R9)
Summary (1-6)
Technical Approach (7-7)
Organization of the Report (8-8)
How Automatic Passenger Counter Data are Used (9-9)
Implementation of Automatic Passenger Counting Systems (10-10)
Summary (11-11)
Why Collect Ridership and Travel Time Data (12-12)
Means of Collecting Ridership Data (13-13)
Use of Automatic Passenger Counters at Transit Agencies (14-14)
Automatic Passenger Counting Data: Processing, Validating, and Reporting (15-17)
Orgainization and Resource Requirements (18-19)
Summary (20-22)
Satisfaction with Automatic Passenger Counter Systems (23-23)
Lessons Learned from Survey Responses (24-25)
Summary (26-26)
OC Transpo (OttawaCarleton Regional Transit Commission), Ottawa, Ontario, Canada (27-28)
RTD (Regional Transportation District), Denver, Colorado (29-30)
NFTA (Niagra Frontier Transportation Authority) - Buffalo, New York (31-32)
RTC (Regional Transportation Commission of Washoe County), Reno, Nevada (33-33)
Metro Transit - Madison, Wisconsin (34-34)
TRIMET (Tri-County Metropolitan Transportation District), Portland, Oregon (35-37)
Automatic Passenger Counter Data: Processing, Validating, and Reporting (38-38)
Lessons Learned (39-39)
Conclusions and Areas of Further Study (40-41)
References (42-43)
Acronyms (44-44)
Appendix A - TCRP Synthesis Survey: Passenger Counting Technologies (45-56)
Appendix B - TCRP Synthesis Survey Results (57-68)
Appendix C - List of Participating Transit Agencies (69-70)
Appendix D - Agencies and Automatic Passenger Counter Manufacturers (71-74)

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 26
26 · Realize that good upfront training is needed. · Results regarding agency satisfaction with the perfor- · Train, train, and train again. mance of its APC system in terms of counting passen- gers are positive. Forty percent were very satisfied, and Survey Responses: Other--Procedures 45% were somewhat satisfied. · The primary benefits of APCs included data disag- · Establish and track bus assignment procedures to iden- gregated at the stop, segment, and trip levels; better tify any problems. quality of ridership data; availability of running time · Make sure a crosssection of the fleet is APC- data to adjust schedules; and a better basis for decision equipped. making. · Provide online assignment instructions to dispatchers · Problems encountered with the APC system included to ensure correct assignments. reporting software, data processing and analysis, data · Realize that integration with scheduling software is a validation, and hardware problems. One-quarter of all major factor in how the system will work. respondents reported either no problems or the usual · Get prior FTA approval to use APC data for National start-up issues. Transit Database (NTD) reporting. · Contract elements, procurement procedures, purchase · Realize that other agencies took their lumps in getting of additional APC units, and the overall approach to approval of APC data for NTD, so you should not have APC implementation were the most frequently men- to do the same. tioned aspects of the APC process that transit agencies would like to change. Stricter contractual requirements, Survey Responses: Other--Staff and Management purchase of a complete system through a single vendor, and changes to internal procedures were all important. · Realize that some employees are not so open to change. Changes to the overall approach included being more · Do not get rid of all traffic checkers; they are needed informed about hardware and software choices, involv- for other purposes such as NTD. ing maintenance personnel at the start of the process, · Realize that ongoing support from upper management dedicating one or more technicians to work full time on is important. APCs, completing the bus stop inventory before instal- lation, and hiring a statistician to develop a methodol- Survey Responses: Other--APC System Inputs ogy for passenger counting before vendor selection. · Almost three-quarters of all survey respondents that · Make sure bus stops have correct GPS coordinates and have implemented APC systems shared lessons learned route inventories are accurate. from the process. Agencies focused on use and valida- · Understand the data requirements for stop matching tion of the APC data, purchase and implementation, and establish a system to generate the required data and ongoing agency maintenance in the discussion before implementation. of lessons learned. Agencies offered lessons in many areas, but the emphasis on data systems and agency procedures suggests that these areas are critical to the SUMMARY success of APC implementation. This chapter has described agency assessments of automatic The following chapter describes findings from six case passenger counter (APC) systems. Findings include the studies that explore issues related to APC implementation following: and use in greater detail.