user’s guide · passenger counting program user’s guide may 1999 san diego association of...

0000

PASSENGER COUNTING PROGRAM

User’s Guide

Volume

1

Board of Directors San Diego Assoc ia t ion o f Governments

The 18 cities and county government are SANDAG serving as the forum for regional decision-making. The Association builds consensus, makes strategic plans, obtains and allocates resources, and provides information

on a broad range of topics pertinent to the region’s quality of life.

CHAIRMAN: Hon. Art Madrid VICE CHAIR: Hon. Ramona Finnila

SECRETARY-EXECUTIVE DIRECTOR: Kenneth E. Sulzer

CITY OF CARLSBAD Hon. Ramona Finnila, Councilmember (A) Hon. Bud Lewis, Mayor (A) Hon. Matt Hall, Mayor Pro Tem CITY OF CHULA VISTA Hon. Shirley Horton, Mayor (A) Hon. Mary Salas, Mayor Pro Tem CITY OF CORONADO Hon. Thomas Smisek, Mayor (A) Hon. Chuck Marks, Councilmember CITY OF DEL MAR Hon. Richard Earnest, Mayor (A) Hon. Crystal Crawford, Councilmember CITY OF EL CAJON Hon. Richard Ramos, Councilmember (A) Hon. Mark Lewis, Mayor CITY OF ENCINITAS Hon. Dennis Holz, Deputy Mayor (A) Hon. Sheila Cameron, Mayor CITY OF ESCONDIDO Hon. Keith Beier, Mayor Pro Tem (A) Hon. June Rady, Councilmember CITY OF IMPERIAL BEACH Hon. Diane Rose, Mayor (A) Hon. Mayda Winter, Mayor Pro Tem (A) Hon. Patricia McCoy, Councilmember CITY OF LA MESA Hon. Art Madrid, Mayor (A) Hon. Barry Jantz, Councilmember (A) Hon. Jay La Suer, Councilmember CITY OF LEMON GROVE Hon. Mary Sessom, Mayor (A) Hon. Jill Greer, Councilmember CITY OF NATIONAL CITY Hon. Ron Morrison, Vice Mayor (A) Hon. George H. Waters, Mayor CITY OF OCEANSIDE Hon. Carol McCauley, Councilmember (A) Hon. Colleen O’Harra, Deputy Mayor CITY OF POWAY Hon. Don Higginson, Councilmember (A) Hon. Mickey Cafagna, Mayor (A) Hon. Robert Emery, Deputy Mayor

CITY OF SAN DIEGO Hon. Barbara Warden, Councilmember (A) Hon. Juan Vargas, Councilmember (A) Hon. Byron Wear, Deputy Mayor CITY OF SAN MARCOS Hon. Hal Martin, Councilmember (A) Hon. Pia Harris-Ebert, Vice Mayor CITY OF SANTEE Hon. Jack Dale, Mayor (A) Hon. Hal Ryan, Councilmember (A) Hon. Jim Bartell, Vice Mayor CITY OF SOLANA BEACH Hon. Marion Dodson, Mayor (A) Hon. Joe Kellejian, Deputy Mayor (A) Hon. Marcia Smerican, Councilmember CITY OF VISTA Hon. Gloria E. McClellan, Mayor (A) Hon. Judy Ritter, Councilmember COUNTY OF SAN DIEGO Hon. Pam Slater, Chairwoman (A) Hon. Greg Cox, Supervisor STATE DEPT. OF TRANSPORTATION (Advisory Member) Jośe Medina, Director (A) Gary Gallegos, District 11 Director U.S. DEPARTMENT OF DEFENSE (Liaison Member) CAPT Tom M. Boothe, USN, CEC Commander, Southwest Division Naval Facilities Engineering Command (A) CAPT Robert Westberg, USN, CEC SAN DIEGO UNIFIED PORT DISTRICT (Advisory Member) Jess Van Deventer, Commissioner SAN DIEGO COUNTY WATER AUTHORITY

(Advisory Member) Frank Chenelle (A) John Fowler TIJUANA/BAJA CALIFORNIA/MEXICO (Advisory Member) Hon. Luis Herrera-Lasso M. Consul General of Mexico Revised March 31, 1999

PASSENGER COUNTING PROGRAM User’s Guide

M A Y 1 9 9 9

San Diego Association of Governments 401 B Street • Suite 800

Telephone 619.595.5300 • Fax 619.595.5305 http://www.sandag.cog.ca.us

ABSTRACT

TITLE: Passenger Counting Program, User’s Guide

AUTHOR: San Diego Association of Governments

DATE: April 1999

LOCAL PLANNING AGENCY: San Diego Association of Governments

SOURCE OF COPIES: San Diego Association of Governments 401 B Street, Suite 800 San Diego, CA 92101

NUMBER OF PAGES: 108

ABSTRACT: This document provides the information necessary to operate the Passenger Counting Program and related utilities. It documents the procedures necessary to obtain count information, process the data, and the generation of various output products.

Table of Contents

Introduction_________________ 1 History _______________________1

Purpose ______________________2

Introduction to Passenger Counting_____________________________3 Sampling Procedure_______________ 3 Preparations for Counting __________ 3 Selecting Trips to Count ___________ 3 Scheduling Counts________________ 3 Counting Passengers ______________ 4 Processing Count Information _______ 4 Output _________________________ 6

Future Directions ______________7

Getting Started with PCP_______ 1 Program Overview _____________1

Getting Your Bearings __________1 PCP Basics______________________ 1

Window Components ____________ 1 Active versus Inactive Window Components ___________________ 3 Hot Keys______________________ 4

Starting PCP ____________________ 5 Starting from an Icon ____________ 5 Starting Manually _______________ 5

PCP Menu Structure ______________ 7 Exiting PCP _____________________ 8

Getting Help __________________9 Dynamic Help on Window Components_______________________________ 9 Help Menus ____________________ 10

Maintaining Codes and Abbreviations ________________ 1

Company Numbers_____________2

Counter IDs ___________________3

Day Codes ____________________4

Direction Codes________________5

Intersection Codes _____________ 6

Miscellaneous Codes____________ 9 New Type______________________10 ADA Codes ____________________11 Bench _________________________12 Block _________________________13 Shelter ________________________14 Vehicle Type ___________________15

Place Codes __________________ 16

Time Periods _________________ 17

Vehicle Codes ________________ 18

Maintaining the Stop Inventory _ 1 Unique Stop Identifiers _________ 1

Stop Information ______________ 2

Field Work ___________________ 2

Editing Stop Data ______________ 3 Selecting a Stop __________________3 Adding a Stop ___________________5 Modifying a Stop _________________5 Deleting Stops ___________________5

Route Information Maintenance_ 1 What is a Route________________ 1

Field Work ___________________ 1

Editing Routes_________________ 2 Selecting a Route _________________2 Route Editing Options _____________3

Displaying Stops on a Route_______4 Editing a Route _________________5 Changing a Route’s Description ____8 Creating a New Route____________8 Deleting a Route ________________9 Using Find ___________________10 Sorting Routes ________________10 Copying Routes _______________10

Processing Counts ____________ 1 Loading Count Data____________ 1

Command Line Utility _____________1 PCP Load Option_________________1

Validation Criteria _____________ 2 Validations for header fields:________2 Validations for stops: ______________2 Validations for stop count rows: _____2

Validations for arrival/departure/scheduled time fields: 2 Validations for fields relating to passengers:______________________ 3

Validating a Count _____________3 Selecting a Count for Validation _____ 3 Editing a Count __________________ 5 Deleting a Count _________________ 7 Combining Counts________________ 7 Using Find ______________________ 8 Sorting Counts ___________________ 8 Copying Counts __________________ 8

Working With Validated Counts__9 Selecting a Validated Count ________ 9 Displaying a Count ______________ 11 Using Find _____________________ 11 Sorting Counts __________________ 11 Copying Counts _________________ 12 Revoking Validation _____________ 12 Using Omit ____________________ 12

Route Reports ________________ 1 Running Route Reports _________1

Output Destinations ____________2 Display_________________________ 2 To a File________________________ 2 To a Printer _____________________ 3 Plain Text vs Postscript ____________ 3

Route Reports _________________4 Report 1: Dates Checked Summary___ 4 Report 2: Route Profile ____________ 5 Report 2A: Route Profile for Trains & Trolley _________________________ 6 Report 3: Trip Summary ___________ 7 Report 4: Ons, Offs, Thrus _________ 8 Report 4A: Detailed Ons, Offs, Thru__ 9 Report 4E: Spreadsheet ___________ 10 Report 5: On Time Summary by Stops______________________________ 11 Report 5A: On Time Summary _____ 12 Report 5B: On Time Summary by TP 13 Report 6: Section 15 _____________ 14 Bus Stop Inventory Field Listing____ 15 Bus Stop Inventory Dump _________ 16

Year End Processing __________ 1 Running Year End Reports ______2

Section 15 Processing ___________3 Section 15 Report ________________ 4

Route Profiles _________________ 5 System Daily Profile ______________5 System Daily Profile (Sunday) ______6 System Daily Profile (Saturday) _____7 On Off Reporting _________________8

On-Off Summary by Trip Ends ____8 On-Off Summary by Ons _________9 On-Off Summary by Offs________10 On-Off Summary by Place _______11 On-Off Summary by Bus Stop Description ___________________12

Other Year End Processing ________12

Count Data Analysis __________ 1 View2Transit Introduction and Count Inputs __________________ 1

Analysis by Geographic Area _______1 Analysis by Jurisdiction____________2 Segment Analysis ________________2

Database Maintenance ________ 1 Managing Counter Data ________ 1

Archiving Counts_________________1 Restoring Counts _________________1

Maintaining the Database _______ 2 Auditing the Counter Database ______2 Optimizing the Counter Database ____2 Performing Database Backups_______3

Checkpoints and Journals _________3 Unloading the Database __________3 Recommended Practices__________4

Table of Figures Figure 1: Help Menu Window _________ 10 Figure 2: Help Window ______________ 10 Figure 3: Dictionary Menu ____________ 1 Figure 4: Company Number Edit Window_ 2 Figure 5: Counter ID Edit Window ______ 3 Figure 6: Day Code Edit Window _______ 4 Figure 7: Direction Code Edit Window ___ 5 Figure 8: Bus Stop Intersection Diagram _ 6 Figure 9: Intersection Edit Window______ 8 Figure 10: Miscellaneous Codes Menu ___ 9 Figure 11: New Type Window _________ 10 Figure 12: ADA Code Edit Window_____ 11 Figure 13: Bench Edit Window ________ 12 Figure 14: Block Code Diagram _______ 13 Figure 15: Block Edit Window_________ 13 Figure 16: Shelter Code Edit Window___ 14 Figure 17: Vehicle Type Edit Window___ 15 Figure 18: Place Code Edit Window ____ 16 Figure 19: Time Period Edit Window ___ 17 Figure 20: Vehicle Information Company Select Menu _______________________ 18 Figure 21: Vehicle Information Edit Window __________________________ 19 Figure 22: Stop Selection on Dictionary Menu _____________________________ 3 Figure 23: Maintain Stop Inventory Window__________________________________ 3 Figure 24: Selecting Stops by Street _____ 4 Figure 25: Stop Selection Results for a Street _____________________________ 4 Figure 26: Route Select on Dictionary Menu__________________________________ 2 Figure 27: Maintain Route Dictionary Window ___________________________ 3 Figure 28: Maintain Route Dictionary Options____________________________ 3 Figure 29: Stops on Route Window ______ 4 Figure 30: Stop Information Window ____ 5 Figure 31: Error Message Window about Counts on Route_____________________ 5 Figure 32: Route Edit Window _________ 6 Figure 33: Route Edit Option Menu _____ 6 Figure 34: Route Description Change Window ___________________________ 8

Figure 35: Create New Route Slide Out Menu______________________________8 Figure 36: Create New Route Window ___9 Figure 37: Find Route Window ________10 Figure 38: Main PCP Window for Count Validation__________________________3 Figure 39: Unvalidated Count Display Window____________________________4 Figure 40: Count Validation Menu ______4 Figure 41:Route Count Editor Window ___5 Figure 42: Count Combine Window _____7 Figure 43: Main Window for Validated Counts ____________________________9 Figure 44: Display of Validated Counts _10 Figure 45: Validated Count Menu ______10 Figure 46: Detail Validated Count Information Window_________________11 Figure 47: Route Reports Window_______1 Figure 48: Report File Directory Structure 2 Figure 49: Output Selection Option______3 Figure 50: Year End Report Window_____2

Table of Tables Table 1: Company Number Field Descriptions ________________________ 2 Table 2: Counter ID Field Descriptions __ 3 Table 3: Day Code Descriptions ________ 4 Table 4: Direction Code Field Descriptions__________________________________ 5 Table 5: Bus Stops Near Street Intersection6 Table 6: Bus Stops in Mid-Block ________ 6 Table 7: Intersection Field Descriptions __ 8 Table 8:ADA Code Field Descriptions __ 11 Table 9: Bench Field Descriptions _____ 12 Table 10: Block Code Field Descriptions 13

Table 11: Shelter Code Field Descriptions_________________________________14

Table 12: Vehicle Code Field Descriptions_________________________________15

Table 13: Place Code Field Descriptions 16 Table 14: Time Period Field Descriptions 17 Table 15: Vehicle Field Descriptions____19 Table 16: Information Maintained about a Stop_______________________________2 Table 17: Stops on Route Column Descriptions ________________________4 Table 18: Route Count Editor Table Columns ___________________________5

1111

Introduction The Passenger Counting Program provides ridership and other performance data to the region's fixed-route transit operators. There are currently eight fixed-route transit operators providing service in the San Diego region:

1. San Diego Transit Corporation (SDTC),

2. North County Transit District (NCTD),

3. Chula Vista Transit (CVT),

4. San Diego County Transit Service (CTS),

5. National City Transit (NCT),

6. MTDB contract Routes (MTDB),

7. San Diego Trolley Inc. (SDTI),

8. San Diego Northern (SDN)

This on-going program updates passenger boardings and alightings by bus stop for each route on an annual basis.

History The Passenger Counting Program (PCP) was begun in 1979 in response to the Urban Mass Transit Administration’s (UMTA) Section 15 requirements. Since then the UMTA has become the Federal Transit Administration (FTA). The original program was written in FORTRAN by Robert Parrot. Various updates were made over a period of 15 years and the software was hosted on a Prime minicomputer at SANDAG. In 1995 the program was totally re-written using a fourth generation object oriented language called OpenROAD coupled to a fully relational database, Ingres.

Chapter

1

2222

Purpose The Passenger Counting Program (PCP) was begun in 1979 in response to the Urban Mass Transit Administration’s (UMTA), now the Federal Transit Administration (FTA), Section 15 requirements. FTA grants federal subsidies to local transit agencies to assist the local transit companies in developing and improving mass transportation facilities, equipment, and systems. SDTC and NCTD are required to report transit operation and performance indicators to FTA in order to receive operating funds under Section 15. The data obtained from the Passenger Counting Program satisfy FTA Section 15 requirements as well as provide all transit companies with information used in planning efforts such as: · Route realignment · On-time performance evaluation · Service frequency evaluation · Facility improvements · Bus stop location Basic information provided in reports includes the number of passengers boarding and alighting at each bus stop, ridership by trip and time of day, and on-time performance at each time point. Calculated data includes the number of passenger and revenue miles, average trip lengths, passenger and revenue minutes, standing and seated capacities, maximum loads, gallons of fuel used, and miles over seated capacity.

Transit Operators

SANDAG

FTA

PCP

Counter DB

Funding

Reports

Funding

Reports

Reports

Schedules, Stop

inventory, Vehicle

information

Counters

Schedules Counts

Arcview

3333

Introduction to Passenger Counting

Sampling Procedure SANDAG uses an accepted alternative sampling procedure for counting bus routes. Each route is counted once per fiscal year (July 1 - June 30) and the order by which it is counted is randomly selected. At times this is inefficient for the transit operators because they cannot always get data for a particular route when they need it. Special counts may be requested when data for a particular route is needed at a specific time, but data from these special counts are not used in FTA Section 15 reporting. An example of a special count would be in the case of a randomly selected count falling outside the regular school year on a route having a high percentage of student riders, either K-12 or college. In such a case, a special count for planning purposes during the school year could be requested by the transit agency. Due to the large number of regional routes that must be counted, the number of special counts should be kept to a minimum.

Preparations for Counting The individual operators assist SANDAG in maintaining up-to-date schedule, bus stop inventory and other information. SDTC and NCTD provide scheduling information to reflect each new bid implementation; all other operators provide scheduling information upon request. Bus stop inventories are either provided annually or as updated. All operators should update their fleet rosters when adding new vehicles to their fleets. Information provided to SANDAG includes vehicle fleet number, seated capacity, and fuel mileage.

Selecting Trips to Count Counts are made on weekdays and weekends, excluding holidays only. By counting all weekday trips, the counts obtained represent weekday ridership for that time period. Weekend counts are scheduled at the same time the route is randomly selected for weekday counts and are processed separately from the weekday counts. Data collected on weekends are only a sampling of all trips and are used mainly for Section 15 reporting rather than in the transit planning process. A random process is used to select the sample of trips to be counted on weekends.

Scheduling Counts Scheduling for transit passenger counts is done in an Access data base. Trips are selected from scheduling materials provided by the operators with the following information entered into a data table: route number, company, bus yard name, run number, schedule number, how bus is to be met, shift start time, shift end time, number of hours to work, counter name, day of week, date, and whether another counter will be met at mid-route. From this information, a weekly schedule sheet is generated for each counter, as well as labels with the same information for individual

4444

daily assignment sheets. A list of weekly assignments is also generated for operators so that dispatchers are notified of all counts taking place.

Counting Passengers Once a route is selected for counting, all scheduled trips appearing in the public timetable for that route are counted. Tripper buses, which are either used to provide extra capacity for regularly scheduled trips or special service for schools and industry, are not counted. Depending on the level of service provided, some routes can be counted in a day, while others might take several days or weeks to count all scheduled trips of a route. San Diego Trolley counts typically take more than three months to accomplish. When counting smaller routes, the shifts should be spread over a two to four week period to get a more average representation of the route.

Processing Count Information Figure 1 shows the general structure of work flow in the passenger counting program. Passenger counting on the selected trips is done by two methods. Data may be entered directly into a TELXON electronic data collection device, or it may be manually recorded on a form for keypunch data entry. The information collected in the field is processed for each route individually. When the data from both sources, TELXON and paper, has been properly formatted, it is loaded in an INGRES database. Here the data may be validated for completeness with time points checked for accuracy. After all corrections have been made, the trip data is passed to a “validated table” where it may be accessed by the INGRES report writer. Reports may be produced for individual routes and for entire companies.

5555

Passenger Counting Program Processing

Update Counter Stop Inventory (in Excel)

Schedule Work for Counters

Obtain Schedules from Operators

Count Route(s)

Update Stop Inventory STOPS and VEHICLES

(Access ArcView, if necessary)

PAPER: (Data Entry)

TELXON: (Conversion)

Load into Counter DB (RAW_COUNT)

Validation

Route Analysis and Reporting

Output to Screen, File, or Printer

End of Year Processing

PCP Program Archive Fiscal Year

Counts

Reports to Transit Operators & FTA

6666

Output Prior to generating output reports, the following input parameters must be current and accurate: · Current bus stop inventory, including: Bus stop location codes GIS attributes Direction of bus at bus stop Mileage between bus stops Direction of travel · Current route schedule information · Coach seating capacity and vehicle miles per gallon The input parameters are combined with boardings/alightings and timepoint data to produce the following reports for operators: Report 1 Route Summary of boardings, alightings, maximum load, and

bus capacities by terminal time and direction. Daily boardings and alightings, average passengers per trip, average maximum load, and peak load factor by direction and daily total.

Report 2 Bus Route Profile shown graphically displaying maximum load by trip and direction.

Report 2A Rail Route Profile shown graphically displaying maximum load by trip and direction

Report 3 Trip Summary reporting starting terminal location, total passengers, most active bus stops, maximum load and maximum load point.

Report 4 Boardings, alightings, on-boards and thrus, by bus stop for the following time periods: Daily Total, AM (6:00 - 8:59), Midday (9:00 - 14:59), PM (15:00 - 17:59), and Other (18:00 – 5:59). Summarizes by direction and daily total for total passengers, passenger miles, average trip lenth, revenue miles, passengers per revenue mile, miles over capacity, and percent over capacity.

Report 4A Boardings, alightings, on-boards, thrus, number above seated capacity, and miles above seated capacity by bus stop for each scheduled trip. Provides trip summation of boardings and alightings, passengers carried over from the previous trip, passenger miles, average trip lenth, revenue miles, passengers per revenue mile, percent over capacity, seated capacity miles, and total capacity miles.

Report 4E This report is in tab delimited format for use in exporting to either a spreadsheet or database. Trip by trip data is provided by date of count, bus stop name, X geographic coordinate, Y geographic coordinate, boardings, alightings, on-boards, thrus,

7777

number above seated capacity, and miles above seated. Report 5 On time Summary for each trip reporting schedule adherence at

each time point. Report 5A On time Summary for all trips sorted by direction and time

period listing percent more than five minutes slow or departing time points early. A summation of total actual run time, trips counted, and passengers per revenue hour is provided.

Report 5B On time Summary for each trip listing scheduled time of time points along with actual arrival and departure times.

Report 6 FTA Section 15 statistics for route by time period. · Two additional reports, the bus stop inventory field listing and the bus stop inventory dump, are used by SANDAG for maintenance purposes. Year end reports available to each operator include: · On-off bus stop report This report can be generated with any number of operators’ data and may

be sorted by trip-ends, ons, offs, alphabetically, or by jurisdiction (alphabetically).

· System daily profile for weekday, Saturday, or Sunday for any number of operators.

· FTA Section 15 Report · ArcView Analysis Data for use in ArcView applications for planning purposes.

Future Directions The Passenger Counting Program is constantly evolving to meet the needs of transit operators. The next major enhancement will be the publication of counter information on the Internet.

1111

Getting Started with PCP

Program Overview The PCP system consists of the PCP Windows based program, various utility programs and the Counter database.

Getting Your Bearings

PCP Basics A program that uses windows can appear very complex at first glance. The following sections provide some basic information on operating a windows program with specific references to the PCP program.

Window Components The PCP program uses multiple “windows” to interact with the user. Each window consists of a number of “components” such as buttons, fields, menus, and tables. These components are illustrated below.

Chapter

2

Title Bar

Menu Bar

Dynamic Help Bar

Data Table

Data Field

Drop Down Combo Box

Scroll Bar

“Thumb”

Control Button

Button

Radio Buttons

Close ButtonMaximize Button Minimize Button

Scroll Button

2222

Buttons: A button is an area in a window you can click on with your mouse to instigate some action.

Control Button: Each data table has a control button located in the upper right corner. Clicking on the control button brings up a menu of operations that can be performed upon the currently selected row (or rows of information) in a data table.

Data Field: Data fields are rectangular boxes that the user can enter or edit information. The user can enter or edit information within a data field under program control.

Data Tables: Data tables are groups of data fields arranged in columns and rows. The user can enter or edit information within the data fields under program control. Data tables may contain more rows of information than the ones actually showing on the display. You can think of a data table as a window onto a larger table as shown in the example below.

To move through the information in the data table the users “scrolls” up or down using “thumb” or “scroll buttons” on the scroll bar as described under their respective headings.

Drop Down Combo Boxes: Some data fields permit only certain values to be entered. In order to make the selection of valid values easier for the user “Drop Down Combo Boxes” are used. Each box has a button with

Displayed portion of data table

Data Table

Contents

Additional undisplayed data above the scrolling “window”

Additional undisplayed data below the scrolling “window”

3333

a downward pointing arrow on the right hand side. When you click on the arrow the box expands to show the valid entries. You can scroll through the values and click on the one you want to select. The selected value is then displayed in the contents of the box.

Dynamic Help Bar: When you move the mouse over various components of the window messages appear in the “Dynamic Help Bar” describing what the component is (if information is available). For example, if you are not sure what goes in a field or what a button does, point to it with the mouse and look for an explanation in the “Dynamic Help Bar”.

Maximize Button: The maximize button is the middle of the three buttons located at the top right corner of the window. It allows you to toggle between a window that fills the entire screen or only fills a portion of it. When the window is maximized, the button looks like two overlapping rectangles and when window is “normal” (fills only part of the screen) it looks like just one rectangle.

Menu Bar: The second bar at the top of the window is the menu bar. It has a series of words you can click on to select an action. Most of the selections provide additional menus that allow you to select from a subset of related actions.

Minimize Button: The minimize button is leftmost of the three buttons located at the top right corner of the window. It allows you to shrink the window to an icon at the bottom of the screen. This normally done to clear the screen temporarily in order to perform other work without closing the application. To bring the application back up you double click on the icon.

Radio Buttons: Radio buttons are collections of buttons where only one can be selected at a time (like a car radio). The currently selected button has a dark center. When you select a different button the original button is cleared automatically.

Scroll Bar: Each data table has a scroll bar on the right side that allows you to scroll through the rows of information in the table (the displayed table as apposed to a database table). You move through the table using the scroll buttons and “thumb” (see the specific component descriptions below).

Scroll Button: At the top and bottom of a scroll bar (see definition above) are scroll buttons that allow you to move through the rows of a data table one row at a time. The button with an arrow pointing up will scroll the table up one row each time the button is clicked. The button with an arrow pointing down will scroll the table down one row each time the button is clicked.

Thumb: The “thumb” is a button that sits on a scroll bar (see definition above) and allows you to scroll through the rows of a data table using your mouse. To scroll you point to the “thumb” and hold down the left button while moving the mouse up or down. The data table will scroll in the direction you move the mouse. Some data table will dynamically scroll as you move the mouse while others the “thumb” will move but the displayed rows are not “scrolled” until you release the mouse button.

Title Bar: The top bar in window is the title bar and contains a header describing the window.

Active versus Inactive Window Components Window components can be active (available for interaction or selection by the user) or inactive (unavailable to the user). Window components become inactive when their use is not appropriate in the current context. Inactive components are display “grayed out” as shown in the example below.

4444

This example is taken from the menu of actions available for a validated count. The total range of actions for all counts is shown as “Display” through “Revoke Validation” but the “Edit”, “Delete” and “Combine” actions are “grayed out”. These actions cannot be selected since they do not apply to validated counts and are therefore made unavailable to the user.

Hot Keys Some PCP menu actions can be invoked by simply pressing one or a combination of keys. Such keys (or key combinations) are referred to as “hot keys”. If hot keys are available for a specific action, the corresponding key combination will be shown to the right of the menu item as shown below.

In this example you can invoke the “Display stops” action by simply pressing the “F8” key. Similarly, the “Delete current route” action can be invoked by pressing the “F3” key.

5555

Starting PCP PCP can be started in a number of ways with the two primary ones being through an icon or manually.

Starting from an Icon PCP is normally started from the Windows NT or Windows 95/98 environment by clicking on the OpenRoad runtime icon labeled PCP. The icon is located on the left-hand side of the main display. The icon shown below is a typical example of what the PCP icon would look like although the actual graphic used may vary at the whim of the user or system administrator. The icon should have a label of “PCP” as shown.

Starting Manually If the icon is not on your main display, PCP can be started by going to the start button and selecting Programs, CA OpenIngres x.x OpenROAD, Runimage (where x.x is the version number that is loaded on your system). This brings up the following window.

Enter the image file name, database and any other fields specified by the PCP system administrator. If you cannot find “CA OpenIngres x.x OpenROAD” or “Runimage” on your selection of programs, see your system administrator for assistance.

PCP

6666

Once the PCP application has been started, the following widow appears:

This is the main (top frame) window of the SANDAG transit passenger counting system application. It allows you to select the type of route counts you want to retrieve: validated or unvalidated. If you wish, you may set values in the company and/or counter fields to limit your selection. If you are retrieving validated counts, you may also set minimum and maximum dates for your selection. Further information on running specific operations using the PCP program, see the relevant section of this user manual.

