| Attributes | [{"attribute_display_order_id": 1, "db_format": "DATE", "db_name": "Date", "definition": "Date on which services are run", "id": "15291", "name": "Date (Metropolitan Bus)", "ref_number": "AT-15291"}, {"attribute_display_order_id": 2, "db_format": "TEXT", "db_name": "Line/Route", "definition": "Line/Route on which services are run", "id": "15292", "name": "Line/Route (Metropolitan Bus)", "ref_number": "AT-15292"}, {"attribute_display_order_id": 3, "db_format": "TEXT", "db_name": "Operator", "definition": "Operator that deliver the service per route", "id": "15293", "name": "Operator Name", "ref_number": "AT-15293"}, {"attribute_display_order_id": 4, "db_format": "DOUBLE", "db_name": "% allocated", "definition": "Proportion of services loaded in the bus tracking system that have been allocated.\n\n# journeys allocated (Bus) / # journeys loaded (Bus)", "id": "15301", "name": "Proportion of services allocated", "ref_number": "AT-15301"}, {"attribute_display_order_id": 5, "db_format": "DOUBLE", "db_name": "% journeys monitored (Bus)", "definition": "Proportion of services scheduled that were monitored by the bus tracking system (BTS)\n\n# journeys monitored (Bus) / # journeys scheduled (Bus)\n\nThe reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators.", "id": "15302", "name": "Proportion of services monitored", "ref_number": "AT-15302"}, {"attribute_display_order_id": 6, "db_format": "DOUBLE", "db_name": "% ontime (ArrDep|tp)", "definition": "Proportion of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points.\n\n# of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points / # of services observed arriving and departing at timing points.", "id": "15303", "name": "Punctuality - Ontime arrival and departure at timing points", "ref_number": "AT-15303"}, {"attribute_display_order_id": 7, "db_format": "DOUBLE", "db_name": "# service unique", "definition": "Number of unique services scheduled to operate in the bus tracking system.", "id": "15296", "name": "Number of unique services in timetable", "ref_number": "AT-15296"}, {"attribute_display_order_id": 8, "db_format": "DOUBLE", "db_name": "# journeys monitored (Bus)", "definition": "Number of scheduled services monitored by the bus tracking system (BTS) at one or more location. The reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators.", "id": "15298", "name": "Number of scheduled services monitored", "ref_number": "AT-15298"}, {"attribute_display_order_id": 9, "db_format": "DOUBLE", "db_name": "# ontime (ArrDep|tp)", "definition": "Number of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points.", "id": "15295", "name": "Number of services ontime", "ref_number": "AT-15295"}, {"attribute_display_order_id": 10, "db_format": "DOUBLE", "db_name": "# not ontime (ArrDep|tp)", "definition": "Number of services arriving more than 4 minutes and 59 seconds late or departing more than 59 seconds early at timing points.", "id": "15294", "name": "Number of services not ontime", "ref_number": "AT-15294"}, {"attribute_display_order_id": 11, "db_format": "DOUBLE", "db_name": "# punctuality events (ArrDep|tp)", "definition": "Number of punctuality events monitored", "id": "15297", "name": "Number of punctuality events delivered", "ref_number": "AT-15297"}, {"attribute_display_order_id": 12, "db_format": "DOUBLE", "db_name": "# loaded", "definition": "Number of journeys loaded in Smartrak bus tracking system.\n\nNote: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report.", "id": "15300", "name": "Number of services loaded in bus tracking system", "ref_number": "AT-15300"}, {"attribute_display_order_id": 13, "db_format": "DOUBLE", "db_name": "# allocated", "definition": "Number of journeys allocated in the Smartrak bus tracking system.\n\nNote: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report.", "id": "15299", "name": "Number of services allocated in bus tracking system", "ref_number": "AT-15299"}] |
|---|