This Capital Metro Automatic Passenger Counter (APC) Ridership data set is unprocessed, pure, raw, flaws and all straight from our Automatic Vehicle Location (AVL) system. Capital Metro, in partnership with a third-party vendor, applies a process that reviews the data to determine the validity and flags various elements to ensure final reported data has any bad elements excluded. Utilizing this data without applying your own methods to remove errors WILL NOT produce results corresponding to the published Ridership Reports.
Field Descriptions:
apc_date_time
'apc_date_time' is a date field describing the date on which the
vehicle data was collected. The date comes from the System Date in
the Data Logging files.
day_type_vs
'day_type_vs' is an identification number for both the day of the
week and the schedule number for that day for vehicle schedules. It
matches the id field in the day_type_vs table.
vehicle_id
'vehicle_id' is a numeric key which identifies the vehicle that was
picking up and dropping off passengers. The valid range is 1 to
65,535. This is a soft key to the 'vehicle' table.
route_id
'route_id' is a foreign key field to the route table. Valid “route_id” are
numbers between 1 and 65,535. Combined with the 'block_id' field, it
is the primary key of the 'block' table. This is a static field defined
upon record creation.
block_id
'block_id' is the block identification number assigned that uniquely
defines a particular route/block combination. A block usually
identifies a unique schedule from other blocks upon a common
primary route. Valid values for the “block_id” are between 1 and
999,999. Combined with the 'route_id' field, it is the primary key of
the 'block' table.
current_route_id
The 'current_route_id' is the trip route for a specified entry.
direction_code_id
'direction_code_id' is a primary key field that identifies the route
direction associated with the route path. Combined with the
'route_id' and 'variation' fields, it defines a unique path for route
directions. It is obtained by consulting the apattern_id reported by
the vehicle against the apattern table. It is also a software foreign
key to the 'direction_codes' table.
variation
'variation' is a primary key field that differentiates a route path from
others on the same route and direction. Combined with the 'route_id'
and 'direction_code_id' fields, it defines a unique path for route
directions. It is obtained by consulting the apattern_id reported by
the vehicle against the apattern table.
start_trip_time
'start_trip_time' is a timestamp that equals the scheduled time
associated to the first timepoint of the trip. The date portion of the
timestamp is not used.
actual_sequence
'actual_sequence' is the numeric ordering of door
events/logons/trips collected in the vehicle data logging files. This is
the actual sequence, not the scheduled sequence of bus stops as in
the 'bus_stop_pattern' table.
bs_id
'bs_id' is the bus stop identification number assigned to a particular
geographical bus stop within a service region. It may be matched
against bs_id field in the bus_stop_data table, along with other
items, to acquire detailed information about a stop.
import_error
'import_error' is a software foreign key to the 'apc_error_types' table.
The 'apc_error_types' table describes the types of errors, if any,
detected in correlating this door event.
garage_id
'garage_id' is the division assigned to this route/block.
transit_date_time
'transit_date_time' is the day of the month associated to the
schedule being used on the vehicle. For a given date/time, the
transit day would be the same day or the day before. The transit day
will be the day before in the early morning time periods.
run_id
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