7777

PCP Menu Structure The following diagram provides an overview of the PCP menu structure.

File Output DB Utilities Dictionary Help

Load Raw Data

Get Data

Clear

Quit

Route Reports

Year End

Reports

Count Listing

Archive

Restore

Routes

Stops

Vehicles

Places

Counter IDs

Companies

Directions

Miscellaneous

About this Application

About this Frame

8888

Exiting PCP To exit the PCP program click on the Quit button from the main window as shown below. You may have to exit secondary windows (using the close button on those windows) in order to get back to the main window.

Quit Key

9999

Getting Help There are three levels of help in the PCP program; dynamic help on displayed windows components, help on the currently displayed frame and help on the program in general.

Dynamic Help on Window Components Each window has a dynamic help bar and the bottom which displays information about the component the mouse is currently pointing to. Not all components have help information defined causing the bar to sometimes be blank. When there is information it describes what the field or component is and what it is used for. In the example below, the mouse is pointing to the “Get Data” button and the dynamic help bar provides information on what the button does.

Dynamic Help Bar

10101010

Help Menus Help is also available using menus. When you select “Help” on the main menu the following menu of help choices appears.

Figure 1: Help Menu Window

The first selection, “About this application” brings up a window with information specific to the PCP application. The second selection brings up information regarding the currently displayed window of “frame”. An example of the latter case is shown below.

Figure 2: Help Window

1111

Maintaining Codes and Abbreviations Various codes and abbreviations are used throughout the Passenger Counter Program. They are managed by the PCP program from the “Dictionary” menu. When you click on the Dictionary Menu from the main PCP window the possible codes are displayed as shown below. Select a particular code by pointing to it and double clicking.

Figure 3: Dictionary Menu

Routes and Stops are described in Chapters dedicated to each. The other codes are described in detail in this chapter..

Chapter

3

2222

Company Numbers Each transit company is assigned a unique number. The numbers are used to develop statistics on a specific company or group of companies. When “Companies” is selected from the Dictionary menu, the following window appears populated with the existing companies in company number order.

Figure 4: Company Number Edit Window

Company information can be edited or added using the “Maintain dictionary for companies” window. To edit information, click on the desired field and type in the change. To add a new company, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new companies. The table below provides guidelines for the proper values to enter in each field.

Table 1: Company Number Field Descriptions

Field Description Contents Code The company’s unique identification number A number between 1 and 9 that has not

already been assigned. Definition The name of the company The name of the transit company First Stop # The unique SANDAG stop identification

number for the first transit stop for this transit operator.

A number in the form 0-n001 to 0-n999 where n is the transit operators company number.

Last Stop # The unique SANDAG stop identification number for the last transit stop for this transit operator.

A number in the form 0-n001 to 0-n999 where n is the transit operators company number

3333

Counter IDs Each counter has an assigned unique counter ID. The ID numbers are used to track who performed a particular count so they can be consulted if there are questions regarding the numbers reported. When “Counter IDs” is selected from the Dictionary menu the following window appears populated with the existing counters in counter ID number order.

Figure 5: Counter ID Edit Window

Counter ID information can be edited or added using the “Maintain dictionary for counter ID” window. To edit information, click on the desired field and type in the change. To add a new counter, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new counter IDs. The table below provides guidelines for the proper values to enter in each field.

Table 2: Counter ID Field Descriptions

Field Description Contents

Code The counter’s unique identification number A number between 0 and 9999 that has not already been assigned.

Definition The name of the counter The first and last name of the counter

4444

Day Codes Each day of the week has a unique sequence number assigned to it starting with Sunday with a value of 1. The code is used to identify counts made during the week and those made on weekends. When “Days of Week” are selected from the Dictionary menu, the following window appears populated with the existing day codes in day code order.

Figure 6: Day Code Edit Window

Day code information should be considered static and only changed for a strong compelling reason. Changes in the day codes may not be automatically propagated throughout the logic of the program so changes should only be made by persons familiar with the program software. The table below provides guidelines for the proper values to enter in each field.

Table 3: Day Code Descriptions


Code The days unique identification number A number between 1 and 7 that has not already been assigned.

Definition The day of the week and whether it is a week or a weekend day.

A name of a day of the week with the type of day (week or weekend) in parenthesis.

5555

Direction Codes Each direction a transit vehicle can take has an assigned direction code. The direction codes are used to develop statistics on passenger volumes relative to the direction of travel. When “Directions” is selected from the Dictionary menu, the following window appears populated with the existing directions in direction code order.

Figure 7: Direction Code Edit Window

Direction code information can be edited or added using the “Maintain dictionary for direction code” window. To edit information, click on the desired field and type in the change. To add a new direction, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new direction codes. The table below provides guidelines for the proper values to enter in each field.

Table 4: Direction Code Field Descriptions

Field Description Contents Code The direction’s unique

identification number A number between 0 and 99 that has not already been assigned.

Definition A description of the direction

In Bound = traveling towards the main station Out Bound = traveling away from the main station North Bound = traveling in a northerly direction South Bound = traveling in a southerly direction East Bound = traveling in an easterly direction West Bound = traveling in a westerly direction Loop = route goes in a circle of undetermined direction Loop, Clockwise = route goes clockwise in a circle Loop, Counter Clockwise = route goes counter clockwise in a circle

6666

Intersection Codes Stops can occur at many different points relative to an intersection (sometimes referred to as a node). Intersection codes are used to specify exactly where a stop is, relative to the nearest intersection. The following figure and tables describe the currently defined intersection codes.

Figure 8: Bus Stop Intersection Diagram

Table 5: Bus Stops Near Street Intersection

Location From Street Intersection

Nearside Farside Direction of Bus at Stop

1 2 Eastbound 3 4 Westbound 5 6 Southbound 7 8 Northbound

Table 6: Bus Stops in Mid-Block

Direction from Intersection North South East West

Direction of Bus at Bus Stop

B A Eastbound D C Westbound

E F Southbound H G Northbound

1

4 3

2N

C

Northbound

7

Eastbound

Westbound

Southbound

58

6

B

GF

HE

D

A

8888

When “Intersection” is selected from the Dictionary menu, the following window appears populated with the existing Intersection information in intersection code order.

Figure 9: Intersection Edit Window

Intersection code information can be edited or added using the “Maintain dictionary for intersection code” window. To edit information, click on the desired field and type in the change. To add a new intersection, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new intersection codes. The table below provides guidelines for the proper values to enter in each field.

Table 7: Intersection Field Descriptions

Field Description Contents Code A unique intersection location

code A number between 1 and 8 or a letter between A and H that has not already been assigned.

Definition The meaning of the intersection code

Provides the compass orientation of the stop relative to the intersection and the orientation to the closest intersection corner.

9999

Miscellaneous Codes In addition to the primary abbreviations and codes described in the previous portion of this chapter there are also some miscellaneous codes. When you select “Miscellaneous codes” from the Dictionary menu, the “Maintain dictionary for miscellaneous codes” window appears. The desired code is selected from the drop down list as shown below.

Figure 10: Miscellaneous Codes Menu

10101010

New Type When “New type” is selected from the Dictionary menu, you are given the opportunity to define a new miscellaneous code using the window below

Figure 11: New Type Window

The database column name that the code will be used for is entered and the OK button clicked. If this option was selected in error, the Cancel button can be clicked to return to the Miscellaneous codes selection menu. Use of this option requires specific knowledge of the database schema and column names. It should only be used by persons familiar with the PCP database design.

11111111

ADA Codes The Americans with Disabilities Act (ADA) requires transit operators to determine which stops comply with the act. Three codes have been established to define the ADA accessibility of a transit stop. When “ADA code” is selected from the Dictionary menu, the following window appears populated with the existing ADA codes in ADA code order.

Figure 12: ADA Code Edit Window

ADA code information can be edited or added using the “Maintain dictionary for miscellaneous codes” window. To edit information, click on the desired field and type in the change. To add a new code, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new ADA codes. The table below provides guidelines for the proper values to enter in each field.

Table 8:ADA Code Field Descriptions


Code A unique code for the ADA accessibility of a transit stop

An alphanumeric character that has not already been assigned.

Definition A description of the ADA accessibility of a transit stop

Accessible = The stop is accessible by disabled persons Not accessible = The stop is not accessible by disabled personsUpgradable = The stop is not currently accessible by disabled persons but can be upgraded to comply

Old Code The old numeric ADA code value

This field should be left zero for all new codes. It only provides a mapping to numeric ADA codes used previously.

12121212

Bench Some reporting requirements placed upon SANDAG and the transit operators requires identifying which transit stops have a bench for passengers to sit while waiting. When “Bench” is selected from the Dictionary menu, the following window appears populated with the existing bench codes in bench code order.

Figure 13: Bench Edit Window

Bench code information can be edited or added using the “Maintain dictionary for miscellaneous codes” window. To edit information, click on the desired field and type in the change. To add a new bench code, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new bench codes. The table below provides guidelines for the proper values to enter in each field.

Table 9: Bench Field Descriptions


Code A unique bench code for the transit stop


Definition A description of the bench at the transit stop

blank = The stop has no bench B = The stop has a bench

Old Code The old numeric bench code value

This field should be left zero for all new codes. It only provides a mapping to numeric bench codes used previously.

13131313

Block The location of a transit stop relative to its position in a block is defined by a block code as shown in the diagram below.

Figure 14: Block Code Diagram

When “Block” is selected from the Dictionary menu, the following window appears populated with the existing block codes in block code order.

Figure 15: Block Edit Window

Block code information can be edited or added using the “Maintain dictionary for miscellaneous codes” window. To edit information, click on the desired field and type in the change. To add a new block code, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new block codes. The table below provides guidelines for the proper values to enter in each field.

Table 10: Block Code Field Descriptions

Field Description Contents Code A unique block code

for the transit stop An alphanumeric character that has not already been assigned.

Definition A description of where the transit stop is located on the block

F = The stop is located at the far end of the block M = The stop is located in the middle of the block N = The stop is located at the near end of the block

Old Code Unused for block codes This field should be left zero for all new codes. It is unused for block codes.

Direction of Travel

Block Near Mid Far

14141414

Shelter Some reporting requirements placed upon SANDAG and the transit operators requires identifying which transit stops have a shelter provided for passengers while waiting. When “Shelter” is selected from the Dictionary menu, the following window appears populated with the existing shelter codes in shelter code order.

Figure 16: Shelter Code Edit Window

Shelter code information can be edited or added using the “Maintain dictionary for miscellaneous codes” window. To edit information, click on the desired field and type in the change. To add a new shelter code, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new shelter codes. The table below provides guidelines for the proper values to enter in each field.

Table 11: Shelter Code Field Descriptions


Code A unique shelter code for the transit stop


Definition A description of the shelter at the transit stop

blank = The stop has no shelter S = The stop has a shelter

Old Code The old numeric shelter code value

This field should be left zero for all new codes. It only provides a mapping to numeric shelter codes used previously.

15151515

Vehicle Type Each class of transit vehicles used by a transit operator is assigned a unique vehicle type. The types are used to relate modes of transportation to ridership. When “Vehicle type” is selected from the Dictionary menu, the following window appears populated with the existing vehicles types in vehicle type order.

Figure 17: Vehicle Type Edit Window

Vehicle type information can be edited or added using the “Maintain dictionary for miscellaneous codes” window. To edit information, click on the desired field and type in the change. To add a new vehicle type, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new vehicle types. The table below provides guidelines for the proper values to enter in each field.

Table 12: Vehicle Code Field Descriptions


Code A unique vehicle type code for the class of transit vehicles

An alphanumeric string of up to 10 characters that has not already been assigned.

Definition A description of the class of transit vehicles

Bus, Trolley, etc.

Old Code Unused for vehicle type codes This field should be left zero for all new codes. It is unused for vehicle type codes.

16161616

Place Codes Each area of San Diego County has an assigned place code. The codes are used to develop statistics on the use of transit facilities relative to specific regions of the County. Each place code has an incorporation flag (Inc) that indicates if the region is incorporated into a city. The incorporation flag is used to develop statistics on the use of transit facilities within the unincorporated areas of the County. When “Places” is selected from the Dictionary menu, the following window appears populated with the existing place codes in place code order.

Figure 18: Place Code Edit Window

Place information can be edited or added using the “Maintain dictionary for place num” window. To edit information, click on the desired field and type in the change. To add a new place, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new places. The table below provides guidelines for the proper values to enter in each field.

Table 13: Place Code Field Descriptions


Code The Transit Operator’s unique number for the vehicle.

A number between 0 and 999 that has not already been assigned.

Definition The name of the region The proper name for the region

Inc The incorporation flag value N = unincorporated, Y = incorporated (a city)

17171717

Time Periods Each operating day is divided into four time periods. The time periods are used to group transit ridership into a common set of commuter groups. The “AM” and “PM” periods generally cover the morning and afternoon commutes while “Mid-day” and “Other” cover the remaining time periods. When “Time Period” is selected from the Dictionary menu, the following window appears populated with the existing time periods in time period code order.

Figure 19: Time Period Edit Window

Place information can be edited or added using the “Maintain dictionary for Time Period” window. To edit information, click on the desired field and type in the change. To add a new time period, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new time period. The table below provides guidelines for the proper values to enter in each field.

Table 14: Time Period Field Descriptions


Code The unique number code for the time period. A number between 0 and 9 that has not already been assigned.

Definition The common reference for the time period The term most commonly used to describe the time period

18181818

Vehicle Codes Each vehicle used by a transit company has a vehicle number assigned. The number is unique within a specific transit company. Information on the type of vehicle (bus, trolley, etc.), propulsion method (gas, diesel, etc.), passenger capacity and average miles per gallon are maintained in the PCP database. The information is used in various calculations such as when a vehicle has reached capacity or the number of passengers carried per gallon of fuel. When you select “Vehicles” from the Dictionary menu, the “Maintain dictionary for vehicles” window appears. The desired Transit Company is selected from the drop down list as shown below.

Figure 20: Vehicle Information Company Select Menu

19191919

Once a company is selected, the information on known vehicles used by that operator is displayed as shown below.

Figure 21: Vehicle Information Edit Window

Vehicle information can be edited or added once a transit company has been selected. To edit information, click on the desired field and type in the change. To add a new vehicle, use the scroll bar to move to the bottom off the displayed list. The last entry in the displayed list is empty and is for adding new vehicles. The table below provides guidelines for the proper values to enter in each field.

Table 15: Vehicle Field Descriptions


Vehicle # The Transit Operator’s unique number for the vehicle.

A number between 0 and 9999

Type The type of vehicle BUS, TRAIN or TROLLEY

Propulsion The propulsion method used by the vehicle D (for diesel), E (for electric), N (for natural gas)

Capacity The number of passengers the vehicle is designed to carry

A number between 1 and 999

MPG The miles per gallon (or equivalent) the vehicle averages in regular use.

A number between 00.01 and 999.99

1111

Maintaining the Stop Inventory An essential part of passenger counting is knowing exactly where transit stops are. PCP keeps track of transit stops in what is known as the “Stop Inventory” (a.k.a. “Bus Stop Inventory”). Each transit stop is represented along with information specific to the location and facilities located at the stop. This information is periodically updated using information provided by the transit operators and from observations made during field work.

Unique Stop Identifiers Each stop in the Stop Inventory is assigned a unique Stop ID consisting of two parts. The first part is the company number of the Transit Company primarily responsible for maintaining the stop. The second part is a four-digit number that uniquely identifies the stop within that company. The Stop ID is displayed in the following format:

c-nnnn Where: c = The transit company number nnnn = The unique stop number within that company

It is common for several transit companies to use the same stop, which are usually transfer points. The decision as to what company is “primarily responsible” for the stop is somewhat arbitrary, but certain guidelines apply. For example, San Diego Trolley is usually “primarily responsible” for all trolley stops although they frequently also include bus stops.

Chapter

4

2222

Stop Information The following information is maintained for each stop:

Table 16: Information Maintained about a Stop

Datum Description Company # Transit company number. Stop # Stop identification number. Census Tract Census tract number Place Code Census place code Intersection Stop location relative to intersection (1 thru 8 or A thru G) Block Stop location relative to block (N, M or F) Street 1 First cross street name Street 2 Second cross street name (if applicable) X X state place coordinate Y Y state place coordinate ADA Code ADA accessibility (A= Accessible, U= Upgradable, N= Not Upgradable). Bench Bench (contains a B if there is a bench otherwise blank) Shelter Shelter (contains an S if there is a shelter otherwise blank).

Field Work

3333

Editing Stop Data

Selecting a Stop To select a stop, click on ”Dictionary” in the main PCP window. The Dictionary Menu will appear showing the possible dictionary items to explore. Double click on “Stops”.

Figure 22: Stop Selection on Dictionary Menu

The ”Maintain Stop Inventory” window appears and is initially blank.

Figure 23: Maintain Stop Inventory Window

4444

The “Maintain Stop Inventory” window allows you to add, edit, or delete information from the stop inventory. To select stops for editing, enter the selection criteria (if any) and click the “Get Data” button. You may select a single stop by stop number, or you may limit the selection to stops maintained by a single transit company and/or for a single place or street name. When entering selection criteria for Street 1 or Street 2, you may enter the complete name or only the first few characters. The following figure shows the “Maintain Stop Inventory” window configured to select all stops with the first cross street starting with “El Cajon”.

Figure 24: Selecting Stops by Street

After clicking on the “Get Data” button, the first stop with street 1 starting with “El Cajon” is displayed as shown below.

Figure 25: Stop Selection Results for a Street

5555

To move through the selected stops use 'Next' and 'Previous' buttons. When the selection is initially returned the “Previous” button is greyed out since you are at the first stop in the selection. When you reach the last stop in the selection the “Next” button will be greyed out.

To define a new query click on the “Query” button. If you have made changes to the displayed information without clicking on “Update” first, an error message will be displayed giving you the opportunity to save the changes before specifying a new query.

To exit the “Maintain Stop Inventory” window, click on the “Close” button.

Adding a Stop New stops can be added using the “NewStops” button. The “Maintain Stop Inventory” window will clear and you will be placed at the “Street 1” field. Enter the information about the stop in the desired fields and click the “Insert” button when you are done. Some fields are mandatory and if they do not contain data when you click on “insert”, an error message will be displayed indicating the first mandatory field found. When the transit company has been selected, a unique stop number will be generated automatically.

Modifying a Stop To modify a stop, first select the stop (or stops) to be modified as described above. Make the desired changes and click on the “Update” button.

Deleting Stops To delete a stop, first select the stop (or stops) to be deleted as described above and click on the “Delete” button. WARNING: Deleting a stop will effect route inventories that use the deleted stop.

1111

Route Information Maintenance Accurate route information is necessary for proper passenger counting. Each transit operator provides SANDAG with current route information that is used to update the Counter database. Generally, these updates occur three times a year although some routes may be updated more frequently due to changes to accommodate passenger demands. Some changes are driven by temporary construction projects or the opening of new roadways and transit capabilities.

What is a Route A route is a collection of transit stops that is uniquely identified by the transit company number, fiscal year, route number, variation and direction. Each stop is assigned a sequential stop sequence number. The numbering is usually in increments of five although edits made during the course of a fiscal year may result in some inserted stops having numbering of a lesser increment.

The stop sequence number used in PCP is sometimes referred to as the SANDAG stop sequence number and is sometimes different (although not always) than the transit operator stop sequence number. This is due to the SANDAG numbers being assigned and maintained by SANDAG and the transit operator numbers being assigned and maintained by their respective companies. SANDAG does maintain the transit operator’s stop sign (identification) numbers in the Counter database for various purposes, such as of generating specialized reports.

Field Work

Chapter

5

2222

Editing Routes

Selecting a Route To select a route click on ”Dictionary” in the main PCP window. The Dictionary Menu will appear showing the possible dictionary items to select. Double click on “Routes”.

Figure 26: Route Select on Dictionary Menu

3333

The ”Maintain Route Dictionary” window appears and is initially blank. Select the desired companies using the drop down company combo box and enter the desired fiscal year. Click on the “Get Data” button to retrieve the routes. The example below shows fiscal year 1999 routes for National City Transit.

Figure 27: Maintain Route Dictionary Window

Route Editing Options To select operations to perform on a specific route, highlight the route and click on the control button at the top right corner of the table field. This will bring up a list of valid actions as shown below.

Figure 28: Maintain Route Dictionary Options

4444

Displaying Stops on a Route To display the stops on a route highlight the route you are interested in and select “Display Stops” from the control button menu (seen when you click on the control button above the table field scroll bar). This will bring up the display of stops on the route as shown below.

Figure 29: Stops on Route Window

In addition to the company number, fiscal year, route number, variation, direction and general description, the table field displays specific information about each stop on the route as detailed in the table below.

Table 17: Stops on Route Column Descriptions

Heading Description StopSeq The SANDAG stop sequence number for the stop

Type The type of stop (R = regular, D = detour, T = transfer

TP Time point flag, if the stop is a time point this column will contain a ‘T’

Stop# The SANDAG unique stop number identifier for the stop in the stop inventory

TO# The transit operators stop number

Distance The distance to this stop from the previous one

Street 1 The street the route is on when it arrives at the stop

Cross Street The nearest cross street to the stop

5555

Detailed information about a specific stop can be displayed by highlighting the desired stop, clicking on the control button above the table field scroll bar and selecting ‘Display Stop Info’. This will bring up the Stop Information window shown below.

Figure 30: Stop Information Window

Editing a Route To edit a route start by highlighting the desired route, clicking on the control button above the table field scroll bar and selecting ‘Edit Current Route’. If counts have been performed on the route you will not be able to edit it and the following message window will appear.

Figure 31: Error Message Window about Counts on Route

6666

If the route can be edited the following window will appear with the stop information for the selected route.

Figure 32: Route Edit Window

This window allows you to edit data for an existing route. For a list of available directions, use the control button to the right of the direction field. The available editing options are found by clicking on the control button above the table field scroll bar, which brings up the menu shown, below.

Figure 33: Route Edit Option Menu

The first three menu items permit making modifications to the stops on a route. The first option inserts a stop before the currently selected stop on the table field. The second option deletes the currently selected stop. The final option should be used with care as it removes all stops from the route. This is normally done when a route radically changes or there are so many errors as to make starting over reasonable. When you add a stop and enter the stop number, the distance and street information is automatically filled in from the stop inventory.

7777

The second set of options relates to displaying or manipulating information on the table field. The first option allows you to see detailed information about a stop, as described earlier. The second option allows you to search for a specific stop or stops. The next two options permit sorting the displayed stop information in various orders. The final option, Copy Table, allows you to copy the contents of the route table to the clipboard for dropping into other applications.

When making edits to a route it is important to keep several constraints in mind. Stops added to a route must be in the stop inventory, and the first and last stops must be time points. Distances are retrieved from the database if available. If a distance has not been previously defined, you will be prompted for this information. If the distance you enter is > 100, the distance will be assumed to be in feet and is automatically converted to miles (the standard displayed distance unit).

8888

Changing a Route’s Description The description for a route can be changed by highlighting the desired route, clicking on the control button above the table field scroll bar and selecting ‘Change Description’. This will bring up a window that allows you to enter a new route description.

Figure 34: Route Description Change Window

Creating a New Route New routes must be entered for each new fiscal year. The easiest way to do this is to create a new route as a variation on the old one, changing fiscal year and any other information that has changed. Then save the new route. To do this select a route, click on the control button above the scroll bar and point to “Create New Route”. An additional menu will “slide” out as shown below.

Figure 35: Create New Route Slide Out Menu

Selecting “From Scratch” will bring up a blank route display ready for entry of route information. Selecting “From copy of current route” will bring up a route display populated with information from the currently selected route.

9999

The following is an example of the “Create New Route” window.

Figure 36: Create New Route Window

This frame allows you to create new routes. After you have saved stops for a new route, you can add, change, or delete stops and then save the route again with a different variation (see the section on editing a route for specific information on performing those operations). For a list of available directions, use the control button to the right of the direction field. To see detailed information about a stop, click on the row with that stop number and use the control button above the table field scroll bar and select 'Display stop info.' To have continuous access to information about stops, you can open the Stop Inventory from the Dictionary menu and leave it open while you work.

Stops added to this route must be in the stop inventory, and the first and last stops must be time points. The distance from the previous stop is retrieved from the database if it is available. If a distance has not been previously defined, you will be prompted for this information. If the distance entered is > 100, it will be assumed to be in feet and will automatically converted to miles (the standard displayed distance unit).

Deleting a Route

Delete a route by highlighting a route and selecting the “Delete current route” on the control button option menu. Before the route is actually deleted you will be asked to confirm the request to delete.

10101010

Using Find

When you select “Find” from the control button option menu the following window appears.

Figure 37: Find Route Window

Enter all or a portion of the route description you are looking for and click “Find”. The first occurrence of that matches your description will be made the current route in the Route Dictionary window. As the options on the window imply, you can control the find by specifying which characters to match and whether to ignore case.

Sorting Routes

Using the options on the control button menu, you can sort the selected route information on ascending or descending route number order.

Copying Routes The “Copy Table” option on the control button menu causes the selected route information to be copied to the clipboard for insertion into other applications.

1111

Processing Counts Once field counts have been completed and put in machine-readable form, the process of validating counts can begin. There are essentially two steps in processing counts; 1) loading the raw data and 2) validating the count information. Once counts have been validated they may be used for generating reports.

Loading Count Data Count data is loaded using the “lrc” (load_raw_count) program or by invoking the “Load raw data” option under “File” on the main menu.

Command Line Utility To load raw count data files using the “lrc” (load_raw_count) program, first go to the directory where the data resides and enter the following command:

lrc <raw file 1> <raw file2> . . . <raw file n>

where “<raw file 1>”, etc. are the names of the raw data files to load. In the following example the counts for Routes 1, 2, 5, and 8 are loaded (using the common file names for the raw data files, although the name can be anything you choose).

lrc RT001 RT002 RT005 RT008

During the loading of the data, information will be displayed to the screen about the progress of the loading and whether any errors were detected.

PCP Load Option Selecting “Load raw data” under “File” on the main menu will bring up the “Load Data” window. You enter the directory where the files to be loaded reside and the names of the files to load. Clicking on the “Load” button will cause the files to be loaded.

The loading of data using the PCP program requires a specific operating environment and the option may not be available in all cases.

Chapter

6

2222

Validation Criteria

Validations for header fields: • Dictionary must contain entries for the company, counter, vehicle.

• Dictionary must contain a route (including its stops) with this route number, variation, and direction for the fiscal year in which the route count was made.

• Number of stops counted should not exceed 200.

Validations for stops: • Duplicate stop sequences are not allowed.

• If stop is not on the regular route, it must be a detour stop. You will be prompted to enter a stop number for all detour stops.

• When a row is inserted or a stop sequence changed, you may be prompted to enter a new distance from the previous stop.

Validations for stop count rows: Information about time points is taken from the route stop dictionary, not from the raw stop count data. If there is no count record for a time-point on the route, a record is created and marked as an error. A count for a stop that is not on the route is marked as an error unless the stop is a detour stop.

Validations for arrival/departure/scheduled time fields: • All times must be valid (e.g., 12:99 is not a valid time). Times may be > 24:00 for routes that continue past

midnight.

• The first stop needs actual departure time only and the last stop needs actual arrival time only. All other stops that are time points require both arrival and departure time. If the stop is not a time point, it need not have departure or arrival time, but if it does it will NOT be marked as an error.

• Arrival times must be greater than the departure times from the previous time point, and the departure times must be >= to the arrival times. A departure time more than 45 minutes after the scheduled time for the stop is an error.

• There must be a schedule time for each time point. Schedule time for the first stop must match scheduled start time for the route, and for the last stop must match scheduled finish time for the route. Each scheduled time must be greater than the preceding one. If the stop is not a time point but has a scheduled time, it is an error.

3333

Validations for fields relating to passengers: • No offs allowed at first stop; carryovers are allowed at first stop only.

