Public transport network and stop place model and its importance for multimodal information systems THNS - Shanghai, November 202 Kasia Bourée
Outline. Introduction 2. Main CEN Data & Interface Standards for Public Transport 3. Public Transport Network and Stop Model Use Cases & Projects: Management information & statistics User Information: Inter-regional / multimodal trip planning Stop place information: stop representation accessibility Passenger guidance Stop identification 4. Conclusion & Invitation THNS, Shanghai, November 202 2
Inter-System Exchanges & Multi-Source Data: Need for Unambgious Data Standard Data Models (Transmodel/IFOPT) Interfaces (NeTEx/SIRI) Introduction 3
Main Standardisation Organisations & Structure WORLD-WIDE Also: IEC : International Electrotechnical Commission ITU: International Telecommunications Union EUROPE-WIDE Also: ETSI, CENELEC Standardisation Organisational Aspects 4
Documentation Types and Characterisitcs Result of standardisation: textual documentation (e.g. functional specification of a system, terminology, data model specification, interface specification, etc) Standards are in general not mandatory (except a small percentage) Have a different status than regulations/directives which are mandatory Directives sometimes recommend the use of norms: this is the case for the CEN norm Transmodel and the European Directve for Rail Standardisation Organisational Aspects 5
Standardisation Topics in CEN Working Group Dedicated to Public Transport SIRI : Service Interface for Realtime Information NeTEx: Network & Timetable Exchange DJPS: Distributed Journey Planning (planned) TI-VIP: Traveller Information for Visually Impaired (dormant) TC278 WG3 Public Transport Inter-system communication Functional models Data models Transmodel: Reference Data Model for PT IFOPT: Fixed Objects for PT ISO/ CEN: Geographic Data models Integrated Fare Management Standardisation Organisational Aspects 6
Reminder: Data Modelling Levels Three main steps: Semantics of a domain Hardware Independent No redundancy UML :Unified Modelling Language CONCEPTUAL DATA MODEL Additional attributes Data formats LOGICAL DATA MODEL Choice of a DBMS Controlled denormalization optimisations & redundancies Organisational rules PHYSICAL DATA MODEL Application Application Application Data Standards: Transmodel 7
Reminder: UML Formalism for Data Models Semantics of a domain -a reference for 0.. -referencing to * -id[] -name POINT -start of -end of * -from * -to +id[] -length LINK A link between two points (here stop points) Data Standards: Transmodel 8
Transmodel to Solve System Complexity & Lack of Interoperability Complex System Architecture TRANSMODEL based System Architecture Numerous inter-application links Information system complexity lack of interoperability proprietary applications lack of open, common system specifications Common data structure Allows for a progressive migration Opens the market Reduces development costs Considers intermodality & multi-operators Is hardware independent Considers a variety of practices Transmodel: Conceptual & Static Data Standards: Transmodel 9
Transmodel Philosophy Application User B User 2 Application A C User 5 Application Concept User 3 User 4 Application E D Application Data Standards: Transmodel 0
Field Trial in Lyon/France: TITAN project Stop Point Management Scheduling (vehicle+driver) Schedule Assignment, Budget Management Data Access System Passenger information (telematic and telephone servers, displays) TITAN Data Base Transmodel On-line Control System Production follow-up Personnel Disposition, Payroll Data Standards: Transmodel
Transmodel-based Implementations in UK Stops NaPTAN Places, Areas Nat Gazetteer Bus Timetables TransXChange Train Timetables RJIS CIF Points of Interest e.g. PointX Data Build Mapping OS MasterMap + ITN Layer Journey Planner Engines Real-Time Server JourneyWeb 2. Points Operators Services Journeys StopEvents Timetables StopEvents Client Transmodel: Common Abstract model Data Standards: Transmodel 2
A Robust Basis for Information System Architecture Contributors over 0 years: France UK Germany The Netherlands Spain Austria Italy Greece Sweden/Denmark Support of EC & French/German/Dutch Ministries http://www.normes-donnees-tc.org/spip.php?rubrique22 http://www.transmodel.org Data Standards: Transmodel 3
IFOPT: Stop Place Model Physical view Logical/macroscopic view IFOPT Bercy 4 Gare de Lyon Cour St Emilion Transmodel Details of a stop Global view of a stop Data Standards: IFOPT
IFOPT Complex Monomodal Stop Place IFOPT means: Identification of Fixed Objects for Public Transport Gives a precise definition of the concept STOP and its physical «reality»: Dedicated zone Quay Boarding position Vehicle stopping position Entrance Equipment & services Navigations paths IFOPT became recently a norm (EN) Data Standards: IFOPT 5
IFOPT Complex Multi-Modal Stop Place Transmodel STOP POINT is a view of the IFOPT STOP PLACE IFOPT Stop Model is multimodal Rail, coach, metro stations, bus stops, airports, etc. Example of an Airport (Paris Charles de Gaulle Courtesy of bonjourfrance) Data Standards: IFOPT 6
NeTEx Interfaces: Planned Information Exchange Planning System A: Network Timetables Fares NeTEx Planning System B: Network Timetables Fares Passenger Information System Automatic Vehicle Monitoring System NeTEx stands for Network and Timetable Exchange and is a TS Interface Standards: NeTEx 7
NeTEx Approach From Transmodel to NeTEx. Modularised: Transmodel Domain Model + harmonised with IFOPT 2. Created: a physical UML model: add attributes, formats, etc 3. Encoded: as XML schema Reusable, Modular subpackages Well defined dependencies Uniform versioning and data ownership model Validation with Examples of data from each country Interface Standards: NeTEx 8
SIRI : Real-Time Information Exchange Real-time vehicle location AVMS System SIRI Example of Use case: Estimated arrival time at stops NeTEx Passenger Information System Timetable Planning System Timetabled passing times NeTEx Estimated Vehicle Arrival Time Interface Standards: SIRI 9
SIRI Interfaces SIRI is for Real Time Information Exchange Structured into a range of services Common data transport layer SIRI is a TS Transmodel: PT model Stop Points, Vehicle Journeys, Lines, Journey Patterns, Vehicles, etc Production timetable Estimated timetable Stop timetable Stop monitoring Connection timetable Connection monitoiring Vehicle monitoring General Message Situation Management Facility Management Status SIRI : Common Services Pull Push Interface Standards: SIRI 20
Currently Known SIRI Users EU : Germany, France, Ireland, Norway, Sweden, UK Switzerland, Australia - considered Israel Canada, USA China (Shanghai) https://groups.google.com/group/siri-developers Interface Standards: SIRI 2
Transmodel + IFOPT => Standard PT Network Model The PT topology is a submodel of Transmodel: Line, Route, Route Point, Journey Pattern, Stop Point, Timing Point IFOPT: Stop Place & related concepts PT Network & Stop Model 22
Transmodel+IFOPT=> Standard PT Network Model class ISO Transmodel&IFOPT Network Basic MODEL (as in NeTEx) Route MODEL::LINE + Name :MultilingualString + ShortName :MultilingualString [0..] + Description :MultilingualString [0..] + LineUrl :any [0..] + Monitored :boolean [0..] «PK» + id :LineIdType +uses Route MODEL:: DIRECTION «PK» + Id :DirectionIdType +allowing for +used by+allowed 0..* for 0..* Route MODEL:: ALLOWED LINE DIRECTION LINK SEQUENCE Route MODEL:: ROUTE Serv ice Pattern MODEL::STOP POINT IN JOURNEY PATTERN Stop Assignment MODEL::STOP ASSIGNMENT + AlightingUse :boolean [0..] + StopAssignmentType :StopAssignmentIdTypeEnum [0..] + BoardingUse :boolean «PK» ~ id :StopAssignmentIdType +for 0..* 0..* subzone of +used as primary for +for 0..* +to 0.. STOP PLACE SPACE Stop Place MODEL:: QUAY +composed by +to 0.. +on +made up of..* +oriented by * 0.. +a part of 0..* STOP PLACE SPACE Stop Place MODEL:: BOARDING POSITION MODE Reusable Transport Mode MODEL:: VEHICLE MODE +primarily run by +for 0.. +the opposite of 0.. * +on +covered by * +the opposite of 0.. +made up of +defining * 0..* +made up of 0..* +operated by LINK SEQUENCE Journey Pattern MODEL::JOURNEY PATTERN +in +containing 0..* +operating +defined on +for 0..* +comprising Service Pattern MODEL:: SERVICE PATTERN «PK» + id :ServicePatternIdType * +viewed as +to +for +to 0..* * +a view of * +made up of +contributing to Serv ice Pattern MODEL::SCHEDULED STOP POINT + ShortName :MultilingualString [0..] + Description :MultilingualString [0..] + RequestStop :boolean + Label :MultilingualString [0..] + Url :abyuri [0..] + StopType :StopPlaceTypeEnum + ForAlighting :boolean + ForBoarding :boolean + ByRequest :boolean «PK» + id :ScheduledStopPointIdType 0..* Stop Place MODEL::STOP PLACE Generic Point & Link MODEL::LINK Generic Point & Link MODEL::POINT SITE + Weighting :integer [0..] + BorderCrossingPoint :boolean [0..] «PK» + id :StopPlaceIdType..* +a view of neighbour of 0..* +on Journey Pattern MODEL:: POINT IN JOURNEY PATTERN +viewed as +start +end of of Generic Point & Link Sequence MODEL::POINT IN LINK SEQUENCE Name: ISO Transmodel&IFOPT Network Basic MODEL (as in NeTEx) Author: NeTEx Version:.0 Created: 06/07/202 0:0:09 Updated: 04/09/202 8:06:5 * +from +to * * +viewed as +a view of * Service Pattern MODEL::STOP AREA + PublicCode :normalizedstring [0..] «PK» + id :StopAreaIdType TRANSFER Service Pattern MODEL:: CONNECTION «PK» ~ id :ConnectionIdType +from * +to * +start of+end of +viewed as +a view of +included in 0..* Service Pattern MODEL:: CONNECTION END..* +composed of 0.. UML Data Model: Description of a Public Transport Multimodal Network PT Network & Stop Model 23
What is the Use of a Network and Stop Model? Management Information Systems Multisource Data Collection by A PT Authority for statistics: A common reference model facilitates data aggregation Use Cases for a PT Network and Stop Model 24
What is the Use of a Network and Stop Model? Passenger Information (2) General Architecture of the CAMERA Project Data Entry PT data Tools - Bus Stop Points - Entranced - Path Links - Quays - Stairs - Lfts - Escalators Additional data IFOPT IFOPT-based CAMERA DB GIS 2D, 3D, WEB application Use Cases - Street Network - 2D / 3D Buildings - Green areas - Maps (i.a. pdf) INSPIRE Stop Place Representation In-door Passenger Guidance Accessibility for disabled PT search around a POI Stop Publication according to INSPIRE Use Cases for a PT Network and Stop Model 25
What is the Use of a Network and Stop Model? Passenger Information (3): navigation paths CAMERA: 2D/3D representations of complex stations no restriction restricted mobility wheelchair Navigation paths through complex stations according to mobility constraints Implementation of webservices: http://stationways.dryadebox.net Use Cases for a PT Network and Stop Model 26
What is the Use of a Network and Stop Model? Passenger Information (4) Stop Place maps for trip preparation : pilot stop places Use Cases for a PT Network and Stop Model 27
What is the Use of a Network and Stop Model? Passenger Information (5) Representation of Complex Stations Use Cases for a PT Network and Stop Model 28
What is the Use of a Network and Stop Model? Passenger Information (6) Virtual visit of Stop Places Use Cases for a PT Network and Stop Model 29
What is the Use of a Network and Stop Model? Passenger Information (7) Inter-regional Trip Planning A trip from Paris to the Swiss Alps may involve several systems and several modes: in order to correctly describe each part of the trip a common stop place identification is necessary. IFOPT indicates a method for such an unambigous identification. Use Cases for a PT Network and Stop Model 30
What is the Use of a Network and Stop Model? Network Planning & Management: Stop Identification Method to build clusters of physical stops (STOP PLACEs) Systematic built of IDs stop «numbering» method Example: Project of the Greater Paris Region (PT Authority STIF) Use Cases for a PT Network and Stop Model 3
What is the Use of a Network and Stop Model? Multi-Modal On-board Information Private Car/Public Transport (ISO) Currently discussed at ISO NeTEx for planned SIRI for RT info Use Cases for a PT Network and Stop Model 32
class ISO Transmodel&IFOPT Network Basic MODEL (as in NeTEx) Route MODEL::LINE + Name :MultilingualString + ShortName :MultilingualString [0..] + Description :MultilingualString [0..] + LineUrl :any [0..] + Monitored :boolean [0..] «PK» + id :LineIdType +uses Route MODEL:: DIRECTION «PK» + Id :DirectionIdType +allowing for +used by+allowed 0..* for 0..* Route MODEL:: ALLOWED LINE DIRECTION LINK SEQUENCE Route MODEL:: ROUTE Serv ice Pattern MODEL::STOP POINT IN JOURNEY PATTERN Stop Assignment MODEL::STOP ASSIGNMENT + AlightingUse :boolean [0..] + StopAssignmentType :StopAssignmentIdTypeEnum [0..] + BoardingUse :boolean «PK» ~ id :StopAssignmentIdType +for 0..* +made up of subzone of +used as primary for STOP PLACE SPACE 0..* Stop Place MODEL:: QUAY +for 0..* +to 0.. +composed by +to 0.. * +on..* +oriented by 0.. +a part of 0..* MODE Reusable Transport Mode MODEL:: VEHICLE MODE +primarily run by +for 0.. +the opposite of 0.. * +on +covered by * +the opposite of 0.. +made up of STOP PLACE SPACE Stop Place MODEL:: BOARDING POSITION +operated by 0..* LINK SEQUENCE Journey Pattern MODEL::JOURNEY PATTERN * +for 0..* +operating 0..* +comprising +defined on Service Pattern MODEL:: SERVICE PATTERN «PK» + id :ServicePatternIdType +for 0..* +made up of * +a view of +to * +made up of +contributing to Serv ice Pattern MODEL::SCHEDULED STOP POINT + ShortName :MultilingualString [0..] + Description :MultilingualString [0..] + RequestStop :boolean + Label :MultilingualString [0..] + Url :abyuri [0..] + StopType :StopPlaceTypeEnum + ForAlighting :boolean + ForBoarding :boolean + ByRequest :boolean «PK» + id :ScheduledStopPointIdType + Weighting :integer [0..] + BorderCrossingPoint :boolean [0..] «PK» + id :StopPlaceIdType +on..* +a view of neighbour of +to 0..* +in +containing 0..* SITE 0..* Stop Place MODEL::STOP PLACE Name: ISO Transmodel&IFOPT Network Basic MODEL (as in NeTEx) Author: NeTEx Version:.0 Created: 06/07/202 0:0:09 Updated: 04/09/202 8:06:5 Journey Pattern MODEL:: POINT IN JOURNEY PATTERN * Generic Point & Link MODEL::LINK +from +to * * +viewed as +start +end of of Generic Point & Link MODEL::POINT +viewed as +a view of * Generic Point & Link Sequence MODEL::POINT IN LINK SEQUENCE TRANSFER Service Pattern MODEL:: CONNECTION «PK» ~ id :ConnectionIdType +from * +to * +start of+end of +viewed as +a view of Service Pattern MODEL:: 0..* CONNECTION END +included in..* +composed of 0.. Service Pattern MODEL::STOP AREA + PublicCode :normalizedstring [0..] «PK» + id :StopAreaIdType Importance of Coherent Data and Interface Standards Data Base A possibily a proprietary implementation Data Base B possibily a proprietary implementation +defining * export/import +viewed as Standard Data Model Standard Exchange Messages A coherence between standard interfaces & data models - basis for data bases simplifies export/import applications Conclusion 33
Use of Standards Suite in France: Standard based DB and Interface Network topology Exchange messages Timetables s Name\Line A A Grub Street d 8:02 0:02 Tin Pan Alley d 8:2 0:2 Sinister Street d 8:37 0:37 Swans Way d 8:45 0:45 Howard s End a 8:55 0:55 Connections CHOUETTE DB Trans model& based data Export files NEPTUNE Format (based on Transmodel) NeTEx like Network & Time Tables CHOUETTE - tool : data capture & export Conclusion 34
Invitation Use Standard Data Models for Your Data Bases and Interfaces! Join the Standardisation Groups! Your Input and Needs will be Taken Into Account Shanghai, November 202 35
谢 谢 Thank you! Thanks to MobiGIS and to my CEN TC278 WG3 colleagues Christophe Duquesne and Nick Knowles for providing some of the pictures for this presentation kbouree@wanadoo.fr http://kasia.bouree.fr