main schema e-service developers V1.0 Christophe Duquesne Nicholas Knowles Europe First drafted for NeTEx version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. 2010-09-04 2011-02-05Name Space changes 2017-02-05CR006 Allow reference to FlexibleServiceProperties as choice with embedding 2017-05-25PR Correct definition of SERVICE JOURNEY. Doc change only. 2018-06-01CR057 Add VehicleJourney By Value Reference 2018-06-01FIX Add Topographical Place to endpoint for GROUP OF SERVICES

NeTEx is a European CEN standard for the exchange of Public Transport data including timetables.

This sub-schema describes the SERVICE JOURNEY types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.netex.org.uk/schemas/1.0/xsd/netex_part_2/part2_journeyTimes}netex_serviceJourney_version.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsd Unclassified CEN, Crown Copyright 2009-2023
  • Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
Version 1.0 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and Road transport CEN TC278 WG3 SG9. NeTEx SERVICE JOURNEY types. Standard NeTEx: SERVICE JOURNEY types. Type for containment in frame of GROUP OF SERVICEs. Dummy SERVICE JOURNEY Supertype. A passenger carrying VEHICLE JOURNEY for one specified DAY TYPE. The pattern of working is in principle defined by a SERVICE JOURNEY PATTERN. The VIEW includes derived ancillary data from referenced entities. Data type for a planned VEHICLE JOURNEY (Production Timetable Service). Elements for a SERVICE JOURNEY, including additional derived data. Flexible properties Elements for parts of a SERVICE JOURNEY, i. JOURNEY PARTs of a journey - for a multi-part journey only. Complete sequence of stops along the route path, in calling order. FACILITies available associated with JOURNEY. CHECK CONSTRAINTs which apply to SERVICE JOURNEY, e.g. check in time, security time. These are advisory only and not for use in journey planning. Reference elements for a SERVICE JOURNEY, including additional derived data. LINE followed by SERVICE JOURNEY Use view to get derived values. NOTE: Use LineView over FlexibleLineView as FLEXIBLE LINE is marked deprecated in v2.0. Grouping of services of a journey - for a multi-part journey only. Other TIME DEMAND TYPEs used in journey. TRAIN NUMBERs -= derived through JOURNEY PARTs of a journey - for a multi-part journey only. Advertisement Elements for info about publicising SERVICE JOURNEY. Whether the journey is included in printed media. Default is true. When SERVICE JOURNEY is to be publicised in dynamic media. Default is always. Elements for Service Categorisation. Time of departure. Frequency of Journey. Total length of Journey. Can be computed from individual times. Add to Departure time to obtain JOURNEY arrival time. If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. Whether journey is as planned, a cancellation or an extra journey. Default is as Planned. Elements for origin and destination of JOURNEY. Can be derived from the Pattern. Must not contradict the calls. Origin for JOURNEY. Destination for JOURNEY. Data type for Planned VEHICLE JOURNEY (Production Timetable Service). A VEHICLE JOURNEY with a set of frequencies that may be used to represent a set of similar journeys differing only by their time of departure. Type for TEMPLATE VEHICLE JOURNEY. Type for a list of SPECIAL SERVICE s. A passenger carrying VEHICLE JOURNEY for one specified DAY TYPE. The pattern of working is in principle defined by a SERVICE JOURNEY PATTERN. Type for SPECIAL SERVICE. Elements for SPECIAL SERVICE. Elements for SERVICE time. Client of Special Service. DAY TYPEs for Journey. Reference to a JOURNEY PATTERN. Usage of BookingArrangementGroup is DEPRECATED: use bookingArrangements Set of possible Booking Arrangements for stop if different from those for SERVICE JOURNEY. +v2.0 A group of SERVICEs, often known to its users by a name or a number. Type for a GROUP OF SERVICEs. Elements for a GROUP OF SERVICEs. Services in GROUP. NOTICEs relevant for the whole GROUP OF SERVICEs. Elements for common properties a GROUP OF SERVICEs. The DAY TYPEs of all the services in this group. The DAY TYPE of all the services in this group. Origin associated with this GROUP OF SERVICEs. Destination associated with this GROUP OF SERVICEs. Destinations associated with this GROUP OF SERVICEs, including via points. Type for SIMPLE SCHEDULED STOP POINT VIEW. Name of Stop Point. Type for a list of Member of GROUP OF SERVICE Member. Member of GROUP OF SERVICE. Type for a Member of GROUP OF SERVICE Member. Parent GROUP OF SERVICEs to which this GROUP OF SERVICEs MEMBER assigns a JOURNEY. NOTICEs Relevant for this grouping. Type for DEAD RUN. Elements for DEAD RUN. Reference Elements for a SERVICE JOURNEY, including additional derived data. Type of DEAD RUN. Elements for origin and destination of DEAD RUN Can be derived from the Pattern. Must not contradict the JOURNEY PATTERN. Origin for DEAD RUN. Can be Derived from JORUNEY PATTERN. Destination for DEAD RUN. Can be derived from JORUNEY PATTERN. Type for DEAD RUN ENDPOINT (Production Timetable Service). Should not Contradict EDEAD RUN JOURNEY PATTERN. Elements for a DEAD RUN., including additional derived data. GROUPS OF SERVICEs to which a DEAD RUN belongs. TRAIN NUMBERs -= derived through JOURNEY PARTs of a JOURNEY - for a multi-part JOURNEY only. A non-service VEHICLE JOURNEY. Type for DEAD RUN. Elements for DEAD RUN. Complete sequence of stops along the route path, in calling order.