• Number of passengers on board (calculated from ons, offs, and carryovers) must not be negative. IMPORTANT NOTE: In order to facilitate validations, values displayed for passengers on board represent the numbers on board after the vehicle leaves the stop. However, when the count is validated and added to the permanent tables, the on-board values stored will represent those on board when the vehicle ARRIVES at the stop. These are the values required for Report 4 and the year-end reports.

Validating a Count

Selecting a Count for Validation To select a count for validation start from the main PCP window as shown below.

Figure 38: Main PCP Window for Count Validation

Using the drop down box labeled company, select the company that the desired count was performed for and make sure “Unvalidated counts is selected. To select all the unvalidated counts for that company click the “Get Data” button. The number of unvalidated counts that are selected can be further narrowed by selecting a specific counter by selecting an individual counter from the Counter drop down combo box.

4444

Once the desired selection criteria has been entered, click on the “Get Data” button to display the counts. Shown below is an example of unvalidated counts selected for San Diego Transit.

Figure 39: Unvalidated Count Display Window

To edit or display details for a route count, first highlight the desired route count. Next, click on the control button above the scroll bar on the table field to display the available options as shown below.

Figure 40: Count Validation Menu

Select the desired operation from the list displayed. If an operation is grayed out (as are “Display” and “Revoke Validation” in the example above) that operation is not available for the route count selected. In this example, “Revoke Validation” is grayed out since the selected route count has not yet been validated.

5555

Editing a Count When you select the “edit” option the route count editor window will come up as shown below with the count information displayed.

Figure 41:Route Count Editor Window

Table 18: Route Count Editor Table Columns

Column Description Rec# The original raw data file input record number. This is used to find certain kinds of errors. StopSeq The stop sequence number on the route. TmPt This column contains a ‘T’ if the stop is a time point. SchedTime The schedule time. Arrive The time the bus arrived at the stop Depart The time the bus departed from the stop. CyOvrs The number of passengers carried over from the route On The number of passengers getting on at the stop Off The number of passengers getting off at the stop OnBd The number of passengers onboard when the bus departed Pg The page number on the count form the information came from (99 if Texlon was used)

6666

When the frame opens, it displays raw data for the selected route count. Stops are sorted by stop sequence and should not be resorted during the validation process, since times are validated by comparing them with previous rows in the table field. There is the option of resorting by the original input record number as a method of detecting certain errors but should be used with caution. If date counted and route identification info are ok, data about stops assigned to that route is loaded and matched with the stops actually counted. If stop data cannot be loaded at this point, you will see an error message. You must correct information in the header and then click on the 'Validate' button.

When route stop information is loaded, rows are added to the table field for stops on the route but for which counts do not exist. You should leave these rows in the data to ensure that distances shown on reports are correct. After route stop data is loaded, validation of all stop count fields is attempted.

Note: You can add routes or route stops from this frame by selecting the appropriate item from the Dictionary menu. However, these changes will not show up in the current frame until it is closed and re-opened. Thus if dictionary information for the route you are editing is missing, you have to close and re-open this frame to have the new data matched to the actual stop counts.

After stop data is loaded, stop counts are validated as far as possible until some error is found that needs to be corrected before later rows can be checked (for example, missing times for a time point, negative number of passengers on board, etc.). Fields with errors are displayed with a different color background (same as window title bar). When user enters a field with an error, by clicking on it or tabbing to it, an explanation of the error will appear at the bottom of the form. When errors are properly corrected, their background color reverts to normal and the error message will no longer appear.

To look up route, vehicle, or counter numbers, select 'Lookup' from the control bottons located to the right of the relevant field. As errors are corrected or data is changed, validation continues as needed. For example, when a time is changed, times in succeeding counts are checked. All fields should be valid by the time no errors are indicated by field colors, but you need to click on 'Validate' again for a final complete validation. If all validation checks are passed, edit status changes to 'VAL'.

When edit status is 'VAL', you may click on 'StoreValid' to store the edited route count data in route_count and stop_count tables and delete it from raw_route and raw_stop. However, if you change the value of any field, edit status changes back to 'INV' and you must click again on 'Validate' before you can store.

You may save changed data at any time for continued editing later by clicking on 'Save'. Any reports generated from this frame on this set of raw data are based on data actually in the database, not what appears on the screen. So you should save before generating such reports.

7777

Deleting a Count To delete a count select “Delete” from the control button menu after highlighting the count you want to delete. The system will ask for confirmation of the desire to delete before actually deleting the count. The delete option is frequently used when the number of errors in the input make validation impossible or a serious error requires the count to be redone.

Combining Counts Sometimes one count may accidentally be split into two during the input process or one statistical count may be split intentionally for scheduling purposes. In these cases the counts need to be merged before they are validated. This is done by selecting the “Combine” option on the control button menu. When this is done a column is added to the displayed counts as shown below.

Figure 42: Count Combine Window

You may combine ('stitch together') unvalidated route counts by selecting 'Combine' from the control button menu list and indicating one as the master, one to eight as the children. Offs, ons, and carryovers from child stops will be added to those of master stops. In addition, stops in child count but not in master will be added to master. The child route counts will be removed from the database. The combined count must be edited and validated again before it can be moved from the raw data to the permanent data tables.

8888

Using Find Find can be used to select counts by their validation status. To use find, select the “Find” option from the control button menu and the find window will appear. Enter the status you want to find and click the “Find” button. The first occurrence of the row with the desired status will be made the current row.

Sorting Counts The sort option allows the sorting of the displayed counts by ascending or descending status order. You perform the sort by selecting the desired sort option and the table is resorted.

Copying Counts The contents of the count table can be copied to the clipboard using the “Copy Table” option. This allows you to transfer the count information to other applications.

9999

Working With Validated Counts

Selecting a Validated Count To select validated counts, start from the main PCP window as shown below.

Figure 43: Main Window for Validated Counts

Using the drop down box labeled company, select the company that the desired count was performed for and make sure “Validated counts” is selected. To select all the validated counts for that company, click the “Get Data” button. The number of validated counts that are selected can be further narrowed by selecting a specific counter by selecting an individual counter from the Counter drop down combo box. It is also possible (for validated counts only) to specify a range of dates the count, or counts, were performed on.

10101010

Once the desired selection criterion has been entered, click on the “Get Data” button to display the counts. Shown below is an example of validated counts selected for San Diego Transit.

Figure 44: Display of Validated Counts

To select an operation to perform on the count, first highlight the desired route count. Next, click on the control button above the scroll bar on the table field to display the available options as shown below.

Figure 45: Validated Count Menu

Select the desired operation from the list displayed. If an operation is grayed out (as are “Edit”, “Delete” and “Combine” in the example above) that operation is not available for the route count selected. In this example, “Edit” is grayed out since the selected route count has been validated.

11111111

Displaying a Count To display the details about a validated count select the “Display” option on the control button menu. The following window appears with the detail information for the count.

Figure 46: Detail Validated Count Information Window

Using Find Find can be used to select counts by their validation status. To use find, select the “Find” option from the control button menu and the find window will appear. Enter the status you want to find and click the “Find” button. The first occurrence of the row with the desired status will be made the current row.

Sorting Counts The sort option allows the sorting of the displayed counts by ascending or descending status order. You perform the sort by selecting the desired sort option and the table is resorted.

12121212

Copying Counts The contents of the count table can be copied to the clipboard using the “Copy Table” option. This allows you to transfer the count information to other applications.

Revoking Validation Sometimes errors are found in validated counts or it is determined that two counts should be combined. When this occurs the validation for a count can be revoked by selecting the count and clicking on “Revoke Validation” control button menu option. The count will then be returned to the pool of unvalidated counts and can be edited.

Using Omit The validated count display adds a column titled “Omit” that can be checked. If the box is checked the count remains in the count inventory but is omitted from reports. This can occur when a count was performed for some special purpose and should not be included in the regularly published reports.

1111

Route Reports

Running Route Reports To run a route report select “Route Reports” from the Output menu on the main window of PCP. The Request Route Reports window will appear as shown below.

Figure 47: Route Reports Window

This frame displays reports available for validated route counts of a single route. You must specify a company, route number, and fiscal year and may then generate several reports for this route at one time. Reports include all route counts for the specified route and fiscal year except for those that have been marked 'OMIT FROM REPORTS'.

Chapter

7

2222

Output Destinations

Display The default for all reports is to display to the screen. Once a report is displayed it can be printed but without the special capabilities of the options described below.

To a File If you choose "Write to File," the report will be written to a file. The file names will be:

Rt<n><y><d><#>.<t>

where n = route number (three digits), y = fiscal year (two digits), d = day type (wkd, sat, or sun), # = the report number, and t = the file extension (txt for text and ps for postscript). The files are automatically written to a directory tree on your root drive starting with a directory named pcprpts. Subsequent directories contain the reports for each fiscal year named “Fy9999” where 9999 is the year (i.e. 1998). Additional subdirectories hold weekday and weekend reports and subdirectories for each report number. If these directories do not exist when you run the report, they will be created automatically. An example of this directory structure is shown below.

Figure 48: Report File Directory Structure

3333

To a Printer If you choose “Print” the report is first written to a file and then spooled to the default printer for you system. The report file is not deleted after it is submitted for printing and resides in the appropriate directory as described above.

Plain Text vs Postscript When you select “Write to file” or “Print” and additional selection box appears on the report window as shown below.

Figure 49: Output Selection Option

Leaving the box marked “Plain Text Output” unchecked will cause the report to written to a file in plain text with an extension of “txt”. If you click the box it will toggle to “Postscript Output” and the report will be also be written to a file in Postscript format with a “ps” extension. Files in Postscript format can be sent to most modern printers without loss of special formatting information such as character point size.

4444

Route Reports

Report 1: Dates Checked Summary This report provides a summary by terminal time of boardings (Ons), alightings (Offs), maximum load (Max on bus) and vehicle capacities for each direction on a route. The number of passengers staying on the vehicle from one trip to the next (Carried Over From Last Trip) is also shown. The information for each direction is further summarized after the listing of terminal times with total riders, total number of trips, average passengers per trip, average maximum load, peak-load factor and peak load hour.

Report 1: DATES CHECKED SUMMARY FY 1999 11/6/98 09:28 Company: North County Transit Dist Route: 342 Week Days Direction: Loop STARTING CARRIED TERMINAL DATE DAY OF TOTAL TOTAL MAX. OVER FROM TIME CHECKED WEEK ONS OFFS ON BUS LAST TRIP CAPACITY ------ ------- ------ ----- ----- ------ --------- -------- 7:15 10/27/98 TUE 14 14 11 0 38 7:45 10/27/98 TUE 19 19 18 0 38 8:15 10/27/98 TUE 33 34 20 1 38 8:45 10/27/98 TUE 11 12 8 1 38 9:10 10/27/98 TUE 8 8 6 0 38 9:40 10/27/98 TUE 12 12 7 0 38 10:10 10/27/98 TUE 12 13 8 1 38 10:40 10/27/98 TUE 16 16 10 0 38 11:10 10/27/98 TUE 9 9 5 0 38 11:40 10/27/98 TUE 16 16 11 0 38 12:10 10/27/98 TUE 12 12 6 0 38 12:40 10/21/98 WED 3 3 2 0 38 13:10 10/21/98 WED 7 7 3 0 38 13:40 10/21/98 WED 11 11 7 0 38 14:10 10/21/98 WED 11 11 9 0 38 14:45 10/21/98 WED 16 17 8 1 38 15:20 10/21/98 WED 14 15 10 1 38 15:55 10/21/98 WED 5 5 4 0 38 16:30 10/21/98 WED 12 12 6 0 38 17:05 10/21/98 WED 7 7 5 0 38 17:40 10/21/98 WED 6 6 5 0 38 18:15 10/21/98 WED 5 5 3 0 38 Total riders: 259 Number of trips: 22 Average riders per trip: 11.8 Average maximum load: 7.8 Average capacity: 38.0 Peak load factor: 0.474 Peak hour: 7:45 TOTALS BOTH DIRECTIONS Total riders: 259 Number of trips: 22 Average riders per trip: 11.8 Average maximum load: 7.8 Average capacity: 38.0 - 1 - PCP 3.2, RPT1 v07

Formulas: Average Riders per Trip = total riders / number of trips Average Maximum Load = total maximum load / number of trips Average capacity = total capacity / number of trips Peak Load Factor = The maximum ratio of load to capacity reached during the trip Peak Hour = The first hour the peak load factor was reached. Total Riders = Total number of riders for all trips Number of Trips = Number of trips in count Average Maximum Load = Total Riders / Number of Trips Average Maximum Load = Total maximum load for all trips / Number of Trips Average Capacity = Total capacity for all trips / Number of Trips

5555

Report 2: Route Profile This report graphically displays the maximum load and total riders for each trip with one graph per direction of travel. Trips over capacity are indicated by a “/” at the point the bus reaches capacity. The maximum load is indicated by “O” and “X” indicates total passengers.

Report 2: ROUTE PROFILE 11-6-98 09:29 Page 1 Company: North County Transit Dist FY: 1999 - Week Days Route: 342 Direction: Loop STARTING 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 MAX TOTAL TERMINAL +----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+ LOAD PASS. TIME 7:15 OOOOOXX 11 14 7:45 OOOOOOOOOX 18 19 8:15 OOOOOOOOOOXXXXXXX 20 34 8:45 OOOOXX 8 12 9:10 OOOX 6 8 9:40 OOOXXX 7 12 10:10 OOOOXXX 8 13 10:40 OOOOOXXX 10 16 11:10 OOXX 5 9 11:40 OOOOOXXX 11 16 12:10 OOOXXX 6 12 12:40 OX 2 3 13:10 OXX 3 7 13:40 OOOXX 7 11 14:10 OOOOX 9 11 14:45 OOOOXXXXX 8 17 15:20 OOOOOXXX 10 15 15:55 OOX 4 5 16:30 OOOXXX 6 12 17:05 OOX 5 7 17:40 OOX 5 6 18:15 OX 3 5

6666

Report 2A: Route Profile for Trains & Trolley This report graphically displays the maximum load and total riders for each trip with one graph per direction of travel. Trips over capacity are indicated by a “/” at the point the vehicle reaches capacity. The maximum load is indicated by “O” and “X” indicates total passengers.

Report 2: ROUTE PROFILE 14-01-99 14:27 Page 1 Company: San Diego Northern FY: 1998 - Week Days Route: 398 Direction: North Bound STARTING 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 MAX TOTAL TERMINAL +----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+ LOAD PASS. TIME 6:36 OOOOOOOOXX 85 97 7:45 OOOOOOOOX 79 86 14:15 OOOOOOOOOOOOOOOX 153 159 15:40 OOOOOOOOOOOOOOOOOOOOX 199 208 16:20 OOOOOOOOOOOOOOOOOOOOOOOOOOX 264 273 16:50 OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXX 314 327 17:20 OOOOOOOOOOOOOOOOOOOOOOOOOOOOOX 293 301 18:05 OOOOOOOOOOOOOOOX 147 156 18:42 OOOOOOO 69 70

7777

Report 3: Trip Summary This report provides a trip summary by the starting terminal time. It shows the total number of passengers, the stop with the most boardings (ons), the stop with the most alightings (offs), the maximum load value and the stop the maximum load was first reached.

North County Transit Dist -- Week days ROUTE: 342 FY 1999 DIRECTION: Loop STARTING TERMINAL TIME PASSENGERS STOP 7:15 Total 14 Max On 11 PALOMAR COLLEGE TRANSIT CENTER Max Off 6 VIA VERA CRUZ & COMMERCE ST Max Load 11 LAS POSAS & DESCANSO AV 7:45 Total 19 Max On 18 PALOMAR COLLEGE TRANSIT CENTER Max Off 7 VALPREDA & RANCHEROS DR Max Load 18 VIA VERA CRUZ & COMMERCE ST 8:15 Total 33 Max On 19 PALOMAR COLLEGE TRANSIT CENTER Max Off 14 CSU SAN MARCOS Max Load 20 VIA VERA CRUZ & COMMERCE ST 8:45 Total 11 Max On 4 PALOMAR COLLEGE TRANSIT CENTER Max Off 7 PALOMAR COLLEGE TRANSIT CENTER Max Load 8 CSU SAN MARCOS 9:10 Total 8 Max On 2 CSU SAN MARCOS Max Off 5 PALOMAR COLLEGE TRANSIT CENTER Max Load 6 MISSION RD & PICO AV . . . . 17:05 Total 7 Max On 2 CSU SAN MARCOS Max Off 5 PALOMAR COLLEGE TRANSIT CENTER Max Load 5 PALOMAR COLLEGE TRANSIT CENTER 17:40 Total 6 Max On 4 CSU SAN MARCOS Max Off 5 PALOMAR COLLEGE TRANSIT CENTER Max Load 5 PALOMAR COLLEGE TRANSIT CENTER 18:15 Total 5 Max On 3 PALOMAR COLLEGE TRANSIT CENTER Max Off 2 PALOMAR COLLEGE TRANSIT CENTER Max Load 3 DISCOVERY ST & 809 (MHP) - 2 -

8888

Report 4: Ons, Offs, Thrus This report shows the boardings (Ons), Alightings (Offs), Onboard, and Thrus (the number of passengers onboard from the last stop) for each stop by time period. It also shows total ons, total offs, passenger miles, average trip length, revenue miles, passengers per revenue mile, miles over capacity, and percentage over capacity. Directional and daily totals are also indicated. The daily summary includes the gallons of fuel used and passenger miles per gallon of fuel. The latter calculations are based on average fuel consumption data for the vehicle rather than actual values. The detailed report provides this analysis by trip. In the summary report portion, aggregate information for each bus stop is summarized by direction of travel.

