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 disruptions data or GTFS converted forms) are not represented on the data catalogue.
The data catalogue zip contains 4 distinct CSVs:
- Overall data catalogue: this contains a high-level overview of all timetables data on BODS.
- 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).
- Organisations data catalogue: this contains helpful counts of data at an organisation level: which is at the level of the publishing operators (e.g. overall service data)
- Location data catalogue: this contains an overview of the location data within BODS.
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 |
| TXC File Name | The value of the FileName attribute in the TransXChange 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 Codes for the particular publisher as extracted from the TransXChange file they provided. |
| Service Code | The ServiceCode for the particular publisher as extracted from the TransXChange file they provided. |
| Line Name | The linename for the particular publisher as extracted from the TransXChange file they provided. |
Timetables data catalogue:
| Field name | Definition |
|---|---|
| Requires Attention | No: Default state for correctly published services, will be “No” unless any of the logic below is met. Yes: Yes IF Staleness Status does not equal “Not Stale”. Yes IF Published Status = Unpublished and OTC status = Registered and Scope Status = In scope and Seasonal Status = Not Seasonal. Yes IF Published Status = Unpublished and OTC status = Registered and Scope Status = In scope and Seasonal Status = In season. |
| 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 published or unpublished services to BODS. Assumed in scope unless marked as exempt in the service code exemption flow. Out of Scope: Service code has been marked as exempt by the DVSA in the service code exemption flow. |
| Seasonal Status | In season: Service code has been marked with a date range within the seasonal services flow and the date from which the file is created falls within the date range for that service code. Out of Season: Service code has been marked with a date range within the seasonal services flow and the date from which the file is created falls outside the date range for that service code. Not Seasonal: Default status for published or unpublished services to BODS. Assumed Not seasonal unless service code has been marked with a date range within the seasonal services flow. |
| Staleness Status | Not Stale: Default status for service codes published to BODS. Stale - End date passed: If 'Effective stale date due to end date' (if present) is sooner than 'Effective stale date due to effective last modified date' and today’s date from which the file is created equals or passes 'Effective stale date due to end date' and Last modified date < OTC Effective start date - FALSE. Stale - 12 months old: If 'Effective stale date due to effective last modified' date is sooner than 'Effective stale date due to end date' (if present) and today’s date from which the file is created equals or passes 'Effective stale date due to effective last modified date' and Last modified date < OTC Effective start date - FALSE. Stale - OTC Variation: If Last modified date < 'Effective stale date due to OTC effective date' - TRUE and Today’s date greater than or equal to than 'Effective stale date due to OTC effective date'. |
| Organisation Name | The name of the operator/publisher providing data on BODS. |
| Dataset ID | The internal BODS generated ID of the operator/publisher providing data on BODS. |
| DQ Score | The DQ score assigned to the publisher’s data set as a result of the additional data quality checks done on timetables data on BODS. |
| BODS Compliant | The validation status and format of timetables data. |
| Last Updated Date | The date that the data set/feed was last updated on BODS |
| Last Modified Date | Date of last modified file within the service codes dataset. |
| Effective Last Modified Date | Equal to Last Modified Date. |
| XML Filename | The exact name of the file provided to BODS. This is usually generated by the publisher or their supplier |
| Licence Number | The License number(s) as extracted from the files provided by the operator/publisher to BODS. |
| National Operator Code | The National Operator Code(s) as extracted from the files provided by the operator/publisher to BODS. |
| Service Code | The ServiceCode(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. |
| 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. |
| Effective stale date due to end date | If end date exists within the timetable file Then take end date from TransXChange file minus 42 days. |
| Effective stale date due to effective last modified date | Take 'Effective Last Modified date' from timetable data catalogue plus 12 months. |
| Last modified date < Effective stale date due to OTC effective date | If last modified date is less than Effective stale date due to OTC effective date Then TRUE Else FALSE. |
| Effective stale date due to OTC effective date | Effective date” (timetable data catalogue) minus 70 days. |
| Effective Seasonal Start Date | 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. |
| Service Revision Number | The service revision number date 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. |
| Origin | The origin element as extracted from the files provided by the operator/publisher to BODS. |
| Destination | The destination element as extracted from the files provided by the operator/publisher to BODS. |
| Operator ID | The operator ID element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Operator Name | The operator name element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Address | The address as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| OTC Licence Number | The licence number element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Licence Status | The licence status element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Registration Number | The registration number element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Service Type Description | The service type description element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Variation Number | The variation number element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Service Number | The service number element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Start Point | The start point element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Finish Point | The finish point element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Via | The via element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Granted Date | The granted date element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Expiry Date | The expiry date element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Effective Date | The effective date element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Received Date | The received date element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
| Service Type Other Details | The service type other details element as extracted from the database of the Office of the Traffic Commissioner (OTC) |
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. |
| Number of Fare Products | The total number of fares products found in the fares data provided by the operator/publisher to BODS. |
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 |
| Feed Compliance Status | The compliance status of data feed on BODS as a result of the SIRI-VM validation checks done on BODS to check for the mandatory SIRI-VM profile elements |
| Compliance Report URL | The link to the exact report generated as a result of the SIRI-VM validation check done on BODS. The results of the validation check can be viewed here |
Previous
Quick start
Next
Data by operator or location