256.3. The toplevel element netex:ServiceJourney
|
|
Type for ENTITY. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Name of Class of the ENTITY. Allows reflection. Fixed for each ENTITY type. |
|||
|
|
1:1 |
Identifier of ENTITY. |
|||
|
|
1:1 |
Name of source of the data. |
|||
|
|
1:1 |
xs:dateTime |
Date ENTITY was first created. |
||
|
|
1:1 |
xs:dateTime |
Date ENTITY or version was last changed. |
||
|
|
1:1 |
Nature of last modification: new, revise, delete, unchanged, delta. Default is "new". |
|||
|
|
1:1 |
Version number of entity. The value may be "any" or a VERSION number adhering to agreed-upon formatting and interpretation rules (representing, e.g., a number or a date). Consecutive VERSION numbers should be strictly increasing. |
|||
|
|
1:1 |
Whether ENTITY is currently in use. Default is "active". |
|||
|
|
1:1 |
Version of this object from which this version of ENTITY was derived. |
|||
|
|
1:1 |
Version of frame from with which this version of ENTITY is compatible. Assumes Frame of the same Id as current frame. |
|||
|
|
1:1 |
Identity of object from which this object of ENTITY was derived. Normally the same. |
|||
|
|
1:1 |
Reference to RESPONSIBILITY SET for managing the object. If absent, then responsibility is same as for containing context of this object. |
|||
|
Base type content is restricted, resulting in the following own content: |
|||||
|
|
1:1 |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
| netex:EntityInVersionGroup |
a |
|
-1:1 |
VALIDITY CONDITIONs conditioning entity. |
|
|
b |
-1:* |
OPTIMISATION. Simple version of a VALIDITY CONDITION. Comprises a simple period. NO UNIQUENESS CONSTRAINT. |
|||
|
|
0:1 |
Additional Translations of text elements. |
|||
| netex:DataManagedObjectGroup |
0:1 |
A list of alternative Key values for an element. |
|||
|
0:1 |
A list of private codes that uniquely identifiy the element. May be used for inter-operating with other (legacy) systems. +v2.0 |
||||
|
0:1 |
User defined Extensions to ENTITY in schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
|
0:1 |
Reference to a BRANDING. |
||||
| netex:LinkSequenceGroup |
|
0:1 |
Name of LINK SEQUENCE. |
||
|
|
0:1 |
Short Name of LINK SEQUENCE. |
|||
|
|
0:1 |
Further Description of a LINKSEQUENCE. |
|||
|
|
0:1 |
Overall distance of LINK SEQUENCE. Can be derived from component LINKs. |
|||
|
0:1 |
A private code that uniquely identifies the element. May be used for inter-operating with other (legacy) systems. |
||||
|
|
0:1 |
PROJECTIONs of LINK SEQUENCE onto another ENTITY or layer. |
|||
|
|
0:1 |
Hyperlinks associated with JOURNEY. |
|||
|
|
0:1 |
SECTIONS that make up route. Can be used as an alternative to points in sequence. POINTS and LINKS must be of same type as sequence, eg ROUTE, ROUTE POINT, ROUTE LINK |
|||
| netex:JourneyGroup |
|
0:1 |
PT MODE of JOURNEY. |
||
|
0:1 |
A submode of a public or private TRANSPORT MODE. |
||||
|
|
0:1 |
An alternative code that uniquely identifies the JOURNEY. Specifically for use in AVMS systems. For VDV compatibility. DEPRECATED - use privateCodes. -v2.0 |
|||
|
0:1 |
Reference to a TYPE OF PRODUCT CATEGORY. Product of a JOURNEY. e.g. ICS, Thales etc See ERA B.4 7037 Characteristic description code. |
||||
|
0:1 |
Reference to a TYPE OF SERVICE. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a LINK SEQUENCE PROJECTION. |
|||
|
b |
-1:1 |
A Projection of a whole LINK SEQUENCE as an ordered series of POINTs. |
|||
|
|
0:1 |
xs:boolean |
Whether the journey will be monitored in real time. |
||
|
0:1 |
The accessibility characteristics of an entity used by passengers such as a STOP PLACE, or a STOP PLACE COMPONENT. Described by ACCESSIBILITY LIMITATIONs, and/or a set of SUITABILITies. |
||||
|
|
0:1 |
JOURNEY ACCOUNTING to be used to attribute JOURNEY costs. |
|||
|
|
0:1 |
NOTICEs relevant for the whole GROUP OF SERVICEs. |
|||
|
|
0:1 |
OCCUPANCYs associated with this JOURNEY. +v2.0 |
|||
| netex:ServiceAlterationGroup |
|
0:1 |
Whether journey is as planned, a cancellation or an extra journey. Default is as Planned. |
||
| netex:ServiceTimeGroup |
|
0:1 |
xs:time |
Time of departure. |
|
|
|
0:1 |
Day offset if day of departure time of VEHICLE JOURNEY differs from the current OPERATING DAY. |
|||
|
|
0:1 |
Frequency of Journey. |
|||
|
|
0:1 |
xs:duration |
Total length of Journey. Can be computed from individual times. Add to Departure time to obtain JOURNEY arrival time. |
||
| netex:VehicleJourneyReferencesGroup |
|
0:1 |
DAY TYPEs for Journey. |
||
|
0:1 |
Reference to a ROUTE. |
||||
|
0:1 |
Reference to a JOURNEY PATTERN. |
||||
|
|
0:1 |
Reference to a TIME DEMAND TYPE used at start of JOURNEY. |
|||
|
0:1 |
Reference to a TIMING ALGORITHM TYPE. |
||||
|
0:1 |
Reference to a JOURNEY FREQUENCY GROUP. |
||||
|
0:1 |
Reference to a VEHICLE TYPE. |
||||
|
0:1 |
Reference to a VEHICLE EQUIPMENT PROFILE. |
||||
|
0:1 |
VehicleTypeRef is the normally used field, as in many cases only the VEHICLE TYPE is known in advance. VehicleRef is then the exception and used only when the concrete VEHICLE is known in advance. Then also only one vehicle is possible. Reference to a VEHICLE. |
||||
|
0:1 |
Reference to an OPERATIONAL CONTEXT. |
||||
|
0:1 |
Reference to a BLOCK. |
||||
|
0:1 |
Reference to a COURSE OF JOURNEYS (Run). |
||||
|
|
0:1 |
Public code for JOURNEY. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| netex:ServiceJourneyReferencesGroup |
a |
-1:1 |
Reference to an OPERATOR. |
||
|
b |
-1:1 |
Simplified view of OPERATOR. All data except the identifier will be derived through the relationship. |
|||
|
The element contains none or one of the following elements (a-c) |
|||||
|
a |
-1:1 |
Reference to a LINE. |
|||
|
b |
-1:1 |
Simplified view of a LINE. |
|||
|
c |
-1:1 |
A group of FLEXIBLE ROUTEs of which is generally known to the public by a similar name or number and which have common booking arrangements. |
|||
|
0:1 |
A Direction of a ROUTE. One of a restricted set of values. Default is "Outbound" |
||||
|
0:1 |
Simplified view of a JOURNEY PATTERN. |
||||
|
|
0:1 |
Grouping of services of a journey - for a multi-part journey only. |
|||
|
|
0:1 |
Other TIME DEMAND TYPEs used in journey. |
|||
|
|
0:1 |
TRAIN NUMBERs -= derived through JOURNEY PARTs of a journey - for a multi-part journey only. |
|||
| netex:ServiceJourneyEndpointsGroup |
|
0:1 |
Origin for JOURNEY. |
||
|
|
0:1 |
Destination for JOURNEY. |
|||
| netex:ServiceJourneyAdvertisementGroup |
|
0:1 |
xs:boolean |
Whether the journey is included in printed media. Default is true. |
|
|
|
0:1 |
When SERVICE JOURNEY is to be publicised in dynamic media. Default is always. |
|||
| netex:VehicleJourneyTimesGroup |
|
0:1 |
WAIT TIMEs for VEHICLE JOURNEY at different TIMING POINTs. |
||
|
|
0:1 |
Run times for VEHICLE JOURNEY over different TIMING LINKs. |
|||
|
|
0:1 |
LAYOVER times for VEHICLE JOURNEY. |
|||
|
|
0:1 |
PASSING TIMEs for VEHICLE JOURNEY. |
|||
|
|
0:1 |
Times for passenger to be at stop if earlier than departure time. +v2.0 |
|||
| netex:ServiceJourneyPartsGroup |
|
0:1 |
JOURNEY PARTs of a journey - for a multi-part journey only. |
||
|
|
0:1 |
Complete sequence of stops along the route path, in calling order. |
|||
|
|
0:1 |
FACILITies available associated with JOURNEY. |
|||
|
|
0:1 |
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. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| netex:ServiceRequirementTypeGroup |
a |
-1:1 |
Reference to a PASSENGER CARRYING REQUIREMENT. |
||
|
b |
-1:1 |
Requirements for carrying passengers. |
|||
|
0:1 |
Requirements for TRAIN SIZe. |
||||
|
|
0:1 |
VEHICLE EQUIPMENT available on service. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| netex:ServiceJourneyGroup |
a |
-1:1 |
Reference to a FLEXIBLE SERVICE PROPERTIES. |
||
|
b |
-1:1 |
Additional characteristics of a FLEXIBLE SERVICE. A service may be partly fixed, partly flexible. |
|||