Data Terminology Catalogue

The structure for providing StopPointRef data in TransXChange.

This allows for the inclusion of the data elements from NaPTAN. 

StopPointRef minimum requirements are StopPointRef and CommonName.

The definition of a service, as stated in the introduction to this section, is that it is a collection of lines that together make up a coherent set of vehicle journeys.

For example a service consisting of line 1 and line 1A, highlighting one use case of two lines operated by the same operator.

However, there is a second class of service, which is one that is operated by multiple operators.

For example, many services are operated as commercial services by operators Monday to Saturday, from early morning through to early evening, with local authorities then contracting a second operator to run evening trips, or trips on Sundays. Another example is a quality partnership, such as is found in Oxford, with two operators alternating trips on the same line to provide a high frequency service to passengers. In both these cases, the two operators’ individual services together make up the overall service that the passenger sees. 

In order to ensure, as far as possible, that the linkage between the different operators’ services is maintained, use should be made within TXC-PTI of the facilities to identify the alternate operators and the alternate services.

This is also a suitable mechanism for a single operator to use where there is a split registration with different sections in separate documents based on registrations, and where the operator wishes to indicate that they are linked. 
Within Service, this linkage can be shown using the AssociatedOperators element, which identifies the operator(s) that are linked, and ToBeMarketedWith, which identifies the service(s) that should be linked.