JourneyWeb allows two or more journey planning engines with knowledge of different areas or transport modes to carry out distributed journey planning, that is to dynamically combine data from both servers to build up composite journeys that span the respective areas covered by the different engines.

JourneyWeb depends on NaPTAN, the UK standard for identifying stops, stations and other access points to Public Transport.

How is JourneyWeb used?

JourneyWeb is a request/response protocol: each exchange of data consists of a request message and a response message. Both journey planners are peers - they can both initiate queries by sending a request. The messages consist of XML documents, whose tags and content are exactly specified by the JourneyWeb Schema.

The JourneyWeb protocol supports six basic types of travel information request between journey planning systems
Request Purpose Version
POINTS Returns a list of remote stops for a NPTG locality or coordinate 1.0
JOURNEYS Calculates a journey between combinations of stops 1.0
LEG DETAILS Returns details about specific Journey Legs 2.4
TIMETABLES Returns a matrix of timetable data suitable for producing columnar timetables. 2.1
STOPEVENTS Returns departures for a stop at a specified time. Responses can include real time as well as scheduled information. 2.1
SERVICES Returns a list of services for which the remote journey planner can return timetables. 2.1
OPERATORS Returns the transport operators supported by the remote journey planner. 2.1

The JourneyWeb Schema also includes additional response messages to handle error conditions.

Compliance levels

Not all journey planners will necessarily support all the features of JourneyWeb. The different named features that can be supported are systematically identified as distinct modules in the 'Compliance' section of the Documentation.

Page last updated: 2013/03/25