Skip to content

VDVde/OJP

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

a89e516 · Dec 20, 2022

History

83 Commits
Dec 15, 2022
Dec 20, 2022
Dec 16, 2022
Nov 23, 2020
Nov 23, 2020
Aug 25, 2021
Jul 14, 2021
Dec 7, 2020
Dec 15, 2022

Repository files navigation

OJP - Open API for distributed Journey Planning

Content

This repository contains the XSD, examples and documentation tables for the "Open API for distributed Journey Planning" published as "CEN/TS 17118:2017: "Intelligent transport systems - Public transport - Open API for distributed journey planning".

OJP consists of a set of services that can be addressed using HTTP requests.

The main services to request information are:

  • Place Information
  • Stop Events (arrival and departure boards)
  • Searching for Trips
  • Information about a given Trip
  • Information about Fares for Trips

OJP systems interacting with each other additionally use:

  • Getting information about Exchange Points (places when a Trip switches from one OJP system to another)

Standard document

Obtain a copy of the standard document "CEN/TS 17118:2017: "Intelligent transport systems - Public transport - Open API for distributed journey planning" at CEN.

Repository

Download the XSD schema files and examples in the git repository found at https://github.com/VDVde/OJP and take a look at the documentation tables.

Regulatory environment of OJP

The ITS Directive Delegated Regulation for provision of EU-wide multimodal travel information services is the legal framework for travel data access and distributed journey planning in Europe. This initiative will provide the necessary requirements to make EU-wide multimodal travel information services accurate and available across borders. One of the key requirements concerns linking travel information services for distributed journey planning. Upon request, travel information service providers shall provide to another information service provider "routing results" based on static, and where possible, dynamic information. The "routing results" shall be based on:

  • the enquirers start and end points of a journey along with the specific time and date of departure or arrival, or both;
  • possible travel options along with the specific time and date of departure or arrival, or both, including any possible connections;
  • the handover point between travel information services;
  • in case of disturbances, alternative possible travel options along with the specific time and date of departure or arrival, or both, and any connections, where available.

The Delegated Regulation recommends that the CEN OPEN API standard for distributed journey planning is used by local, regional and national travel information service providers.