10 Results
filtered by...
Filter
Authority > Official
Tags > apc
Sort
Sort by Most Relevant
Filter
10 Results
filtered by
Tags > apc
Clear All
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.
Use of this data is subject to the terms below as well as the Terms of Service location Capital MetroLabs website.
Copyright 2017 Capital Metropolitan Transportation Authority (CMTA)
Permission is hereby granted, free of charge, to any person obtaining a copy of this data and associated documentation files (the "Data"), to deal in the Data without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Data, and to permit persons to whom the Data is furnished to do so, subject to the following conditions:
1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Data.
2. The name of the copyright holder may not be used to endorse or promote products derived from this Data without specific prior written permission.
THE DATA IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DATA OR THE USE OR OTHER DEALINGS IN THE DATA.
2. The name of the copyright holder may not be used to endorse or promote products derived from this Data without specific prior written permission.
THE DATA IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DATA OR THE USE OR OTHER DEALINGS IN THE DATA.
3. Use of the Capital Metro logo without express written consent is expressly prohibited.
4. Capital Metro may change Data formats at any time without notice.
Tags
apc
Updated
June 26 2020
Views
745
Dataset
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.
Use of this data is subject to the terms below as well as the Terms of Service location Capital MetroLabs website.
Copyright 2017 Capital Metropolitan Transportation Authority (CMTA)
Permission is hereby granted, free of charge, to any person obtaining a copy of this data and associated documentation files (the "Data"), to deal in the Data without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Data, and to permit persons to whom the Data is furnished to do so, subject to the following conditions:
1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Data.
2. The name of the copyright holder may not be used to endorse or promote products derived from this Data without specific prior written permission.
THE DATA IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DATA OR THE USE OR OTHER DEALINGS IN THE DATA.
2. The name of the copyright holder may not be used to endorse or promote products derived from this Data without specific prior written permission.
THE DATA IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DATA OR THE USE OR OTHER DEALINGS IN THE DATA.
3. Use of the Capital Metro logo without express written consent is expressly prohibited.
4. Capital Metro may change Data formats at any time without notice.
Tags
apc
Updated
June 26 2020
Views
284
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
operator_id
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
Updated
June 26 2020
Views
719
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
Updated
June 26 2020
Views
267
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. https://www.capmetro.org/facts/#!
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
o
Tags
apc
Updated
June 26 2020
Views
224
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
Updated
June 26 2020
Views
131
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
operator_id
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
Updated
June 26 2020
Views
141
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
Updated
June 26 2020
Views
123
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
Updated
June 26 2020
Views
93
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.
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.
'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.
'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.
'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.
'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.
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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'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.
'run_id' is the run number that the target is logged onto. If the vehicle
is logged off, this will be zero.
operator_id
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
'operator_id' is the driver logged on when the APC data was
collected. If the vehicle is logged off this will b
Updated
June 26 2020
Views
89
Showing 1 to 10 of 10 results