siri-2.0.xsd.siri_model.siri_monitoredVehicleJourney-v2.0.xsd Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of siri-java-model Show documentation
Java objects based on the public SIRI XSDs
The newest version!




	
		
			
				main schema
				e-service developers
				Cen TC278 WG3 SG7 Team
				Europe
				Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]
				
					2004-03-05
				
				
					2004-10-06
				
				
					2005-05-11
				
				
					2005-11-15
				
				
					2007-03-29
				
				
					2008-11-13
				 Correct Cardinalities on SIRI DESTINATION REF Structure 
				
				
					2011-04-18
				 siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com
 
				
				
					2012-03-22
				SIRI 2.0 
					[VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group
					[VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group
					[VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group
		
					[Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM
					Add JOURNEY PARTs to Vehicle INFO TODO
					[VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
					[VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
					
					[MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
					[MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
					
					[FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST
					[FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
					[FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
					
					[VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
					[VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM
					[UK] add engineOn to vehicle progress group
				
				
					2012-04-27
				SIRI 2.0 
					[MTA] Add DIstanceFromSTop and NumberOfStops away   to  MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET				 
				
				
					2012-04-27
				SIRI 2.0 
					[SE] Add Vehicle Status   
				
				
					SIRI is a European CEN technical standard for the exchange of real-time information .
					This subschema defines common journey elements.
				
				
					text/xml
					http://www.w3.org/2001/XMLSchema
					XML schema, W3C Recommendation 2001
				
				{http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_monitoredVehicleJourney.xsd
				[ISO 639-2/B] ENG
				Kizoom, 109-123 Clifton Street, London EC4A 4LD 
				
					http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd
				
				Unclassified

       CEN, VDV, RTIG 2004-2012
				
				
					
						Derived from the VDV, RTIG CML and Trident standards.
					
				
				Version 2.0 Draft
				
					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 SG7
				
				SIRI XML schema. Service Interface for Real-time  Information relating to Public Transport Operations. Subschema of common Journey elements
				Standard
			
		
		SIRI  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; if not present, not known.
				
			
			
				
					Condition indicating nature of real-time fault. Present if VEHICLE JOURNEY is normally monitored but temporarily cannot be Monitored for a known reason.
				
			
			
			
		
	
	
		
			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'.
				
			
			
				
					Whether the prediction should be judged as inaccurate.
				
			
			
				
					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. +SIRI v2.0
				
			
			
				
					Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0)
				
			
			
				
					How full the VEHICLE is.  If omitted, not known.
				
			
			
				
					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. +SIRI 2.0
				
			
		
	
	
		
			Elements describing the main places bewteen which a VEHICLE JOURNEY runs.
		
		
			
				
					Origin of the VEHICLE JOURNEY.
				
				
					
						
						
					
				
			
			
				
					VIA points for VEHICLE JOURNEY
				
				
					
						
						
						
							
								Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.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 refernces to  JOURNEY PARTs. +SIRI v2.0  
		
		
			
				
					Refrence to a JOURNEY part. +SIRI v2.0 
				
			
			
				
					Train Number for JOURNEY PART +SIRI v2.0
				
			
			
				
					Operator of JOURNEY PART. +SIRI v2.0 
				
			
		
	
	
	
		
			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. +SIRI v2.0
				
				
					
						
							
								TRAIN NUMBER  assigned to VEHICLE JOURNEY.  +SIRI  2.0
							
						
					
				
			
			
				
					JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
				
				
					
						
							
								Information about Parts of JOURNEY  +SIRI v2.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. +SIRI v2.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. +SIRI v2.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. +SIRI v2.0
				
			
			
				
					Prediction quality, either as approcimate level, or more quantitatyive percentile range of   predictions will  fall within a given range of times.  +SIRI v2.0