Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
Derived from the VDV, RTIG XML and Trident standards.
Version 2.1Arts, 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 SG7SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service.StandardSIRI-ET Estimated Timetable Service.A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference.Identifer of a VEHICLE JOURNEY within data Horizon of a service.Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable.
DEPRECATED from SIRI 2.0Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops.If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'.
DEPRECATED from SIRI 2.0Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey.Whether this VEHICLE JOURNEY is a deletion of a previous scheduled journey. Default is 'false': this is not a VEHICLE JOURNEY that has been cancelled. An Extra Journey may be deleted.A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. (since SIRI 2.0)Type for Estimated SERVICE JOURNEY INTERCHANGE.Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. (since SIRI 2.1)Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. (since SIRI 2.0)Reference to a connecting feeder VEHICLE JOURNEY. (since SIRI 2.0)SCHEDULED STOP POINT at which feeder journey arrives.
Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time,
how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always
reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1)Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false,
ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of
despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1)Reference to a connecting distributor VEHICLE JOURNEY. (since SIRI 2.0)SCHEDULED STOP POINT at which distributor journey departs.
Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef
should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1)Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false,
ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of
despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1)Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example,
InterchangeStatus or Will(Not)Wait contain the real-time data. A SERVICE JOURNEY INTERCHANGE may be transmitted with "Guaranteed=true", but also WillNotWait due to major despatching alterations.
However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. (since SIRI 2.1)Whether this interchange is planned, updated, additional or cancelled. (since SIRI 2.1)Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0Details about how (long) the distributor services may be held in order to guarantee the connection. (since SIRI 2.0)Time at which feeder VEHICLE is expected to arrive. (since SIRI 2.1)Time at which distributor VEHICLE is expected to depart. (since SIRI 2.0)Whether connection monitoring is active or not for this connection. (since SIRI 2.0)Contains various types of transfer and wait times of a SERVICE JOURNEY INTERCHANGE.
Implementation Note: what happens if, for example, the interchange times and a QUAY change in xxxStopAssignment of the ESTIMATED VEHICLE JOURNEY suggest contradictory transfer/wait times?
In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. (since SIRI 2.1)Type for Will Wait detailsTime up until which the distributor will wait. (since SIRI 2.0)DEPRECATED since SIRI 2.1Whether an acknowledgement has been received that the driver will wait. (since SIRI 2.1)Type for Real-time info about a VEHICLE JOURNEY.Time at which data of individual journey was recorded if differet from that of frame. ((since SIRI 2.0).)Gives the DATED VEHICLE JOURNEY
which the vehicle is running and if the journey is an alteration to the timetable indicates
the original journey and the nature of the difference.Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0)Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position.Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'.Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered.This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned.This CALL is a cancellation of a previously announced call.Type for real-time info about a VEHICLE JOURNEY Stop.Information relating to real-time properties of call.Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0)Type for recroded Real-time info about a VEHICLE JOURNEY Stop.Information relating to recorded real-time properties of call.
