NETEX - CEN PT STANDARDS CONTEXT JUNE 2021 CHRISTOPHE DUQUESNE - ULF BJERSING - DATA4PT
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
NeTEx - CEN PT
Standards context
June 2021
Christophe Duquesne – Ulf Bjersing
Data4PT has received funding from the European Union’s DG for Mobility and Transport under
grant agreement No MOVE/B4/SUB/2019-104/CEF/PSA/SI2.821136 1
Standards and categories
NeTEx
22/06/2021 2
Data categories in mobility
class Tous les Equipements
But there are a lot of additional, EQUIPMENT
more transverse categories : INSTALLED EQUIPMENT
{exclusion: this equipment
is either fixed or on-board}
•
Name: Tous les Equipements
Equipment (see figure)
Author: Christophe Duquesne
Version: 1.0
Created: 25/07/2017 00:00:00
+using ACTUAL VEHICLE
Updated: 26/07/2017 12:37:40
+using EQUIPMENT
PLACE EQUIPMENT
0..1
•
0..1
Accessibility
+used as +used as
PASSENGER
0..1
0..1 EQUIPMENT
WHEELCHAIR VEHICLE VEHICLE ACCESS
EQUIPMENT EQUIPMENT
• Roles and Responsibilities
PLACE ACCESS
EQUIPMENT
• Data Frames QUEUING EQUIPMENT CROSSING EQUIPMENT ENTRANCE EQUIPMENT ROUGH SURFACE STAIR EQUIPMENT CYCLE STORAGE
EQUIPMENT
TICKET VALIDATOR
EQUIPMENT
PASSENGER SAFETY
EQUIPMENT
PASSENGER
INFORMATION
EQUIPMENT
RUBBISH DISPOSAL
+classified as
SANITARY EQUIPMENT
0..* 0..*
•
+characterised
Versioning
by
VEHICLE CHARGING TICKETING EQUIPMENT TYPE OF SANITARY +a classification for
EQUIPMENT FACILITY
0..1
PLACE LIGHTING TRAVELATOR LIFT EQUIPMENT STAIRCASE EQUIPMENT
•
EQUIPMENT
Etc.
TYPE OF GENDER 0..1
LIMITATION
+characterised 0..* 0..* +characterisation of
RAMP EQUIPMENT by ESCALATOR
EQUIPMENT
+a characterisation
for 0..1 +characterised
+characterised 0..*
or more detailed ones, for
by +a characteriation +a characterisation by
for TYPE OF HANDRAIL for SITE EQUIPMENT SIGN EQUIPMENT
0..1
0..1
example in PT Schedule LOCAL SERVICE
LUGGAGE LOCKER TROLLEY STAND WAITING EQUIPMENT
PLACE SIGN HEADING SIGN GENERAL SIGN
information you will have :
EQUIPMENT EQUIPMENT
•
ASSISTANCE SERVICE TICKETING SERVICE CUSTOMER SERVICE LUGGAGE SERVICE LEFT LUGGAGE SERVICE
Network topology (lines, etc.)
SHELTER EQUIPMENT SEATING EQUIPMENT WAITING ROOM
EQUIPMENT
0..* 0..* 0..*
0..*
+characterised
+characterised by
•
by
Timetables (services, calendars,
COMPLAINTS SERVICE LOST PROPERTY MEETING POINT
SERVICE SERVICE
+characterised
by +description
passing times, etc.)
of
0..*
+classified COMMUNICATION
as SERVICE
TYPE OF ACCESSIBILITY
TOOLS
• Operational information (run
CATERING SERVICE
+description
of TYPE OF STAFFING
times, blocks, vehicles, etc.)
0..*
+classification RETAIL SERVICE
for
TYPE OF ASSISTANCE
0..1
0..* SERVICE
+description
•
of MONEY SERVICE
Etc. TYPE OF EMERGENCY
SERVICE
HIRE SERVICE
22/06/2021 3
Public Transport related business cases
• Multiple and often complex buisiness cases
• Each system or tool has a specific (and partial) point of
view
Mobility needs analysis and transport plan
definition (Authorities)
Rostering, scheduling (timetable,
Scheduling and production plan vehicle, run times…)
AVMS (Automateg Vehicle
Operations Monitoring System)
Journey planner, displays, app &
Passenger Information web sites
Indicators and statistics Analysis, BI, optimisation
Fare offer definition and Ticketing Ticketing systems
22/06/2021 4
PT Standard dependencies and relations
Conceptual data model covering
all the public transport data domaine
Exchange data format for Exchange data format for Exchange data format for
scheduled information real time information observed information
GTFS
GTFS
RT
22/06/2021 5
Transmodel ecosystem 22/06/2021 6
Transmodel content 22/06/2021 7
Transmodel content associated with
exchange standard NeTEx
22/06/2021 8
NeTEx
Name : NeTEx
Reference : CEN TS 16614-1, 16614-2 and 16614-3
Status : Part 1 : Common concepts and Network Description
Part 2 : Timing information
Part 3 : Fare Information
Part 4 : EPIP - EU Passenger information profile
Part 5 : New Modes (under TC review)
Part 6 : EU Accessibility Profile (under development)
Conceptual model : no (based on Transmodel, aligned with Transmodel 6)
Exchange format : yes
Data category : Scheduled data for mobility
(operational and passenger information data)
Temporal scope : Scheduled data, and static data
Main scope : Network description, timetables and fares.
Example of covered objects : Stop Place, Timing point, Equipment, Facilities, Line,
Route, Fare product, Access rights, Accessibility, etc.
Web site http://netex-cen.eu
22/06/2021 9class Lignes
NT Route MODEL::NETWORK
«UID»
NeTEx ::GROUP OF LINES Name: Lignes
+ id :GroupOfLinesIdType Author: Aurige (TM6 Extract)
Version: 1.0
+made up of 1 Created: 16/07/2014 15:27:11
Updated: 16/07/2014 18:12:02
+part of 0..*
NT Route MODEL::GROUP OF LINES
NT Route MODEL::TYPE OF LINE
«UID»
«UID»
+ id :GroupOfLinesIdType
+ Id :TypeOfLineIdType
+represented 0..* *
by +composed of +a classification
0..1
for
+main line for +included in
0..1 1..*
+classified by
NT Route MODEL::LINE
+operated by
Description :MultilingualString [0..1] 0..*
+
+
LineUrl :any [0..1]
0..*
+
Monitored :boolean [0..1] 0..* +run primarily by
+
Name :MultilingualString
XSD
+primarily run by
+
ShortName :MultilingualString [0..1]
* «UID» +run by
+ Id :LineIdType 0..*
+characterised by 0..1
+operating +used as primary for
+operating +primary for
0..* 0..1 +characterising 0..1 0..* 0..1
MODE ORGANISATION
CC Generic Accessibility MODEL::ACCESSIBILITY
CC Transport Mode MODEL:: ASSESSMENT CC Transport Organisations MODEL::
VEHICLE MODE OPERATOR
+ MobilityImpairedAccess :boolean [0..1]
::MODE ::ORGANISATION
«UID»
+ Name :MultilingualString [0..1] + Description :MultilingualString [0..1]
+ Id :AsssesmentIdType
«UID» + LegalName :MultilingualString [0..1]
+ Id + Name :normalizedString
+limited 1
::MODE + Remarks :MultilingualString [0..1]
by
+ Id :ModeIdType + ShortName :MultilingualString [0..1]
+ TradingName :MultilingualString [0..1]
+determining
0..* «UID»
::ORGANISATION
CC Generic Accessibility MODEL::ACCESSIBILITY + Id :OrganisationIdType
LIMITATION
+ AudibleSignsAvailable :LimitationStatusEnum [0..1]
+ EscalatorFreeAccess :LimitationStatusEnum [0..1]
+ LiftFreeAccess :LimitationStatusEnum [0..1]
+ StepFreeAccess :LimitationStatusEnum [0..1]
+ VisualSignsAvailable :LimitationStatusEnum [0..1]
+ WheelchairAccess :LimitationStatusEnum [0..1]
«UID»
+ Id :LimitationIdType
22/06/2021 10NeTEx is a data exchange formats
(possible use via an API)
22/06/2021 11Transmodel and NeTEx’s modes
MODE
air
bus
trolleyBus
tram
coach
rail
metro
water
ferry
cableway
funicular
lift
snowAndIc
e
selfDrive
foot
bicycle
motorcycle
scooter
car
shuttle
22/06/2021 12NeTEx: use cases examples
CEN TS 16614-1 to 5
Scheduled data exchange
To feed journey planner
Passenger information system feed
Open data feed (often as an ehanced complement to
GTFS)
AVMS feed
Exchange for co-operated network
Late schedule update (on a specific day) dissemination
Ticketing system feed
22/06/2021 13Profiles 22/06/2021 14
Profiles: why ?
Standards are by their nature, consensus documents, taking into account a wide
range of requirement
Standards may contain some redundant features in order to take into account some
alternate national specific ways of working with PT.
The scope of a standard most often goes much further than the one of a single use
case
Standards’ documents are often quite large and detailed (also due to the expected
detail level and prescribed editorial rules)
Standards contains a lot of non mandatory features (services, attributes, processes,
etc.)
Specific local rules (coding, local processes, etc.) are not described in standards
• For example, reference to NaPTAN (national Stop reference database) in UK
22/06/2021 15Profiles: why ?
As a summary
A profile
• facilitates the implementation of a standard
• improves interoperability
by
• focusing only on what is needed
• filling the small gaps voluntarily left by the standard
• taking into account the local context.
22/06/2021 16Profiles: what ?
The profile contains information such as:
• Details of used services
• Details of the objects used in an exchange
• Details on the options proposed by the standard
• Details on optional elements
• Precision on the codifications to be used
• …
To define a profile, you need to:
• Define/identify use cases and requirements
• Identify local constraints (processes, coding rules, reference data, etc.)
• Select in the standard what is necessary or useful to fulfil the two above
• Complement the standard with some specific (but standard compliant) local
rules
From a practical point of view, profiles can be seen as an
implementation guideline for a certain standard.
22/06/2021 17Resources
Support and resources (tools, etc.)
https://data4pt-project.eu/
http://netex-cen.eu/
https://github.com/NeTEx-CEN/NeTEx
https://data4pt.org/wiki/NeTEX
http://www.normes-donnees-tc.org/format-dechange/donnees-theoriques/netex/ (in French)
http://www.transmodel-cen.eu/
http://siri-cen.eu/
National NeTEx Profiles
http://www.normes-donnees-tc.org/profils/
https://transportdatamanagement.ch/content/uploads/2020/11/NeTEx_Core-Realisation_Guide_TP_Suisse-v0.8.8.4.pdf
https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic%2BNeTEx%2BProfile
https://www.vdv.de/vdv-462-netex-recommendation-v00-22-english.pdfx
http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf
https://bison.dova.nu/standaarden/nederlands-netex-profiel
https://data4pt.org/NeTEx/GraphicKit/XSD_reduced.zip (XSD reduced to EPIP scope)
Tools
https://github.com/entur/
https://github.com/enroute-mobi/ (https://enroute.mobi/chouette/ )
https://github.com/skinkie/hastus
http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/
https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
https://mobilitx.diginext.fr/ 18
22/06/2021
https://www.lumiplan.com/produit/mobiref/Thank you for your attention Data4PT has received funding from the European Union’s DG for Mobility and Transport under grant agreement No MOVE/B4/SUB/2019-104/CEF/PSA/SI2.821136 19
You can also read
