Data Catalogue
The data catalogue zip contains a series of CSVs which gives a machine-readable overview of all the data that resides in BODS currently.
Note that the data catalogue only covers the data from primary data sources on BODS which is timetables data in TransXChange format, bus location data in SIRI-VM format and fares data in NeTEx format. Other non-primary data on BODS (e.g GTFS converted forms) are not represented on the data catalogue.
The data catalogue zip contains 7 distinct CSVs:
- Overall data catalogue: this contains a high-level overview of all the static data on BODS: timetables and fares data.
- Timetables data catalogue: this contains a detailed granular view of the timetables data within BODS. It also contains a detailed mapping of the BODS timetables data with the data from the Office of the Traffic Commissioner (OTC).
- Fares data catalogue: this contains a detailed granular view of the fares data within BODS.
- Disruptions data catalogue: this contains a detailed view of all of the disruptions active and pending within BODS.
- Organisations data catalogue: this contains helpful counts of data at an organisation level.
- Location data catalogue: this contains an overview of the location data within BODS.
- Operator NOC data catalogue: this describes all organisations on BODS and the National Operator Codes (NOCs) that are associated with them.
Field definitions:
The data catalogue contains certain fields the definitions and explanations of which can be found below.
Overall data catalogue:
| Field name | Definition |
|---|---|
| Operator | The name of the operator/publisher providing data on BODS. |
| Operator ID | The internal BODS generated ID of the operator/publisher providing data on BODS. |
| Profile NOCs | The National Operator Codes for the particular publisher as extracted from their BODS profile. |
| Data Type | The type of data being published. |
| Status | The publication status of the data set/feed. |
| Last Updated | The date that the data set/feed was last updated on BODS. |
| File Name | The exact name of the file provided to BODS. This is usually generated by the publisher or their supplier |
| XML File Name | The value of the FileName attribute in the TransXChange or NeTEx file. |
| Data Set/Feed Name | The internal BODS generated data set name given for a particular data set. |
| Data ID | The internal BODS generated ID of the data set / feed provided to BODS. |
| Mode | The mode of transport as extracted from the TransXChange file they provided. |
| National Operator Code | The National Operator Code(s) for the particular publisher as extracted from the TransXChange or NeTEx file they provided. |
| Service Code | The ServiceCode for the particular publisher as extracted from the TransXChange file they provided. |
| Line Name | The line name(s) for the particular publisher as extracted from the TransXChange or NeTEx file they provided. |
| Licence Number | The License number(s) as extracted from the files provided by the operator/publisher to BODS. |
| Public Use Flag | The Public Use Flag element as extracted from the files provided by the operator/publisher to BODS. |
| Revision Number | The service revision number date as extracted from the files provided by the operator/publisher to BODS. |
| Operating Period Start Date | The operating period start date as extracted from the files provided by the operator/publisher to BODS. |
| Operating Period End Date | The operating period end date as extracted from the files provided by the operator/publisher to BODS. |
| % AVL to Timetables feed matching score | The latest score for the active AVL feed this row belongs to (Data ID). |
| Latest matching report URL | This will be the same report url as the AVL data feed page report url from the dataset review page. |
Timetables data catalogue:
| Field name | Definition |
|---|---|
| XML:Service Code | The ServiceCode(s) as extracted from the files provided by the operator/publisher to BODS. |
| XML:Line Name | The line name(s) as extracted from the files provided by the operator/publisher to BODS. |
| Requires Attention | No: Default state for correctly published services, will be “No” unless any of the logic below is met. Yes: Yes If OTC status = Registered and Scope Status = In scope and Seasonal Status ≠ Out of season and Published Status = Unpublished. Yes if OTC status = Registered and Scope Status = In scope and Seasonal Status ≠ Out of season and Published Status = Published and Timeliness Status ≠ Up to date. |
| Published Status | Published: Published to BODS by an Operator/Agent. Unpublished: Not published to BODS by an Operator/Agent. |
| OTC Status | Registered: Registered and not cancelled within the OTC database. Unregistered: Not Registered within the OTC. |
| Scope Status | In scope: Default status for services registered with the OTC and other enhanced partnerships. Out of Scope: Service code has been marked as exempt by the DVSA or the BODS team. |
| Seasonal Status | In season: Service code has been marked as seasonal by the operator or their agent and todays date falls within the relevant date range for that service code. Out of Season: Service code has been marked as seasonal by the operator or their agent and todays date falls outside the relevant date range for that service code. Not Seasonal: Default status for published or unpublished servicesto BODS. Assumed Not seasonal unless service code has been marked with a date range within the seasonal services flow. |
| Timeliness Status | Up to date: Default status for service codes published to BODS. Timeliness checks are evaluated in this order: 1) OTC Variation not published: If 'XML:Last modified date' is earlier than 'Date OTC variation needs to be published' and 'Date OTC variation needs to be published'is earlier than today's date. and No associated data has been published. NB there are two association methods: Method 1: Data for that service code has been updated within 70 days before the OTC variation effective date. Method 2: Data for that service code has been updated with a 'XML:Operating Period Start Date' which equals OTC variation effective date. 2) 42 day look ahead is incomplete: If not out of date due to 'OTC variation not published' and 'XML:Operating Period End Date' is earlier than 'Date for complete 42 day look ahead'. 3) Service hasn't been updated within a year: If not out of date due to '42 day lookahead is incomplete' or 'OTC variation not published' and 'Date at which data is 1 year old' is earlier than today's date. |
| Organisation Name | The name of the operator/publisher providing data on BODS. |
| Data set ID | The internal BODS generated ID of the dataset that contains the data for this row. |
| Date OTC variation needs to be published | OTC:Effective date from timetable data catalogue minus 42 days. |
| Date for complete 42 day look ahead | Today's date + 42 days. |
| Date when data is over 1 year old | 'XML:Last Modified date' from timetable data catalogue plus 12 months. |
| Date seasonal service should be published | If Seasonal Start Date is present, then Seasonal Start Date minus 42 days, else null. |
| Seasonal Start Date | If service has been assigned a date range from within the seasonal services flow, then take start date, else null. |
| Seasonal End Date | If service has been assigned a date range from within the seasonal services flow, then take end date, else null. |
| XML:Filename | The exact name of the file provided to BODS. This is usually generated by the publisher or their supplier. |
| XML:Last Modified Date | Date of last modified file within the service codes dataset. |
| XML:National Operator Code | The National Operator Code(s) as extracted from the files provided by the operator/publisher to BODS. |
| XML:Licence Number | The License number(s) as extracted from the files provided by the operator/publisher to BODS. |
| XML:Public Use Flag | The Public Use Flag element as extracted from the files provided by the operator/publisher to BODS. |
| XML:Revision Number | The service revision number date as extracted from the files provided by the operator/publisher to BODS. |
| XML:Operating Period Start Date | The operating period start date as extracted from the files provided by the operator/publisher to BODS. |
| XML:Operating Period End Date | The operating period end date as extracted from the files provided by the operator/publisher to BODS. |
| OTC:Origin | The origin element as extracted from the files provided by the operator/publisher to BODS. |
| OTC:Destination | The destination element as extracted from the files provided by the operator/publisher to BODS. |
| OTC:Operator ID | The operator ID element as extracted from the OTC database. |
| OTC:Operator Name | The operator name element as extracted from the OTC database. |
| OTC:Address | The address as extracted from the OTC database. |
| OTC:Licence Number | The licence number element as extracted from the OTC database. |
| OTC:Licence Status | The licence status element as extracted from the OTC database. |
| OTC:Registration Number | The registration number element as extracted from the OTC database. |
| OTC:Service Type Description | The service type description element as extracted from the OTC database. |
| OTC:Variation Number | The variation number element as extracted from the OTC database. |
| OTC:Service Number | The service number element as extracted from the OTC database. |
| OTC:Start Point | The start point element as extracted from the OTC database. |
| OTC:Finish Point | The finish point element as extracted from the OTC database. |
| OTC:Via | The via element as extracted from the OTC database. |
| OTC:Granted Date | The granted date element as extracted from the OTC database. |
| OTC:Expiry Date | The expiry date element as extracted from the OTC database. |
| OTC:Effective Date | The effective date element as extracted from the OTC database. |
| OTC:Received Date | The received date element as extracted from the OTC database. |
| OTC:Service Type Other Details | The service type other details element as extracted from the OTC database. |
| Traveline Region | The Traveline Region details element as extracted from the OTC database. |
| Local Transport Authority | The Local Transport Authority element as extracted from the OTC database. |
Fares data catalogue:
| Field name | Definition |
|---|---|
| Dataset ID | The internal BODS generated ID of the operator/publisher providing data on BODS. |
| XML file name | The exact name of the file provided to BODS. This is usually generated by the publisher or their supplier. |
| Organisation Name | The name of the operator/publisher providing data on BODS. |
| National Operator Code | The National Operator Code(s) for the particular publisher as extracted from the NeTEx file they provided. |
| Operator ID | The internal BODS generated ID of the operator/publisher providing data on BODS. |
| BODS Compliant | The validation status and format of the files provided by the operator/publisher to BODS. |
| Last updated date | The date that the data set/feed was last updated on BODS. |
| Valid from | The operating period start date as extracted from the files provided by the operator/publisher to BODS. |
| Valid to | The operating period end date as extracted from the files provided by the operator/publisher to BODS. |
| Line ids | The Line id(s) as extracted from the files provided by the operator/publisher to BODS. |
| Line Name | The line name(s) as extracted from the files provided by the operator/publisher to BODS. |
| ATCO Area | The ATCO Area (s) extracted from the ScheduledStopPoints in the files provided by the operator/publisher to BODS. |
| TariffBasis | The TariffBasis element as extracted from the files provided by the operator/publisher to BODS. |
| ProductType | The ProductType element as extracted from the files provided by the operator/publisher to BODS. |
| ProductName | The Name element within PreassignedFareProduct as extracted from the files provided by the operator/publisher to BODS. |
| UserType | The origin element as extracted from the files provided by the operator/publisher to BODS. |
| Multioperator | Status derived from comparing the BODS organisation of publisher and the National Operator Codes extracted from the files provided by the operator/publisher to BODS. |
Disruptions data catalogue:
| Field name | Definition |
|---|---|
| Organisation | The name of the organisation publishing the disruptions data. |
| Situation Number | The internal BODS generated ID of the disruption. |
| Validity Start Date | The start date of the disruption provided by the publisher to BODS. |
| Validity End Date | The end date of the disruption provided by the publisher to BODS. |
| Publication Start Date | The start date of the publication window for the disruption provided by the publisher to BODS. |
| Publication End Date | The end date of the publication window for the disruption provided by the publisher to BODS. |
| Reason | The reason for the disruption provided by the publisher to BODS. |
| Planned | The planned or unplanned nature of the disruption provided to the publisher to BODS. |
| Modes Affected | The modes of public transport affected by the disruption. |
| Operators Affected | The operators of services affected by the disruption. |
| Services Affected | The total number of services affected by the disruption. |
| Stops Affected | The total number of stops affected by the disruption. |
Organisations data catalogue:
| Field name | Definition |
|---|---|
| Name | The name of the operator/publisher providing data on BODS |
| Status | The registration status of the operator/publisher on BODS. 'Active' are signed up on BODS, 'Inactive' no longer have functioning accounts on BODS, 'Pending Invite' still haven't signed up and 'Not yet invited' have been added to BODS but not yet invited to complete the full sign up procedure |
| Date Invite Accepted | The date at which the operator/publisher accepted their invite and signed up |
| Organisation creation date | The date at which the Operator/publisher organisation are added to BODS which may or may not be the same date as the invited date. |
| Date Invited | The date at which they were originally invited to sign up to BODS |
| Last Log-In | The last time there was activity for the operator/publisher on BODS. |
| Permit Holder | The permit status as declared by operator/publisher in the Organisation profile section on BODS (Permit holder is 'Yes' if the user clicks the tickbox of 'I don't have a PSV license number') |
| National Operator Codes | The National Operator Codes of the operator/ publisher as declared by them in the Organisation Profile section on BODS. |
| Licence Numbers | The Licence number(s) of the operator/publisher as declared by them in the Organisation Profile section on BODS. |
| Number of Licences | The total count of services of the operator/publisher as declared by them in the Organisation Profile section on BODS. This informs us to understand the total number of licence numbers the organisation is representing. |
| Unregistered Services | The total number of unregistered services (UZ declared in ServiceCode field) are published in total by the operator/publisher to BODS. |
| OTC Registered Services | The total count of services of the operator/publisher as extracted from the database of the Office of the Traffic Commissioner (OTC). This informs us to understand the total number of services expected to be published from the licences associated in the organisational profile. |
| Out of scope services(exempted) | The total number of registered services that have been marked as exempt from publishing to BODS by the DVSA/DfT admin user. |
| Registered Services in scope(for BODS) | The total number of in scope, registered services for the organisation that require data in BODS |
| Registered Services Published | The total number of registered services that an organisation has published. |
| Compliant Registered Services Published | The total number of compliant, in scope, registered services are published in total by the operator/publisher to BODS. |
| % Compliant Registered Services Published | The percentage of an organisation's in scope, registered services that are PTI compliant. |
| Number of School or Works Services | The total count of school or works services of the operator/publisher as extracted from the database of the Office of the Traffic Commissioner (OTC). This informs us to understand the total number of services expected to be published from the licences associated in the organisational profile that are 'School or Works'. |
| School or Works Services Subsidised | The total count of school or works services that are subsidised for the operator/publisher as extracted from the database of the Office of the Traffic Commissioner (OTC). This informs us to understand the total number of services expected to be published from the licences associated in the organisational profile that are 'School or Works' and are fully subsidised (Yes). |
| School or Works Services Subsidised In Part | The total count of school or works services that are subsidised in part for the operator/publisher as extracted from the database of the Office of the Traffic Commissioner (OTC). This informs us to understand the total number of services expected to be published from the licences associated in the organisational profile that are 'School or Works' and are in part subsidised (In Part). |
| Flexible Registration | The total count of flexible services for the operator/publisher as extracted from the database of the Office of the Traffic Commissioner (OTC). This informs us to understand the total number of services expected to be published from the licences associated in the organisational profile that are 'Flexible' services, so we can prepare organisations for this technical implementation. |
| Number of Published Services with Valid Operating Dates | The total number of services published on BODS that have a valid operating period today. |
| Additional Published Services with Future Start Date | The total number of additional published services that have future start dates on BODS. This informs us to understand the additional number of new services codes that will become valid in the future, which is just a difference to the total already provided, to give an indicator to services that are published but not valid now. |
| Number of Published Timetable Datasets | The total number of published timetables datasets provided by the operator/publisher to BODS. |
| Number of Published AVL Datafeeds | The total number of published location data feeds provided by the operator/publisher to BODS. |
| Number of Published Fare Datasets | The total number of published fares datasets provided by the operator/publisher to BODS. |
| % Compliant Published Fare Datasets | The percentage of an organisation's published fare datasets that are BODS compliant. |
| Number of Pass Products | The total number of pass products as extracted from the files provided by the operator/publisher to BODS. |
| Number of Trip Products | The total number of trip limited products as extracted from the files provided by the operator/publisher to BODS. |
| % Operator overall AVL to Timetables matching score | The overall score for an operator as per ‘Review my location data’ blue dashboard for an operator. |
| Archived matching reports URL | The same archived reports url as the ‘Review my location data’ blue dashboard for an operator in Download all archived matching reports. |
Location data catalogue:
| Field name | Definition |
|---|---|
| Organisation Name | The name of the operator/publisher providing data on BODS. |
| Datafeed ID | The internal BODS generated ID of the operator/publisher providing data on BODS. |
| % AVL to Timetables feed matching score | This will be the latest score for the AVL feed this row belongs to (Data ID). |
| Latest matching report URL | This will be the same report url as the AVL data feed page report url from the dataset review page. |
Operator NOC data catalogue:
| Field name | Definition |
|---|---|
| Operator | The name of the operator on BODS. |
| NOC | The National Operator Code (NOC) that is associated with that operator on BODS. |