SIST-TS CEN/TS 17118:2025
(Main)Intelligent transport systems - Public transport - Open API for distributed journey planning
Intelligent transport systems - Public transport - Open API for distributed journey planning
The Technical Specification will be adapted in the following way:
• OJP will be realigned with the latest Transmodel version and NeTEx issues, where appropriate (e.g.
New Modes)
• The integration of new modes especially the conceptual equivalency to major multi-modal standards
shall be studied and if necessary, adaptions to OJP occur. The idea is to study OSDM, TOMP, TRIAS
and GBFS/GOFS. The interactions should be smooth. Interaction between OJP and distribution
features will be settled.
• OJP is extended as far into the distribution area as it is considered a good idea. For the actual
booking and purchase steps, OSDM, TOMP, TRIAS and/or GOFS are to be used. The line we think to
draw is: booking. OJP should not transfer personalized information. This results in the following
proposed adaptions to fit OJP into a full MaaS roaming environment:
o An availability request (with response)
o Token/id handling for trips and trip legs (for hand-over) and pushed information during trips. We will
need to model bookable items on some level.
o OJPFare needs to be extended/adapted.
o TripInfoRequest and -Response need to be updated to reflect, information about trips and trip legs
and not only vehicle and journey.
• All work prepared under the heading OJP 1.1 will be finalised.
• EPIAP (Accessibility) minimal profile will be used to verify that the trip planning can make use of it.
• The provision of an OpenAPI and REST/JSON derived directly from the XSD shall be studied
(eventually using a converter).
Intelligente Verkehrssysteme - Öffentlicher Verkehr - Offene API für verteilte Reiseplanung
Inteligentni transportni sistemi - Javni potniški promet - Odprt API za načrtovanje porazdeljenih poti
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-maj-2025
Nadomešča:
SIST-TS CEN/TS 17118:2018
Inteligentni transportni sistemi - Javni potniški promet - Odprt API za načrtovanje
porazdeljenih poti
Intelligent transport systems - Public transport - Open API for distributed journey
planning
Intelligente Verkehrssysteme - Öffentlicher Verkehr - Offene API für verteilte
Reiseplanung
Ta slovenski standard je istoveten z: CEN/TS 17118:2024
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
CEN/TS 17118
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
December 2024
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 17118:2017
English Version
Intelligent transport systems - Public transport - Open API
for distributed journey planning
Intelligente Verkehrssysteme - Öffentlicher Verkehr -
Offene API für verteilte Reiseplanung
This Technical Specification (CEN/TS) was approved by CEN on 26 May 2024 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17118:2024 E
worldwide for CEN national Members.
Contents Page
European foreword . 12
0 Introduction . 13
0.1 General . 13
0.2 An Open API for distributed journey planning (OJP) . 13
0.3 The public transport information tensions . 13
0.4 Distributed journey planning architecture beyond scope . 14
0.4.1 General . 14
0.4.2 The distributed journey planning approach . 14
0.4.3 Distributed or centralised approaches . 15
0.4.4 The basis for the Open API . 15
0.4.5 Other possible uses for the Open API . 16
0.5 The European ITS Directive . 16
1 Scope . 17
2 Normative references . 17
3 Terms and definitions . 17
3.1 Terms used in OJP schema . 17
3.2 Terms in OJP Schema . 33
4 Symbols and abbreviations . 34
5 Use cases . 35
5.1 General . 35
5.2 Key tasks for Distributed Journey Planning . 37
5.2.1 Planning of a trip . 37
5.2.2 Discovering relevant stops . 38
5.2.3 Obtaining information about accessibility and services for those with special needs . 38
5.2.4 Seeking route information that can be displayed on maps . 38
5.2.5 Refine a trip . 38
5.2.6 Changing a Trip . 39
5.3 Additional tasks for a Distributed Journey Planning system . 39
5.3.1 Requesting a stop timetable . 39
5.3.2 Requesting times and other information for all intermediate stops in a trip. 40
5.3.3 Requesting expected events at a particular stop . 40
5.3.4 Requesting information about a given journey or vehicle . 40
5.3.5 Requesting information about the fares and ticket options for a particular trip . 40
5.3.6 Requesting information about lines . 40
5.3.7 Requesting information about availability of journeys/vehicles . 40
5.3.8 Other possible questions . 41
5.4 Advanced concepts/considerations . 41
5.4.1 Routing for passengers with special needs. 41
5.4.2 Via, fixed legs . 42
5.4.3 User preferences . 43
5.4.3.1 Definition . 43
5.4.3.2 Usage . 43
5.4.3.3 Good user preferences . 43
5.4.3.4 Mechanism . 44
5.4.3.5 Suggested user preferences. 44
5.4.4 IncludeAlternativeOptions in trips . 47
5.4.5 Handling of slow traffic . 47
5.4.6 Demand responsive transport . 48
5.4.6.1 Relevant mode . 49
5.4.6.2 Handling demand responsive buses in the stop event service . 49
5.4.7 Formations, Occupancy and Capacity . 50
5.4.8 International ServiceJourney (mainly trains). 51
5.4.9 Interaction OJP with fare calculating systems and reservation systems . 52
6 System architectures, metadata and data . 52
6.1 General . 52
6.2 General considerations – distributed planning . 52
6.3 Modular interface construction . 54
6.4 General considerations – pipelines . 55
6.5 Responsibility of a Distributing System to find gaps/overlaps in the results and to
correct them . 55
6.6 Metadata requirements . 55
6.7 Core data requirements . 56
6.7.1 Locations . 56
6.7.2 Topographic map . 57
6.7.3 Timetables . 57
6.7.4 Fares and booking information . 57
6.7.5 Other modes . 57
7 Open API for distributed journey planning – OJP services . 58
7.1 Identification of objects beyond system borders . 58
7.1.1 General . 58
7.1.2 Stops and Stopping Points . 58
7.1.3 Localities and Districts . 59
7.1.4 Addresses and POIs . 59
7.1.5 Organisations: transport companies and transport authorities . 59
7.1.6 Lines and line directions . 60
7.1.7 Journeys . 61
7.1.8 Vehicles . 61
7.1.9 Operating days . 61
7.1.10 Owners . 61
7.1.11 Stop and vehicle equipment.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.