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.
main schemae-service developersCen TC278 WG3 SG7 TeamEuropeDrafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]2004-03-052004-10-062005-05-112005-11-152007-03-292008-11-132011-04-182012-03-222012-04-272012-04-27
SIRI is a European CEN technical standard for the exchange of real-time information .
Derived from the VDV, RTIG CML 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 XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elementsStandardSIRI MONITORED VEHICLE JOURNEY Model.Type for Monitored VEHICLE JOURNEY.Elements describing the real-time progress of a monitored VEHICLE JOURNEY.Whether there is real-time information available for journey. Default is 'true'.
It is recommended to specify a MonitoringError if Monitored is set to 'false'.If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc.
MonitoringError must not be used if Monitored is omitted or set to 'true'.Elements describing the qua;ity of real-time progress data of a journey.Whether the VEHICLE iis in traffic congestion. If not, present, not known.Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'.System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds.Confidence QUALITY LEVEL of data. Default is 'reliable'.Elements describing the real-time progress of a journey.Current geospatial location of VEHICLE. Measured to front of vehicle.Time at which location was recorded. If not present assume that the recorded at time on the containing delivery.Bearing in compass degrees in which VEHICLE is heading.Rate of progress of VEHICLE. Default is 'normal'Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0)Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0)Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values.An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0)An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0)Elements describing the main places bewteen which a VEHICLE JOURNEY runs.Origin of the VEHICLE JOURNEY.VIA points for VEHICLE JOURNEYRelative priority for incliding via in displays. 1 Is high 3 is low. (since SIRI 2.0)Destination of VEHICLE JOURNEY.The service pattern of a monitored VEHICLE JOURNEY. CALLs should be assigned to one of three groups according to the vehicle's current position.Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested.Monitored CALL at the current stop.
For SIRI-SM this is the stop for which data is requested.
For SIRI-VM this is the most recent stop visited by the VEHICLE.Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested.Whether the above CALL sequence is complete, i.e. represents every CALL of the ROUTE and so can be used to replace a previous CALL sequence. Default is 'false'.Type for a reference to JOURNEY PART. (since SIRI 2.0)Reference to a JOURNEY part. (since SIRI 2.0)Train Number for JOURNEY PART (since SIRI 2.0)OPERATOR of JOURNEY PART. (since SIRI 2.0)Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1)
A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged.Type for a reference to JOURNEY PART. (since SIRI 2.1)Reference to a JOURNEY part.Train Number for JOURNEY PART.OPERATOR of JOURNEY PART.Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1)
A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged.
If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). (since SIRI 2.1)Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins.Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends.Time at which the related JOURNEY PART begins.Time at which the related JOURNEY PART ends.Type for BLOCK part elements of VEHICLE JOURNEY.Total number of BLOCK parts making up the train of which this is part.Reference to a train BLOCK part.Description of position of train BLOCK part within Train to guide passengers where to find it. E.g. 'Front four coaches'.Operational information about the monitored VEHICLE JOURNEY.If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.TRAIN NUMBERs for journey. (since SIRI 2.0)TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.Information about Parts of JOURNEY (since SIRI 2.0)Operational information about the monitored VEHICLE JOURNEY.If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.TRAIN NUMBERs for journey. (since SIRI 2.0)TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.Information about Parts of JOURNEY (since SIRI 2.0)Type for Ordered list of CALLs at previous stop.Type for CALL at previous stop.Type for Current CALL at stop.Elements for a monitored CALL.Elements describing the Real-time CALL properties.Exact location that VEHICLE will take up / or has taken at STOP POINT.Elements describing theProperties specific to a rail CALLs.Whether VEHICLE will reverse at stop. Default is 'false'.For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough.Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green.Elements describing the the arrival of a VEHICLE at a stop.Arrival times for CALL.Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0)Elements describing the the departure of a VEHICLE from a stop.Departure times for CALL.Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0).Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0)Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0)
