SIST EN 15531-3:2015
(Main)Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces
Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces
There are many potential ways for passenger transport operations centres to interact. The approach taken by SIRI is for an open-ended set of standard data structures, carried over a communications channel constructed using one of a small number of specific options.
Part 2 of this European Standard specifies the communications channel. Part 3 specifies a number of functional modules, based on the ‘use cases’ identified in Annex B to Part 1:
— Production Timetable (PT): this service enables the provision of information on the planned progress of vehicles operating a specific service, identified by the vehicle time of arrival and departure at specific stops on a planned route for a particular Operational Day.
— Estimated Timetable (ET): this service enables the provision of information on the actual progress of Vehicle Journeys operating specific service lines, detailing expected arrival and departure times at specific stops on a planned route. There will be recorded data for stops which have been passed, and predicted data for stops not yet passed. In addition the Estimated Timetable service allows Vehicle Journeys to be cancelled, added or changed.
— Stop Timetable (ST): this service provides a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. It can be used to reduce the amount of information that needs to be transmitted in real-time to stops and displays, as reference data for a Stop Monitoring Service; and provides a data feed of the static timetables.
— Stop Monitoring (SM): this service provides a stop-centric view of vehicle arrivals and departures at a designated stop. It can be used by displays and other presentation services to provide departure board and other presentations of timetable and real-time journey information both at stops and at a distance.
— Vehicle Monitoring (VM): this service enables the provision of information on the current location and status of a set of vehicles. It provides all the current relevant information from one AVMS relating to all vehicles fulfilling a set of selection criteria.
— Connection Timetable (CT): this service may be used to provide information about the scheduled arrivals of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then plan how to guarantee the connection, either with the expected vehicle or a different vehicle.
— Connection Monitoring (CM): this service is used to provide information about the expected arrival of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then manage the service to guarantee the connection, based on actual vehicle running.
— General Message (GM): the SIRI "General Message” service is used to exchange informative messages between identified individuals in free or an arbitrary structured format. It enables messages to be sent and to be revoked. Messages are assigned validity periods in addition to the actual content.
Öffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen, bezogen auf Operationen im öffentlichen Verkehr - Teil 3: Funktionelle Serviceschnittstelle
Transport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 3: Modules d'interface d'application individuels
Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza - 3. del: Funkcionalni vmesniki storitve
Posodobitev standarda CEN/TS 15531 ob upoštevanju rezultatov projektov v različnih državah, ki so uporabljale specifikacijo, in ob upoštevanju novih zahtev. Obstoječi standard so začeli razvijati v okviru CEN TC278 WG3 SG7 leta 2002 in ga objavili leta 2007. Olajšuje interoperabilnost med sistemi za obdelavo informacij o izvajalcih prevoza (avtomatski nadzorni sistemi za vozila: AVMS), da se omogoči boljše upravljanje vozil kot tudi zagotavljanje informacij za končne uporabnike v realnem času. Glavni elementi standarda so: - komunikacijska plast, ki določa skupne postopke za povpraševanje po podatkih in njihovo izmenjavo. Komunikacijski postopki so enaki za vse storitve in s tem predstavljajo infrastrukturo vmesnika (povezovanje sporočil, obravnavanje napak, vedenje ob ponastavitvi). Ponovna uporaba infrastrukture vmesnika za razne tehnične storitve zagotavlja stroškovno učinkovito izvajanje in razširitev vmesnika. o Zahteva/odziv o Objava/naročnina Naročnine določajo tip in količino podatkov za izmenjavo. - Vmesnik med kontrolnimi centri (AVMS) s funkcijami o zaščita povezave (v povezavi s časom ali potovanjem) o informacije o povezavi (v povezavi s časom) o informacije o potniku v realnem času (tabela odhodov, postanki) o splošna sporočila (storitev obveščanja o dogodkih in informacije) o informacije o voznem redu in topologija omrežja (načrtovana izmenjava podatkov) o aktivnost vozila (VIS) - vmesnik za informacije o voznem redu med kontrolnimi centri (AVMS) in informacijske sisteme s funkcijami o informacije o razporedu v realnem času o storitev referenčnih podatkov za informacije o razporedu. Nova delovna postavka bo obravnavala delo - drugih podskupin pf WG3: * SG4 podatkovni model za javni prevoz (TRANSMODEL) * SG9 omrežje in izmenjava voznega reda (NeTEx) - Obrazložitev nacionalnih zrcalnih odborov; od pojava aplikacije SIRI so se znatno povečale zahteve po informacijah s strani zainteresiranih javnih organov in predvsem odjemalcev javnega potniškega prevoza. Obstoječi nacionalni in mednarodni »standardi« (zlasti TRIDENT, RTIG in VDV-453/454), ki so bili v uporabi še pred pojavom aplikacije SIRI, so dosegli visoko raven izvajanja. Zdaj pa je prišel čas za zamenjavo starih sistemov s SIRI in CEN/TS 15531 se mora prilagoditi novim zmogljivostim. Zato je treba nujno okrepiti in izboljšati SIRI, da bo ustrezala stopnji, ki jo danes dosega upravljanje podatkov v realnem času.
General Information
- Status
- Withdrawn
- Public Enquiry End Date
- 31-Dec-2013
- Publication Date
- 01-Nov-2015
- Withdrawal Date
- 19-Sep-2022
- Technical Committee
- ITC - Information technology
- Current Stage
- 9900 - Withdrawal (Adopted Project)
- Start Date
- 20-Sep-2022
- Due Date
- 13-Oct-2022
- Completion Date
- 20-Sep-2022
Relations
- Effective Date
- 01-Dec-2015
- Effective Date
- 01-Nov-2022
Frequently Asked Questions
SIST EN 15531-3:2015 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces". This standard covers: There are many potential ways for passenger transport operations centres to interact. The approach taken by SIRI is for an open-ended set of standard data structures, carried over a communications channel constructed using one of a small number of specific options. Part 2 of this European Standard specifies the communications channel. Part 3 specifies a number of functional modules, based on the ‘use cases’ identified in Annex B to Part 1: — Production Timetable (PT): this service enables the provision of information on the planned progress of vehicles operating a specific service, identified by the vehicle time of arrival and departure at specific stops on a planned route for a particular Operational Day. — Estimated Timetable (ET): this service enables the provision of information on the actual progress of Vehicle Journeys operating specific service lines, detailing expected arrival and departure times at specific stops on a planned route. There will be recorded data for stops which have been passed, and predicted data for stops not yet passed. In addition the Estimated Timetable service allows Vehicle Journeys to be cancelled, added or changed. — Stop Timetable (ST): this service provides a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. It can be used to reduce the amount of information that needs to be transmitted in real-time to stops and displays, as reference data for a Stop Monitoring Service; and provides a data feed of the static timetables. — Stop Monitoring (SM): this service provides a stop-centric view of vehicle arrivals and departures at a designated stop. It can be used by displays and other presentation services to provide departure board and other presentations of timetable and real-time journey information both at stops and at a distance. — Vehicle Monitoring (VM): this service enables the provision of information on the current location and status of a set of vehicles. It provides all the current relevant information from one AVMS relating to all vehicles fulfilling a set of selection criteria. — Connection Timetable (CT): this service may be used to provide information about the scheduled arrivals of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then plan how to guarantee the connection, either with the expected vehicle or a different vehicle. — Connection Monitoring (CM): this service is used to provide information about the expected arrival of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then manage the service to guarantee the connection, based on actual vehicle running. — General Message (GM): the SIRI "General Message” service is used to exchange informative messages between identified individuals in free or an arbitrary structured format. It enables messages to be sent and to be revoked. Messages are assigned validity periods in addition to the actual content.
There are many potential ways for passenger transport operations centres to interact. The approach taken by SIRI is for an open-ended set of standard data structures, carried over a communications channel constructed using one of a small number of specific options. Part 2 of this European Standard specifies the communications channel. Part 3 specifies a number of functional modules, based on the ‘use cases’ identified in Annex B to Part 1: — Production Timetable (PT): this service enables the provision of information on the planned progress of vehicles operating a specific service, identified by the vehicle time of arrival and departure at specific stops on a planned route for a particular Operational Day. — Estimated Timetable (ET): this service enables the provision of information on the actual progress of Vehicle Journeys operating specific service lines, detailing expected arrival and departure times at specific stops on a planned route. There will be recorded data for stops which have been passed, and predicted data for stops not yet passed. In addition the Estimated Timetable service allows Vehicle Journeys to be cancelled, added or changed. — Stop Timetable (ST): this service provides a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. It can be used to reduce the amount of information that needs to be transmitted in real-time to stops and displays, as reference data for a Stop Monitoring Service; and provides a data feed of the static timetables. — Stop Monitoring (SM): this service provides a stop-centric view of vehicle arrivals and departures at a designated stop. It can be used by displays and other presentation services to provide departure board and other presentations of timetable and real-time journey information both at stops and at a distance. — Vehicle Monitoring (VM): this service enables the provision of information on the current location and status of a set of vehicles. It provides all the current relevant information from one AVMS relating to all vehicles fulfilling a set of selection criteria. — Connection Timetable (CT): this service may be used to provide information about the scheduled arrivals of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then plan how to guarantee the connection, either with the expected vehicle or a different vehicle. — Connection Monitoring (CM): this service is used to provide information about the expected arrival of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then manage the service to guarantee the connection, based on actual vehicle running. — General Message (GM): the SIRI "General Message” service is used to exchange informative messages between identified individuals in free or an arbitrary structured format. It enables messages to be sent and to be revoked. Messages are assigned validity periods in addition to the actual content.
SIST EN 15531-3:2015 is classified under the following ICS (International Classification for Standards) categories: 35.240.60 - IT applications in transport. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 15531-3:2015 has the following relationships with other standards: It is inter standard links to SIST-TS CEN/TS 15531-3:2009, SIST EN 15531-3:2022. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
SIST EN 15531-3:2015 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.GHORYDQMDÖffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen, bezogen auf Operationen im öffentlichen Verkehr - Teil 3: Funktionelle ServiceschnittstelleTransport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 3: Modules d'interface d'application individuelsPublic transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and tradeICS:Ta slovenski standard je istoveten z:EN 15531-3:2015SIST EN 15531-3:2015en,fr,de01-december-2015SIST EN 15531-3:2015SLOVENSKI
STANDARDSIST-TS CEN/TS 15531-3:20091DGRPHãþD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15531-3
August 2015 ICS 35.240.60 Supersedes CEN/TS 15531-3:2007English Version
Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces
Transport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 3 : Modules d'interface d'application individuels
Öffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen, bezogen auf Operationen im öffentlichen Verkehr - Teil 3: Funktionelle Serviceschnittstelle This European Standard was approved by CEN on 20 June 2015.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2015 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15531-3:2015 ESIST EN 15531-3:2015
FilterByValidityPeriod 1:1 xsd:boolean Whether results can be filtered by Validity Period. Required Capability: Fixed is true. FilterByOperatorRef 1:1 xsd:boolean Whether results can be filtered by OPERATOR. Default is ‘true’. FilterByLineRef 1:1 xsd:boolean Whether results can be filtered by LINE. Default is ‘true’. SIST EN 15531-3:2015
Language 1:* xsd:language National languages used by service.
Translations 0:1 xsd:boolean Whether the producer supports translations. SIRI 2.0 Default is false.
choice Location reference system for coordinates. a GmlCoordinateFormat 0:1 SrsNameType Default coordinate format is given by a GML value. b WgsDecimalDegrees EmptyType Default coordinate data system is WGS 84 latitude and longitude. Sub-scription Policy SubscriptionPolicy 0:1 +Structure Which features of Subscription Policy are supported by the service?
HasIncremental-Updates 0:1 xsd:boolean Whether incremental updates can be specified for updates. Default is ‘true’. Access Control AccessControl 0:1 +Structure Which optional Access Control features are supported by service?
RequestChecking 1:1 xsd:boolean Whether access control of requests is supported. Default is ‘false’.
CheckOperatorRef 0:1 xsd:boolean If access control is supported, whether access control by OPERATOR is supported. Default is ‘true’. CheckLineRef 0:1 xsd:boolean If access control is supported, whether access control by LINE is supported. Default is ‘true’. CheckConnection-LinkRef 0:1 xsd:boolean If access control is supported, whether access control by CONNECTION link is supported. Default is ‘true’. any Extensions 0:1 xsd:any* Placeholder for user extensions.
5.2.2 Permission Matrix If the implementation supports both Capability Discovery and Access Controls, then the ProductionTimetableCapabilitiesResponse response can include the access permissions for the requestor participant to access data. Table 2 shows this. Table 2 — Production Timetable Service — Permissions ProductionTimetablePermission +Structure Permissions to use implementation of Production Timetable service. In-herit ::: 1:1 xxxService-Permissions See SIRI Part 2 for Common Permission elements. Topic OperatorPermissions 0:1 +Structure OPERATOR permissions for participant. See Part 2. LinePermissions 0:1 +Structure LINE permissions for participant. See Part 2. ConnectionLinkPermissions 0:1 +Structure CONNECTION link permissions for participant. See Part 2.
+Structure Request for daily production timetables Attributes version 1:1 VersionString Version identifier of Production Timetable Service, e.g. 1.0c Endpoint Properties Request-Timestamp 1:1 xsd:dateTime See SIRI Part 2 for common properties of SIRI Functional Service Requests. Message-Identifier 0:1 Message-Qualifier Line Topic ValidityPeriod 0:1 ClosedTimestampRange-Structure Start and end of timetable validity (time window) of journeys for which schedules are to be returned. Refers to the departure time at the first stop of each VEHICLE JOURNEY. If blank the configured data horizon will be used.
Start 1:1 xsd:dateTime The (inclusive) start time.
End 1:1 xsd:dateTime The (inclusive) end time. Timetable-VersionRef 0:1 xsd:string Communicate only differences to the timetable specified by this version of the timetable. OperatorRef 0:* :lperator-Code Filter the results to include only results for the specified operator or operators. Optional SIRI capability: TopicFiltering / Bylperatorh Lines
LineDirection
LineRef 0:1 :iineCode Filter the results to include only results for the given LINE or LINEs.
DirectionRef 0:1 :airection-Code Filter the results to include only journeys for VEHICLEs running in a specific relative DIRECTION. Optional SIRI capability: TopicFiltering / Byairection. Policy Language 0:1 xml:lang Preferred language in which to return text values. Optional SIRI capability: Nationalianguageh Include-Translations 0:1 xsd:boolean Whether the producer should include any available translations of NLString text elements into multiple languages. If false elements only one value per text element will be provided. +SIRI.2.0 Default is false. Incremental-Updates 0:1 xsd:boolean Whether the producer should return the complete set of current data, or only provide updates to the last timetable returned, i.e. additions, modifications and deletions, as indicated by the TimetableVersionRef. If false each subscription response will contain the full information as specified in this request. any Extensions 0:1 xsd:any* Placeholder for user extensions.
The ProductionTimetableRequest can be used in both a direct request, and for a subscription. If used for a subscription, additional ProductionTimetableSubscriptionPolicy parameters can be specified. SIST EN 15531-3:2015
2004-12-17T09:30:47-05:00
NADER
2001-12-17T09:30:47-05:00
14:20:00
14:20:00
002
Smooth
123
Outbound
124
5.4 ProductionTimetableSubscriptionRequest 5.4.1 ProductionTimetableSubscriptionRequest — Element The ProductionTimetableSubscriptionRequest (Table 4) requests the asynchronous delivery of the information described by a ProductionTimetableRequest. The ProductionTimetableSubscriptionRequest Policy parameters control the processing of the subscription. Table 4 — ProductionTimetableSubscriptionRequest Parameters ProductionTimetableSubscriptionRequest +Structure Request for a subscription to the SIRI Production Timetable Service. Identity SubscriberRef 0:1 :marticipantCode See SIRI Part 2 for common SubscriptionRequest parameters. SubscriptionIdentifier 1:1 SubscriptionQualifier Lease InitialTerminationTime 1:1 xsd:dateTime Request ProductionTimetable-Request 1:1 +Structure See ProductionTimetableRequest.
Extensions 0:1 xsd:any* Placeholder for user extensions. 5.4.2 ProductionTimetableSubscriptionRequest — Example The following is an example of a ProductionTimetableSubscriptionRequest. SIST EN 15531-3:2015
2004-12-17T09:30:47-05:00
NADER
NADER
0000456
2001-12-17T09:30:47-05:00
2001-12-17T09:30:47-05:00
14:20:00
14:20:00
002
Smooth
123
Outbound
124
5.5 ProductionTimetableDelivery 5.5.1 Introduction The ProductionTimetableDelivery returns the position of a VEHICLE or group of VEHICLEs. 5.5.2 ServiceDelivery with a ProductionTimetableDelivery One or more ProductionTimetableDelivery elements may be returned as part of a SIRI Functional ServiceDelivery. Table 5 shows this element. Table 5 — ServiceDelivery / ProductionTimetableDelivery — Attributes ServiceDelivery +Structure See SIRI Part 2 ServiceDelivery HEADER ::: 1:1 See ServiceDelivery
Payload ProductionTimetableDelivery 0:* +Structure See ProductionTimetableDelivery element. 5.5.3 ProductionTimetableDelivery — Element Each ProductionTimetableDelivery is made up of DatedTimetableVersionFrame elements. There will be status messages for any request that could not be returned. Table 6 shows this element. Table 6 — ProductionTimetableDelivery — Attributes ProductionTimetableDelivery +Structure Describes one or more Dated Timetables. Attributes version 1:1 VersionString Version identifier of Production Timetable Service. Fixed, e.g. 1.0. LEADER ::: 1:1 xxxServiceDelivery See SIRI Part 2.xxxServiceDeliveryh Payload DatedTimetableVersionFrame 0:* +Structure A version of the timetable to run on a specified date. See DatedTimetableVersionFrame element. any Extensions 0:1 xsd:any* Placeholder for user extensions. SIST EN 15531-3:2015
of journey. One per language (+SIRI v2.0). DestinationDisplay 0:* NLString Name of DESTINATION of journey. One per language (Unbounded 0:* since +SIRI v2.0). LineNote 0:* NLString Text associated with LINE.
One per language (Unbounded 0:* since +SIRI v2.0).
FirstOrLastJourney 0:1 unspecified Whether journey is first or last jouurney of day. +SIRI v2.0 Real time defaults HeadwayService 0:1 xsd:boolean Whether this is a Headway Service, that is one shown as operating at a prescribed interval rather than to a fixed timetable. Monitored 0:1 xsd:boolean Whether there is real-time information available for journey, if not present, not known. Journeys DatedVehicleJourney 0:* +Structure Provides schedule information about the VEHICLE JOURNEY along which a VEHICLE is running. Inter-changes ServiceJourney-Interchange 0:* +Structure Provides schedule information about the planned SERVICE JOURNEY INTERCHANGEs that connect services. any Extensions 0:1 xsd:any* Placeholder for user extensions. 5.5.4.2 DatedVehicleJourney — Element Each DatedVehicleJourney contains an ordered list of DatedCall elements representing the sequence of stop CALLs, as well as other properties that apply to the VEHICLE JOURNEY as a whole. Table 8 shows this element. SIST EN 15531-3:2015
+SIRI v2.0). One per language
DestinationDisplay 0:* NLString The appropriate text to be used as Destination for this VEHICLE JOURNEY. Can be overridden at individual calling points.
One per language (Unbounded 0:* since +SIRI v2.0). LineNote 0:* NLString Additional text associated with LINE. Inherited property. One per language (Unbounded 0:* since +SIRI v2.0). FirstOrLastService 0:1 xsd:boolean Whether journey is first or last jouurney of day. +SIRI v2.0 Timetable-info HeadwayService 0:1 xsd:boolean Whether this is a HEADWAY JOURNEY, that is one shown as operating at a prescribed interval rather than to a fixed timetable. Real-time Info Monitored 0:1 xsd:boolean Whether there is real-time information available for journey, if not present, not known. lperation-al Block ::: 0:1 lperationalBlockGroup See SIRI Part 2 OperationalBlockGroup. Children a DatedCalls 1:1 +Structure Complete sequence of stops along the route path, in calling order. CALLs are in order within a JOURNEY PATTERN.
DatedCall 2:* +Structure Individual DatedCall. See below. any Extensions 0:1 xsd:any* Placeholder for user extensions. SIST EN 15531-3:2015
5.5.4.3 DatedCall — Element Each DatedCall describes the PASSING TIMEs of a VEHICLE JOURNEY at a stop, together with other data elements relating to the CALL. A journey shall contain at least two CALLs. Table 9 shows this element. Table 9 — DatedCall — Attributes DatedCall +Structure Provides information about a CALL in a DATED VEHICLE JOURNEY. Stop Identity StopPointRef 1:1 :ptopmointCode Reference to a SCHEDULED STOP POINT. Defaults to that of context i.e. that specified on StopPoint. VisitNumber 0:1 VisitNumberType For JOURNEY PATTERNs that involve repeated visits by a VEHICLE to a stop, the VisitNumber count is used to distinguish each separate visit. Default is ‘1’ Order 0:1 xsd:positive-Integer For implementations for which the overall Order within JOURNEY PATTERN is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the overall Order as well if useful. StopPointName 0:* NLString Name of Stop. One per language (Unbounded 0:* since +SIRI v2.0). Info TimingPoint 0:1 xsd:boolean Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is ‘true’. BoardingStretch 0:1 xsd:boolean Whether this is a Hail and Ride stop. A hail and ride stop may represent a linear stretch in the stop model. Default is ‘false’. RequestStop 0:1 xsd:boolean Whether VEHICLE stops only if requested explicitly by passenger. Default is ‘false’. Service Info OriginDisplay 0:* NLString The publicised ORIGIN at this point in the journey; used to help identify the VEHICLE to the public. Since VEHICLEs can change their published ORIGIN during a journey, the Origin included here should be what the VEHICLE will display when it reaches this stop. The ORIGIN DISPLAY is specified by exception: if none is specified, the value from any previous DatedCall instances for the same journey will be used. If there are none then any values from the underlying DatedVehicleJourney will be used, or failing that, from the DatedTimetableVersionFrame. One per language (Unbounded 0:* since +SIRI v2.0). DestinationDisplay 0:* NLString The publicised DESTINATION at this point in the journey; used to help identify the VEHICLE to the public. Since VEHICLEs can change their published DESTINATION during a journey, the destination included here should be what the VEHICLE will display when it reaches this stop. The DESTINATION DISPLAY is specified by exception: if none is specified, the value from any previous DatedCall instances for the same journey will be used. If there are none then any values from the underlying DatedVehicleJourney will be used, or failing that, from the DatedTimetableVersionFrame. One per language (Unbounded 0:* since +SIRI v2.0). SIST EN 15531-3:2015
AimedQuayRef 0:1 :nuayCodeType Physical QUAY to use according to the planned timetable. +SIRI v2.0 Aimed-QuayName 0:1 NLString Scheduled Platform name. Can be used to indicate a platform change. +SIRI v2.0. aepart-ure Aimed-DepartureTime 0:1 xsd:dateTime Aimed Departure Time in either the original or Production Timetable. Departure-PlatformName 0:1 NLString Bay or platform (QUAY) name from which VEHICLE will depart. Departure-BoardingActivity 0:1 aeparture-BoardingActivityEnum Type of boarding allowed at stop. Default is ‘boarding’h boarding | noBoarding| passthru DepartureStop-Assignment 0:1 +Structure Assignments of departure platform for SCHEDULED STOP POINT to a physical QUAY. +SIRI v2.0.
+SIRI v2.0. aetailievel: normal.
AimedQuayRef 0:1 :nuayCodeType Physical QUAY (Platform) to use according to the planned timetable. +SIRI v2.0 Aimed-QuayName 0:* NLString Scheduled QUAY (Platform) name. Can be used to indicate a platform change. +SIRI v2.0 One per language
AimedLatestPassengerAccessTime 0:1 xsd:dateTime Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI 2.0 Head-way AimedHeadway-Interval 0:1 Positive-aurationqype Target headway interval between services for frequency based services. Interchange Targeted-Interchange 0:* +Structure Information on any planned connections. If omitted: No connections, i.e. TargetedInterchangeh aeprecated from pfof vlhj Interchange FromServiceJourneyInterchange 0:* +Structure Information on any feeder of a planned connections.
+SIRI v2.0 Interchange ToServiceJourneyInterchange 0:* +Structure Information on any distributor of a planned connections.
+SIRI v2.0 any Extensions 0:1 xsd:any* Placeholder for user extensions.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...