Report 4: ONS, OFFS, THRUS 06-nov-1998 09:29 Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop Daily Total AM Period Midday Period PM Period Other Period ON ON ON ON ON Bus Stop ON OFF BRD THRU ON OFF BRD THRU ON OFF BRD THRU ON OFF BRD THRU ON OFF BRD THRU PALOMAR COLLEGE TRANSIT 129 0 5 5 52 0 2 2 59 0 2 2 15 0 1 1 3 0 0 0 LAS POSAS & DESCANSO AV 0 1 134 133 0 1 54 53 0 0 61 61 0 0 16 16 0 0 3 3 VIA VERA CRUZ & COMMERCE 12 34 133 99 0 13 53 40 8 15 61 46 4 6 16 10 0 0 3 3 VIA VERA CRUZ & SAN MARC 10 13 111 98 1 5 40 35 6 5 54 49 3 3 14 11 0 0 3 3 DISCOVERY ST & 809 (MH 19 12 108 96 7 1 36 35 12 10 55 45 0 1 14 13 0 0 3 3 CRAVEN RD & FOXHALL DR 6 5 115 110 3 0 42 42 2 4 57 53 1 0 13 13 0 1 3 2 CSU SAN MARCOS 42 55 116 61 8 24 45 21 19 25 55 30 14 4 14 10 1 2 2 0 TWIN OAKS VALLEY RD & CR 4 5 103 98 0 3 29 26 2 2 49 47 2 0 24 24 0 0 1 1 TWIN OAKS VALLEY RD & BA 4 2 102 100 0 0 26 26 2 2 49 47 2 0 26 26 0 0 1 1 VALPREDA & RANCHEROS DR 11 14 48 34 0 7 7 0 11 5 20 15 0 2 21 19 SAN MARCOS BL & SAN MARC 1 2 101 99 0 0 19 19 0 0 55 55 1 2 26 24 0 0 1 1 MISSION RD & VINEYARD RD 3 3 100 97 0 0 19 19 3 2 55 53 0 1 25 24 0 0 1 1 MISSION RD & JOSLYN SEN 2 1 100 99 0 0 19 19 2 0 56 56 0 1 24 23 0 0 1 1 MISSION RD & PICO AV 9 11 101 90 5 0 19 19 3 8 58 50 1 3 23 20 0 0 1 1 MISSION RD & MARCOS 6 6 99 93 1 0 24 24 4 6 53 47 0 0 21 21 1 0 1 1 MISSION RD & SAN MARCOS 0 0 99 99 0 0 25 25 0 0 51 51 0 0 21 21 0 0 2 2 MISSION RD & UNITED METH 1 0 99 99 0 0 25 25 0 0 51 51 1 0 21 21 0 0 2 2 PALOMAR COLLEGE TRANSIT 0 100 100 0 0 25 25 0 0 51 51 0 0 22 22 0 0 2 2 0 Report 4: ONS, OFFS, THRUS Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop -- week days Total passengers: 259 Passenger miles: 791.6 Average trip length: 3.1 Revenue Miles: 157.3 Passengers/mile: 1.6 Miles over capacity: 0.0 Percent miles over capacity: 0.0 - 1 - Report 4: ONS, OFFS, THRUS Company: North County Transit Dist FY: 1999 Route: 342 -- week days TOTALS BOTH DIRECTIONS Total passengers: 259 Passenger miles: 791.6 Average trip length: 3.1 Revenue Miles: 157.3 Passengers/mile: 1.6 Miles over capacity: 0.0 Percent miles over capacity: 0.0 - 2 -

9999

Report 4A: Detailed Ons, Offs, Thru Boardings, alightings, on-boards, thrus, number above seated capacity, and miles above seated capacity by bus stop for each scheduled trip. Provides trip summation of boardings and alightings, passengers carried over from the previous trip, passenger miles, average trip lenth, revenue miles, passengers per revenue mile, percent over capacity, seated capacity miles, and total capacity miles.

Report 4A: ONS, OFFS, THRUS 02-02-99 08:22 Page 1 Company: North County Transit FY: 1999 - Week Days Route: 342 Direction: Loop Terminal Time: 7:15 (Tue 10/27/98) MILES ON OVER OVER Stop ON OFF BOARD THRU CAP. CAP. ---- -- --- ----- ---- ---- ----- PALOMAR COLLEGE TRANSIT CENTER 11 0 0 0 LAS POSAS & DESCANSO AV 0 1 11 10 VIA VERA CRUZ & COMMERCE ST 0 6 10 4 VIA VERA CRUZ & SAN MARCOS BLVD 0 1 4 3 DISCOVERY ST & 809 (MHP) 0 0 3 3 CRAVEN RD & FOXHALL DR 2 0 3 3 CSU SAN MARCOS 0 2 5 3 TWIN OAKS VALLEY & CRAVEN RD 0 1 3 2 TWIN OAKS VALLEY & BARHAM DR 0 0 2 2 SAN MARCOS BL & SAN MARCOS CIVIC CENTER 0 0 2 2 MISSION & VINEYARD RD 0 0 2 2 MISSION & JOSLYN SENIOR CENTER 0 0 2 2 MISSION & PICO AV 1 0 2 2 MISSION & MARCOS ST 0 0 3 3 MISSION & SAN MARCOS JR HIGH 0 0 3 3 MISSION & UNITED METHODIST CHURCH 0 0 3 3 PALOMAR COLLEGE TRANSIT CENTER 0 3 3 0 Total Ons: 14 Total Offs: 14 Passengers on from last trip: 0 Passenger Miles: 29.3 Average Trip Length: 2.1 Revenue Miles: 6.5 Passengers/Mile: 0.5 Percent over Capacity: 0 Seated Capacity Miles: 248.5 Total Capacity Miles: 372.8

10101010

Report 4E: Spreadsheet This report is in tab delimited format for use in exporting to either a spreadsheet or database. Trip by trip data is provided by date of count, bus stop name, X geographic coordinate, Y geographic coordinate, boardings, alightings, on-boards, thrus, number above seated capacity, and miles above seated. This report provides the same information as presented in Report 4A in a bar (“|”) delimited format suitable for loading into a spreadsheet.

Variation|direction|Terminal Time|Date Counted|Stop|X|Y|Ons|Offs|On Board|Thru|Over Cap|Miles Over |Loop| 7:15|Tue 10/27/98|PALOMAR COLLEGE TRANSIT CENTER|6275034|******| 11| 0| 0| 0|| |Loop| 7:15|Tue 10/27/98|LAS POSAS & DESCANSO AV|6273922|******| 0| 1| 11| 10|| |Loop| 7:15|Tue 10/27/98|VIA VERA CRUZ & COMMERCE ST|6274247|******| 0| 6| 10| 4|| |Loop| 7:15|Tue 10/27/98|VIA VERA CRUZ & SAN MARCOS BLVD|6274534|******| 0| 1| 4| 3|| |Loop| 7:15|Tue 10/27/98|DISCOVERY ST & 809 (MHP)|6276792|******| 0| 0| 3| 3|| |Loop| 7:15|Tue 10/27/98|CRAVEN RD & FOXHALL DR|6277373|******| 2| 0| 3| 3|| |Loop| 7:15|Tue 10/27/98|CSU SAN MARCOS|6282605|******| 0| 2| 5| 3|| |Loop| 7:15|Tue 10/27/98|TWIN OAKS VALLEY & CRAVEN RD|6281412|******| 0| 1| 3| 2|| |Loop| 7:15|Tue 10/27/98|TWIN OAKS VALLEY & BARHAM DR|6281753|******| 0| 0| 2| 2|| |Loop| 7:15|Tue 10/27/98|SAN MARCOS BL & SAN MARCOS CIVIC CENTER|6282549|******| 0| 0| 2| 2|| |Loop| 7:15|Tue 10/27/98|MISSION & VINEYARD RD|6282947|******| 0| 0| 2| 2|| |Loop| 7:15|Tue 10/27/98|MISSION & JOSLYN SENIOR CENTER|6281605|******| 0| 0| 2| 2|| |Loop| 7:15|Tue 10/27/98|MISSION & PICO AV|6281274|******| 1| 0| 2| 2|| |Loop| 7:15|Tue 10/27/98|MISSION & MARCOS ST|6279988|******| 0| 0| 3| 3|| |Loop| 7:15|Tue 10/27/98|MISSION & SAN MARCOS JR HIGH|6278598|******| 0| 0| 3| 3|| |Loop| 7:15|Tue 10/27/98|MISSION & UNITED METHODIST CHURCH|6277194|******| 0| 0| 3| 3|| |Loop| 7:15|Tue 10/27/98|PALOMAR COLLEGE TRANSIT CENTER|6275034|******| 0| 3| 3| 0|| |Loop| 8:15|Tue 10/27/98|PALOMAR COLLEGE TRANSIT CENTER|6275034|******| 19| 0| 1| 1|| |Loop| 8:15|Tue 10/27/98|LAS POSAS & DESCANSO AV|6273922|******| 0| 0| 20| 20|| |Loop| 8:15|Tue 10/27/98|VIA VERA CRUZ & COMMERCE ST|6274247|******| 0| 4| 20| 16|| . . . A|Loop|17:40|Wed 10/21/98|TWIN OAKS VALLEY & CRAVEN RD|6281412|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|TWIN OAKS VALLEY & BARHAM DR|6281753|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|VALPREDA & RANCHEROS DR|6284495|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|SAN MARCOS BL & SAN MARCOS CIVIC CENTER|6282549|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|MISSION & VINEYARD RD|6282947|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|MISSION & JOSLYN SENIOR CENTER|6281605|******| 0| 1| 5| 4|| A|Loop|17:40|Wed 10/21/98|MISSION & PICO AV|6281274|******| 1| 0| 4| 4|| A|Loop|17:40|Wed 10/21/98|MISSION & MARCOS ST|6279988|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|MISSION & SAN MARCOS JR HIGH|6278598|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|MISSION & UNITED METHODIST CHURCH|6277194|******| 0| 0| 5| 5|| A|Loop|17:40|Wed 10/21/98|PALOMAR COLLEGE TRANSIT CENTER|6275034|******| 0| 5| 5| 0|| 259 |264 |5 |791.6 |3.1 |157.3 |1.6 |0 |5976.6 |8965.0

11111111

Report 5: On Time Summary by Stops This report provides an on time summary for each trip reporting schedule adherence at each time point.

06-nov-1998 09:29 Report 5 - ON TIME SUMMARY: Difference Schedule Time and Arrival Time Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop - Week Days PALOMAR VIA CSU SAN VALPRED SAN PALOMAR COLLEGE VERA MARCOS A & MARCOS COLLEGE TRANSIT CRUZ & RANCHER BL & TRANSIT CENTER SAN OS DR SAN CENTER MARCOS MARCOS ------- ------- ------- ------- ------- ------- 7:15 -9 -9 -9 -7 -8 7:45 -5 -8 -8 -8 -10 -9 8:15 -4 -4 -6 -4 -3 8:45 -5 -6 -8 -7 -6 9:10 -3 -3 -4 -4 -4 -4 9:40 -4 -5 -5 -3 -4 10:10 -1 -1 -2 -2 -2 -3 10:40 -3 -4 -5 -2 -2 11:10 -1 -4 -3 -3 -3 -3 11:40 -1 -2 -2 -3 -4 12:10 0 -1 -1 -4 -7 -7 12:40 -2 -1 -1 1 -1 13:10 0 -1 -1 -2 -4 -5 13:40 0 -1 -2 -1 -1 14:10 0 -1 0 1 1 2 14:45 0 -3 -2 0 0 15:20 0 -2 0 -2 -2 -3 15:55 0 -4 -1 0 1 16:30 -1 -3 -1 -6 -6 -6 17:05 -1 -4 -3 -1 0 17:40 -4 -3 -2 0 0 1 18:15 0 -4 -2 0 1 AVG -2.0 -3.4 -3.1 -3.0 -2.9 -2.9

- 1 -

12121212

Report 5A: On Time Summary On time Summary for all trips sorted by direction and time period listing percent more than five minutes slow or departing time points early. A summation of total actual run time, trips counted, and passengers per revenue hour is provided

06-nov-1998 09:29 Report 5a: On-Time Percentages Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop -- week days PERCENT SLOW PERCENT HOT AM 71.429 0.000 MID 3.030 6.061 PM 10.714 7.143 OTHER 0.000 20.000 TOTAL 16.667 5.833 Buses are considered slow when more than 5 minutes late or hot when departing early. Totals actual run time hours: 9.17 ( 22 trips counted) Passengers/Revenue Hour: 28.3

13131313

Report 5B: On Time Summary by TP This report provides an on-time summary information for each trip. For every time point, the report shows the scheduled time, arrival time, departure time, run time between time points, cumulative run time, on-time performance (+ or – minutes) and the boardings (Ons) and Alightings (Offs) between time points. The summary report portion provides aggregate statistics summarized by direction.

06-nov-1998 09:29 Report 5b: On-Time Summary by Time Point Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop -- week days Terminal Time: 715 Cum Start Terminal Sch Arr Dep Run Run On Time Time Time Time Time Time Ons Offs PALOMAR COLLEGE TRANSIT CENTER 715 724 -9 11 0 Time Points VIA VERA CRUZ & SAN MARCOS BLV 720 729 729 5 5 -9 0 1 CSU SAN MARCOS 725 734 734 5 10 -9 0 2 SAN MARCOS BL & SAN MARCOS CIV 732 739 739 5 15 -7 0 0 PALOMAR COLLEGE TRANSIT CENTER 736 744 744 5 20 -8 0 3 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . 06-nov-1998 09:29 Report 5b: On-Time Summary by Time Point Company: North County Transit Dist FY: 1999 Route: 342 Direction: Loop -- week days Terminal Time: 1815 Cum Start Terminal Sch Arr Dep Run Run On Time Time Time Time Time Time Ons Offs PALOMAR COLLEGE TRANSIT CENTER 1815 1815 0 3 0 Time Points VIA VERA CRUZ & SAN MARCOS BLV 1820 1824 1824 9 9 -4 0 0 CSU SAN MARCOS 1827 1829 1829 5 14 -2 1 2 SAN MARCOS BL & SAN MARCOS CIV 1837 1836 1837 8 22 0 0 0 PALOMAR COLLEGE TRANSIT CENTER 1842 1841 1841 4 26 1 0 2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

14141414

Report 6: Section 15 This report shows the Federal Transportation Administration Section 15 statistics for a route by time period.

06-nov-1998 09:29 Report 6: SECTION 15 DATA Company: North County Transit Dist FY: 1999 Route: 342 -- week days AM MID PM OTHER TOTAL -- --- -- ----- ----- 1. Passengers boarded 77 133 44 5 259 2. Passengers on board 509 893 342 30 1774 3. Bus trip distance 27 87 37 7 157 4. Passenger miles 242 385 151 13 792 5. Bus trip time 89 293 142 26 550 6. Passenger minutes 777 1324 594 53 2748 7. Capacity miles 1568 4932 2093 373 8965 8. Seat miles 1045 3288 1395 249 5977 9. Trips in sample 4 12 5 1 22 10. Total number of trips 0 0 0 0 0 11. Unlinked passengers per trip 19 11 9 5 12 12. Passenger miles per trip 60 32 30 13 36 13. Unlinked passenger trip time 194 110 119 53 125

15151515

Bus Stop Inventory Field Listing This report provides a listing of all stop inventory information for a given route and direction.

SANDAG Bus Stop Inventory -- Company North County Transit Dist, FY 1999 Route 342 Direction 7 1/20/99 08:55 Seq# IBT Stop# TOS# Dis Bus Stop Description ---- --- ----- ---- ---- -------------------- 5 HMT 22197 0.00 PALOMAR COLLEGE TRANSIT CENTER 10 5N 22387 0.45 LAS POSAS & DESCANSO AV 15 6F 22388 0.75 VIA VERA CRUZ & COMMERCE ST 20 6FT 21214 0.20 VIA VERA CRUZ & SAN MARCOS BLVD 25 AM 21818 0.38 DISCOVERY ST & 809 (MHP) 30 2F 22389 0.65 CRAVEN RD & FOXHALL DR 35 DMT 22020 1.00 CSU SAN MARCOS 40 8F 22380 0.45 TWIN OAKS VALLEY & CRAVEN RD 45 8F 21215 0.35 TWIN OAKS VALLEY & BARHAM DR 55 2FT 22390 0.65 SAN MARCOS BL & SAN MARCOS CIVIC CENTER 60 4F 20725 0.10 MISSION & VINEYARD RD 65 CM 21968 0.17 MISSION & JOSLYN SENIOR CENTER . . . 80 DM 20723 0.30 MISSION & SAN MARCOS JR HIGH 85 DM 22199 0.27 MISSION & UNITED METHODIST CHURCH 90 HMT 22197 0.42 PALOMAR COLLEGE TRANSIT CENTER - 2 -

16161616

Bus Stop Inventory Dump This report provides information from the Bus Stop Inventory in a form that can be easily loaded into a spreadsheet.

Stop#|Census Tract|Place#|Intersection|Block|Street 1|Street 2|X|Y|ADA Code|Bench|Shelter 10368| 8313|2475|2|F|LA JOLLA VILLAGE|TORREY PINES RD| 6256956| 1897799|U|| 10374| 8305|2475|2|F|GILMAN|MEYERS LN| 6258910| 1900316|A|| 10377| 8305|2475|2|F|GILMAN|RUSSELL DR| 6259542| 1900296|U|| 10378| 8315|2475|2|F|LA JOLLA VILLAGE|VILLA LA JOLLA DR| 6259584| 1898316|A|| 10391| 8316|2475|2|F|LA JOLLA VILLAGE|LEBON DR| 6262786| 1898011|N|| 10400| 8316|2475|2|F|LA JOLLA VILLAGE|REGENTS RD| 6264367| 1898235|U|| 10772| 8305|2475|3|N|GILMAN|MEYERS LN| 6258910| 1900316|A|| 10775| 8305|2475|3|N|GILMAN|RUSSELL DR| 6259542| 1900296|A|| 10793| 8316|2475|3|N|LA JOLLA VILLAGE|REGENTS RD| 6264367| 1898235|A|| 11153| 8305|2475|4|F|LA JOLLA VILLAGE|LEBON DR| 6262786| 1898011|U|| 11537| 8312|2475|5|N|N TORREY PINES|EXPEDITION WY| 6256632| 1898235|N|| 11538| 8312|2475|6|F|N TORREY PINES|TORREY PINES SCENIC DR| 6256614| 1904219|U|| 11539| 8312|2475|6|F|N TORREY PINES|SCIENCE PARK RD SOUTH| 6256589| 1911966|U|| 11541| 8312|2475|6|F|N TORREY PINES|SCIENCE PARK RD| 6256993| 1909292|U|| 11548| 8305|2475|5|N|GILMAN|FOOTBRIDGE| 6258257| 1899260|U|| 11751|17027|2475|5|N|W BERNARDO DR|THE POINTE| 6304894| 1949343|U|| 11875| 8312|2475|6|F|N TORREY PINES|ALMAHURST ROW| 6256537| 1901803|A|| 11876| 8312|2475|6|F|N TORREY PINES|LA JOLLA SHORES DR| 6256606| 1899714|U|| 11877| 8305|2475|6|F|N TORREY PINES|SALK INSTITUTE RD| 6256571| 1903634|A|| 11882| 8312|2475|6|F|N TORREY PINES|SCRIPPS CLINIC DRVWY| 6257483| 1906119|A|| . . . 22472|20204| 935|4|F|MISSION|DAISY ST| 6313994| 1996512|A|| 22473|20204| 935|4|F|MISSION|SUMAC PL| 6313154| 1995904|A|| 22474|20007|2537|5|N|VALPREDA|RANCHEROS DR| 6284495| 1995419|N|| 22475| 8317|2475|8|F|N TORREY PINES|SCIENCE PARK RD NORTH| 6256348| 1913307|A|| 40885|20701| 935|F|M|ESCONDIDO BL|FELICITA PARK & RIDE| 6310001| 1982082|U|| 80007|18000| 405|H|M|CARLSBAD VILLAGE STATION|| 6224904| 2003680|A|B|S

1111

Year End Processing At the end of each fiscal year, the Federal Transportation Administration (FTA) requires transit companies receiving federal Section 15 subsidies to provide certain performance statistics. The required performance statistics are calculated using several different reports collectively referred to as the “Year End Reports”. Currently, San Diego Transit Corporation and the North County Transit District receive FTA Section 15 funding and are subject to the reporting requirement.

Once all counts have been completed and the operators have received individual route reports for their routes, the end of year processing commences. A Section 15 report is generated for SDTC and NCTD as required for their Section 15 reporting. Route profiles and On-Off reports are generated for all operators and for the entire region.

Chapter

8

2222

Running Year End Reports To run a year end report select “Year End Reports” from the Output menu on the main window of PCP. The Year-End Reports window will appear as shown below.

Figure 50: Year End Report Window

This frame displays available year_end reports. These include all reports that cover all routes for a single company or set of companies. You must specify a fiscal year and one or more companies, and may generate several reports for the selected criteria at one time. If more than one company is specified, their counts will be combined in a single report. Reports cover all route counts except for those that have been marked 'OMIT FROM REPORTS'.

Note that data for year-end reports is selected from tables YEAR_END_DATA and SECTION15_DATA. These tables must be populated correctly before year-end reports are run. SECTION15_DATA must be entered thru QBF or copy. YEAR_END_DATA is populated for a given route when Report 6 is run. Thus Report 6 must be run for all routes before year-end reports can be run.

See the section on output methods in the Route Report chapter for specific information regarding output in various forms.

3333

Section 15 Processing SANDAG provides SDTC and NCTD with company level Section 15 profiles and a Section 15 Sample Data Report which addresses their FTA Section 15 reporting requirements. These reports are generated after the transit operators provide the number of days service was provided during the fiscal year for trips made on weekdays, Saturdays and Sundays. The operators also provide the number of trips, which operated during those days of service by the time period. The “AM” period runs from 6 A.M. to 8:59 A.M.. The “Mid” period runs from 9 A.M. to 2:59 P.M.. The “PM” period runs from 3:00 P.M. to 5:59 P.M.. All other trips are counted in the “Other” period.

4444

Section 15 Report North County Transit Dist Section 15 Report for FY98 10/28/98 14:47 TOTAL TOTAL TOTAL AM MID PM OTHER WEEKDAYS* SATURDAYS SUNDAYS TOTAL -- --- -- ----- -------- --------- ------- ----- 1 Passengers boarded 7,719 14,489 8,067 5,224 35,499 8,675 7,688 51,862 2 Passengers on board 108,529 202,184 114,822 79,998 505,533 115,775 120,483 741,791 3 Bus trip distance 4,586 8,801 4,769 6,042 24,198 7,113 5,504 36,815 4 Passenger miles 44,771 83,230 49,752 35,767 213,519 60,447 51,600 325,566 ------------------------------------------------------------------------------------------------------------------------------------ 5 Bus trip time 13,763 26,884 14,935 16,028 71,610 20,036 16,000 107,646 6 Passenger minutes 134,997 257,278 155,231 97,153 644,659 166,867 153,686 965,212 ------------------------------------------------------------------------------------------------------------------------------------ 7 Capacity miles 283,749 549,329 296,239 382,576 1,511,891 451,019 348,167 2,311,078 8 Seat miles 189,166 366,219 197,492 255,050 1,007,928 300,680 232,111 1,540,719 9 Trips in sample 235 450 255 300 1,240 366 276 1,882 10 Total number of trips 59,160 114,240 63,240 80,325 316,965 52,676 38,744 408,385 11 Unlinked passengers per trip 32.85 32.20 31.64 17.41 28.63 23.70 27.86 12 Passenger miles per trip 191 185 195 119 172 165 187 ------------------------------------------------------------------------------------------------------------------------------------ 13 Unlinked passenger trip time 17 18 19 19 18 19 20 ------------------------------------------------------------------------------------------------------------------------------------ 14 Unlinked passenger trips 1,943,217 3,678,274 2,000,616 1,398,726 9,074,146 1,248,536 1,079,217 15 Passenger miles 11,270,811 21,129,196 12,338,551 9,576,553 54,579,147 8,699,762 7,243,400 ------------------------------------------------------------------------------------------------------------------------------------ 16 Avg. wkdy. passengers(unlinked) 7,620 14,425 7,846 5,485 35,585 24,010 18,607 17 Avg. wkdy. passenger miles 44,199 82,860 48,386 37,555 214,036 167,303 124,886 18 Avg. trip length (miles) 5.80 5.74 6.17 6.85 6.01 6.97 6.71 ------------------------------------------------------------------------------------------------------------------------------------ * These totals are not included in the Form 406A

5555

Route Profiles

System Daily Profile This report shows summary statistics by route and for the entire system of a given transit operator. SANDAG generates this report for San Diego Transit Corporation (SDTC) and the North County Transit District (NCTD) for attachment with their Section 15 Reports. Profiles are also generated for each sub operator and provided to SANDAG’s transportation division to be included in Federal Transportation Administration (FTA) reports. A region wide bus system profile is also generated using this report.

28-oct-1998 15:04 FY1998 San Diego Transit Corp BUS SYSTEM DAILY PROFILE PASS MI PASS MI MONTH # OF # OF REVENUE PASSENGERS PASSENGER ATL REVENUE PASSENGERS PASSENGER ATL OVER OVER BUS ROUTE COUNTED TRIPS PASSENGERS MILES PER MILE MILES (MILES) HOURS PER HOUR HOURS (MINUTES) SEAT MI GAL-FUEL SPEED 1 01-98 67 4500 725.9 6.20 10121.5 2.25 66.62 67.55 928.90 12.39 0.31 42.34 10.90 2 10-97 188 8880 1467.7 6.05 17028.5 1.92 119.45 74.34 1385.88 9.36 0.26 36.03 12.29 3 07-97 122 6879 1167.9 5.89 14249.5 2.07 109.63 62.75 1337.58 11.67 0.27 39.43 10.65 4 01-98 72 3518 906.8 3.88 9824.2 2.79 67.15 52.39 727.46 12.41 0.25 32.31 13.50 5 11-97 71 5156 1661.9 3.10 17260.7 3.35 113.05 45.61 1174.17 13.66 0.24 29.67 14.70 6 07-97 64 3441 860.9 4.00 10546.0 3.06 69.93 49.20 856.72 14.94 0.26 40.24 12.31 7 03-98 198 17617 2040.9 8.63 47638.9 2.70 189.53 92.95 4424.13 15.07 0.37 56.35 10.77 9 08-97 68 1630 584.4 2.79 5887.8 3.61 36.58 44.56 368.57 13.57 0.23 31.06 15.97 . . . 81 12-97 66 2337 881.1 2.65 11423.5 4.89 63.33 36.90 821.12 21.08 0.32 34.08 13.91 115 02-98 59 3672 1142.2 3.21 16444.8 4.48 77.63 47.30 1117.69 18.26 0.33 42.05 14.71 150 08-97 22 652 326.5 2.00 8835.3 13.55 13.52 48.24 365.78 33.66 0.44 67.17 24.15 210 09-97 12 396 370.3 1.07 5405.2 13.65 15.25 25.97 222.59 33.73 0.30 39.67 24.28 270 03-98 2 31 28.4 1.09 336.9 10.87 1.25 24.80 14.82 28.68 0.27 35.54 22.74 Totals: 2302 123260 33615.5 3.67 482336.7 3.91 2347.12 52.52 33677.90 16.39 0.31 40.08 14.32 - 1 -

6666

System Daily Profile (Sunday) This report shows summary statistics by route and for the entire system of a given transit operator for trips made on Sundays. FY1998 BUS SYSTEM DAILY PROFILE (Sunday) 24-nov-1998 11:44 Chula Vista Transit PASS MI PASS MI MONTH # OF # OF REVENUE PASSENGERS PASSENGER ATL REVENUE PASSENGERS PASSENGER ATL OVER OVER BUS ROUTE COUNTED TRIPS PASSENGERS MILES PER MILE MILES (MILES) HOURS PER HOUR HOURS (MINUTES) SEAT MI GAL-FUEL SPEED 701 06-98 8 186 86.9 2.14 624.6 3.36 5.37 34.66 38.58 12.45 0.18 32.35 16.19 702 06-98 12 234 98.0 2.39 552.1 2.36 6.95 33.67 39.14 10.04 0.14 25.34 14.11 705 06-98 8 103 68.5 1.50 396.4 3.85 4.15 24.82 24.01 13.98 0.15 26.03 16.51 708 06-98 10 41 10.4 3.94 19.4 0.47 1.53 26.74 2.86 4.18 0.07 8.76 6.78 709 05-98 12 205 141.6 1.45 800.8 3.91 7.03 29.15 39.78 11.64 0.15 25.45 20.13 712 06-98 18 177 79.7 2.22 322.8 1.82 4.77 37.13 19.32 6.55 0.10 18.24 16.71 716 06-98 4 86 36.5 2.36 281.9 3.28 2.98 28.83 23.06 16.09 0.20 34.78 12.23 Totals: 72 1032 521.6 1.98 2998.0 2.91 32.78 31.48 2.78 0.16 0.15 25.89 15.91 - 1 -

7777

System Daily Profile (Saturday) This report shows summary statistics by route and for the entire system of a given transit operator for trips made on Saturdays.

FY1998 BUS SYSTEM DAILY PROFILE (Saturday) 24-nov-1998 11:45 Chula Vista Transit PASS MI PASS MI MONTH # OF # OF REVENUE PASSENGERS PASSENGER ATL REVENUE PASSENGERS PASSENGER ATL OVER OVER BUS ROUTE COUNTED TRIPS PASSENGERS MILES PER MILE MILES (MILES) HOURS PER HOUR HOURS (MINUTES) SEAT MI GAL-FUEL SPEED 701 06-98 12 198 130.3 1.52 630.0 3.18 7.72 25.66 37.30 11.30 0.12 21.75 16.89 702 06-98 10 139 81.7 1.70 230.1 1.66 5.43 25.58 15.30 6.60 0.07 12.67 15.04 703 06-98 10 247 112.8 2.19 615.9 2.49 7.17 34.47 39.13 9.51 0.19 25.66 15.74 704 05-98 12 114 107.1 1.06 440.5 3.86 5.55 20.54 22.83 12.01 0.11 18.51 19.30 705 05-98 14 228 116.7 1.95 668.2 2.93 7.35 31.02 42.08 11.07 0.15 25.76 15.88 706 05-98 12 307 75.7 4.05 531.8 1.73 6.00 51.17 42.14 8.24 0.24 33.01 12.62 707 06-98 10 99 59.2 1.67 272.7 2.75 3.27 30.31 15.06 9.13 0.16 21.67 18.11 708 05-98 34 218 35.4 6.17 101.0 0.46 3.73 58.39 10.67 2.94 0.16 13.71 9.47 709 05-98 8 146 94.4 1.55 629.9 4.31 4.32 33.82 28.80 11.84 0.17 30.03 21.87 712 06-98 18 194 79.7 2.44 352.8 1.82 4.95 39.19 21.92 6.78 0.11 19.93 16.09 716 05-98 9 226 82.1 2.75 596.9 2.64 6.97 32.44 50.66 13.45 0.29 34.18 11.78 Totals: 149 2116 975.0 2.17 5069.8 2.40 62.45 33.88 17.80 0.50 0.15 23.80 15.61 - 1 -

8888

On Off Reporting In addition to Section 15 and Profile reports, SANDAG produces On-Off reports at the end of each fiscal year. The On-Off reports show the number of passengers getting on and off transit vehicles at each transit stop and list the routes which use a particular stop. The On-Off reports can be generated in various sort orders such as by Ons, Offs, total trip ends, and bus stop description. They can also be generated to contain transit stop activity for a particular transit company, or an aggregate of companies. Examples of the various possible On-Off reports follows.

On-Off Summary by Trip Ends 1/14/99 14:41 FY 1998 On-Off Summary by TRIPENDS Page 1 For San Diego Transit Corp, North County Transit Dist, Chula Vista Transit, San Diego Cty Transit, National City Trans it, MTDB Contract Routes, San Diego Trolley Inc. BUS STOP LOCATIONS PLACE DIR F/N ONS OFFS TOTAL ACCESS SHELTER ROUTES ------------------ ----- --- --- --- ---- ----- ------ ------- ------ INTERNATIONAL BORDER STATION San Diego N M 9964 8398 18362 A S 510 932 OLD TOWN TRANSIT CENTER San Diego M 9028 9228 18256 A S 5 6 9 26 28 34 35 44 81 510 511 908 IMPERIAL & 12TH ST STATION San Diego S M 9432 8716 18148 A S 1 4 11 510 520 929 CITY COLLEGE STATION San Diego E M 5050 5662 10712 A S 510 520 H ST TROLLEY STATION Chula Vist S M 5510 5176 10686 A S 510 701 702 703 704 706 707 709 EUCLID TROLLEY STATION San Diego W M 5290 4851 10141 A S 3 4 5 13 16 19 55 520 603 816 913 EL CAJON TRANSIT CENTER El Cajon E M 4617 4814 9431 A S 15 520 848 858 864 870 871 872 873 5TH AV STATION - C ST San Diego E M 4158 4992 9150 A S 510 520 PALOMAR ST TROLLEY STATION Chula Vist N M 4471 4623 9094 A S 510 701 702 703 712 24TH ST TROLLEY STATION & (NATI National C N M 3989 3962 7951 A S 510 601 602 IRIS AV TROLLEY STATION San Diego S M 3899 4018 7917 A S 510 929 932 FASHION VALLEY TROLLEY STATION San Diego E M 3717 3812 7529 A 6 13 16 20 25 27 41 81 511 913 990 CIVIC CENTER STATION San Diego E M 3824 3297 7121 A S 510 520 ESCONDIDO TRANSIT CENTER Escondido W M 3235 2919 6154 A S 302 307 308 320 381 382 384 385 386 388 810 AMERICAN PLAZA San Diego W M 3065 2898 5963 A S 510 520 VISTA TRANSIT CENTER Vista E F 2971 2637 5608 A S 302 306 311 318 320 331 332 OCEANSIDE TRANSIT CENTER Oceanside W M 2683 2523 5206 A S 301 302 303 305 310 312 313 314 316 317 318 320 E ST BAYFRONT TROLLEY STATION Chula Vist N M 2526 2532 5058 A S 510 705 708 716 932 BROADWAY & 3RD AV San Diego E N 2899 1911 4810 A 2 7 11 15 20 30 34 40 50 70 115 150 210 270 850 860 901 922 923 929 932 992 PLAZA CAMINO REAL Carlsbad N M 2391 2207 4598 A S 302 309 310 311 312 316 319 320 321 322 MARKET & 12TH ST STATION San Diego S M 2011 2109 4120 A S 510 520 UNIVERSITY TOWNE CENTER San Diego E M 1927 2056 3983 A S 5 30 34 41 50 150 301 310 921 931 GROSSMONT CENTER STATION La Mesa E M 1964 1950 3914 A S 15 81 520 854 855 IRIS AV TROLLEY STATION San Diego W M 2079 1815 3894 A 901 933 934 PALM CITY STATION San Diego N M 1912 1982 3894 A S 510 BEYER ST TROLLEY STATION San Diego S M 1855 2026 3881 A S 510 BROADWAY & 4TH AV San Diego W N 1065 2420 3485 A 2 7 11 15 20 30 34 40 50 70 115 150 210 270 901 922 923 929 932

9999

On-Off Summary by Ons 1/20/99 09:14 FY 1998 On-Off Summary by ONS Page 1 For San Diego Cty Transit BUS STOP LOCATIONS PLACE DIR F/N ONS OFFS TOTAL ACCESS SHELTER ROUTES ------------------ ----- --- --- --- ---- ----- ------ ------- ------ EL CAJON TRANSIT CENTER El Cajon E M 1728 1874 3602 A S 848 858 864 870 871 872 873 SANTEE TRANSIT CENTER Santee N M 813 785 1598 A S 831 832 833 834 854 870 PARKWAY PLAZA TRANSIT CENTER El Cajon E M 759 714 1473 A 833 848 858 864 871 872 SPRING STREET STATION La Mesa E M 446 396 842 A S 851 853 855 GROSSMONT COLLEGE El Cajon W M 428 406 834 A 854 858 GROSSMONT CENTER STATION La Mesa E M 422 384 806 A S 854 855 BROADWAY & MAIN (TROLLEY) Lemon Grov E N 367 98 465 A 856 BROADWAY & MAIN (TROLLEY) Lemon Grov W F 195 412 607 A 856 875 WILLOWS RD & 5000 (CASINO) Other Unin E M 195 151 346 A 864 CUYAMACA COLLEGE Rancho San W M 173 170 343 A 856 858 EUCLID TROLLEY STATION San Diego W M 157 117 274 A S 816 JAMACHA & DOUBLETREE RD Spring Val E N 148 160 308 A 853 855 856 FLETCHER PKWY & MAGNOLIA AV El Cajon W F 144 180 324 A 833 848 858 864 872 877 ESCONDIDO TRANSIT CENTER Escondido W M 120 112 232 A S 810 B ST & 5TH AV San Diego W N 116 179 295 A 810 820 850 860 BROADWAY & 7081 (SOCIAL SERVICE Lemon Grov E M 99 14 113 A 816 856 875 BROADWAY & MOLLISON AV El Cajon W F 97 34 131 A 848 864 RANCHO PENASQUITOS BLVD & PASEO San Diego S F 97 7 104 A 844 845 MAPLEVIEW & ASHWOOD ST Lakeside E F 95 190 285 A 848 854 MASSACHUSETTS AV STATION Lemon Grov W M 95 89 184 A S 816 MASSACHUSETTS AV TROLLEY STA Lemon Grov E N 94 44 138 A 875 WELD TROLLEY STATION El Cajon E M 94 36 130 A S 877 MAST BL & 8756 (WEST HILLS HS) Santee E M 87 73 160 A 831 834 THE GROVE TRANSIT CENTER San Diego N M 86 79 165 A 816 856 MADISON AV & MOLLISON El Cajon W F 78 20 98 A 873 MAGNOLIA AV & MAST BLVD Santee S N 78 11 89 A 832 MIDLAND RD & POWAY RD Poway S N 77 115 192 A 820 845 5TH AV & B ST San Diego N F 73 0 73 A 850 860 BROADWAY & 2ND ST El Cajon W F 73 38 111 A 848 864 4TH ST & MADISON (HIGH SCHOOL) El Cajon S F 69 90 159 A 873 SWEETWATER RD & ST GEORGE Spring Val N F 69 25 94 U 856 LAKE MURRAY & BALTIMORE DR La Mesa E F 68 20 88 U 854 SWEETWATER RD & BLOSSOM Spring Val N F 67 19 86 N 851 856 BALLANTYNE & E MAIN ST El Cajon N F 65 24 89 A 872 CHASE & ESTES ST El Cajon S N 63 26 89 A 871 BROADWAY & FRONT ST San Diego E N 62 0 62 A 850 860 CAMPO & BANCROFT DR Casa de Or W N 62 22 84 A 855 JAMACHA BLVD & GRAND Spring Val W N 61 20 81 A 851 856 MADISON AV & 2ND ST El Cajon W F 61 12 73 A 873 A ST & 1ST AV San Diego E N 59 0 59 A 810 820

10101010

On-Off Summary by Offs 1/20/99 09:16 FY 1998 On-Off Summary by OFFS Page 1 For San Diego Cty Transit BUS STOP LOCATIONS PLACE DIR F/N ONS OFFS TOTAL ACCESS SHELTER ROUTES ------------------ ----- --- --- --- ---- ----- ------ ------- ------ EL CAJON TRANSIT CENTER El Cajon E M 1728 1874 3602 A S 848 858 864 870 871 872 873 SANTEE TRANSIT CENTER Santee N M 813 785 1598 A S 831 832 833 834 854 870 PARKWAY PLAZA TRANSIT CENTER El Cajon E M 759 714 1473 A 833 848 858 864 871 872 BROADWAY & MAIN (TROLLEY) Lemon Grov W F 195 412 607 A 856 875 GROSSMONT COLLEGE El Cajon W M 428 406 834 A 854 858 SPRING STREET STATION La Mesa E M 446 396 842 A S 851 853 855 GROSSMONT CENTER STATION La Mesa E M 422 384 806 A S 854 855 MAPLEVIEW & ASHWOOD ST Lakeside E F 95 190 285 A 848 854 FLETCHER PKWY & MAGNOLIA AV El Cajon W F 144 180 324 A 833 848 858 864 872 877 B ST & 5TH AV San Diego W N 116 179 295 A 810 820 850 860 CUYAMACA COLLEGE Rancho San W M 173 170 343 A 856 858 JAMACHA & DOUBLETREE RD Spring Val E N 148 160 308 A 853 855 856 WILLOWS RD & 5000 (CASINO) Other Unin E M 195 151 346 A 864 EUCLID TROLLEY STATION San Diego W M 157 117 274 A S 816 MIDLAND RD & POWAY RD Poway S N 77 115 192 A 820 845 ESCONDIDO TRANSIT CENTER Escondido W M 120 112 232 A S 810 MADISON AV & MOLLISON El Cajon E N 45 104 149 A 873 BROADWAY & MAIN (TROLLEY) Lemon Grov E N 367 98 465 A 856 4TH ST & MADISON (HIGH SCHOOL) El Cajon S F 69 90 159 A 873 MASSACHUSETTS AV STATION Lemon Grov W M 95 89 184 A S 816 10TH AV & A ST San Diego S F 0 83 83 A 810 820 850 860 JAMACHA BLVD & GILLESPIE DR Spring Val W F 30 81 111 A 851 856 JAMACHA BLVD & GRAND Spring Val E N 16 80 96 A 856 THE GROVE TRANSIT CENTER San Diego N M 86 79 165 A 816 856 BROADWAY & 7086 (LEMON GROVE PL Lemon Grov W M 18 78 96 A 816 856 875 MAPLEVIEW & ASHWOOD ST Lakeside W N 14 78 92 A 854 CAMPO & CONRAD DR Casa de Or E N 31 76 107 A 853 855 BROADWAY & MOLLISON AV El Cajon E F 46 74 120 A 848 864 BROADWAY & BALLANTYNE ST El Cajon W F 39 74 113 A 848 864 872 RANCHO PENASQUITOS BLVD & PASEO San Diego N N 9 74 83 A 844 845 MAST BL & 8756 (WEST HILLS HS) Santee E M 87 73 160 A 831 834 MADISON AV & 2ND (TACO BELL) El Cajon E N 10 71 81 A 873 SWEETWATER RD & JAMACHA BLVD Spring Val S F 9 71 80 U 856 SWEETWATER RD & BLOSSOM Spring Val S F 18 69 87 N 851 856 BROADWAY & MASSACHUSETTS AV Lemon Grov W F 10 63 73 A 816 856 875 CAMPO & BANCROFT DR Casa de Or E F 15 63 78 A 855 SWEETWATER SPRINGS & MONTE VIST Spring Val E M 34 63 97 U 855 1ST AV & C ST San Diego N F 0 59 59 A 810 820 CAMINO CANADA & WALMART Other Unin E M 37 57 94 A 864 CAMPO & BONITA ST Casa de Or E N 17 57 74 A 853 855

11111111

On-Off Summary by Place 11/13/98 16:20 FY 1998 On-Off Summary by PLACE Page 1 For MTDB Contract Routes BUS STOP LOCATIONS PLACE DIR F/N ONS OFFS TOTAL ACCESS SHELTER ROUTES ------------------ ----- --- --- --- ---- ----- ------ ------- ------ 9TH ST & IMPERIAL BEACH BLVD Imperial B S N 13 30 43 A 901 9TH ST & PALM AV Imperial B S F 64 113 177 A 901 9TH ST & GROVE Imperial B S F 10 26 36 A 933 9TH ST & ELM Imperial B S F 9 10 19 A 901 9TH ST & HOLLY AV Imperial B N F 16 19 35 A 934 9TH ST & FERN Imperial B N F 13 13 26 N 934 9TH ST & IMPERIAL BEACH BLVD Imperial B N F 19 24 43 U 901 9TH ST & ELM Imperial B N F 8 14 22 A 901 11TH ST & IRIS AV Imperial B N N 5 14 19 A 933 11TH ST & HEMLOCK Imperial B N N 5 4 9 A 934 11TH ST & HOLLY AV Imperial B N F 8 13 21 A 933 13TH ST & HOLLY AV Imperial B S N 54 56 110 U 934 13TH ST & FERN Imperial B S N 34 64 98 A 934 13TH ST & HOLLY AV Imperial B N N 34 40 74 A 933 13TH ST & GROVE Imperial B N N 27 33 60 A 933 13TH ST & FERN Imperial B N F 9 22 31 A 933 HOLLY AV & 9TH ST Imperial B E F 15 17 32 A 933 HOLLY AV & 10TH Imperial B W N 17 20 37 A 934 IMPERIAL BEACH BLVD & 3RD Imperial B E N 12 26 38 A 933 IMPERIAL BEACH BLVD & CALIFORNI Imperial B E N 34 64 98 N 933 IMPERIAL BEACH BLVD & CONNECTIC Imperial B E N 26 23 49 A 933 IMPERIAL BEACH BLVD & EMORY Imperial B E N 13 21 34 A 901 IMPERIAL BEACH BLVD & 11TH ST Imperial B E N 11 11 22 N 901 IMPERIAL BEACH BLVD & 13TH ST Imperial B E N 117 104 221 U 901 933 IMPERIAL BEACH BLVD & GRANGER Imperial B E N 36 18 54 N 901 933 IMPERIAL BEACH BLVD & SEACOAST Imperial B E F 33 40 73 U 933 IMPERIAL BEACH BLVD & 4TH Imperial B E F 27 31 58 A 933 IMPERIAL BEACH BLVD & 3RD Imperial B W N 14 12 26 N 934 IMPERIAL BEACH BLVD & 4TH Imperial B W N 15 15 30 A 934 IMPERIAL BEACH BLVD & CONNECTIC Imperial B W N 17 15 32 U 934 IMPERIAL BEACH BLVD & EMORY Imperial B W N 15 14 29 N 901 IMPERIAL BEACH BLVD & FLORIDA Imperial B W N 10 25 35 U 901 . . . PALM AV & 3RD Imperial B W F 22 51 73 U 933 PALM AV & CORVINA Imperial B W F 9 29 38 A 933 PALM AV & 7TH Imperial B W F 45 81 126 A 933 PALM AV & 9TH ST Imperial B W F 194 213 407 A 901 910 933 PALM AV & 11TH ST Imperial B W F 31 117 148 A 933 PALM AV & 170 (AMERICAN YOUTH H Imperial B W M 11 43 54 A 933 RAINBOW DR & BONITO AV Imperial B S N 4 18 22 A 901 SEACOAST DR & EVERGREEN Imperial B S N 20 47 67 A 933 SEACOAST DR & PALM AV Imperial B S N 17 19 36 U 933 SEACOAST DR & DONAX AV Imperial B S F 21 60 81 U 933 SEACOAST DR & PALM AV Imperial B N N 32 16 48 A 934 SEACOAST DR & EVERGREEN Imperial B N F 47 33 80 U 934 SEACOAST DR & DAISY Imperial B N F 34 8 42 U 934 SILVER STRAND & 7TH Imperial B W N 32 10 42 A 901

12121212

On-Off Summary by Bus Stop Description 1/14/99 15:11 FY 1998 On-Off Summary by STREET Page 1 For San Diego Transit Corp, North County Transit Dist, Chula Vista Transit, San Diego Cty Transit, National City Trans it, MTDB Contract Routes, San Diego Trolley Inc. BUS STOP LOCATIONS PLACE DIR F/N ONS OFFS TOTAL ACCESS SHELTER ROUTES ------------------ ----- --- --- --- ---- ----- ------ ------- ------ 1ST AV & ASH ST San Diego N N 175 79 254 A 11 30 50 150 1ST AV & BROOKES San Diego S N 6 10 16 A 11 1ST AV & BROOKES San Diego N F 8 10 18 A 11 1ST AV & C ST San Diego N F 178 105 283 A 11 30 50 150 810 820 1ST AV & CEDAR San Diego N N 34 38 72 U 11 1ST AV & E San Diego N F 7 96 103 A 4 1ST AV & ELM San Diego N F 19 30 49 A 11 1ST AV & F ST Chula Vist S F 3 6 9 U 701 1ST AV & F ST Chula Vist N N 5 10 15 U 701 1ST AV & G Chula Vist S F 2 8 10 U 701 1ST AV & G Chula Vist N N 2 2 4 U 701 1ST AV & G ST San Diego N F 14 38 52 A 4 1ST AV & GRAPE ST San Diego N N 19 50 69 A 11 1ST AV & IVY San Diego N F 23 66 89 U 11 . . . 1ST AV & QUINCE San Diego N N 6 18 24 A 11 1ST AV & REDWOOD ST San Diego S F 8 9 17 A 11 1ST AV & ROBINSON San Diego S F 19 13 32 A 11 1ST AV & ROBINSON San Diego N F 4 22 26 A 11 1ST AV & SPRUCE San Diego N N 11 16 27 A 11 1ST AV & THORN ST San Diego S F 11 14 25 A 11 1ST AV & UPAS ST San Diego N N 14 18 32 A 11 1ST AV & WALNUT San Diego S F 22 19 41 A 11 1ST AV & WALNUT San Diego N F 7 11 18 A 11 1ST AV & WASHINGTON AV San Diego N F 1 20 21 U 3 1ST ST & A ST Encinitas N F 9 1 10 U 301 1ST ST & B AVE (FERRY) Coronado E F 5 64 69 U 904 1ST ST & B AVE (FERRY) Coronado W F 82 1 83 U 904 1ST ST & BASIL ST Encinitas N F 7 3 10 U 301 1ST ST & EL PORTAL ST Encinitas N N 3 11 14 U 301 1ST ST & H ST Encinitas S N 9 4 13 A 301

Other Year End Processing

1111

Count Data Analysis This report provides stop level activity for all routes in the region in a delimited ASCII file. The file is parsed in Microsoft Excel, where modifications are made before it is output as a dBase file. This dBase file is used in SANDAG’s View2Transit, an ArcView application provided directly to transit operators to answer short range transit planning and marketing questions.

Modifications made to this database include column headings, some reorganization of the columns, addition of 2 columns used internally by ArcView, and filling in blank cells (e.g. no counts for a particular time period for a commuter express bus) with zeros. The figure below shows the Excel spreadsheet with these modifications.

View2Transit Introduction and Count Inputs

Analysis by Geographic Area

Chapter

9

2222

Analysis by Jurisdiction

Segment Analysis

1111

Database Maintenance

Managing Counter Data Counter data builds over time and it may become necessary to archive older counts to free up storage space. The following sections describe how that is done.

Archiving Counts To archive a count, run the archive_counter program. Currently the program is set up to archive all count information for fiscal year 1995 to a file in the C:\temp directory. THE PROGRAM IS SET TO AUTOMATICALLY DELETE THE INFORMATION at the conclusion of the archive process. It is therefore important to make sure you have a full database backup before attempting to archive count data.

Restoring Counts To restore a count run the restore_counter program and follow the directions provided by the program.

Chapter

10

2222

Maintaining the Database There are two programs for maintaining the Counter database, audit_counter and optimize_counter which are described in detail in the sections below. An additional section describes the procedure for performing database backups.

Auditing the Counter Database The audit_counter program performs an audit of the database checking that all the required tables are present and the data is correct. It also provides information on the number of counts in a raw and edited state for each fiscal year. The program is run from the command prompt (MS-DOS window) from any directory. The command is:

audit_counter <database-name>

where <database name> is the name of the counter database you want to audit. For example:

audit_counter pavo::counter3

will audit the counter3 database on Pavo. This is probably what the command will usually look like. The output of the program is sent to the screen by default and contains information about the tables audited and any errors found. You can save the output of the audit program to a file by adding " > audit-counter.lis " to the command as shown below:

audit_counter pavo::counter3 > audit-counter.lis

The output file name (audit_counter.lis in the above example) can be anything you like. It will be written to the current directory (the one you run the program from). The program takes about 3-5 minutes to run.

Optimizing the Counter Database The optimize_couner program performs various optimizations on the counter database including rebuilding table structures and indices. The program is run from the command prompt (MS-DOS window) from any directory. The command is:

optimize_counter <database-name>

where <database name> is the name of the counter database you want to optimize. For example:

optimize_counter pavo::counter3

3333

will optimize the counter3 database on Pavo. The output is sent to the screen by default and contains information on the tables processed. If you would like to save the output use the same syntax as shown above for audit counter.lis. The program should take about 5 minutes 'Eo run.

Optimizepcp This is a batch file (has the bat extension) and is in the root (C:\) directory. The batch file is run by going to the C:\ directory and entering: optimizepcp

The batch file contains commands to run optimize-counter, optimizedb and sysmod. The first program, optimize_counter, is specific to the counter program and is described above. The second two programs (optimizedb and sysmod) are Ingres programs that create optimizer statistics and rebuild the database system tables respectively. It is necessary to make sure that no one is using the counter database when optimizepcp is run since sysmod will abort if it finds active sessions. The entire process (all three programs) should take 10-20 minutes.

Performing Database Backups Checkpoints and Journals The primary Ingres backup is called a checkpoint, which is a binary snapshot of everything in the database at that time. Counter3 runs with journals activated. Journals contain everything that happens to a database in between checkpoints. Ingres contains a recovery command called Rollforward which restores a database or a table from the last checkpoint and the current journals. When a checkpoint is performed, a new snapshot is taken, and the journals are cleared.

The checkpoint command is <ckpdb -d +j counter3>. The -d tells Ingres; to delete the last checkpoint. If you omit this option you can save a history of the database. However, checkpoints require a lot of disk space and you shouldn't keep too many around. In fact, I never keep any but the last one. The +j option tells Ingres to turn on the journals. You should always do this for counter3.

The checkpoint file is written to the directory lapps/ingres12/ingres/ckpldefault/counter3. You have to be the Ingres id to get to this directory. You should never have to go there. Incidentally, the journals are stored in a similar directory lapps/ingres12/ingres/jnl/default/counter3. Both of these are on PAVO.

Unloading the Database Another common backup technique is to do a complete unload of the database. This is a technique to get all of the system tables and user tables in a common format that can be used to completely rebuild a database from scratch. A redundant backup is recommended. It's not as fast (either going to disk or coming from disk) as a checkpoint, but it offers some other features such as restoring a single table or a procedure or whatever in a more timely fashion than a checkpoint. It is recommended that you run an unload periodically and save it to tape.

> cd /box4/udm/mod/dbdump/counter3

The unload command is <unloaddb counter3>. This will create two SQL script files unload.ing and reload.ing, the purposes of each being obvious. to actually get the database to disk enter the command <unload.ing>. The data will be stored in binary format in whatever directory to start the script. Counter3 needs a lot of room. Have your system administrator set up with a convenient place to save your unloads. If

4444

you have occasion to save the data in ASCII, enter the command <unloaddb -c counter3> and then run unload.ing. Be advised, the ASCII version of this database is HUGE. Remember, stop_count has over 2 million records.

Recommended Practices Periodically copy your checkpoint and unloaddb to tape. This is another redundant backup procedure. Normally these will get backed-up in the daily system backup procedures. You can't have too many backups.

Put in tape tar –cvf /dev/rmt/0 * Periodically run a system consistency check on the database. This gets Ingres to reorganize its list of what you have in the system. The command is <sysmod counter3>. This takes a couple of minutes and should be a routine part of your backup procedures. Run sysmod after a checkpoint.

Periodically (about once a month or after a lot of updates) run an optimization of the database. This forces Ingres to rebuild statistics about each table that it uses to optimize its query responses. The command is <optimizedb -zk counter3>. This takes a long time, so do this when you don't want to get into the database for a while. Don't forget the -zk option.

Finally, make sure you are logged out of the Counter Application before you run any of your backup procedures. These are all Unix commands and you need to login to PAVO. You can do this by going into the cold room and getting on PAVO directly, or by logging into another Sun box and then starting a telnet session to PAVO, or using PC X-WARE. You should backup whenever you have entered enough data that would be difficult to recover if you lost it.

1111

Index

A Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2 Index 3, 3

Index 1, 1 Index 1, 1

B Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2

C Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

D Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

E Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2 Index 1, 1 Index 1, 1 Index 1, 1

G Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

H Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

K Index 1, 1

L Index 1, 1

Index 2, 2 Index 1, 1 Index 1, 1

Index 2, 2 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

M Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2

N Index 1, 1 Index 1, 1 Index 1, 1


R Index 1, 1 Index 1, 1

S Index 1, 1 Index 1, 1 Index 1, 1


T Index 1, 1 Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2

W Index 1, 1 Index 1, 1 Index 1, 1

Index 2, 2 Index 1, 1 Index 1, 1 Index 1, 1 Index 1,

0000

PASSENGER COUNTING PROGRAM

System Manual

Volume

2

Board of Directors San Diego Assoc ia t ion o f Governments

The 18 cities and county government are SANDAG serving as the forum for regional decision-making. The Association builds consensus, makes strategic plans, obtains and allocates resources, and provides information on a broad range of topics pertinent to the region’s quality of life.

CHAIRMAN: Hon. Art Madrid VICE CHAIR: Hon. Ramona Finnila

SECRETARY-EXECUTIVE DIRECTOR: Kenneth E. Sulzer

CITY OF CARLSBAD Hon. Ramona Finnila, Councilmember (A) Hon. Bud Lewis, Mayor (A) Hon. Matt Hall, Mayor Pro Tem CITY OF CHULA VISTA Hon. Shirley Horton, Mayor (A) Hon. Mary Salas, Mayor Pro Tem CITY OF CORONADO Hon. Thomas Smisek, Mayor (A) Hon. Chuck Marks, Councilmember CITY OF DEL MAR Hon. Richard Earnest, Mayor (A) Hon. Crystal Crawford, Councilmember CITY OF EL CAJON Hon. Richard Ramos, Councilmember (A) Hon. Mark Lewis, Mayor CITY OF ENCINITAS Hon. Dennis Holz, Deputy Mayor (A) Hon. Sheila Cameron, Mayor CITY OF ESCONDIDO Hon. Keith Beier, Mayor Pro Tem (A) Hon. June Rady, Councilmember CITY OF IMPERIAL BEACH Hon. Diane Rose, Mayor (A) Hon. Mayda Winter, Mayor Pro Tem (A) Hon. Patricia McCoy, Councilmember CITY OF LA MESA Hon. Art Madrid, Mayor (A) Hon. Barry Jantz, Councilmember (A) Hon. Jay La Suer, Councilmember CITY OF LEMON GROVE Hon. Mary Sessom, Mayor (A) Hon. Jill Greer, Councilmember CITY OF NATIONAL CITY Hon. Ron Morrison, Vice Mayor (A) Hon. George H. Waters, Mayor CITY OF OCEANSIDE Hon. Carol McCauley, Councilmember (A) Hon. Colleen O’Harra, Deputy Mayor CITY OF POWAY Hon. Don Higginson, Councilmember (A) Hon. Mickey Cafagna, Mayor (A) Hon. Robert Emery, Deputy Mayor

CITY OF SAN DIEGO Hon. Barbara Warden, Councilmember (A) Hon. Juan Vargas, Councilmember (A) Hon. Byron Wear, Deputy Mayor CITY OF SAN MARCOS Hon. Hal Martin, Councilmember (A) Hon. Pia Harris-Ebert, Vice Mayor CITY OF SANTEE Hon. Jack Dale, Mayor (A) Hon. Hal Ryan, Councilmember (A) Hon. Jim Bartell, Vice Mayor CITY OF SOLANA BEACH Hon. Marion Dodson, Mayor (A) Hon. Joe Kellejian, Deputy Mayor (A) Hon. Marcia Smerican, Councilmember CITY OF VISTA Hon. Gloria E. McClellan, Mayor (A) Hon. Judy Ritter, Councilmember COUNTY OF SAN DIEGO Hon. Pam Slater, Chairwoman (A) Hon. Greg Cox, Supervisor STATE DEPT. OF TRANSPORTATION (Advisory Member) Jośe Medina, Director (A) Gary Gallegos, District 11 Director U.S. DEPARTMENT OF DEFENSE (Liaison Member) CAPT Tom M. Boothe, USN, CEC Commander, Southwest Division Naval Facilities Engineering Command (A) CAPT Robert Westberg, USN, CEC SAN DIEGO UNIFIED PORT DISTRICT (Advisory Member) Jess Van Deventer, Commissioner SAN DIEGO COUNTY WATER AUTHORITY

(Advisory Member) Frank Chenelle (A) John Fowler TIJUANA/BAJA CALIFORNIA/MEXICO (Advisory Member) Hon. Luis Herrera-Lasso M. Consul General of Mexico Revised March 31, 1999

iiiiiiii

PASSENGER COUNTING PROGRAM System Manual

M A Y 1 9 9 9

San Diego Association of Governments 401 B Street • Suite 800

Telephone 619.595.5300 • Fax 619.595.5305 http://www.sandag.cog.ca.us

iiiiiiiiiiii

ABSTRACT

TITLE: Passenger Counting Program, System Manual

AUTHOR: San Diego Association of Governments

DATE: April 1999

LOCAL PLANNING AGENCY: San Diego Association of Governments

SOURCE OF COPIES: San Diego Association of Governments 401 B Street, Suite 800 San Diego, CA 92101

NUMBER OF PAGES: 108

ABSTRACT: This document provides the system administration and design information necessary to maintain the Passenger Counting Program and related utilities. It documents the database schema, metadata, input/output files, operating requirements, program design and software components.

Table of Contents

INTRODUCTION..................................... 1

HISTORY................................................... 1 PURPOSE................................................... 2 INTRODUCTION TO PASSENGER COUNTING................................................................. 3

Sampling Procedure ............................. 3 Preparations for Counting.................... 3 Selecting Trips to Count ....................... 3 Scheduling Counts ................................ 3 Counting Passengers ............................ 4 Processing Count Information.............. 4 Output ................................................... 6

FUTURE DIRECTIONS ................................ 7

TECHNICAL DESCRIPTION................ 1

SYSTEM DESCRIPTION .............................. 1 System Name......................................... 1 Risk Factors.......................................... 2 System Level Use Case Diagram.......... 3 Architecture .......................................... 4 Subsystem Descriptions ........................ 5

USE CASES ............................................... 6 Use Case 1 ............................................ 6

Actors ...................................................... 6 Priority..................................................... 6 Status ....................................................... 6 Preconditions ........................................... 6 Postconditions.......................................... 6 Extension Points ...................................... 6 “Used” Use Cases .................................... 6 Flow of Events......................................... 6 Activity Diagram ..................................... 6 User Interface........................................... 6 Secondary Senarios.................................. 6 Sequence Diagrams.................................. 6 Subordinate Use Cases............................. 6 View of Participating Use Cases.............. 6 Other Artifacts ......................................... 6 Other Requirements ................................. 6

Secondary Use Cases............................ 6

DATABASE DESCRIPTION .................. 8

OVERVIEW................................................ 8 Stop Inventory Tables ........................... 8 Count Tables......................................... 9

TABLES................................................... 10

ALPHA_CODE ...................................11 Storage Structure.................................... 11 Source Notes .......................................... 11 Secondary Indices .................................. 11

ERROR_MESSAGES ..........................12 Storage structure .................................... 12 Source Notes .......................................... 12 Secondary Indices .................................. 12

NUM _CODE......................................13 Storage structure .................................... 13 Source Notes .......................................... 13 Secondary Indices .................................. 13

RAW_ROUTE .....................................14 Storage structure .................................... 14 Source Notes .......................................... 14 Secondary Indices .................................. 15

RAW_STOP ..........................................16 Storage structure.................................16 Source Notes .......................................16 Secondary Indices ...............................17

ROUTE ..................................................18 Storage structure.................................18 Source Notes .......................................18 Secondary Indices ...............................18

ROUTE_COUNT...................................19 Storage structure.................................19 Source Notes .......................................19 Secondary Indices ...............................19

ROUTE_STOP ......................................20 Storage structure.................................20 Source Notes .......................................20 Secondary Indices ...............................20

RPTMENU ............................................21 Storage structure.................................21 Source Notes .......................................21 Secondary Indices ...............................21

SANDAG_2_TO_STOP_NUM.............22 Storage structure.................................22 Source Notes .......................................22 Secondary Indices ...............................22

SECTION15_DATA..............................23 Storage structure.................................23 Source Notes .......................................23 Secondary Indices ...............................23

STOP_COUNT ......................................24 Storage structure.................................24

Source Notes....................................... 24 Secondary Indices............................... 24

STOP_DISTANCE................................ 25 Storage structure ................................ 25 Source Notes....................................... 25 Secondary Indices............................... 25

STOP_INV ............................................ 26 Storage structure ................................ 27 Source Notes....................................... 27 Secondary Indices............................... 27

VEHICLE .............................................. 28 Storage structure ................................ 28 Source Notes....................................... 28 Secondary Indices............................... 28

YEAR_END_DATA ............................. 29 Storage structure ................................ 29 Source Notes....................................... 29 Secondary Indices............................... 29

PCP PROGRAM....................................... 1

INTRODUCTION ................................... 1 PROGRAMMING................................... 1 NOMENCLATURE ................................ 2 GLOSSARY OF PCP TERMS ....................... 2 SYSTEM COMPONENTS ............................. 4

System Components by Component Name..................................................... 4 PCP Components by Component Type.6

BUILDING AND RUNNING IMAGES ............ 7

DATA LOAD PROGRAM....................... 1

BUILDING THE PROGRAM ......................... 1 RUNNING THE PROGRAM .......................... 1

OUTPUT PRODUCTS & REPORTS..... 1

ROUTE REPORTS....................................... 1 YEAR END REPORTS................................. 2

SUPPORT PROGRAMS.......................... 1

ARCHIVE AND RESTORE PROGRAMS......... 1 Archive_Counter................................... 1 Restore_Counter................................... 1

DATABASE MAINTENANCE PROGRAMS .... 1 Audit_Counter ...................................... 1 Optimize_counter.................................. 1

Introduction The Passenger Counting Program provides ridership and other performance data to the region's fixed-route transit operators. There are currently eight fixed-route transit operators providing service in the San Diego region:

1. San Diego Transit Corporation (SDTC),

2. North County Transit District (NCTD),

3. Chula Vista Transit (CVT),

4. San Diego County Transit Service (CTS),

5. National City Transit (NCT),

6. MTDB contract Routes (MTDB),

7. San Diego Trolley Inc. (SDTI),

8. San Diego Northern (SDN)

This on-going program updates passenger boardings and alightings by bus stop for each route on an annual basis.

History The Passenger Counting Program (PCP) was begun in 1979 in response to the Urban Mass Transit Administration’s (UMTA) Section 15 requirements. Since then the UMTA has become the Federal Transit Administration (FTA). The original program was written in FORTRAN by Robert Parrot. Various updates were made over a period of 15 years and the software was hosted on a Prime minicomputer at SANDAG. In 1995 the program was totally re-written using a fourth generation object oriented language called OpenROAD coupled to a fully relational database, Ingres.

Chapter

1

2222

Purpose The Passenger Counting Program (PCP) was begun in 1979 in response to the Urban Mass Transit Administration’s (UMTA), now the Federal Transit Administration (FTA), Section 15 requirements. FTA grants federal subsidies to local transit agencies to assist the local transit companies in developing and improving mass transportation facilities, equipment, and systems. SDTC and NCTD are required to report transit operation and performance indicators to FTA in order to receive operating funds under Section 15. The data obtained from the Passenger Counting Program satisfy FTA Section 15 requirements as well as provide all transit companies with information used in planning efforts such as: · Route realignment · On-time performance evaluation · Service frequency evaluation · Facility improvements · Bus stop location Basic information provided in reports includes the number of passengers boarding and alighting at each bus stop, ridership by trip and time of day, and on-time performance at each time point. Calculated data includes the number of passenger and revenue miles, average trip lengths, passenger and revenue minutes, standing and seated capacities, maximum loads, gallons of fuel used, and miles over seated capacity.

Transit Operators

SANDAG

FTA

PCP

Counter DB

Funding

Reports

Funding

Reports

Reports

Schedules, Stop

inventory, Vehicle

informatio

Counters

SchedulesCounts

ArcviewTransit

Operators

SANDAG

FTA

PCP

Counter DB

Funding

Reports

Funding

Reports

Reports

Schedules, Stop

inventory, Vehicle

informatio

Counters

SchedulesCounts

Arcview

3333

Introduction to Passenger Counting Sampling Procedure SANDAG uses an accepted alternative sampling procedure for counting bus routes. Each route is counted once per fiscal year (July 1 - June 30) and the order by which it is counted is randomly selected. At times this is inefficient for the transit operators because they cannot always get data for a particular route when they need it. Special counts may be requested when data for a particular route is needed at a specific time, but data from these special counts are not used in FTA Section 15 reporting. An example of a special count would be in the case of a randomly selected count falling outside the regular school year on a route having a high percentage of student riders, either K-12 or college. In such a case, a special count for planning purposes during the school year could be requested by the transit agency. Due to the large number of regional routes that must be counted, the number of special counts should be kept to a minimum.

Preparations for Counting The individual operators assist SANDAG in maintaining up-to-date schedule, bus stop inventory and other information. SDTC and NCTD provide scheduling information to reflect each new bid implementation; all other operators provide scheduling information upon request. Bus stop inventories are either provided annually or as updated. All operators should update their fleet rosters when adding new vehicles to their fleets. Information provided to SANDAG includes vehicle fleet number, seated capacity, and fuel mileage.

Selecting Trips to Count Counts are made on weekdays and weekends, excluding holidays only. By counting all weekday trips, the counts obtained represent weekday ridership for that time period. Weekend counts are scheduled at the same time the route is randomly selected for weekday counts and are processed separately from the weekday counts. Data collected on weekends are only a sampling of all trips and are used mainly for Section 15 reporting rather than in the transit planning process. A random process is used to select the sample of trips to be counted on weekends.

Scheduling Counts Scheduling for transit passenger counts is done in an Access data base. Trips are selected from scheduling materials provided by the operators with the following information entered into a data table: route number, company, bus yard name, run number, schedule number, how bus is to be met, shift start time, shift end time, number of hours to work, counter name, day of week, date, and whether another counter will be met at mid-route. From this information, a weekly schedule sheet is generated for each counter, as well as labels with the same information for individual daily assignment sheets. A list of weekly assignments is also generated for operators so that dispatchers are notified of all counts taking place.

4444

Counting Passengers Once a route is selected for counting, all scheduled trips appearing in the public timetable for that route are counted. Tripper buses, which are either used to provide extra capacity for regularly scheduled trips or special service for schools and industry, are not counted. Depending on the level of service provided, some routes can be counted in a day, while others might take several days or weeks to count all scheduled trips of a route. San Diego Trolley counts typically take more than three months to accomplish. When counting smaller routes, the shifts should be spread over a two to four week period to get a more average representation of the route. Processing Count Information Figure 1 shows the general structure of work flow in the passenger counting program. Passenger counting on the selected trips is done by two methods. Data may be entered directly into a TELXON electronic data collection device, or it may be manually recorded on a form for keypunch data entry. The information collected in the field is processed for each route individually. When the data from both sources, TELXON and paper, has been properly formatted, it is loaded in an INGRES database. Here the data may be validated for completeness with time points checked for accuracy. After all corrections have been made, the trip data is passed to a “validated table” where it may be accessed by the INGRES report writer. Reports may be produced for individual routes and for entire companies.

5555

Passenger Counting Program Processing

Update Counter Stop Inventory (in Excel)

Schedule Work for Counters

Obtain Schedules from Operators

Count Route(s)

Update Stop Inventory STOPS and VEHICLES

(Access ArcView, if necessary)

PAPER: (Data Entry)

TELXON: (Conversion)

Load into Counter DB (RAW_COUNT)

Validation

Route Analysis and Reporting

Output to Screen, File, or Printer

End of Year Processing

PCP Program Archive Fiscal Year

Counts

Reports to Transit Operators & FTA

6666

Output Prior to generating output reports, the following input parameters must be current and accurate: · Current bus stop inventory, including: Bus stop location codes GIS attributes Direction of bus at bus stop Mileage between bus stops Direction of travel · Current route schedule information · Coach seating capacity and vehicle miles per gallon The input parameters are combined with boardings/alightings and timepoint data to produce the following reports for operators: Report 1 Route Summary of boardings, alightings, maximum load, and

bus capacities by terminal time and direction. Daily boardings and alightings, average passengers per trip, average maximum load, and peak load factor by direction and daily total.

Report 2 Bus Route Profile shown graphically displaying maximum load by trip and direction.

Report 2A Rail Route Profile shown graphically displaying maximum load by trip and direction

Report 3 Trip Summary reporting starting terminal location, total passengers, most active bus stops, maximum load and maximum load point.

Report 4 Boardings, alightings, on-boards and thrus, by bus stop for the following time periods: Daily Total, AM (6:00 - 8:59), Midday (9:00 - 14:59), PM (15:00 - 17:59), and Other (18:00 – 5:59). Summarizes by direction and daily total for total passengers, passenger miles, average trip lenth, revenue miles, passengers per revenue mile, miles over capacity, and percent over capacity.

Report 4A Boardings, alightings, on-boards, thrus, number above seated capacity, and miles above seated capacity by bus stop for each scheduled trip. Provides trip summation of boardings and alightings, passengers carried over from the previous trip, passenger miles, average trip lenth, revenue miles, passengers per revenue mile, percent over capacity, seated capacity miles, and total capacity miles.

Report 4E This report is in tab delimited format for use in exporting to either a spreadsheet or database. Trip by trip data is provided by date of count, bus stop name, X geographic coordinate, Y geographic coordinate, boardings, alightings, on-boards, thrus, number above seated capacity, and miles above seated.

7777

Report 5 On time Summary for each trip reporting schedule adherence at each time point.

Report 5A On time Summary for all trips sorted by direction and time period listing percent more than five minutes slow or departing time points early. A summation of total actual run time, trips counted, and passengers per revenue hour is provided.

Report 5B On time Summary for each trip listing scheduled time of time points along with actual arrival and departure times.

Report 6 FTA Section 15 statistics for route by time period. · Two additional reports, the bus stop inventory field listing and the bus stop inventory dump, are used by SANDAG for maintenance purposes. Year end reports available to each operator include: · On-off bus stop report This report can be generated with any number of operators’ data and may

be sorted by trip-ends, ons, offs, alphabetically, or by jurisdiction (alphabetically).

· System daily profile for weekday, Saturday, or Sunday for any number of operators.

· FTA Section 15 Report · ArcView Analysis Data for use in ArcView applications for planning purposes.

Future Directions The Passenger Counting Program is constantly evolving to meet the needs of transit operators. The next major enhancement will be the publication of counter information on the Internet.

P A S S E N G E R C O U N T I N G P R O G R A M S Y S T E M M A N U A L

1111

Technical Description

System Description System Definition The Passenger Counting Program actually has two possible definitions. The first is the entire SANDAG “program” for passenger counting and the second being the software based “program”. The elements of the SANDAG “program” are described in the following section for informational purposes. All other references to the Passenger Counting Program in this document refer to the software based “program”.

SANDAG Program The SANDAG “program” covers all aspects of passenger counting including:

• Hiring and management of passenger counting staff

• Supporting transit operators in the selection of stops

• Maintenance of transit stop information in conjunction with the transit operators

• Scheduling routes for counts

• Scheduling counter staff to perform counts

• Collection and validation of count information

• Analyzing and reporting the results of passenger counts to the transit operators

• Analyzing and reporting the results of passenger counts to local, state and federal agencies

• Providing passenger count information in response to public requests

• Maintenance and storage of passenger count information for historical analysis

• Assist transit operators in the optimization of transit resource utilization

• Assisting various public and private organizations in planning and developing transit systems to meet the needs of the San Diego region

Chapter

2


2222

Software Program The software “program” covers the following aspects from taken from the broader list above:

• Maintenance of transit stop information in conjunction with the transit operators

• Loading and validation of count information

• Analyzing and reporting the results of passenger counts to the transit operators

• Analyzing and reporting the results of passenger counts to local, state and federal agencies

• Providing passenger count information in response to public requests

• Maintenance and storage of passenger count information for historical analysis

Some of the analysis and reporting functions, specifically those incorporating the use of Arcview, are not currently detailed as part of the software “program” documentation. Some information is provided to guide the PCP system administrator in identifying the interfaces and needs of these activities.

Risk Factors The risk factors associated with the passenger counting program, listed in priority order are:

• The lack of passenger counting data may result in transit systems that do not address the needs of the community

• Inaccurate passenger counting data may result in the misuse of scarce transit operating funds

• Count information is collected using low wage staff and is subject to human error

• Failure of the validation process to catch errors early in the processing of data can result in costly remedial measures later

• Historical information must be maintained to provide for the analysis of transit utilization trends


3333

System Level Use Case Diagram

System

PCP Manager

Transit Operators

«uses»

LoginMaintain Stop

Inventory

Maintain RouteInventory

Load Raw CountInformation

Validate Count

Run Reports

«uses»

«uses»

«uses»

«uses»

«uses»

MaintainDictionary«uses»

«uses»


4444

Architecture

«subsystem»Database

«subsystem»Load Raw Count

«subsystem»OpenROAD PCP Program

«utility»Archive/Restore

«utility»Audit_counter

«utility»Optimize_counter


5555

Subsystem Descriptions The Passenger Counting Program consists of five subsystems; data load, validation, reporting, archive/restore and database. These subsystems are described in the sections that follow.

Count Data Load Subsystem This subsystem loads raw count information into the database performing some correcting of errors when possible.

Validation Subsystem This subsystem assists the staff in the validation of count information

Report Subsystem This subsystem provides for the generation of various reports on passenger ridership and transit utilitization.

Stop Inventory Subsystem This subsystem assists staff in maintaining an accurate inventory of transit stop information.

Route Inventory Subsystem This subsystem assists staff in maintaining an accurate inventory of transit routes and the stops they incorporate.

Vehicle Inventory Subsystem This subsystem assists staff in maintaining an accurate inventory of transit operator vehicle information necessary for capacity and fuel use analysis.

Dictionary Subsystem This subsystem assists staff in maintaining information on the codes, abbreviations and terms used in the passenger counting process.

Archive/Restore Subsystem This subsystem archives passenger count information for those fiscal years that are not needed on a regular basis and provides for the restoration of the data to the database when necessary.

Database Subsystem The database system maintains the count information and serves it to various subsystems and needed.


6666

Use Cases

Primary Use Case Actors Priority Status Preconditions Postconditions Extension Points “Used” Use Cases Flow of Events Activity Diagram User Interface Secondary Senarios Sequence Diagrams Subordinate Use Cases View of Participating Use Cases Other Artifacts Other Requirements

Secondary Use Case 1 Actors Priority Status Preconditions Postconditions Extension Points “Used” Use Cases Flow of Events Activity Diagram User Interface Secondary Senarios Sequence Diagrams Subordinate Use Cases View of Participating Use Cases Other Artifacts

Other Requirements


7777


8888

Database Description

Overview Stop Inventory Tables The entity relation diagram below shows the relationships between the tables used for storing count information.

Chapter

3

U1U1U1U1U1

PK

company_numroute_numvariationdirectionfiscal_yearroute_descriptionlast_editedit_by

route_key

route

FK2

PK,FK1PK

stop_keystop_typetime_pointstop_numdistancelast_editedit_by

route_keystop_sequence

route_stop

I1

PK

company_numstop_keycensus_tractplace_numintersectionblockstreet_flagstreet_1street_2old_streetxyada_codebenchsheltereffective_dateend_datelast_editedit_by

stop_num

Stop_Inv


9999

Count Tables The entity relation diagram below shows the relationships between the tables used for storing count information.

FK1,I1

PK,FK1PK

route_keystop_numoffsonscarryoversonboardarrival_timedeparture_timedetour_stoptime_pointsched_arrival_timesched_departure_timepagedistance

set_keystop_sequence

stop_count

U1U1U1U1U1

PK

company_numroute_numvariationdirectionfiscal_yearroute_descriptionlast_editedit_by

route_key

route

I1

FK1

PKPK

set_keyedit_statusroute_keyroute_numvariationdirectionday_codeschedule_idcounter_numvehicle_numsched_start_timesched_finish_time

company_numraw_date

raw_route

FK1FK1

PKPK

orig_recnumstop_numoffsonscarryoversarrival_timedeparture_timedetour_stoptime_pointsched_arrival_timesched_departure_timepagecompany_numraw_date

set_keystop_sequence

raw_stop

PK,I1PK,FK1

date_countedschedule_idcounter_numvehicle_numsched_start_timesched_finish_timeday_codereport_omitlast_editedit_bytime_periodtrip_milestrip_minutespassenger_milesmiles_over_capacitytotal_onstotal_onboard

set_keyroute_key

route_count

PKPKPKPK

ndaysntrips

fiscal_yearcompany_numday_codetime_period

section15_data

PKPK

vehicle_typepropulsion_typecapacitympglast_editedit_by

company_numvehicle_num

vehicle

PKPKPKPKPK

date_countedntripstotal_passengersrevenue_milespassenger_milestrip_minutespassenger_minutesseat_milesfuel_consumptionpassengers_on_boardlast_edit

fiscal_yearcompany_numroute_numday_codetime_period

year_end_data


10101010

Tables The following provides a brief description of the current database schema. This design is based on the original Counter program on the Prime with modifications to normalize the database and incorporate improvements requested by Mark. The current 16 production tables are:

Table Description alpha_code Table of alphanumeric codes used by the program error_messages Table of error messages used during the editing process num_code Table of numeric codes used by the program raw_route Raw route information awaiting or in the process of editing raw_stop Raw stop information awaiting or in the process of editing route General information for each route route_count Count information relative to a specific route route_stop The stops for a given route rptmenu Information for reports menu sandag_2_to_stop_num SANDAG stop number to transit operator stop number cross reference section15_data Data provided by transit companies for Section 15 reports stop_count Count information relative to a specific stop stop_distance Stores distances between adjacent stops stop_inv The stop_inv table contains one row for each physical transit stop vehicle Transit vehicle information year_end_data Stores summarized data for year-end reports.


11111111

ALPHA_CODE Lookup table for various alphanumeric codes. As of 12-17-96 the column names were ada_code, bench, block, shelter and vehicle type. Column Name Key Data Type Null Default Source Description column_name 1 varchar(32) No No 1 Name of column to which code applies alpha_code 2 char(10) No No 2 Alphanumeric code definition varchar(36) No No 2 Definition of code old_code integer2 No Yes 3 Value for code in old (Prime) system last_edit date No Yes 4 Date last edited. edit_by char(12) No Yes 4 Username of person who last edited this row.

Storage Structure

btree unique

Source Notes 1. Loaded upon table creation from archive information or automatically when a new row is added by the user using the

OpenRoad application.

2. Loaded upon table creation from archive information or when added by the user using the OpenRoad application.

3. Loaded upon table creation from archive information. Field is blank when a row is added by the user using the OpenRoad application.

4. Set automatically when the row is entered or changed.

Secondary Indices None


12121212

ERROR_MESSAGES This table contains the error messages used when editing stop counts. This is a static lookup table and should be set to use a 100% fill factor.

Column Name

Key Data Type Null Default Source Description

err_no 1 integer2 No Yes 1 Error number in EditCounts frame msg varchar(100) No Yes 1 Error message for EditCounts frame error number

Storage structure ISAM unique

Source Notes 1. Loaded upon table creation from an error message list for the OpenRoad application. This table may be updated to

contain additional error messages as needed by the application in the future. Such updates will be made manually by the system developer(s).



13131313

NUM _CODE Lookup table for various numeric codes.

Column Name Key Data Type Null Default Source Description column_name 1 varchar(32) No No 1 Name of column to which code applies num_code 2 integer2 No No 2 Numeric code definition varchar(36) No No 2 Definition of code incorporated char(1) No Yes 2 Incorporation flag (Y or N). This field is used

only when column_name is “place”. start_range integer4 Yes Null 2 Starting range of stop numbers for this

company. Stop numbers will be unique across companies and each company's stop numbers will be within this specified range. This field is used only when column_name is “company”.

end_range integer4 Yes Null 2 End of stop number range for this company. This field is used only when column_name is “company”.

last_edit date No Yes 3 Date last edited. edit_by char(12) No Yes 3 Username of person who last edited this row.

Storage structure BTREE unique

Source Notes 1. Loaded upon table creation from archive information or automatically when a new row is added by the user using the

OpenRoad application.

2. Loaded upon table creation from archive information or when added by the user using the OpenRoad application.

3. Set automatically when the row is entered or changed.



14141414

RAW_ROUTE When a count is initially loaded into the database the general route information is placed in the table raw_route for editing. Once the data has been validated it is moved to the route_count table.

Column Name Key Data Type Null Default Source Description set_key integer4 No No 1 A unique internal surrogate key identifying a

specific set of count (trip) information. This key is used to relate the raw_route and raw_stop tables that contain the raw trip information.

edit_status char(3) Yes Null 2 The status code of the editing process for this route record. Valid codes are: NEW = Information has been loaded but no validation checks have been performed INV = The editing process has begun on the data and errors have been found VAL = The information passes validation and is ready to be moved to route_count

route_key integer4 No Yes 3 A unique internal surrogate key identifying a specific route. This key is used to relate the raw_route and route tables.

company_num 1 integer2 No Yes 4 Transit company code. See company in the num_code table.

route_num integer2 No Yes 4 The transit company route number. This number is assigned by the transit company operator

variation char(1) No Yes 5 A single character suffix to the route number identifying a variation to a route.

direction integer2 No Yes 4 The direction code for the route indicating the direction of travel. See direction in num_code table.

raw_date 2 integer4 No Yes 4 The count date as entered by the counter. It is expected to be in the form YYMMDD.

day_code integer2 No Yes 6 An indicator of the day of the week the count was performed. (1=Sunday, etc.).

schedule_id char(5) No Yes 4 The schedule number of the specific transit run. This field may include alpha characers.

counter_num integer2 No Yes 4 The ID number of the counter performing the count (trip)

vehicle_num integer2 No Yes 4 The vehicle identification number assigned by the transit company.

sched_start_time integer2 Yes Null 4 The scheduled start time for the count (trip) sched_finish_time integer2 Yes Null 4 The scheduled finish time for the count (trip)

Storage structure BTREE

Source Notes 1. Set automatically by the lrc (load_raw_count) program when the data is loaded by adding one to the highest set_key

value found in raw_route and route_count.

2. Set automatically to “NEW” by the lrc (load_raw_count) program when the data is loaded. The edit_status field is changed to “INV” once the user has begun editing the data. After the data has passed all validation checks and the user clicks on the “Store Valid” button, the field is changed to “VAL”. Since the information for the count (trip) is automatically transferred to the route_count table after the “Store Valid” button is clicked, no rows should be in the raw_route table with such a status.


15151515

3. Set automatically by the lrc (load_raw_count) program when the data is loaded by looking up the company/.route_num in the route table

4. Loaded from a raw count (trip) data file by the lrc (load_raw_count) program.

5. Set by the user during the validation process.

6. Set automatically by the lrc (load_raw_count) program when the data is loaded based on the contents of raw_date.

Secondary Indices raw_route_index_1 hash on set_key


16161616

RAW_STOP When a count is initially loaded into the database the general route information is placed in the table raw_stop for editing. Once the data has been validated it is moved to the stop_count table. Column Name Key Data Type Null Default Source Description set_key 1 integer4 No No 1 A unique internal surrogate key identifying

a specific set of count (trip) information. stop_sequence 2 integer2 No Yes 2 The transit operator stop number for the

route. stop_num integer4 No Yes 3 Stop identification number. This is the

unique internal surrogate key used to map the route stop to the physical stop information in the stop_inv table

offs integer2 No Yes 2 The number of people getting off at the stop

ons integer2 No Yes 2 The number of people getting on at the stop

carryovers integer2 No Yes 2 The number of people already on the transit vehicle from a prior route. This is always zero except for the first stop.

arrival_time integer2 Yes Null 2 The time the transit vehicle arrived at the stop

departure_time integer2 Yes Null 2 The time the transit vehicle departed from the stop

detour_stop char(1) No Yes 2 A flag indicating whether this stop was a detour. Y = It is a detour stop, N or blank = it is not a detour stop.

time_point char(1) No Yes 2 Indicates if the stop is a time point for counters

sched_arrival_time integer2 Yes Null 2 The scheduled arrival time at this stop. (Not currently used).

sched_departure_time integer2 Yes Null 2 The scheduled departure time from this stop.

page integer2 No Yes 2 The count form page number (Has a value of 99 entry was made using a Telxon).

orig_recnum Integer2 No Yes 4 This field records the original sequence of the records read in from the raw data file. This information is used to sort the count records in their original order during validation processing to more easily detect certain errors.

Storage structure BTREE Source Notes 1. Set automatically by the lrc (load_raw_count) program when the data is loaded by adding one to the highest

set_key value found in raw_route and route_count. 2. Loaded from a raw count (trip) data file by the lrc (load_raw_count) program. 3. Set automatically by the lrc (load_raw_count) program when the data is loaded based on the route and

stop_sequence. 4. Set automatically by the lrc (load_raw_count) program when the data is loaded recording the original order of

the records read.


17171717



18181818

ROUTE The general information for each route is stored in the route table. There are currently 98 distinct routes in the Bus Stop Inventory for 1995 (subject to additional editing). Column Name Key Data Type Null Default Source Description route_key 1 integer4 No No 1 A unique internal surrogate key identifying a

specific route. company_num integer2 No No 2 Transit company code. route_num integer2 No No 2 The transit company route number variation char(1) No No 2 A single character suffix to the route

number identifying a variation to a route. direction integer2 No No 2 The direction code for the route fiscal_year integer2 No No 2 The fiscal year during which this Route is

valid. route_description varchar(10

) No No 2 A description of the route. Example: '6A' is

the route_description for route_num 6, variation A.

last_edit date No Yes 3 Date stop information last edited edit_by char(12) No Yes 3 User name of person who last edited the

stop information

Storage structure BTREE unique. Source Notes 1. Set automatically by adding one to the highest route_key value found in route. 2. Loaded from original counter Program data. At the beginning of a new fiscal year the prior year’s route

information is copied in to “seed” the route table for the new fiscal year. 3. Set automatically when the row is entered or changed. Secondary Indices route_index_1 on company_num, route_num, variation, direction, fiscal_year


19191919

ROUTE_COUNT The stop_count table contains count (trip) information relative to a specific route.

Column Name Key Data Type Null Default Source Description set_key 2 integer4 No No 1 Surrogate key for associating stops to a

trip route_key 1 integer4 No No 1 A unique internal surrogate key

identifying a specific route. date_counted date No No 1 Date of count for route schedule_id char(5) No No 1 The schedule number of the specific

transit run counter_num integer2 No No 1 The ID number of the counter

performing the count vehicle_num integer2 No No 1 The vehicle identification number sched_start_time integer2 Yes Null 1 The scheduled start time for the count

(aka Terminal Time) sched_finish_time integer2 Yes Null 1 The scheduled finish time for the count day_code integer2 No Yes 1 An indicator of the day of the week the

count was performed (Sun=1 . . . Sat=7)

report_omit integer2 No Yes 2 Omit from reports flag. 1 = omit from reports; 0 = include

last_edit date No Yes 3 Date stop information last edited edit_by char(12) No Yes 3 User name of person who last edited

the stop information time_period integer2 No Yes 4 Time period for reports. Redundant,

but will improve report performance 1=AM (0600-0859), 2=Mid (0900-1459), 3=PM (1500-1759), 4=Other (1800-0559)

trip_miles float8 No Yes 4 Distance from first stop to last. Redundant, but will improve report performance

trip_minutes integer4 No Yes 4 Time between scheduled start time & scheduled finish time. Redundant.

passenger_miles float8 No Yes 4 Sum over all stops (onboard * distance from previous stop). Redundant

miles_over_capacity float8 No Yes 4 Miles bus traveled with onboard > capacity. Not currently used

total_ons integer4 No Yes 4 Total number of passengers boarding this trip. Redundant, for performance

total_onboard integer4 No Yes 4 Sum(onboard) for this trip. Redundant, but will improve report performance

Storage structure BTREE unique. Source Notes 1. Transferred from raw_count when the data is moved over after validation. 2. Set by user using the OpenRoad Counter application program. 3. Set automatically when the row is entered or changed. 4. Calculated by the OpenRoad Counter application program when the data is brought over from raw_count. Secondary Indices route_count_index_1 btree on set_key


20202020

ROUTE_STOP The stops for a given route are stored in the route_stop table. There are currently 1,871 distinct route stops in the 1995 Bus Stop Inventory (subject to additional editing). Column Name Key Data Type Null Default Source Description route_key 1 integer4 No No 1 A unique internal identifier for the specific

route. stop_key integer4 No Yes 2 A unique internal surrogate key identifying

a specific physical stop. stop_sequence 2 integer2 No No 2 The transit operator stop number for the

route. stop_type char(1) No No 2 Indicates whether this is a regular or special

stop. Stop types are R=regular, D=detour, T=Transfer. See column stop_type in table alpha_code.

Time_point char(1) No Yes 2 Indicates if the stop is a time point for counters

stop_num integer4 No No 2 The internal unique stop identifier used to link the route stop information with physical stop information contained in the stop_inv table.

Distance float8 No No 2 The distance between to this stop from the previous stop. The unit of measurement varies depending on the transit company although it is stored here in miles. The user should be allowed user to convert to different units of measure on request

last_edit date No Yes 3 Date stop information last edited edit_by char(12) No Yes 3 User name of person who last edited the

stop information

Storage structure BTREE unique. Source Notes 1. Set automatically by adding one to the highest route_key value found in route. 2. Loaded from original counter Program data. At the beginning of a new fiscal year the prior year’s route

information is copied in to “seed” the route table for the new fiscal year. 3. Set automatically when the row is entered or changed. Secondary Indices None


21212121

RPTMENU Information for reports menu. Column Name Key Data Type Null Default Source Description called_by 1 varchar(32) No Yes 1 Name of frame in which this report option

appears sequence_no 2 integer2 No Yes 1 Order in which items appear on report

menu report_name varchar(32) No Yes 1 Name of frame/procedure to call or report

to run object_type char(1) No Yes 1 Type of object to call. (R=report, F=frame,

P=4GL procedure, S=system call, X=not yet implemented)

report_id varchar(6) No Yes 1 print_params varchar(10) No Yes 1 The parameters that are passed to the

Postscript formatter menu_text varchar(32) No Yes 1 Text to appear on menu options list to

describe a report parameters varchar(256) No Yes 1 Parameters needed by report. Example:

for system call, the command line text; for report, passed parameters

Storage structure ISAM unique. This is a static table and a high fill factor should be used. Source Notes 1. This table is loaded when the OpenRoad application is installed. It contains information on all the reports that

can be generated by the application. The table contains information for populating report menus, running the reports and controlling printed output. This table may be updated to contain additional reports as needed by the application in the future. Such updates will be made manually by the system developer(s).



22222222

SANDAG_2_TO_STOP_NUM This table contains a cross-reference between the stop numbers used by SANDAG and those used by the various transit operators. The information was originally bulk loaded from information received from the operators. Updates can be made using the PCP OpenROAD program.

Column Name Key Data Type Null Default Source Description company_num 1 integer2 No No 1 Transit company code sandag_stop_num 2 Integer4 No No 1 SANDAG stop number transit_oper_stop_num Integer4 No No 1 Transit operator stop number

Storage structure BTREE unique. Source Notes 1. Entered by the user from information provided by the transit operators. Secondary Indices None


23232323

SECTION15_DATA Data provided by transit companies for Section 15 reports. Use QBF to enter data.

Column Name Key Data Type Null Default Source Description fiscal_year 1 integer2 No No 1 Fiscal year during which this object is

valid company_num 2 integer2 No No 1 Transit company code day_code 3 integer2 No No 1 Day of week (1=Sunday, etc.) time_period 4 integer2 No No 1 Time period for reports ndays integer2 No No 1 Number of days in the year of this type ntrips integer4 No No 1 Number of trips

Storage structure BTREE unique. Source Notes 2. Entered by the user from information provided by the transit operators. Secondary Indices None


24242424

STOP_COUNT The stop_count table contains validated count (trip) information relative to a specific physical stop.

Column Name Key Data Type

Null Default Source Description

set_key 1 integer4 No No 1 Surrogate key for associating stops to a trip route_key integer4 No No 1 A unique internal identifier for the specific

route. stop_sequence 2 integer2 No No 1 The transit operator stop number for the

route. stop_num integer4 No No 1 Stop identification number. This is the unique

internal key used to map the route stop to the physical stop information in the stop_inv table. Redundant, but stored here for performance

offs integer2 No Yes 1 The number of people getting off at the stop ons integer2 No Yes 1 The number of people getting on at the stop carryovers integer2 No Yes 1 The number of people already on the transit

vehicle from a prior route. onboard integer2 No Yes 1 The number of people on board arrival_time integer2 Yes Null 1 The time the transit vehicle arrived at the stop departure_time integer2 Yes Null 1 The time the transit vehicle departed from the

stop detour_stop char(1) No Null 1 A flag indicating whether this stop was a

detour time_point char(1) No Yes 1 Indicates if the stop is a time point for

counters. Redundant, but stored here for performance

sched_arrival_time integer2 Yes Null 1 The scheduled arrival time sched_departure_time integer2 Yes Null 1 The scheduled departure time page integer2 No Yes 1 The count form page number (not used if

entry was made using a Telxon). distance float8 No Yes 1 Distance in miles between previous stop and

this one. Redundant, but will improve report performance

Storage structure BTREE unique. Source Notes 1. Transferred from raw_stop when the data is moved over after validation. Secondary Indices Stop_count_index_1 btree on route_key


25252525

STOP_DISTANCE Stores distances between adjacent stops Column Name

Key Data Type

Null Default Source Description

stop1_num 1 integer4 No No 1 First stop number stop2_num 2 integer4 No No 1 Second stop number distance float8 No No 1 Distance in miles between previous stop

and this one Storage structure BTREE unique. Source Notes 1. Entered by the user from information provided by the transit operators. Secondary Indices None


26262626

STOP_INV The stop_inv table contains one row for each physical transit stop. The current Bus Stop Inventory being used for 1995 contains 7,585 unique stops (subject to additional editing).: Column Name Key Data Type Null Default Source Description company_num integer2 No No 1 Transit company code. There has

been considerable discussion regarding whether the stop inventory should be relative to all physical stops regardless of transit company or by transit company. For now the inventory is kept by transit company number although this may change in a future version.

Stop_key integer4 No Yes A unique internal surrogate key identifying a specific physical stop.

stop_num 1 integer4 No No 2 Stop identification number. This is not the bus stop number used by the transit companies but rather a unique stop identifier used internally by the counter program.

census_tract integer4 No No 1 Census tract number Place_num integer2 No No 1 Census place code intersection char(1) No No 1 Stop location relative to intersection

(1 thru 8 or A thru G) block char(1) No No 1 Stop location relative to block (N,

M or F) street_flag char(1) No No 1 Street flag which contains a plus (+)

sign when only street 1 is used. This is a carry over from the Prime implementation and may be dropped in a future version.

street_1 varchar(30) No No 1 First street name street_2 varchar(30) No Yes 1 Second street name old_street varchar(31) No Yes 1 Original street name from the

Prime system. This is retained for historical purposes until the extraction into first and second street names is verified. This field will be dropped in a future version. This field was used in the transition to Ingres and is now obsolete.

x integer4 No No 1 X state place coordinate y integer4 No No 1 Y state place coordinate ada_code char(1) No No 1 ADA accessibility (A= Accessible,

U= Upgradable, N= Not Upgradable). The original Prime


27272727

version used 1, 2 & 3 for accessible, upgradable and not upgradable respectively.

bench char(1) No Yes 1 Bench (contains a B if there is a bench otherwise blank)

shelter char(1) No Yes 1 Shelter (contains an S if there is a shelter otherwise blank). The original Prime system used 1 for shelter and 2 for no shelter).

effective_date date No Yes 1 Date the stop became active end_date date No Yes 1 Date the stop becomes inactive last_edit date No Yes 3 Date stop information last edited edit_by char(12) No Yes 3 User name of person who last

edited the stop information Storage structure BTREE unique. Source Notes 1. Set automatically by adding one to the highest stop_num value found in stop_inv. 2. Loaded from original counter Program data after extensive edits to remove duplicate and ambiguous data. 3. Set automatically when the row is entered or changed. Secondary Indices Stop_inv_x1on stop_key


28282828

VEHICLE Lookup table for vehicles. One row for each vehicle for each company. Column Name Key Data Type Null Default Source Description company_num 1 integer2 No No 1 Transit company code. Foreign key

(num_code) vehicle_num 2 integer2 No No 1 Vehicle identification number

assigned by transit company vehicle_type char(10) No No 1 Vehicle type. Foreign key

(alpha_code) propulsion_type varchar(4) No Yes 1 Vehicle propulsion type capacity integer2 Yes Null 1 Vehicle capacity mpg float8 Yes Null 1 Miles per gallon of fuel last_edit date No Yes 2 Date vehicle information last editededit_by char(12) No Yes 2 User name of person who last

edited the vehicle information Storage structure BTREE unique. Source Notes 1. Entered by the user from information provided by the transit operators. 2. Set automatically when the row is entered or changed. Secondary Indices None


29292929

YEAR_END_DATA This table stores summarized data for year-end reports. Rows are added when Report 6 (Section 15 Statistics) is run. Column Name Key Data

Type Null Default Source Description

fiscal_year 1 integer2 No No 1 Fiscal year during which this object is valid

company_num 2 integer2 No No 1 Transit company code. Foreign key (num_code)

route_num 3 integer2 No No 1 Route number assigned by the transit company

day_code 4 integer2 No No 2 Day of week (1=Sunday, 7 for Saturday, 9 for week days)

time_period 5 integer2 No No 1 Time periods for reports date_counted date No No 1 Date count was made (first count

for route & direction) ntrips integer2 No No 1 Number of trips in sample total_passengers integer4 No No Sum(total_ons) revenue_miles float8 No No Sum(trip_miles) passenger_miles float8 No No 1 Sum over all stops, all trips

(onboard * distance from previous stop)

trip_minutes integer4 No No 1 Passenger_miles*trip_minutes/revenue_miles

passenger_minutes integer4 No No 1 Sum(passenger_miles*trip_minutes/trip_miles)

seat_miles float8 No No 1 Sum(distance*capacity) fuel_consumption float8 No No 1 revenue_miles/mpg passengers_on_board

integer4 No No 1 Sum(onboard)

last_edit date No No 3 Date vehicle information last editededit_by char(12) No No 3 User name of person who last

edited the vehicle information Storage structure BTREE unique. Source Notes 1. When Report 6 is run, information for the fiscal year, company and route specified for the report is

loaded into the year_end_data table. Any previous information for that fiscal year, company and route is deleted. The information is selected from the route, route_count and vehicle tables.

2. The day of the week value is altered from the original Sunday=1, Monday=2, Tuesday=3, etc. sequence, when the information is loaded by Report 6 to the values specified above. This is necessary to facilitate selection and sorting for year-end reports.

3. Set automatically when the row is entered or changed. Secondary Indices None


1111

PCP Program

INTRODUCTION This chapter provides general programming information for the Passenger Counter Program (PCP. The discussion covers the current program organization and operation, and provides inforamtion to assist in making changes to source code and in the preparation of an operational system. Additional technical information describing the various relationships and equations is provided. Detailed program documentation is provided in each source file as described below. Furthermore, much of what is discussed here may be described in more detail in database section of this document, which contains the detailed database formats and organization for the input and output data discussed in each section.

PROGRAMMING The PCP system is an Ingres relational database application, coded primarily in the Ingres object-oriented, fourth-generation programming language (4GL) OpenRoad. An OpenRoad application is a custom-designed user interface that provides access to a database to retrieve, maintain, and report on data. It consists of program code and a variety of input screens and displays called frames. Each frame may have associated executable scripts, reports, global variables and user-defined data classes and procedures.

Each of the components of PCP is referred to as an object. Many of the PCP objects, in particular, those objects that relate specifically to database actions, are physically stored in the formal Ingres counter database. The OpenRoad programming environment manages these components of PCP and maintains strict program version control and configuration for objects written in the OpenRoad 4GL. Other PCP objects, including Structured Query Language (SQL) scripts and ASCII files. They are maintained in a more traditional manner and require some programmer responsibilities for ensuring proper version control and management.

Because of some formatting (fonts and pitch) restrictions within the OpenRoad reporting capabilities, the formal reports from PCP can be output in plain text and Postscript. The later case is provided by invoking a special Postscript formating program. These reports and queries, can also be thought of as objects.

Nominally, Ingres OpenRoad applications are platform independent; they may be run from either the UNIX enviromnent or from a suitably equipped PC running Microsoft Windows 3.1, Windows 95/98 or Windows NT/2000. Platform differences in display fonts and resolution, however, limit the practical application of device-independent applications. This version of PCP was developed for the Windows NT environment. The

Chapter

4


2222

underlying Ingres database is Counter. A PC platform running the PCP application must have the following software installed:

• Ingres Net software (A CA-Ingres product)

• Ingres OpenRoad runtime software (A CA-Ingres product)

• Current Ingres ODBC device drivers (A CA-Ingres product produced by Intersolve)

NOMENCLATURE In general, an object's name is descriptive of its use. OpenRoad is case sensitive. Because the code comprising PCP is object oriented and managed by the development software (OpenRoad), most of the scripts, source files, and objects and are stored in the associated databases. This obviates traditional path names. For editing convenience, a set of source files is retained in a development directory. In the following text, object names and, where necessary, file names, are listed in italics.

Glossary of PCP Terms The various objects in the PCP system are defined in the glossary below.

Component Description ASCII files Text files containing data, used for some reports and for bulk loading some Ingres tables. Application The general name for the collection of objects and components that constitute the operational system. Ingres database The principal storage medium for the PCP OpenRoad application and data. A formal Ingres database consists of tables, views, database procedures, indexes and other Ingres objects. Resides on the SANDAG Ingres database server. Events Events are not objects per se, but rather are user or program actions, such as a button clicks, a procedure return, a timer expiring and so on, that trigger some kind of response. Events are used to signal the application that something requires attention and usually demands some action. User Frames Frames are the main building blocks of most applications and are the interface through which users interact with the application. A user frame is usually a form with areas for data input or display, status display, labels and control buttons. Each frame includes a script (OpenRoad 4GL source code) with source code that performs various activities as responses to user events registered by selecting buttons, check boxes or other control devices.


3333

Field Templates Field templates are prototypes from which new fields on a form are built. 4GL Procedures A 4GL procedure (subroutine) is a set of statements written in the 4GL application language that can be called from scripts or other procedures. User Classes A user class is a set of user-defined attributes (characteristics) and methods. An example would be an object that consisted of a variety of data types, grouped together in a single reference. These are similar to a C language structure or a C++ system class. SQL Scripts Structured Query Language code used primarily for building Ingres database tables and loading tables from ASCII data files. 4GL Scripts A script is a set of 4GL code that contains variable definitions for a frame, as well as executable instructions for processing events. Global Variables A value defined across the entire application. This is useftil for arguments such as index limits or table sources that appear in many places and may change values periodically.


4444

System Components System Components by Component Name

Component Name Type Description ChangePrompt Ghost Frame Prompt about clearing or closing before save companies Global Variable Global array of company company User Class For validating company ID CompTimes User Class For comparing 2 times CountDetail User Frame Display complete info for validated or unvalidated counts counter User Class For validating counter_num CountHeader User Class Route count data to display in TopFrame dbaname Global Variable DBA name DictAlpha User Frame Display or maintain alphanumeric codes DictNum User Frame Display or maintain numeric codes DictRoute User Frame Display or maintain stop information DictRStop User Frame Display or maintain stop information DictStop User Frame Display or maintain stop information DictVehicle User Frame Display or maintain dictionary for vehicles direction User Class Direction info Directions Global Variable Global array of directions EditCounts User Frame Edit route counts - no detour stops ErrorMessage User Class Maps to table error_messages ErrorMessages Global Variable Array of ErrorMessage find_string User Frame Popup frame to find stringin a TableField GetDistance 4GL Procedure Get distance between two stops header_script Script Boilerplate for script header HelpFrame User Frame Display text of an ASCII file HelpPath Constant Full path name for help file directory LoadCompanies 4GL Procedure Load data into companies array LookupStop User Frame Display or maintain stop information NaturalRouteKey User Class Attributes that determine route key (for Version 2+) PCP_3_5_00 Application Passenger Counter Program 3.5/00 (05-03-99) RawData User Class Raw integer data, its validation status & error message RawDate User Class For validating date_counted as a number RawRoute User Class Data for editing route counts RawStop User Class For validating stop counts (no detour_stop) Report_file_name 4GL Procedure Builds a report file name ReportParameters User Class Search criteria, output option for reports route User Class Fields from route table routestitch DB Procedure DBproc for stitching two routes together Rpt3 4GL Procedure Generate temp table for trip summary report rptmenu User Class Columns from rptmenu table RptRequest User Frame Route Profile S15Data User Frame Edit Section 15 data


5555

Stop User Class Fields in table stop_inv stop_count User Class Fields for stops array in CountDetail frame TopFrame User Frame Top frame for transit application uname Global Variable User name vehicle User Class For validating vehicle_num & getting capacity YrEndReport User Frame Route Profile


6666

PCP Components by Component Type

Component Name Type Description GetDistance 4GL

Procedure Get distance between two stops

LoadCompanies 4GL Procedure

Load data into companies array

Report_file_name 4GL Procedure

Builds a report file name

Rpt3 4GL Procedure

Generate temp table for trip summary report

PCP_3_5_00 Application Passenger Counter Program 3.5/00 (05-03-99)

HelpPath Constant Full path name for help file directory routestitch DB

Procedure DBproc for stitching two routes together

ChangePrompt Ghost Frame Prompt about clearing or closing before save companies Global

Variable Global array of company

dbaname Global Variable

DBA name

Directions Global Variable

Global array of directions

ErrorMessages Global Variable

Array of ErrorMessage

uname Global Variable

User name

header_script Script Boilerplate for script header company User Class For validating company ID CompTimes User Class For comparing 2 times counter User Class For validating counter_num CountHeader User Class Route count data to display in TopFrame direction User Class Direction info ErrorMessage User Class Maps to table error_messages NaturalRouteKey User Class Attributes that determine route key (for

Version 2+) RawData User Class Raw integer data, its validation status & error

message RawDate User Class For validating date_counted as a number RawRoute User Class Data for editing route counts RawStop User Class For validating stop counts (no detour_stop) ReportParameters User Class Search criteria, output option for reports route User Class Fields from route table rptmenu User Class Columns from rptmenu table Stop User Class Fields in table stop_inv stop_count User Class Fields for stops array in CountDetail frame vehicle User Class For validating vehicle_num & getting capacityCountDetail User Frame Display complete info for validated or

unvalidated counts


7777

DictAlpha User Frame Display or maintain alphanumeric codes DictNum User Frame Display or maintain numeric codes DictRoute User Frame Display or maintain stop information DictRStop User Frame Display or maintain stop information DictStop User Frame Display or maintain stop information DictVehicle User Frame Display or maintain dictionary for vehicles EditCounts User Frame Edit route counts - no detour stops find_string User Frame Popup frame to find stringin a TableField HelpFrame User Frame Display text of an ASCII file LookupStop User Frame Display or maintain stop information RptRequest User Frame Route Profile S15Data User Frame Edit Section 15 data TopFrame User Frame Top frame for transit application YrEndReport User Frame Route Profile

Building and Running Images The main PCP application is created, and can be run from, the development environment. To make it available to the general users, an executable format, called an "image" is created by the 4GL utility Makelmage. The PCP application image is saved to the shared SANDAG network directory as m: ~res ~ 10202 ~pcp. img. Once an image is created, it can be run from any PC equiped with the OpenRoad runtime, the Ingres Net software and the Microsoft ODBC drivers. The OpenRoad utility RunImage is used to start the application. A new image must be created when changes to the application code or components are made.


1111

Data Load Program This program reads one or more raw transit counter program counts files and loads them into the raw_route and raw_stop tables for validation. It is written in C with embedded SQL statements. The program performs some data correction during the load process.

Building the Program The program is built using the following make file on Windows NT systems:

!INCLUDE <ntwin32.mak> SDK_DRIVE = d: all: load_raw_count.exe # compile your source file # first do esqlc to 'c' load_raw_count.obj: load_raw_count.sc esqlc load_raw_count.sc cl -I $(SDK_DRIVE)\mstools\h -I $(II_SYSTEM)\ingres\files -c -D_MT -D_DLL -D_X86_=1 load_raw_count.c # now call the Microsoft compiler to get the object file #load_raw_count.obj: load_raw_count.c # cl -I $(SDK_DRIVE)\mstools\h -I $(II_SYSTEM)\ingres\files -c -D_MT -D_DLL -D_X86_=1 load_raw_count.c # finally link our library and object files to get an executable load_raw_count.exe: load_raw_count.obj link /OUT:load_raw_count.exe /subsystem:console /entry:mainCRTStartup /MAP:load_raw_count.map \ load_raw_count.obj sql_error_handler.obj \ $(II_SYSTEM)\ingres\lib\ingres.lib msvcrt.lib /NODEFAULTLIB:libc.lib

Running the Program To run the program use the following command:

load_raw_count <count_file> <count_file> . . . <count_file>

Example: load_raw_count rt030 rt36 rt40

Chapter

5


2222

The <count_file> is the name of a file containing count information. It may have an extension (such as “sat” or “sun”) but it is not required. The count files named in the command string must be in the current default directory. The count files have the following format.

Position Length Format Description 1-6 6 Numeric Date counted in the form MMDDYY 7 1 Numeric Day code 8 1 Numeric Company ID number 9-12 Numeric Route number 13-16 Alphanumeric Schedule number 17-18 Numeric Counter ID number 19-22 Numeric Vehicle number 23-24 Numeric Page number (99 when input is from a Telxon unit) 25-28 Numeric Terminal time 29 Numeric Direction code 30-33 Numeric Bus stop number 34 Alphanumeric Timepoint 35-36 Numeric Offs 37-38 Numeric Ons 39-42 Numeric Schedule time 43-46 Numeric Arrival time 47-50 Numeric Departure time 51-54 Numeric Detour bus stop number 55-57 Numeric Carryovers (or onboard) 58-92 None Additional information that is not processed

The following is an example of a count file:

01269055 60101013302079905387 75T00040538054005400000000 01269055 60101013302079905387 90 01000000000000000000000 01269055 60101013302079905387 105 01000000000000000000000 01269055 60101013302079905387 115T00000544054605460000000 01269055 60101013302079905387 145T00010547054905490000000 01269055 60101013302079905387 150 00010000000000000000000 01269055 60101013302079905387 155 00010000000000000000000 01269055 60101013302079905387 160 01000000000000000000000 01269055 60101013302079905387 180T02000552055305530000000 01269055 60101013302079905387 205T00000556055605560000000 01269055 60101013302079905387 230 00010000000000000000000 01269055 60101013302079905387 235T00000602060006010000000 01269055 60101013302079905387 240 00010000000000000000000 01269055 60101013302079905387 245 00030000000000000000000

NOTE: This program also has a "trolley" mode that is currently disabled. It was used for the loading of trolley counts for FY 95 and 96 which were processed during the transition to the Ingres based PCP program. Those count files had a special three digit count fields for the trolley and the coaster because they had been re-formated in earlier processing. All counts performed after FY 96 use the standard bus format


1111

Output Products & Reports All reports are written using the Ingres report writer. A source file for each report can be found in the reports directory with an extension of “RW” (Report Writer).

Route Reports Called by PCP object

Report Seq #

Report Name Object Type

Report #

Print Params

Report Source File

Report Title and Description

RptRequest 10 rpt1 R 1 -s10 rpt1.rw Rpt 1: Dates Checked Summary RptRequest 20 rpt2 R 2 -s10 -l rpt2.rw Rpt 2: Route Profile RptRequest 22 rpt2a R 2a -s10 -l rpt2a.rw Rpt 2a: Rte Profile for Trains &

Trolley RptRequest 30 rpt3 P 3 -s10 tripsum.rw Rpt 3: Trip Summary RptRequest 40 rpt4 R 4 -s9 -l rpt4.rw Rpt 4: Ons, Offs, Thrus RptRequest 45 rpt4a R 4a -s10 rpt4a.rw Rpt 4a: Detailed Ons, Offs, Thru RptRequest 47 rpt4e R 4e -s10 -l rpt4e.rw Rpt 4e: Spreadsheet RptRequest 50 rpt5 R 5 -s9 rpt5.rw Rpt 5: On Time Summary by

Stops RptRequest 52 rpt5a R 5a -s10 rpt5a.rw Rpt 5a: On Time Summary RptRequest 54 rpt5b R 5b -s10 rpt5b.rw Rpt 5b: On Time Summary by TP RptRequest 60 rpt6 R 6 -s10 rpt6.rw Report 6: Section 15 RptRequest 80 stoplist R sl -s10 stoplist.rw Bus Stop Inventory Field Listing RptRequest 82 stop_inv_dum

p R sid -s10 stop_inv_dump.

rw Bus Stop Inventory Dump

Chapter

6


2222

Year End Reports Called by PCP object

Report Seq #

Report Name Object Type

Report #

Print Params

Report Source File Report Title and Description

YrEndReport 2 section15 R s15 -s9 -l section15.rw Section 15 Report YrEndReport 3 sysprof R sp -s9 -l sysprof.rw System Daily Profile YrEndReport 4 sysprof R sp -s9 -l sysprof.rw System Daily Profile

(Sunday) YrEndReport 5 sysprof R sp -s9 -l sysprof.rw System Daily Profile

(Saturday) YrEndReport 6 onoff_summary R oste -s10 -l onoff_summary.rw On-Off Summary by Trip

Ends YrEndReport 7 onoff_summary R oson -s10 -l onoff_summary.rw On-Off Summary by Ons YrEndReport 8 onoff_summary R osof -s10 -l onoff_summary.rw On-Off Summary by Offs YrEndReport 9 onoff_summary R osp -s10 -l onoff_summary.rw On-Off Summary by Place YrEndReport 10 onoff_summary R osbs -s10 -l onoff_summary.rw On-Off Summary by Bus

Stop Descr YrEndReport 11 rptava R ava -s7 -l rptava.rw ArcView Analysis Data

Support Programs

Archive and Restore Programs Archive_Counter The archive_counter program unloads the count data for a specific fiscal year specified by the user. The data is written to archive files and removed from the active database. Since the data is removed as the last part of the archive process, it is important that a reliable backup of the database be made prior to running the program.

The program is written in C with embedded SQL statements. The source data file name is archive_counter.sc.

Restore_Counter The restore_counter program reloads the count data from an archive file. All data in the archive file specified by the user is loaded. The program is written in C with embedded SQL statements. The source data file name is restore_counter.sc.

Database Maintenance Programs Audit_Counter The audit_counter program performs a variety of checks on the counter database to detect configuration and data integrity errors. The program should be run periodically and whenever problems with the database is suspected. The program only reads the database, but the program should only be run when the database is not in regular production use since the queries can affect response time. The program is written in C with embedded SQL statements. The source data file name is audit_counter.sc.

Optimize_counter The optimize_counter program performs a variety of maintenance tasks on the database to optimize performance. All indices are rebuilt and data distribution histograms are recalculated.. The program should be run periodically and whenever database performance begins to decline. The program locks access to the database and may only be run when the database is not in regular production. The program is written in C with embedded SQL statements. The source data file name is optimize_counter.sc.

Chapter

7

1

Appendix A PASSENGER COUNTING PROCEDURES

BACKGROUND The Regional Transit Passenger Counting Program is intended to collect information on-board the region's transit systems to be used for daily operation planning, problem identification, bus route configuration, analysis of bus stop location, frequency of service and on-time performance. The information will be used by the region's transit operators for daily planning as well as to meet federal, state and local requirements. Transit passenger counters are employed through a temporary employment agency on a part-time basis and are responsible for the field data collection. From time to time the counters may be called upon to assist with other data collection efforts such as on-board passenger surveys or other types of interviews. Their primary responsibility will be to assist in data collection efforts for SANDAG's Assistance to Transit Operators work program. The contents of this manual are designed to help in the training of new persons and to serve as a reference for those who are more experienced. OFFICE PROCEDURES A. Biweekly Meetings

Every other week you will meet with your supervisor, generally on Fridays at a predetermined time in the SANDAG offices. These meetings serve several purposes:

1. Turn in data from the data collection sheets and/or the electronic data collector. Be

sure to bring all your materials pertaining to the work you were assigned during the past week, including the Telxon handheld collector, schedule sheets, and bus stop inventories.

2. Discuss with supervisor any problems or questions regarding the past week's

assignments. This might include changes in schedules and Bus Stop inventories, and any incomplete trips.

3. Receive work assignments for the upcoming week including work schedule, time

schedule, and bus stop inventories. Should there be any questions about locations, bus route, etc., they can be answered here. Also, if there is anything new or unusual about your assignments for the coming week, your supervisor will clarify them at this time.

4. Inform your supervisor of any specific days or partial days off needed during the

week following the next meeting (this would be approximately 1-2 weeks notice, or more).

B. Scheduling

2

Schedules are made up during the previous week for each week's assignments. Because of this time frame, notice regarding days off as described above is essential. Generally, there will be two working shifts. Each person may be assigned morning and/or evening shifts starting as early as 4:00 a.m. and, in a few cases, ending as late as 2:00 a.m. Occasionally there will be slight variations due to unusual bus schedules. Assignments will include working on weekends. Some flexibility in working shifts can be accommodated; however, the demands of the bus schedule have priority.

Timecards are completed by the supervisor.

C. General Rules

Due to the nature of the data collection system, you must be able to work, responsibly, without direct supervision much of the time. Although checks are made periodically on each employee, some basic guidelines must be set in order to insure dependability, responsibility, and quality of work. Overall, remember to inform your supervisor immediately, or as soon as possible, if any of the following should occur:

1. Illness - preventing you from working that day.

2. Missed or partial trips, due to lateness or mix-up in starting time.

3. Other incidents which prevent you from working.

Remember - Anytime you miss a bus, or your work schedule cannot be completed, call your supervisor. It is Your responsibility to contact the supervisor.

Other general guidelines include:

1. Switching daily assignments. Do not trade one day's assignment for another or trade assignments with other counters, without first clearing it with your supervisor.

2. Proper office behavior. Be on time to meetings. Meetings generally last

approximately one-half to one hour. From time to time, you win be asked to work here in the office after your meeting. Whether or not you are asked to stay on after the meeting, you will be paid for 2 hours time. Keeping this in mind, expect to stay the fun 2 hours on meeting days. However, if you need to make plans or definitely need to know how long you will be in the office on a given day, call in on that day and your supervisor will be able to tell you if you need to stay. An exception to this two-hour rule will arise if you are late to the meeting. Because this would disrupt other counters and SANDAG staff, anyone arriving late will be paid only for the time they are at the meeting, not the regular two hours. Conversation should be kept to a minimum waiting in public areas of the office.

3. Unexcused Absences. Three unexcused absences within three months are

considered grounds for termination.

3

4. Vacation/Time-Off Notice. Because passenger counters are not employees of SANDAG, paid vacations are not a benefit of this position. However, time off can be arranged if the supervisor is notified far enough in advance. Due to commitments for survey work and other special projects, you are required to give 2 months notice for consecutive days off, or for more than 2 days off, nonconsecutively, within a two-week period.

5. Turning in data which is not obtained through established counting

procedures will be grounds for immediate dismissal. D. FIELD WORK A. Personal Conduct

Your job requires working extensively with the public. Since you will be representing SANDAG, it is important for you to be courteous at all times and to maintain a professional and pleasant manner. Also, it would be in your best interest to keep conversation between yourself and the passengers and driver to a minimum. However, should there be any confusion with a route or problems with passengers, the driver can help you - ask him for instructions. If you have any problems with the driver, report the incident to your supervisor as soon as the opportunity arises. Do not argue with the driver. Keep in mind also that although you are working while on the bus, you are also a passenger and must adhere to the basic rules all passengers follow.

B. Dress

There is no required dress for passenger counters other than to be neat and comfortable. However, it is in your best interest to be dressed modestly and to be wearing a good pair of shoes to prevent injury if your feet are stepped on. Practicing good hygiene is necessary. Complaints by transit operators or the public may lead to disciplinary action.

C. Work Duties

You are responsible for getting to your work assignment at the appointed time and location. Most shifts will begin and end at the bus company's yard, but at times you will be asked to meet a bus on its route somewhere in the county. Transportation to work is your responsibility.

Your role in the Passenger Counting Program is to collect data. This involves recording passenger boardings and alightings at each bus stop, and recording the on-time performance of the bus. A bus stop inventory with each bus stop on a given route identified and numbered, a route time schedule, and coding forms or other means of data collection are provided for these purposes. Counts may be collected using a handheld data collector, a small electronic recording device, or they may be recorded on paper forms for keypunching. Both data collection methods are described in this guide. A supply of coding sheets should be kept with you even when using the data collector. This is to prevent loss of data in the event of mechanical breakdown or malfunction of the collector.

On occasion, you may also be asked to work in the office to perform related tasks. You will

4

also meet in the office with your supervisor once a week to turn in completed work and to receive your assignment for the following week.

D. Breaks

Breaks should be taken at the end of the run whenever possible. Drivers generally adhere to this type of arrangement and you should try to, also. The bus driver is not responsible for you; therefore, it makes it easier for both of you if you try to stay with his routine. Also, when you take a restroom break, let the driver know so that he does not leave you behind. If the driver should refuse to wait for you, get off the bus and use the restroom, then pick up your run when the originally scheduled run returns on the next trip. Let your supervisor know when this happens.

E. Materials

There is a required set of materials you must have with you while working:

1. A reliable watch 2. #2 pencils. Do not use anything but pencil. 3. Coding Sheets 4. Schedule Sheet 5. Bus Stop Inventory 6. Clip Board 7. Identification Card 8. Telxon Data Collector (if issued)

All of these are available from your supervisor at the SANDAG offices.

F. Emergencies

In the event that something happens to prevent you from working, such as illness, accident, car trouble, etc., call your supervisor at 595-5319. Please call in as soon as possible so that adjustments can be made to cover your assignment.

IV. PASSENGER COUNTING

A. At the Bus Yard

Most of the time you will be required to begin and end your shift at one of the bus company's yard. San Diego Transit (SDTC) Imperial Division (IAD) is located at 100 16th Avenue, at the comer of 16th and Imperial. Just off the Imperial Avenue side is the Driver's Room and Dispatcher's Office. The Kearny Mesa Division (KMD) is located on Ruffner Street between Opportunity Road and Dagget Street. To find the bus and driver assigned to you, tell the Dispatcher your run number and route. He will put you in contact with the driver of that particular schedule. At the start of your shift set your watch with the driver's to assure proper recording of times for the route. When assigned to count routes by other transit operators, you will be advised of the bus yard or starting location of your assignment.

5

B. Passenger Counting - Coding Sheets

After you have found the correct driver and bus, begin filling out the following information at the top of the coding sheets: Date, Day, Company, Route, Schedule #, Counter #, Bus #, Page (an example of the coding sheet is shown in Figure 2). Some items such as Company and Day are given codes listed at the bottom of the coding sheets. This information should be completed for each sheet used for your data collection. The rest of the information needed will all come from either the Schedule sheet or Bus Stop Inventory. List the Terminal Time (trip start time), the direction of the trip, put a "T" in the Timepoint column, and record the Terminal Time in the Schedule Time at the Timepoint column. Record the actual leaving time from the Terminal in the Leaving Time column. Then record the number of passengers getting on the bus at the Terminal in the Passengers-On column.

As you approach each bus stop, keep track of where you are along the route by following your bus stop inventory. Record the bus stop # and the number of people getting off and on the bus at each stop. Only record bus stops where there are ons or offs, or stops that are designated as Timepoints.

Every so often (usually every 10 minutes or so) you will need to record the Timepoint information. By following the Schedule sheet and Bus Stop inventory you will be able to anticipate an approaching Timepoint stop. At each Timepoint, in addition to the regular bus stop information, you will also need to record all the necessary Timepoint information. The Schedule Time is available from your Schedule sheet. The Arrival Time and Leaving Time should be recorded as they occur.

At the end stop of each bus trip, only record the Schedule Time and Arrival Time for the Timepoint information. It is not necessary to record a Leaving Time. Occasionally, you will need to record detours. A typical detour bus stop would be shown by recording the bus stop #, and then recording the detour stop # in the Detour Bus Stop column (example: "Reg Rt go to 510", 510 would be the Detour bus stop).

Each bus trip will be recorded in this manner. At the end of each trip, check to see that the coding form is accurately and completed filled out. Take special care to make sure you have counted the same number of people getting off the bus as on. It is important that your entries are neat, .3, accurate, and complete since someone else will enter the data into the computer directly off the coding forms. It is important to record any special circumstances that may cause the bus to be late by 30 minutes or more. For example, wheelchair lifts that don't work properly, mechanical problems, accidents, etc. should be noted on that day's trip schedule. This will help when the data are edited. Also, when using the electronic data collectors, if data were entered incorrectly, note this on the trip schedule (e.g. incorrect direction code). C. Passenger Counting Telxon Handheld Data Collector

The Data Collector is designed to collect data by record type. This means that depending on what type of data you specify you are collecting, the collector will prompt you. There

6

are six different types of records:

1. Sign on (New Day) 2. New Trip 3. Time Point 4. Regular Bus Stop 5. Detour Bus Stop 6. Trolley Trip

Table 1 identifies each key on the Telxon unit. When the unit is turned on, the following message will appear:

IF FOUND, CALL

SANDAG 401 B Street, SD, CA

(619) 595-5300

By pressing any key, the following menu appears:

1. Ride Check 2. Trolley Check 3. Set Date/Time

(The "Ride Check" is for bus counts.)

Bus or COASTER trip Sign On . By choosing "1" for bus check, the following sign-in menu appears:

EMP ID: DATE: COMPANY:

where EMP ID is the 2-digit ID number of the counter, DATE is automatically displayed, and COMPANY is the 1-digit ID number of the transit company (see Table 2). After each entry, use the "ENTER" key.

New Trip. For ride checks, once the sign-on entries are completed, the next menu to appear is the new trip menu:

RT: VAR: SC: VEH: TERM TIME: DIR: ONB:

7

Table I TELXON FUNCTION KEYS

Top Row on/off powers unit on and off “<” A moves one record towards the beginning of file review B "review mode" allows user to view previously entered data “ > ” C moves one record towards the end of file end displays the version of the softward and available memory Second Row menu D allows user to adjust volume exit E allows user to exit from current function send F allows user to transmit data to PC erase G allows user to erase data in handheld (password protected) next H allows user to enter a load adjustment record Third Row “=” I not used “*” J allows user to enter an exception record modify K allows user to modify field in review mode “#” L allows user to toggle backlight on and off “/” M allows user to adjust contrast Fourth Row Shift allows user to use alpha characters yes N "yes" response for all yes/no? questions search O allows user to enter a "go to" record no P "no" response for all yes/no? questions clear allows user to clear contents of current entry Above ENTER Key “ < “ allows user to go back a field on current screen “ > “ allows user to go forward a field on current screen Bottom Row “-“”sp” allows user to enter a time point record “.” "hot key" timestamp for arrival time enter records data - to be pressed after each entry

8

where RT is the 4-digit route number, VAR is a letter code not usually used in the field, SC is the 4-digit schedule number (this can be alphanumeric; letters can be entered by using the Shift key), VEH is the vehicle number of the bus, TERM TIME is the trip's terminal time, DIR is the direction of the trip (see Table 3), and ONB is the onboard or carryover function.

Time Point. Once the new trip menu is completed, the Time Point menu will automatically appear:

BS: ST: OFF: AR: ON: DP:

where BS is the 4-digit bus stop number, ST is the schedule time, OFF is the number of passengers deboarding, AR is the arrival time at the time point (automatic), ON is the number of passengers boarding, and DP is the departure time (automatic). (NOTE: Since the arrival and departure times are automatic, they are only entered into the record when the ENTER key is pressed.)

Regular Bus Stop. Once the first time point stop is entered, the regular bus stop menu will appear:

STOP #: OFF: ON:

where STOP# is the 4-digit bus stop number, OFF is the number of alightings and ON is the number of boardings at the stop.

Once complete, another blank regular bus stop menu will appear for the next stop. If the next stop is a time point, hit the "SP" key to invoke the time point menu.

Detour Bus Stop. THIS FUNCTION IS NO LONGER USED. Some trips may deviate from the full route configuration. These are indicated in the bus stop inventory by detours or "go to" stops. To invoke the detour bus stop menu, at the regular bus stop menu, hit the "SEARCH" key and the detour bus stop menu appears:

BUS STOP GOTO: STOP #: GOTO #:

where STOP# is the bus stop beginning the detour and GOTO# is the bus stop to go to.

Trolley Trip Sign On. There is different information required for trolley checks and therefore a slightly different menu system. At the sign on menu, select choice "2. Trolley Check" and the following trip menu will appear:

9

DATE: COMPANY: 07 EMP ID: RTE VARIATION: Where DATE is automatically displayed, COMPANY is automatically displayed as “07”, EMP ID is the 2-digit number of the counter, and RTE VARIATION is a single alpha code that is available to the counters on the bottom of the paper data collection form for trolley counts. The next menu to appear is: DIR (1/2): LINE (E/S): TERMTIME: 1ST STOP:

where DIR is the direction of the trip (1 is westbound or inbound, 2 is eastbound or outbound), LINE is the East (Orange) or South (Blue) line (there is no need to use the shift key to enter either E or S here), TERMTIME is the trip terminal time and 1ST STOP is the bus stop number of the first trolley station. Once information on this screen is entered, the trip menu continues:

ONBD: CONSIST: CAR#: TRAIN#:

where ONBD is the number of passengers onboard already (a function not used in trolley counts), CONSIST is the total number of trolley cars on the train at the origin, CAR# is the number of the car which is being counted (for example, the counter is on the second car of a four car train, CONSIST=4 and CAR#=2), and TRAIN# is the schedule number of the trip. Once the trip menu is completed, the following display menu appears:

DISPLAY TIME

1. STOP# 2. DESCRIPTION

By choosing " 1. STOP#," the trolley stations will be identified by the bus stop number and a bus stop inventory will be needed. This format is identical to a bus ride check’s time point screen; "2. DESCRIPTION" will display the stations by an abbreviated description (NOTE: Display by description is usually preferred.) Once a selection is made, a stop menu appears:

STATION NAME # ONBOARD SCHED TIME:

OFFS: AR: ONS: DP:

10

The station name and schedule time will automatically appear. OFFS are the number of alightings, AR is the arrival time, ONS are the number of boardings, and DP is the departure time. (NOTE: Similar to the ride check, arrival and departure times appear automatically, but are only recorded when the ENTER key is pressed.)

Occasionally, trolley trips may be shortened to start or end at different stations. To enter a trip which is shortened at the beginning (for example, a South Line trip that begins at America Plaza), enter the bus stop number as the "1ST STOP" on the trip menu. To end a trip before the normal terminal, use the EXIT key after the last station.

To end trips or days. At the end of the last bus stop, hit EXIT. An "End of Trip?" message will appear. To return to the regular bus stop menu, respond NO. To end the trip, respond YES, which goes to a new trip menu. To begin a new trip, begin completing the menus.

To end the shift or day, hit EXIT again. The "End of Day?" message appears. Responding NO will continue with the new trip menu and responding YES will return to the sign-in menu. Hitting EXIT again will return to the opening screen. At this point, turn the collector off.

Setting the Date or Time. Because dates and arrival and departure times are automatic, it

is important that they be correct in the data collector. At the beginning of a shift, check the time with the bus driver. If necessary, reset the date or time by choosing Set Date/Time" from the opening screen. The following appears:

ENTER: mm/dd/yy DATE:

Enter the two-digit month (for example, February is 02), date, and year without the

slashes. Once entered, a similar time function appears:

ENTER: hh:mm:ss TIME:

Enter the hours as military time (for example, 4:00pm is entered as 16), the minutes and seconds, and hit ENTER.

D. Data Return Using the Data Collector At some point during the weekly meetings, all counters will assist the supervisor in transfering data from the collector to SANDAG's computer system. This is done using a PC, a modem, and the appropriate adapters. After the transfer of data is complete, the data collectors will be cleared of all data contained in them. Therefore, each week each surveyor will start out with a "cleared" data collector. (See uploading instructions later in this document.)

Collected data will be received for processing by SANDAG's Prime computer system. Electronic data can be transferred either by modem or by RS 232 direct connect interface. Normally, data will be transferred by RS 232 direct connect interface in the office. Data will be transferred in the order that the data is collected by checkers.

11

E. Documentation

Each counter must also turn in all time schedules for work completed. Any comments or problems which occurred should be discussed as well as noted on the schedule. Partial trips are not acceptable and should be identified to the supervisor in order to be rescheduled. Data that were entered incorrectly into the Telxon unit such as incorrect company code or direction should be noted. Any problems that caused the bus to be late or even skip a portion of the trip should also be documented on that day's trip schedule.

APPENDIX B THE COUNTER MEETING

Counter meetings are held to collect field data and to distribute new assignments. Data is available in one of two forms: paper, or electronic recorded in a Telxon unit. Accompanying either form of data will be assignment sheets documenting which route trips were counted on an assigned date. The supervisor will use a red felt tip pen to record in the stamped area whether the assignment was completed, whether it was recorded on paper or electronically, and what file name was given to electronically recorded data. If the entire assignment was done on a date different from that recorded in the assignment label, draw a line through the original date and record the new date beneath the old one. If some trips were done on a different date than the assigned one, record those dates to the left of each assigned trip row. Paper data should be immediately checked for completeness. Individual trips should be checked for all time points and the entire day’s assignment checked for all trips. Telxon units can be downloaded on any PC with a serial port. The downloading software is found in the same directory on both the desktop and portable units: C:\CHECKER\da_menu The “da_menu” program is an executable program that is launched from a DOS prompt. Prior to starting the download program, use the 30 inch cable with a ten pin male parallel port end and a female serial port end to connect the Telxon unit to the PC. SLC has been written in indelible ink on the parallel port end. Start the download program by: 1. Going to C:\CHECKER 2. Type da_menu then press the ENTER key. 3. A screen titled SANDAG HANDHELD DATA COLLECTION SYSTEM will appear. 4. Type A or press the ENTER key to go to the DATA TRANSFER screen. 5. A screen will appear to prompt you to connect the Telxon unit to the PC. Press any

key to continue. Further instructions will appear; press any key to continue. A blank screen will appear with a timing clock in the lower left hand corner and download setting information in the lower right hand corner.

6. Press the F2 key to bring up the file naming box. The file naming protocol is the first and last initials of the counter followed by the current date in two digit month and two digit day form. As an example, the file name for Bennie Kyle downloaded on December 3 is bk1203.txn with the .txn ending signifying a Telxon file. After the file name is entered, go to the Telxon unit and press the F key (send) twice. The PC monitor screen will display data as it is received and will stop scrolling when there is no more. DATA SENT will also appear in the Telxon screen when downloading is complete.

7. Press the F3 key to close the current download file. 8. Press the F10 key to exit the download screen and type Y to confirm the exit. 9. If the download is being done on a portable PC, put a disk in the floppy drive.

Create a folder with the name of the current date in “mmddyyyy” format. Copy the

newly downloaded file from the PC to the floppy drive. Check the directory of the floppy drive to ensure that the file copied and what size it was. Now that there are two copies of the downloaded file, the memory of the Telxon unit may be cleared.

10. Press the ERASE (G) key of the Telxon unit two times. The screen will show ENTER PASSWORD in the top line and space for four characters to be entered on the second line. The current password is “KILL” which should be entered followed by pressing the ENTER key. The next screen will show CHANGE PASSWORD (YES/NO). Press the NO (P) key to not change the password and continue to the next screen. That screen will show ERASE FILE ARE YOU SURE Y/N. Press the YES (N) key to erase the file. The next screen will show RIDE FILE HAS BEEN DELETED ! PRESS ENTER. Press ENTER to return to the home screen.

Give the next week(s) assignments to the counter being careful to explain any scheduling that may not be easily apparent. Note any work that has to be made up so that free days may be provided for in future weeks so that those assignments may be made up. Ask the counter if they require any special days or times off in the next month. You have now finished your meeting.

UPLOADING Copy the downloaded files from the floppy to the desktop’s C:\CHECKER\DL directory. Record the downloading on the data tracking form. The .TXN (Telxon) files must be converted before being uploaded to the INGRES database. To do this: • Go to the MSDOS prompt. • Change the directory to C:\CHECKER • Type SNDGCNV7 and press the ENTER key. • A “Bad Command or file name” may appear but it can be ignored. The following

screen will appear: THIS PROGRAM READS A DATA FILE THAT HAS BEEN TRANSFERRED FROM A TELXON 710 HAND HELD DATA COLLECTOR INTO A DISC ENVIRONMENT TO CONTINUE ENTER 1 TO EXIT ENTER 2 • Type 1 and press the ENTER key. PLEASE ENTER SIX (6) DIGIT FILENAME IDENTIFIER • Type the file name without the suffix, i.e. bk1203 for Bennie Kyle’s December 3rd

download. Press the ENTER key. SUMMARY INPUT TELXON FILE NAME: C:\CHECKER\DL\bk1203.TXN OUTPUT RIDE CHECK FILE: C:\CHECKER\CNV\bk1203.CNV

PLEASE REVIEW FILE NAMES TO CONTINUE ENTER 1 TO RETURN TO DOS ENTER 2 • Type 1 and press the ENTER key to continue. C:\CHECKER\DL\bk1203.TXN OPEN FOR READING C:\CHECKER\CNV\bk1203.CNV OPEN FOR WRITING JOB COMPLETED AFTER 569 RECORDS PRESS ENTER TO RETURN TO MENU . . . . . • Press ENTER key. STOP - PROGRAM TERMINATED. C:\CHECKER> Record the file conversion on the data tracking form. To upload the data file to the Ingres database, remain at the DOS prompt. Change to the directory: C:\CHECKER\CNV Type LRC then space once and enter the data file to be uploaded. Press the ENTER key to commence the operation. The command line will look like: LRC BK1203.CNV The following screen will then scroll: SANDAG TRANSIT COUNTER PROGRAM: LOAD RAW COUNT UTILITY REV 14 Connecting to pavo::counter3 database . . . 507 records read from bk1203.cnv 506 records written to c:\temp\load_raw_count.temp Clearing existing raw_count table . . . Loading raw_count bus data from c:\temp\load_raw_count.temp . . . 506 rows loaded Calculating set key values . . . Clearing existing temp_set_key table . . . 27 count sets found Calculating next set key value . . . 54758 Calculating set keys for counts being added . . . 27 rows Initializing the count’s set keys to 54758 – 54784 . . . 506 set keys initialized Setting route key . . . 711 Stop numbers set Setting stop numbers . . . 131 Stop numbers set Setting Detour Stop flag . . . 0 Detour Stop flags set Calculating scheduled start and finish times for each count . . . 506 start/finish times set Loading raw count data into raw_route . . . 27 raw route rows added Loading raw count data into raw_stop . . . 506 raw stop rows added C:\CHECKER\CNV

Record the file upload on the data tracking form in C:\My documents\xls\Counter data tracking form.

Telxon Data

Paper Data

COUNTERS TXN files copied

from floppy

TXN files converted

to CNV files

CNV files uploaded

into Ingres

Checked Given to June

Returned by June

Uploaded into Ingres

Brentley R. Desbrow J. Fleming D. Griffin N. James D. Johnson S. Kyle B. Lunder D. Melrose M. Menges P. Rolison C. Wilson W.

DATA TRACKING FORM (old form) Fiscal Year 2 _ _ _ Dates - - - >

Counter name Initials

Paper Data: Date Route numbers

TROUBLESHOOTING TELXON TROUBLES There are two categories of Telxon failures: those that do not affect the data held in memory and those that cause the loss of all data held in memory. The Telxon PTC-710 has two sources of power: three AA batteries provide the primary power and one watch battery provides backup power for the data flash card. A total loss of power from both sources will cause a loss of all memory for both data and operating programs. The most common malfunction of a Telxon is a program “locking up” which causes the screen to “freeze”. This can usually be cleared by removing the AA batteries and waiting about 15 to 30 seconds before replacing them and turning the unit on again. Pushing the END, CLEAR, or the blue BACK ARROW key are often effective in exiting a screen one does not wish to be at. If the unit has a screen displaying 65> or similar number, then it is at the system prompt and needs to be re-started. The following instructions are for bringing a Telxon unit to the system prompt for re-starting. 1. Power off the handheld. If you are unable to power off the handheld using the

ON/OFF key you should open the back cover plate and remove one of the batteries. Re-insert the battery and replace the back cover.

2. Hold down the bottom corner keys (the SP – and the ENTER keys) and then press the ON/OFF key. Release the ON/OFF key while still holding down the two bottom corner keys.

3. Continue to hold the two bottom corner keys down. The system prompt (ie. 65> ) should appear in seven to ten seconds.

4. If your application appears or nothing happens you should repeat steps 1-3. If you are unable to get to the system prompt, it is likely that you will have to reload the entire system programming. Reloading will erase all data collected in the unit so this should only be done as a last measure. For technical advice call: Rich Gearhardt at SLC Software in Cincinnati. His telephone number is (513) 922-4303 and his e-mail is [email protected]. Rich wrote the software for the Telxon units and holds the maintenance contracts for our units. Repair is done at the manufacturer’s depot in El Paso, Texas. To Load the Application into the Handheld: ON THE PC • Change the directory to your Telxon Load Directory (ie. Cd \telxon ). • At the C:\Telxon> prompt type PCTCOS. The following should appear;

IBM PC TO/FROM TCOS

1. EXIT TO DOS 2. DOWN LOAD FILES TO TCOS 3. SEND/RECEIVE DATA FILES FROM TCOS 4. SET BAUD RATE OR CONNECT TYPE 5. CHANGE STATUS OF DISPLAYED DATA SENT/RECEIVED 6. HELP

ENTER NUMBER: __

• Select Option 2. The following will appear:

DOWNLOAD FILES USING SUBMIT FILE ( Y OR N )? __

• Press the letter N. The following should appear:

ENTER NAME (S) OF FILES TO DOWNLOAD, A RETURN TO QUIT # 1 FILE NAME _

• Enter SANDAGxx (xx being the latest revision number which is currently 12). Press the

ENTER key. The following will appear:

# 2 FILE NAME • Enter ROUTEFIL.R (which is an program used during trolley counts). Press the ENTER

key. The following will appear:

MULTIPLE DOWNLOAD (Y OR N) _ • If you wish to load more than one handheld press the Y key otherwise press the N key. The

following should appear:

CONNECT PTC, WAITING FOR DSR OR ESCAPE KEY Now go to the handheld. ON THE HANDHELD 1. Connect handheld to the PC using the 15 inch serial to parallel port cable. On the parallel

end should be a 2 inch adapter labeled “IBM PC LOAD/UNLOAD TELXON” which converts the 25 pin parallel end to a 10 pin parallel end. Connect the serial end to the PC and the parallel end to the Telxon unit.

2. Power on the unit to the System Prompt (ie. 65>) 3. Press the 8 key on the handheld. 4. Press the ENTER key. 5. Press the ENTER key again. 6. The handheld should start to beep and on the PC monitor you should see the file name

followed by a string of pluses (+) as the file is being loaded.

7. When done press the CLEAR key and go to the instructions for restarting the application on the handheld.

RESTARTING APPLICATION ON THE TELXON HANDHELD 1. Handheld should be at the System Prompt. (ie. 65>) 2. To run the application on the handheld, at the system prompt press the 6 key and the

following will appear: TP__. Press the ENTER key until the application desired (SANDAG12.Y) is shown on the screen. Hold the 3 key down until it beeps three times. This should start the desired application.

3. To delete an application, press the 6 key at the system prompt and the following will appear: TP__. Press the ENTER key until the application desired is shown on the screen. Hold the 1 key down until it beeps three times to delete that application.

REPLACING TELXON COVERS Covers for the Telxon units are available from: Med Covers, Inc 1103 Transport Drive Raleigh, North Carolina 27603 Telephone: (800) 327-4571 Fax: (919) 772-3917 The cost per cover in 1999 was $55.

REPLACING TELXON CHARGING ADAPTERS Charging units for the Telxon units are available from: SLC Software Services Telxon 1958 Anderson Ferry Road 14275 N.W. Freeway Cincinnati, Ohio 45238 Houston, Texas 77040 Telephone: (513) 922-4303 (713) 307-2300 Fax: (513) 922-4439

MAINTENANCE ON TELXON UNITS

The existing maintenance contract requires SANDAG to send all units to the Telxon National Service Center for repair. The telephone number is 1-800-800-8010. The mailing address is: TELXON NATIONAL SERVICE CENTER 12170 Rojas Suite A/B El Paso, Tx 79936

user’s guide · passenger counting program user’s guide may 1999 san diego association of...

Documents