1. OJP.xsd - OJP messages as extension of SIRI

1.1. The toplevel element OJP

OJP

-

@version

1:1

The element contains one of the following elements (a-b)

a

→‍OJPRequest

-1:1

+OJPRequest

OJP Request - Groups individual functional requests.

b

→‍OJPResponse

-1:1

+OJPResponse

OJP Request - Groups individual functional responses.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

1.2. The toplevel element OJPRequest

OJPRequest

+OJPRequest

OJP Request - Groups individual functional requests.

1.3. The toplevel element OJPResponse

OJPResponse

+OJPResponse

OJP Request - Groups individual functional responses.

1.4. The complex type OJPRequestStructure

OJPRequestStructure

Type for OJP Request - Groups individual functional requests.

The element contains one of the following elements (a-d)

In case of choice 'a', the element contains one of the following elements (aa-ac)

siri:ServiceRequest

aa

→‍siri:ServiceRequest

-1:1

+local-type: typedef-77.2

Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest)

ab

→‍siri:SubscriptionRequest

-1:1

+local-type: typedef-77.3

Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse.

ac

→‍siri:TerminateSubscriptionRequest

-1:1

+siri:TerminateSubscriptionRequest

Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse.

In case of choice 'b', the element contains one of the following elements (ba-bb)

siri:DeliveryRequest

ba

→‍siri:DataReadyNotification

-1:1

+siri:DataReadyRequest

Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse.

bb

→‍siri:DataSupplyRequest

-1:1

+siri:DataSupplyRequest

Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery.

In case of choice 'c', the element contains one of the following elements (ca-cb)

siri:StatusRequest

ca

→‍siri:CheckStatusRequest

-1:1

+siri:CheckStatusRequest

Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest.

cb

→‍siri:HeartbeatNotification

-1:1

+siri:HeartbeatNotification

Notification from Producer to Consumer to indicate that the service is running normally.

In case of choice 'd', the element contains one of the following elements (da-db)

siri:SiriDiscoveryRequest

da

→‍siri:CapabilitiesRequest

-1:1

+siri:CapabilitiesRequest

Requests a the current capabilities of the server. Answred with a CpabailitiesResponse.

In case of choice 'db', the element contains one of the following elements (dba-dbh)

siri:SiriReferenceDiscoveryRequest

dba

→‍siri:StopPointsRequest

-1:1

+local-type: typedef-73.1

Requests a list of the STOP POINTs and places covered by a Producer.

dbb

→‍siri:LinesRequest

-1:1

+siri:LinesDiscoveryRequest

Requests a list of the LINEs covered by a Producer.

dbc

→‍siri:ServiceFeaturesRequest

-1:1

+local-type: typedef-73.2

Requests a list of the Service Features covered by a Producer.

dbd

→‍siri:ProductCategoriesRequest

-1:1

+siri:ProductCategoriesDiscoveryRequest

Requests a list of the Product Categories covered by a Producer.

dbe

→‍siri:VehicleFeaturesRequest

-1:1

+siri:VehicleFeaturesRequest

Requests a list of the Vehicle Features covered by a Producer.

dbf

→‍siri:InfoChannelRequest

-1:1

+siri:InfoChannelDiscoveryRequest

Requests a list of the Info Channels covered by a Producer.

dbg

→‍siri:FacilityRequest

-1:1

+siri:FacilityRequest

Requests a list of the Facilities covered by a Producer.

dbh

→‍siri:ConnectionLinksRequest

-1:1

+siri:ConnectionLinksDiscoveryRequest

Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0)

1.5. The complex type OJPResponseStructure

OJPResponseStructure

Type for OJP Response - Groups individual functional responses.

The element contains one of the following elements (a-d)

In case of choice 'a', the element contains one of the following elements (aa-ab)

siri:ServiceResponse

aa

→‍siri:SubscriptionResponse

-1:1

+siri:SubscriptionResponse

Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest.

ab

→‍siri:TerminateSubscriptionResponse

-1:1

+siri:TerminateSubscriptionResponse

Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse.

In case of choice 'b', the element contains one of the following elements (ba-bc)

siri:DeliveryResponse

ba

→‍siri:DataReadyAcknowledgement

-1:1

+siri:DataReadyResponse

Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received.

bb

→‍siri:ServiceDelivery

-1:1

+local-type: typedef-77.4

Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request.

bc

→‍siri:DataReceivedAcknowledgement

-1:1

+siri:DataReceivedResponse

Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery.

In case of choice 'c', the element contains one of the following elements (ca)

siri:StatusResponse

ca

→‍siri:CheckStatusResponse

-1:1

+siri:CheckStatusResponse

Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest.

In case of choice 'd', the element contains one of the following elements (da-db)

siri:SiriDiscoveryResponse

da

→‍siri:CapabilitiesResponse

-1:1

+siri:CapabilitiesResponse

Responses with the capabilities of an implementation.

In case of choice 'db', the element contains one of the following elements (dba-dbh)

siri:SiriDiscoveryReferenceDelivery

dba

→‍siri:StopPointsDelivery

-1:1

+siri:StopPointsDelivery

Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest.

dbb

→‍siri:LinesDelivery

-1:1

+siri:LinesDelivery

Returns the LINEs covered by a web service. Answers a LINEsRequest.

dbc

→‍siri:ProductCategoriesDelivery

-1:1

+siri:ProductCategoriesDelivery

Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest.

dbd

→‍siri:ServiceFeaturesDelivery

-1:1

+siri:ServiceFeaturesDelivery

Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest.

dbe

→‍siri:VehicleFeaturesDelivery

-1:1

+siri:VehicleFeaturesDelivery

Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest.

dbf

→‍siri:InfoChannelDelivery

-1:1

+siri:InfoChannelDelivery

Returns the Info Channels covered by a service. Answers a InfoChannelRequest.

dbg

→‍siri:FacilityDelivery

-1:1

+siri:FacilityDelivery

Returns the Facilities covered by a service. Answers a StopPointsRequest.

dbh

→‍siri:ConnectionLinksDelivery

-1:1

+siri:ConnectionLinksDelivery

Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0)

1.6. The complex type group[siri:ServiceDeliveryRequestStatusGroup]/ErrorCondition#complexType (typedef-50.1)

group[siri:ServiceDeliveryRequestStatusGroup]
  /ErrorCondition #complexType
  (typedef-50.1)

-

The element contains one of the following elements (a-b)

a

→‍siri:CapabilityNotSupportedError

-1:1

+siri:CapabilityNotSupportedError

Error: Service does not support the requested capability.

b

→‍siri:OtherError

-1:1

+siri:OtherError

Error: Error type other than the well defined codes.

siri:Description

0:1

>siri:ErrorDescription

Text description of error.

1.7. The complex type element[siri:StopPointsRequest]#complexType (typedef-73.1)

element[siri:StopPointsRequest]
  #complexType
  (typedef-73.1)

siri:StopPointsDiscoveryRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:AuthenticatedRequest

siri:AccountId

0:1

Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0)

siri:AccountKey

0:1

Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0)

siri:RequestorEndpoint

siri:Address

0:1

siri:EndpointAddress

Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.

→‍siri:RequestorRef

1:1

>siri:ParticipantRef

Reference to a requestor - Participant Code.

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique identifier that can be used to reference this message in subsequent interactions.

@version

1:1

siri:VersionString

Version number of request. Fixed

The element contains one of the following elements (a-c)

siri:StopPointsDiscoveryRequestTopic

a

siri:BoundingBox

-0:1

+siri:BoundingBox

Rectangle containing stops be returned. ((since SIRI 2.0))

b

siri:Circle

-0:1

+siri:Location

Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0))

c

siri:PlaceRef

-0:1

Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0))

siri:OperatorRef

0:1

>siri:OperatorRef

Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0))

siri:LineRef

0:1

>siri:LineRef

Filter the results to include only stops for the given LINE. ((since SIRI 2.0))

siri:StopPointsDiscoveryRequestPolicy

siri:Language

0:*

Preferred languages in which to return text values. (since SIRI 2.0)

siri:StopPointsDetailLevel

0:1

siri:StopPointsDetailEnumeration

Level of detail to include in response. Default is 'normal'. (since SIRI 2.0)

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

1.8. The complex type element[siri:ServiceFeaturesRequest]#complexType (typedef-73.2)

element[siri:ServiceFeaturesRequest]
  #complexType
  (typedef-73.2)

siri:ServiceFeaturesDiscoveryRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:AuthenticatedRequest

siri:AccountId

0:1

Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0)

siri:AccountKey

0:1

Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0)

siri:RequestorEndpoint

siri:Address

0:1

siri:EndpointAddress

Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.

→‍siri:RequestorRef

1:1

>siri:ParticipantRef

Reference to a requestor - Participant Code.

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique identifier that can be used to reference this message in subsequent interactions.

@version

1:1

siri:VersionString

Version number of request. Fixed

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

1.9. The complex type element[siri:ServiceRequest]#complexType (typedef-77.2)

element[siri:ServiceRequest]
  #complexType
  (typedef-77.2)

siri:ServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

siri:ServiceRequestContext

0:1

+siri:ServiceRequestContext

General request properties - typically configured rather than repeated on request.

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:AuthenticatedRequest

siri:AccountId

0:1

Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0)

siri:AccountKey

0:1

Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0)

siri:RequestorEndpoint

siri:Address

0:1

siri:EndpointAddress

Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.

→‍siri:RequestorRef

1:1

>siri:ParticipantRef

Reference to a requestor - Participant Code.

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique identifier that can be used to reference this message in subsequent interactions.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

1.10. The complex type element[siri:SubscriptionRequest]#complexType (typedef-77.3)

element[siri:SubscriptionRequest]
  #complexType
  (typedef-77.3)

siri:SubscriptionRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:AuthenticatedRequest

siri:AccountId

0:1

Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0)

siri:AccountKey

0:1

Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0)

siri:RequestorEndpoint

siri:Address

0:1

siri:EndpointAddress

Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.

→‍siri:RequestorRef

1:1

>siri:ParticipantRef

Reference to a requestor - Participant Code.

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique identifier that can be used to reference this message in subsequent interactions.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:SubscriberEndpoint

siri:ConsumerAddress

0:1

siri:EndpointAddress

Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data.

siri:SubscriptionFilterIdentifier

0:1

Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature.

siri:SubscriptionContext

0:1

+siri:SubscriptionContext

General values that apply to subscription. Usually set by configuration.

→‍siri:AbstractFunctionalServiceSubscriptionRequest

1:*

+siri:AbstractSubscription

Subsititutable type for a SIRI Functional Service subscription request.

1.11. The complex type element[siri:ServiceDelivery]#complexType (typedef-77.4)

element[siri:ServiceDelivery]
  #complexType
  (typedef-77.4)

siri:ServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

siri:ProducerResponseEndpoint

siri:ProducerRef

0:1

>siri:ParticipantRef

Unique identifier of Producer - Participant reference.

siri:Address

0:1

siri:EndpointAddress

Endpoint Address to which acknowledgements to confirm delivery are to be sent.

siri:ResponseMessageIdentifier

0:1

>siri:MessageQualifier

An arbitrary unique reference associated with the response which may be used to reference it.

siri:RequestMessageRef

0:1

>siri:MessageRef

Reference to an arbitrary unique identifier associated with the request which gave rise to this response.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

@srsName

1:1

siri:SrsNameType

Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points.

siri:ServiceDeliveryRequestStatus

siri:Status

0:1

Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'.

siri:ErrorCondition

0:1

+local-type: typedef-50.1

Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails.

siri:ServiceDeliveryBody

siri:MoreData

0:1

Whether there is a further delvery message with more current updates that follows this one. Default is 'false'.

→‍siri:AbstractFunctionalServiceDelivery

1:*

+siri:AbstractServiceDelivery

Subsititutable type for a SIRI Functional Service request.

1.12. The complex type element[ojp:OJP]#complexType (typedef-105.1)

element[ojp:OJP]
  #complexType
  (typedef-105.1)

-

@version

1:1

The element contains one of the following elements (a-b)

a

→‍OJPRequest

-1:1

+OJPRequest

OJP Request - Groups individual functional requests.

b

→‍OJPResponse

-1:1

+OJPResponse

OJP Request - Groups individual functional responses.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2. OJP/OJP_Requests.xsd - OJP service requests and responses

2.1. The toplevel element OJPAvailabilityDelivery

OJPAvailabilityDelivery

+OJPAvailabilityDelivery (↔ siri:AbstractFunctionalServiceDelivery)

The availability service informs about the availability of a MOBILITY SERVICE, a VEHICLE, SERVICE JOURNEY, or SINGLE JOURNEY. This service implements the models PI QR AM Vehicle Type Request and PI QR AM Mobility Service Request from TM 6.

2.2. The toplevel element OJPAvailabilityRequest

OJPAvailabilityRequest

+OJPAvailabilityRequest (↔ siri:AbstractFunctionalServiceRequest)

The availability service informs about the availability of a MOBILITY SERVICE, a VEHICLE, SERVICE JOURNEY, or SINGLE JOURNEY. This service implements the models PI QR AM Vehicle Type Request and PI QR AM Mobility Service Request from TM 6.

2.3. The toplevel element OJPExchangePointsDelivery

OJPExchangePointsDelivery

+OJPExchangePointsDelivery (↔ siri:AbstractFunctionalServiceDelivery)

Distributed journey planning requires several journey planning systems planning parts of the whole trip which shall be assembled. Each of the planners will therefore get a sub-query to plan: the first planner from the origin of the trip to its system boundaries, the next planner must find trips from these boundaries to its boundaries with the next systems. This process will be continued until the final system where the destination of the user’s trip is located. The boundary points where the trip calculation is handed over to the next journey planning system are called exchange points. If they are not known in advance the exchange points can be looked up from a server by using the exchange points service. This service implements the model PI QR Location Request from TM 6.

2.4. The toplevel element OJPExchangePointsRequest

OJPExchangePointsRequest

+OJPExchangePointsRequest (↔ siri:AbstractFunctionalServiceRequest)

Distributed journey planning requires several journey planning systems planning parts of the whole trip which shall be assembled. Each of the planners will therefore get a sub-query to plan: the first planner from the origin of the trip to its system boundaries, the next planner must find trips from these boundaries to its boundaries with the next systems. This process will be continued until the final system where the destination of the user’s trip is located. The boundary points where the trip calculation is handed over to the next journey planning system are called exchange points. If they are not known in advance the exchange points can be looked up from a server by using the exchange points service. This service implements the model PI QR Location Request from TM 6.

2.5. The toplevel element OJPFareDelivery

OJPFareDelivery

+OJPFareDelivery (↔ siri:AbstractFunctionalServiceDelivery)

This service provides general, stop-specific and trip-specific fare information. This service implements the models PI Stop Fare Request, PI FQ Fare Product Request, PI FQ Single Trip Fare Request from TM 6.

2.6. The toplevel element OJPFareRequest

OJPFareRequest

+OJPFareRequest (↔ siri:AbstractFunctionalServiceRequest)

This service provides general, stop-specific and trip-specific fare information. This service implements the models PI Stop Fare Request, PI FQ Fare Product Request, PI FQ Single Trip Fare Request from TM 6.

2.7. The toplevel element OJPLineInformationDelivery

OJPLineInformationDelivery

+OJPLineInformationDelivery (↔ siri:AbstractFunctionalServiceDelivery)

The service provides route information about a given LINE. This helps when displaying the LINE on maps. This implements a small part of PI QR Schedule Request of TM 6.

2.8. The toplevel element OJPLineInformationRequest

OJPLineInformationRequest

+OJPLineInformationRequest (↔ siri:AbstractFunctionalServiceRequest)

The service provides route information about a given LINE. This helps when displaying the LINE on maps. This implements a small part of model PI QR Schedule Request of TM 6.

2.9. The toplevel element OJPLocationInformationDelivery

OJPLocationInformationDelivery

+OJPLocationInformationDelivery (↔ siri:AbstractFunctionalServiceDelivery)

The Location Information service comprises the following four base functions: matching text input against possible origin and destination locations, retrieval of all location objects (bunch delivery), geographical context service that provides location objects within a bounding box, reverse address resolution service that delivers the nearest address for a given coordinate. By means of abstraction these functions are assembled within one single service – the Location Information service. This way, even more possible applications have arisen, such as: finding the nearest stops/stations for a given coordinate, matching text input against the names of locations near a given coordinate. This service implements the model PI QR Location Request from TM 6.

2.10. The toplevel element OJPLocationInformationRequest

OJPLocationInformationRequest

+OJPLocationInformationRequest (↔ siri:AbstractFunctionalServiceRequest)

The Location Information service comprises the following four base functions: matching text input against possible origin and destination locations, retrieval of all location objects (bunch delivery), geographical context service that provides location objects within a bounding box, reverse address resolution service that delivers the nearest address for a given coordinate. By means of abstraction these functions are assembled within one single service – the Location Information service. This way, even more possible applications have arisen, such as: finding the nearest stops/stations for a given coordinate, matching text input against the names of locations near a given coordinate. This service implements the model PI QR Location Request from TM 6.

2.11. The toplevel element OJPMultiPointTripDelivery

OJPMultiPointTripDelivery

+OJPMultiPointTripDelivery (↔ siri:AbstractFunctionalServiceDelivery)

This service provides intermodal trip information from multiple origin location to multiple destination taking various user preferences into account. In the case of OJPMultipointTripRequest it is a set of origins and destinations that are searched. This service implements the model PI QR Trip Request from TM 6.

2.12. The toplevel element OJPMultiPointTripRequest

OJPMultiPointTripRequest

+OJPMultiPointTripRequest (↔ siri:AbstractFunctionalServiceRequest)

This service provides intermodal trip information from multiple origin location to multiple destination taking various user preferences into account. In the case of OJPMultipointTripRequest it is a set of origins and destinations that are searched. This service implements the model PI QR Trip Request from TM 6.

2.13. The toplevel element OJPStatusDelivery

OJPStatusDelivery

+OJPStatusDelivery (↔ siri:AbstractFunctionalServiceDelivery)

The status service provides basic information about the operational status of an OJP system.

2.14. The toplevel element OJPStatusRequest

OJPStatusRequest

+OJPStatusRequest (↔ siri:AbstractFunctionalServiceRequest)

The status service provides basic information about the operational status of an OJP system.

2.15. The toplevel element OJPStopEventDelivery

OJPStopEventDelivery

+OJPStopEventDelivery (↔ siri:AbstractFunctionalServiceDelivery)

This service provides information on arrivals and/or departures of public transport services from stops for a requested time or period of time. Restrictions can be set in the request parameters that filter the result contents accordingly. This service implements PI QR Stop Event Request from TM 6

2.16. The toplevel element OJPStopEventRequest

OJPStopEventRequest

+OJPStopEventRequest (↔ siri:AbstractFunctionalServiceRequest)

This service provides information on arrivals and/or departures of public transport services from stops for a requested time or period of time. Restrictions can be set in the request parameters that filter the result contents accordingly. This service implements the model PI QR Stop Event Request from TM 6

2.17. The toplevel element OJPTripChangeDelivery

OJPTripChangeDelivery

+OJPTripChangeDelivery (↔ siri:AbstractFunctionalServiceDelivery)

A trip can be modified in a limited manner by specifying a longer time duration for a specific interchange or by specifying an estimated leg for which the exact time information shall be retrieved. In both cases, earlier or later legs of the trip may be recalculated as well.

2.18. The toplevel element OJPTripChangeRequest

OJPTripChangeRequest

+OJPTripChangeRequest (↔ siri:AbstractFunctionalServiceRequest)

A trip can be modified in a limited manner by specifying a longer time duration for a specific interchange or by specifying an estimated leg for which the exact time information shall be retrieved. In both cases, earlier or later legs of the trip may be recalculated as well.

2.19. The toplevel element OJPTripDelivery

OJPTripDelivery

+OJPTripDelivery (↔ siri:AbstractFunctionalServiceDelivery)

This service provides intermodal trip information from an origin location to a destination taking various user preferences into account. In the case of OJPTripRequest it is single origin and a single destination that are searched. This service implements the model PI QR Trip Request from TM 6.

2.20. The toplevel element OJPTripInfoDelivery

OJPTripInfoDelivery

+OJPTripInfoDelivery (↔ siri:AbstractFunctionalServiceDelivery)

This service provides information on a single leg (service pattern, real-time status, vehicle facilities etc.). The service always provides information about a VEHICLE or a SERVICE JOURNEY. It doesn't directly provide information about a trip. If the response changes the conditions in such a way that the trip becomes invalid (connection no longer possible, delay, cancellation), a new TripRequest is required for the remainder of the trip. The service also provides information about formation, occupancy, and capacity. The full SIRI elements are used. Therefore, a lot of things can be expressed. Some that go beyond what usually may be required. However, if accessibility is fully to be considered (with stop-vehicle interaction), then SIRI must be used in full. The relevant SIRI documentation should be considered. This service implements PI QR Service Journey Request and PI QR Single Journey Request from TM 6.

2.21. The toplevel element OJPTripInfoRequest

OJPTripInfoRequest

+OJPTripInfoRequest (↔ siri:AbstractFunctionalServiceRequest)

This service provides information on a single leg (service pattern, real-time status, vehicle facilities etc.). The service always provides information about a VEHICLE or a SERVICE JOURNEY. It doesn't directly provide information about a trip. If the response changes the conditions in such a way that the trip becomes invalid (connection no longer possible, delay, cancellation), a new TripRequest is required for the remainder of the trip. The service also provides information about formation, occupancy, and capacity. The full SIRI elements are used. Therefore, a lot of things can be expressed. Some that go beyond what usually may be required. However, if accessibility is fully to be considered (with stop-vehicle interaction), then SIRI must be used in full. The relevant SIRI documentation should be considered. This service implements PI QR Service Journey Request and PI QR Single Journey Request from TM 6.

2.22. The toplevel element OJPTripRefineDelivery

OJPTripRefineDelivery

+OJPTripRefineDelivery (↔ siri:AbstractFunctionalServiceDelivery)

The trip refinement service retrieves additional or updated information (e.g., real-time data) about a given, previously retrieved trip. It does not depend on the assumption that the trip has been retrieved from the same server; it may, in fact, even stem from another source than a OJP system. An example scenario may involve a trip retrieved from a system A and one wishes to refine the trip with real time information from another system B. As it cannot be ascertained that both systems use identical object IDs, this is signalled by setting ExternalObjectRefs to true. System B, being confronted with external IDs, must try to recognise the relevant objects in another way and retrieve them in its own database. In the response it will use its own object IDs. To maintain a consistent mapping, it is imperative that system B reflects the structure of the refine request precisely in its response (principle of structure maintenance).

2.23. The toplevel element OJPTripRefineRequest

OJPTripRefineRequest

+OJPTripRefineRequest (↔ siri:AbstractFunctionalServiceRequest)

The trip refinement service retrieves additional or updated information (e.g., real-time data) about a given, previously retrieved trip. It does not depend on the assumption that the trip has been retrieved from the same server; it may, in fact, even stem from another source than a OJP system. An example scenario may involve a trip retrieved from a system A and one wishes to refine the trip with real time information from another system B. As it cannot be ascertained that both systems use identical object IDs, this is signalled by setting ExternalObjectRefs to true. System B, being confronted with external IDs, must try to recognise the relevant objects in another way and retrieve them in its own database. In the response it will use its own object IDs. To maintain a consistent mapping, it is imperative that system B reflects the structure of the refine request precisely in its response (principle of structure maintenance).

2.24. The toplevel element OJPTripRequest

OJPTripRequest

+OJPTripRequest (↔ siri:AbstractFunctionalServiceRequest)

This service provides intermodal trip information from an origin location to a destination taking various user preferences into account. In the case of OJPMultipointTripRequest it is a set of origins and destinations that are searched. This service implements the model PI QR Trip Request from TM 6.

2.25. The complex type OJPAvailabilityDeliveryStructure

OJPAvailabilityDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

AvailabilityResponse

AvailabilityResponseContext

0:1

+ResponseContext

Context to hold availability response objects that occur frequently.

AvailabilityResult

0:1

+AvailabilityResult

Indication of the availability of the requested service.

Extension

0:1

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.26. The complex type OJPAvailabilityRequestStructure

OJPAvailabilityRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

The element contains one of the following elements (a)

AvailabilityRequest

a

PublicTransport

-1:1

+BookingPTLeg

Definition of the journey leg to be covered by public transport. Other mobility services can be added later.

MobilityUser

1:*

+BookingUser

Passenger(s) for whom the service needs to be booked, one MobilityUser per passenger.

MinMaxTimeBand

EarliestDepartureTime

0:1

Earliest possible departure time from start location.

LatestArrivalTime

0:1

Latest possible arrival time at destination location.

AvailabilityRequest

Extension

0:1

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.27. The complex type OJPExchangePointsDeliveryStructure

OJPExchangePointsDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPExchangePointsRequest

0:1

+OJPExchangePointsRequest

Distributed journey planning requires several journey planning systems planning parts of the whole trip which shall be assembled. Each of the planners will therefore get a sub-query to plan: the first planner from the origin of the trip to its system boundaries, the next planner must find trips from these boundaries to its boundaries with the next systems. This process will be continued until the final system where the destination of the user’s trip is located. The boundary points where the trip calculation is handed over to the next journey planning system are called exchange points. If they are not known in advance the exchange points can be looked up from a server by using the exchange points service. This service implements the model PI QR Location Request from TM 6.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

ExchangePointsResponse

ExchangePointsResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

ContinueAt

0:1

If the response returns fewer results than expected, the value of skip can be used in a follow-up request to get further results. It tells the server to skip the given number of results in its response.

ExchangePointsResult

0:*

+ExchangePointsResult

The exchange points found by the service.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.28. The complex type OJPExchangePointsRequestStructure

OJPExchangePointsRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

ExchangePointsRequest

PlaceRef

0:1

+PlaceRef

Location/Place for which exchange points to other "neighbour" systems are to be searched. This location/place is usually the origin/destination of a passenger journey. May be omitted if all exchange points shall be returned.

Params

0:1

+ExchangePointsParam

E.g. location/place types (stops, addresses, POIs) or specific location/place attributes

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.29. The complex type OJPFareDeliveryStructure

OJPFareDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

FareResponse

FareResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

FareResult

0:*

+FareResult

Fare result choice element.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.30. The complex type OJPFareRequestStructure

OJPFareRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

The element contains one of the following elements (a-e)

FareRequest

a

StopFareRequest

-1:1

+StopFareRequest

A request for stop-related FARE information.

b

PlaceFareRequest

-1:1

+PlaceFareRequest

A request for place-related FARE information.

c

StaticFareRequest

-1:1

+StaticFareRequest

A request for general/static FARE information.

d

TripFareRequest

-1:1

+TripFareRequest

A request to calculate the FARE information of a single trip.

e

MultiTripFareRequest

-1:1

+MultiTripFareRequest

A request to calculate aggregated FARE information of multiple single trips.

Params

0:1

+FareParam

Parameter to filter the response contents.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.31. The complex type OJPLineInformationDeliveryStructure

OJPLineInformationDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPLineInformationRequest

0:1

+OJPLineInformationRequest

The service provides route information about a given LINE. This helps when displaying the LINE on maps. This implements a small part of model PI QR Schedule Request of TM 6.

LineInformationResponse

LineResult

0:*

+LineResult

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.32. The complex type OJPLineInformationRequestStructure

OJPLineInformationRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

LineDirectionFilter

0:1

+LineDirectionFilter

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.33. The complex type OJPLocationInformationDeliveryStructure

OJPLocationInformationDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPLocationInformationRequest

0:1

+OJPLocationInformationRequest

The Location Information service comprises the following four base functions: matching text input against possible origin and destination locations, retrieval of all location objects (bunch delivery), geographical context service that provides location objects within a bounding box, reverse address resolution service that delivers the nearest address for a given coordinate. By means of abstraction these functions are assembled within one single service – the Location Information service. This way, even more possible applications have arisen, such as: finding the nearest stops/stations for a given coordinate, matching text input against the names of locations near a given coordinate. This service implements the model PI QR Location Request from TM 6.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

LocationInformationResponse

LocationInformationResponseContext

0:1

+ResponseContext

Context to hold response objects that occur frequently.

ContinueAt

0:1

If the response returns fewer results than expected, the value of skip can be used in a follow-up request to get further results. It tells the server to skip the given number of results in its response.

PlaceResult

0:*

+PlaceResult

The place/location objects found by the service are ordered in descending order of how well they match the input data. The first result in the list matches best.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.34. The complex type OJPLocationInformationRequestStructure

OJPLocationInformationRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

The element contains one of the following elements (a-b)

LocationInformationRequest

a

InitialInput

-1:1

+InitialLocationInput

Initial input for the location information request. This input defines what is originally looked for. Be aware that this also can contain PLACEs.

b

PlaceRef

-1:1

+PlaceRef

LOCATION / PLACE for further refinement. If a Place in a previous response was marked as not "complete" it can be refined by putting it here. If Places are organised hierarchically, it may be reasonable to identify the Place in a top-down approach with several steps of refining a Place on each level of hierarchy. Following this approach an initial request retrieves a first list of top-level Places (e.g., streets) which are to be refined in a subsequent request to the next level (e.g., house number intervals). The objects of the current level are presented to the user for selection. The object reference of the selected object is then sent in the next request for further refinement.

Restrictions

0:1

+PlaceParam

E.g. place types (stops, addresses, POIs) or specific place attributes

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.35. The complex type OJPMultiPointTripDeliveryStructure

OJPMultiPointTripDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPMultiPointTripRequest

0:1

+OJPMultiPointTripRequest

This service provides intermodal trip information from multiple origin location to multiple destination taking various user preferences into account. In the case of OJPMultipointTripRequest it is a set of origins and destinations that are searched. This service implements the model PI QR Trip Request from TM 6.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

MultiPointTripResponse

MultiPointType

0:1

MultiPointTypeEnumeration

The MultiPointType should be returned because it may differ from the one asked. Many systems will support only a subset of the MultiPointTypes, and it is important to know what the result is based on.

MultiPointTripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

MultiPointTripResult

0:*

+MultiPointTripResult

The trip results found by the server.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.36. The complex type OJPMultiPointTripRequestStructure

OJPMultiPointTripRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

MultiPointTripRequest

Origin

1:*

+PlaceContext

Specifies the origin situation from where the user wants to start.

Destination

1:*

+PlaceContext

Specifies the destination situation where the user is heading to.

Via

0:*

+TripVia

Ordered series of points where the journey must pass through. If more than one via point is given all of them must be obeyed - in the correct order. The server is allowed to replace a via stop by equivalent stops (in Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia).

NotVia

0:*

+NotVia

Not-via restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs that the TRIP is not allowed to pass through. If more than one not via point is given all of them must be obeyed.

NoChangeAt

0:*

+NoChangeAt

no-change-at restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs at which no TRANSFER is allowed within a TRIP (in Transmodel this would be an extension to TRIP MOBILITY FILTER).

Params

0:1

+MultiPointTripParam

Options to control the search behaviour and response contents.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.37. The complex type OJPStatusDeliveryStructure

OJPStatusDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPStatusRequest

0:1

+OJPStatusRequest

The status service provides basic information about the operational status of an OJP system.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

OJPStatusResponse

ServiceStarted

0:1

Time when the service was started.

ServiceReady

0:1

Time when the service started responding to queries.

LastTimetableUpdate

0:1

Time when the timetable was last updated.

ServerBuildVersion

0:1

Information about the server build.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.38. The complex type OJPStatusRequestStructure

OJPStatusRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.39. The complex type OJPStopEventDeliveryStructure

OJPStopEventDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPStopEventRequest

0:1

+OJPStopEventRequest

This service provides information on arrivals and/or departures of public transport services from stops for a requested time or period of time. Restrictions can be set in the request parameters that filter the result contents accordingly. This service implements the model PI QR Stop Event Request from TM 6

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

StopEventResponse

StopEventResponseContext

0:1

+ResponseContext

Container for data that is referenced multiple times.

StopEventResult

0:*

+StopEventResult

Enclosing element for stop event data.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.40. The complex type OJPStopEventRequestStructure

OJPStopEventRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

StopEventRequest

Location

1:1

+PlaceContext

LOCATION / PLACE for which to obtain stop event information. If a coordinate or an address is used, then the result may depend on other parameters: All stops in reasonable walking distance and stops that are within range of limitations of the IndividualTransportOptions should be shown. If the next stop is too far away, then no result is shown. "Reasonable" is usually defined as part of the server configuration.

Params

0:1

+StopEventParam

Request parameter

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.41. The complex type OJPTripChangeDeliveryStructure

OJPTripChangeDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPTripChangeRequest

0:1

+OJPTripChangeRequest

A trip can be modified in a limited manner by specifying a longer time duration for a specific interchange or by specifying an estimated leg for which the exact time information shall be retrieved. In both cases, earlier or later legs of the trip may be recalculated as well.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

TripChangeResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

TripResult

0:1

+TripResult

The trip results refined by the server.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.42. The complex type OJPTripChangeRequestStructure

OJPTripChangeRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

TripChangeRequest

ChangeParams

0:1

+TripChangeParam

Options to control the change.

TripResult

1:1

+TripResult

The trip result to be changed by the server.

TripResponseContext

0:1

+ResponseContext

Context to hold objects, which are referenced within the response.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.43. The complex type OJPTripDeliveryStructure

OJPTripDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPTripRequest

0:1

+OJPTripRequest

This service provides intermodal trip information from an origin location to a destination taking various user preferences into account. In the case of OJPMultipointTripRequest it is a set of origins and destinations that are searched. This service implements the model PI QR Trip Request from TM 6.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

TripResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

TripResult

0:*

+TripResult

The trip results found by the server.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.44. The complex type OJPTripInfoDeliveryStructure

OJPTripInfoDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPTripInfoRequest

0:1

+OJPTripInfoRequest

This service provides information on a single leg (service pattern, real-time status, vehicle facilities etc.). The service always provides information about a VEHICLE or a SERVICE JOURNEY. It doesn't directly provide information about a trip. If the response changes the conditions in such a way that the trip becomes invalid (connection no longer possible, delay, cancellation), a new TripRequest is required for the remainder of the trip. The service also provides information about formation, occupancy, and capacity. The full SIRI elements are used. Therefore, a lot of things can be expressed. Some that go beyond what usually may be required. However, if accessibility is fully to be considered (with stop-vehicle interaction), then SIRI must be used in full. The relevant SIRI documentation should be considered. This service implements PI QR Service Journey Request and PI QR Single Journey Request from TM 6.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

TripInfoResponse

TripInfoResponseContext

0:1

+ResponseContext

Response context.

TripInfoResult

0:1

+TripInfoResult

Result structure.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.45. The complex type OJPTripInfoRequestStructure

OJPTripInfoRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

The element contains one of the following element sequences (a-c)

DatedJourneyRef

a

→‍JourneyRef

-1:1

>JourneyRef

Reference to a Journey

a

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

DatedTrainNumberRef

b

TrainNumber

-1:1

b

OperatorRef

-1:1

>siri:OperatorRef

b

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

TimedVehicleRef

c

→‍siri:VehicleRef

-1:1

>siri:VehicleRef

Reference to a VEHICLE.

c

TimeOfOperation

-1:1

Time stamp when the vehicle is operating. In most use cases equal to "now".

TripInfoRequest

Params

0:1

+TripInfoParam

Request parameter.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.46. The complex type OJPTripRefineDeliveryStructure

OJPTripRefineDeliveryStructure

siri:AbstractServiceDelivery

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

The element contains one of the following elements (a) or element sequences (b)

siri:ContextualisedResponseEndpoint

a

siri:RequestMessageRef

-0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:SubscriptionIdentifierResourceProperty

b

siri:SubscriberRef

-0:1

>siri:ParticipantRef

Unique identifier of Subscriber - reference to a Participant.

b

siri:SubscriptionFilterRef

-0:1

>siri:SubscriptionFilterRef

Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted.

b

siri:SubscriptionRef

-1:1

>siri:SubscriptionRef

Reference to a service subscription: unique within Service and Subscriber.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:DeliveryStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

siri:SuccessInfo

siri:ValidUntil

0:1

End of data horizon of the data producer.

siri:ShortestPossibleCycle

0:1

siri:PositiveDurationType

Minimum interval at which updates can be sent.

siri:DeliveryDefault

siri:DefaultLanguage

0:1

Default language for text elements.

Inherited content is followed by own content:

→‍OJPTripRefineRequest

0:1

+OJPTripRefineRequest

The trip refinement service retrieves additional or updated information (e.g., real-time data) about a given, previously retrieved trip. It does not depend on the assumption that the trip has been retrieved from the same server; it may, in fact, even stem from another source than a OJP system. An example scenario may involve a trip retrieved from a system A and one wishes to refine the trip with real time information from another system B. As it cannot be ascertained that both systems use identical object IDs, this is signalled by setting ExternalObjectRefs to true. System B, being confronted with external IDs, must try to recognise the relevant objects in another way and retrieve them in its own database. In the response it will use its own object IDs. To maintain a consistent mapping, it is imperative that system B reflects the structure of the refine request precisely in its response (principle of structure maintenance).

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

TripRefineResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

UnknownLegRef

0:*

LegObjectIdType

Refers to a leg that was not found in the data of the server. If the to be refined TripResult could not be found or unequivocally determined, all RefineLegRefs are returned as UnknownLegRefs.

TripResult

0:*

+TripResult

The trip results refined by the server.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.47. The complex type OJPTripRefineRequestStructure

OJPTripRefineRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

TripRefineRequest

RefineParams

0:1

+TripRefineParam

Options to control the refine

TripResult

1:1

+TripResult

The trip result to be refined by the server.

TripResponseContext

0:1

+ResponseContext

Context to hold objects, which are referenced within the response.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

2.48. The complex type OJPTripRequestStructure

OJPTripRequestStructure

AbstractOJPServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

Inherited content is followed by own content:

TripRequest

Origin

1:*

+PlaceContext

Specifies the origin situation from where the user wants to start.

Destination

1:*

+PlaceContext

Specifies the destination situation where the user is heading to.

Via

0:*

+TripVia

Ordered series of points where the journey must pass through. If more than one via point is given all of them must be obeyed - in the correct order. The server is allowed to replace a via stop by equivalent stops. Note: Systems may support only one.

ViaSystem

0:*

>siri:ParticipantRef

With this parameter a distributing system is asked to build a trip using a given System to pass through. This helps in selecting Exchange Points for this trip. ViaSystem is also used in sequence. Note: Systems may support only one.

NotVia

0:*

+NotVia

Not-via restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs that the TRIP is not allowed to pass through. If more than one not via point is given all of them must be obeyed.

NoChangeAt

0:*

+NoChangeAt

no-change-at restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs at which no TRANSFER is allowed within a TRIP.

Params

0:1

+TripParam

Options to control the search behaviour and response contents.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).

3. OJP/OJP_RequestSupport.xsd - Supporting definitions for OJP service requests and their responses

3.1. Simple type definitions

CalcTimeType

xs:integer: (empty restriction)

Type definition for calculation time in milliseconds.

CertificateIdType

xs:NMTOKEN: (empty restriction)

Type definition for the form of identification that can be used as a Message Integrity Property (public key cryptography)

OJPGenericProblemTypeEnumeration

Types of problems that may be returned in case of generic problems with the request.

OJPGENERIC_REQUESTNOTSUPPORTED

The server does not support the specific request (e.g.: MultiPointTripRequest).

OJPGENERIC_FEATURENOTSUPPORTED

The server does not support the requested feature (e.g.: parameter NotVia in TripRequest).

OJPGENERIC_LANGUAGENOTSUPPORTED

For the display of texts within the result, the server (at least in the context of this request) does not support the requested language.

OJPGENERIC_EXCEPTIONFROMREQUESTEDLANGUAGE

When displaying texts within the result, the server does not support the requested language for all occurring text elements.

OJPGENERIC_DATAFRAMEREFNOTAVAILABLE

The server cannot provide the requested data frame (data version).

OJPGENERIC_SYSTEMID_NOT_FOUND

The server was not able to work with the SystemID that was provided.

OJPGENERIC_OTHER

A problem has occurred that does not have a specific problem type.

SignatureType

xs:string: (empty restriction)

data for transmission of message signatures (public key cryptography), used to prove Message Integrity

3.2. The toplevel element OJPGenericProblemType

OJPGenericProblemType

+OJPGenericProblemTypeEnumeration (↔ ojp:ErrorType)

3.3. The group MessageIntegrityPropertiesGroup

MessageIntegrityPropertiesGroup

Properties that allow checks for message integrity.

MessageIntegrityProperties

Signature

0:1

SignatureType

Authorisation signature (data for transmission of message signatures (public key cryptography), used to prove Message Integrity).

CertificateId

0:1

CertificateIdType

form of identification that can be used as a Message Integrity Property (public key cryptography)

3.4. The group ServiceRequestContextGroup

ServiceRequestContextGroup

Generic context for all request messages.

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

3.5. The group ServiceResponseContextGroup

ServiceResponseContextGroup

Generic context for all response messages.

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

3.6. The complex type AbstractOJPServiceRequestStructure

AbstractOJPServiceRequestStructure

siri:AbstractFunctionalServiceRequest

Type for General SIRI Request.

The element content starts with items inherited from the base type:

→‍siri:RequestTimestamp

1:1

Timestamp on request.

siri:ContextualisedRequestEndpoint

siri:MessageIdentifier

0:1

>siri:MessageQualifier

Arbitrary unique reference to this message.

Inherited content is followed by own content:

ServiceRequestContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

Extension

0:1

3.7. The complex type Operators_RelStructure

Operators_RelStructure

Structure providing a collection of operators.

Operator

1:*

+siri:AffectedOperator

Operator of the service.

3.8. The complex type PlacesStructure

PlacesStructure

Structure providing a collection of places.

Place

1:*

+Place

3.9. The complex type ResponseContextStructure

ResponseContextStructure

Structure providing response contexts related to journeys, containing collections of places and situations (from Transmodel "view" these are all implementation related aspects of the physical model).

Operators

0:1

+Operators_Rel

Container for OPERATOR objects. Only operator objects that are referenced in the response should be put into the container.

Places

0:1

+Places

Container for place objects. Only place objects that are referenced in the response should be put into the container.

Situations

0:1

+Situations

Container for SIRI SX situation objects. Only situations that are referenced in the response should be put into the container.

4. OJP/OJP_Fare.xsd - Request and response definitions for general, stop-specific and trip-specific fare information

4.1. Simple type definitions

FareResultObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

4.2. The group FareRequestGroup

FareRequestGroup

Fare request structure.

The element contains one of the following elements (a-e)

FareRequest

a

StopFareRequest

-1:1

+StopFareRequest

A request for stop-related FARE information.

b

PlaceFareRequest

-1:1

+PlaceFareRequest

A request for place-related FARE information.

c

StaticFareRequest

-1:1

+StaticFareRequest

A request for general/static FARE information.

d

TripFareRequest

-1:1

+TripFareRequest

A request to calculate the FARE information of a single trip.

e

MultiTripFareRequest

-1:1

+MultiTripFareRequest

A request to calculate aggregated FARE information of multiple single trips.

Params

0:1

+FareParam

Parameter to filter the response contents.

4.3. The group FareResponseGroup

FareResponseGroup

-

FareResponse

FareResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

FareResult

0:*

+FareResult

Fare result choice element.

4.4. The complex type FareResultStructure

FareResultStructure

Wrapper element for Fare results.

Id

1:1

FareResultObjectIdType

ID of this result.

ErrorCondition

0:*

+OJPError

Problems related to this FARE result.

FareEstimated

0:1

Whether the fare is only estimated by the service. Estimated can mean different things: For example, the fare may vary depending on age, PassengerCategory, FareClass, EntitlementProducts. It can also mean that the fare structure used by the service is not entirely accurate or that other factors, such as the time a shared vehicle is used, need to be factored into the price. As a rule, the price should then be given as an approximate and probably lower limit of the actual price. Default is TRUE.

The element contains one of the following elements (a-e)

a

StopFareResult

-1:1

+StopFareResult

Stop-related Fare information.

b

PlaceFareResult

-1:1

+PlaceFareResult

Place-related Fare information.

c

StaticFareResult

-1:1

+StaticFareResult

Static Fare information.

d

TripFareResult

-1:*

+TripFareResult

Fare and FareProducts for a given trip.

e

MultiTripFareResult

-1:*

+MultiTripFareResult

Fare and FareProducts for multiple trips.

4.5. The complex type MultiTripFareRequestStructure

MultiTripFareRequestStructure

Structure of a Multi Trip Fare Request.

TripContext

0:1

+ResponseContext

Context to hold trip related objects that occur frequently.

Trip

1:*

+Trip

Multiple complete trips from multiple origins and multiple destination

4.6. The complex type MultiTripFareResultStructure

MultiTripFareResultStructure

Structure of a Multi Trip Fare Request result

TripFareProductReference

1:*

+TripFareProductReference

Non-empty list of trip references in the corresponding MultiTripFareRequestStructure

FareProduct

0:*

+FareProduct

Zero, one or more FareProducts that are valid for the referenced trips / part of trips.

PassedZones

0:1

+TariffZoneListInArea

The set of passed zones.

StaticInfoUrl

0:*

+WebLink

URL to Fare information pages on the web.

4.7. The complex type PlaceFareRequestStructure

PlaceFareRequestStructure

Sub-request: PLACE related fare information. This doesn't make a lot of sense for addresses, topographic place, and coordinates. However, STOP PLACE, SCHEDULED STOP POINT and POINT OF INTEREST are different.

Place

1:1

+Place

Place to get FAREs from (usually use only StopPoint, StopPlace and PointOfInterest).

Date

0:1

Date for which to retrieve Fare information.

→‍FareProductRef

0:*

>FareProductRef

Reference to a FareProduct.

4.8. The complex type PlaceFareResultStructure

PlaceFareResultStructure

PLACE-related Fare information.

Place

1:1

+Place

The involved PLACE. Usually,a StopPoint, StopPlace or PointOfInterest.

FareProduct

0:*

+FareProduct

[related to FARE PRODUCT in TM and NeTEx] different FARE PRODUCTs that may be available with related information.

StaticInfoUrl

0:*

+WebLink

URL to information page on the web.

Extension

0:1

4.9. The complex type StaticFareRequestStructure

StaticFareRequestStructure

General Fare information. May depend on date.

Date

0:1

Date for which to retrieve Fare information.

→‍FareProductRef

0:*

>FareProductRef

Reference to a FareProduct.

4.10. The complex type StaticFareResultStructure

StaticFareResultStructure

General Fare information.

FareProduct

0:*

+FareProduct

[related to FARE PRODUCT in TM and NeTEx] different FARE PRODUCTs that may be available with related information.

StaticInfoUrl

0:*

+WebLink

URL to information page on the web.

Extension

0:1

4.11. The complex type StopFareRequestStructure

StopFareRequestStructure

Sub-request: stop-related fare information.

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

Date

0:1

Date for which to retrieve Fare information.

4.12. The complex type StopFareResultStructure

StopFareResultStructure

Stop-related Fare information.

TariffZoneListInArea

1:*

+TariffZoneListInArea

One or more lists of Fare zones that belong to a Fare authority/area.

Extension

0:1

4.13. The complex type TripFareProductReferenceStructure

TripFareProductReferenceStructure

Element that connects FareProducts to trips. A TripFareProduct is a FAREPRODUCT covering a part or the whole of a TRIP from boarding the first public transport vehicle to alighting from the last public transport vehicle (corresponds to a package of PREASSIGNED FARE PRODUCTs)

→‍FareProductRef

1:1

>FareProductRef

Reference to a FareProduct.

FromTripIdRef

1:1

TripObjectIdType

Identifies the "valid from" trip.

FromLegIdRef

0:1

LegObjectIdType

Identifies the "valid from" LEG. If missing, then valid from the first LEG.

ToTripIdRef

1:1

TripObjectIdType

Identifies the "valid to" trip.

ToLegIdRef

0:1

LegObjectIdType

Identifies the "valid to" LEG. If missing, then valid to the last LEG.

4.14. The complex type TripFareRequestStructure

TripFareRequestStructure

Structure of a Single Trip Fare Request.

TripContext

0:1

+ResponseContext

Context to hold trip related objects that occur frequently. Especially necessary, when the system answering the fare request is not the same as the one that did the trip request.

Trip

1:1

+Trip

A complete trip from origin to destination

5. OJP/OJP_FareSupport.xsd - Supporting definitions for fare information on passenger trips

5.1. Simple type definitions

BookingAccessEnumeration

Allowed values for Booking Access.

public

-

authorisedPublic

-

staff

-

other

-

BookingMethodEnumeration

Allowed values for a booking method.

callDriver

-

callOffice

-

online

-

other

-

phoneAtStop

-

text

-

mobileApp

-

atOffice

-

none

-

BookingObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a BOOKING Object.

BookingProcessEnumeration

Allowed values for Booking Process UIC 7037 Code list.

productNotAvailable

Product is not available.

productNotBookable

Product cannot be booked.

bookableThroughInternationalSystem

Product can be booked online internationally.

bookableThroughNationalSystem

Product can be booked online nationally.

bookableManually

Product can only be booked by contacting specific authorised retail outlets.

other

Other booking process.

ContactTypeEnumeration

Allowed values for CONTACT role.

any

-

information

-

reservations

-

lostProperty

-

publicRelations

-

complaints

-

emergency

-

other

-

EntitlementProductCodeType

xs:NMTOKEN: (empty restriction)

Identifier of an ENTITLEMENT PRODUCT (e.g., BahnCard50, BahnCard50First, military card, concessionary card). It is defined by the fare authority.

FareAuthorityCodeType

xs:NMTOKEN: (empty restriction)

Identifier of a Fare Authority.

FareProblemTypeEnumeration

Types of problems that may be returned in responses to FARE requests.

FARE_OUTOFAREA

The trip planning has found a route that leaves the area of the fare authority.

FARE_JOURNEYNOTPERMITTED

The trip planning result suggests a service which is not permitted by the fare authority.

FARE_ADDITIONALCHARGES

Passengers may be charged additional fees (e.g.: for road tolls or seat reservation).

FARE_ADDITIONALTICKETS

Additional tickets may be necessary because only parts of the passenger trip could be covered.

FARE_ROUTENOTFEASIBLE

Fare calculation is not possible because the suggested trip is not in compliance with the fare regulations, e.g., because of round trips, LEGs that go forth and return or exceed the maximal total trip duration.

FARE_ALREADYCOVERED

The ticket that has been specified in the request is valid for the suggested trip (or parts of it as defined by LegRange).

FARE_DATEOUTOFRANGE

The fare request cannot be processed because there is no information available for the requested date.

FARE_STOPPOINTUNKNOWN

The fare request cannot be processed because the requested stop is unknown.

FARE_OTHER

A problem has occurred that does not have a specific problem type.

FareProductIdType

xs:NMTOKEN: (empty restriction)

Identifier of a FareProduct

GroupBookingEnumeration

Allowed values for Group Booking.

groupsAllowed

-

groupsNotAllowed

-

groupsAllowedWithReservation

-

groupBookingsRestricted

-

unknown

-

PassengerCategoryEnumeration

[a simplified and specialised view of USER PROFILE in TM and NeTEx] classification of passengers by age or other factors that may determine the fare they will need to pay.

Adult

-

Child

-

Senior

-

Youth

-

Disabled

-

Dog

-

Bicycle

-

Motorcycle

-

Car

-

Truck

-

Group

-

PhoneType

xs:normalizedString: (empty restriction)

Type for an International phone number. + Country + MSISDN e.g., +41 675601 etc.

PurchaseMomentEnumeration

Allowed values for Purchase Moment.

onReservation

Purchase must be made on reservation in advance of travel.

inAdvance

Purchase can be made in advance of travel.

inAdvanceOnly

Purchase can only be made in advance of travel (e.g., for season ticket or advance ticket).

beforeBoarding

Purchase can be made before boarding transport vehicle.

beforeBoardingOnly

Purchase must be made before boarding transport vehicle.

onBoarding

Purchase can be made when boarding the transport vehicle.

onBoardingOnly

Purchase can only be made when boarding the transport vehicle.

afterBoarding

Purchase can be made after boarding transport vehicle.

onCheckIn

Purchase can be made on entering transport system.

onCheckOut

Purchase can be made on leaving transport system.

subscriptionOnly

Purchase can only be made on subscription.

other

Other moment of Purchase.

PurchaseWhenEnumeration

Allowed values for Purchase when.

advanceOnly

-

untilPreviousDay

-

dayOfTravelOnly

-

advanceAndDayOfTravel

-

timeOfTravelOnly

-

subscriptionChargeMoment

-

other

-

TariffZoneCodeType

xs:NMTOKEN: (empty restriction)

Identifier of a fare zone.

5.2. The toplevel element FareAuthorityRef

FareAuthorityRef

+FareAuthorityRef

Reference to a Fare Authority.

5.3. The toplevel element FareProblemType

FareProblemType

+FareProblemTypeEnumeration (↔ ojp:ErrorType)

5.4. The toplevel element FareProductRef

FareProductRef

+FareProductRef

Reference to a FareProduct.

5.5. The toplevel element TariffZoneRef

TariffZoneRef

+TariffZoneRef

Reference to a fare zone.

5.6. The group BookingArrangementsGroup

BookingArrangementsGroup

Elements for BOOKING ARRANGEMENTs.

BookingArrangements

BookingContact

0:1

+ContactDetails

Contact for Booking.

BookingMethods

0:1

+BookingMethodListOfEnumerations

Allowed ways of making a BOOKING.

BookingAccess

0:1

BookingAccessEnumeration

Who can make a booking. Default is public.

BookWhen

0:1

PurchaseWhenEnumeration

When Booking can be made.

BuyWhen

0:1

+PurchaseMomentListOfEnumerations

When purchase can be made.

LatestBookingTime

0:1

Latest time that booking can be made. The exact meaning must be derived also from BookWhen and MinimumBookingPeriod.

MinimumBookingPeriod

0:1

Minimum interval in advance of departure day or time that Service may be ordered.

MaximumBookingPeriod

0:1

Maximum interval in advance of departure day or time that Service may be ordered.

BookingUrl

0:1

+WebLink

URL for booking.

BookingNotes

0:1

+BookingNotes

Notes about booking the LINE.

Extension

0:1

5.7. The group FareAuthorityGroup

FareAuthorityGroup

Group of attributes for an ORGANISATION which has the RESPONSIBILITY ROLE for the definition of FARE PRODUCTs

FareAuthority

→‍FareAuthorityRef

1:1

>FareAuthorityRef

Reference to a Fare Authority.

FareAuthorityText

1:1

Textual description or name of Fare authority.

5.8. The group FareDataFilterGroup

FareDataFilterGroup

Data filter group for Fare request.

FareDataFilter

FareAuthorityFilter

0:*

>FareAuthorityRef

Fare authority for which to retrieve Fare information.

PassengerCategory

0:*

PassengerCategoryEnumeration

sequence of all passenger categories, for which this FareProduct is valid

FareClass

0:1

siri:FareClassEnumeration

Fare class for which to retrieve FareProducts. Refers to TYPE OF FARE CLASS (e.g., first class). Transmodel: CLASS OF USE.

5.9. The group FareProductBookingGroup

FareProductBookingGroup

[aggregation of DISTRIBUTION CHANNEL and BOOKING ARRANGEMENT in TM and NeTEx] Group of information elements related to information to support the process of booking a FARE PRODUCT.

FareProductBooking

InfoUrl

0:*

+WebLink

URL to information for this FareProduct

SaleUrl

0:*

+WebLink

URL to buy the FareProduct online.

BookingArrangements

0:*

+BookingArrangementsContainer

Multiple sets of multiple booking arrangements for different legs of a journey.

5.10. The group FareProductPriceGroup

FareProductPriceGroup

[related to FARE PRODUCT PRICE in TM and NeTEx] price at which a FARE PRODUCT can be purchased.

FareProductPrice

Price

0:1

FareProduct price as decimal number.

NetPrice

0:1

Net FareProduct price as decimal number for accounting purposes.

Currency

0:1

iso 4217 currency code, e.g., EUR for Euro or GBP for Pound Sterling

VatRate

0:1

Percentage

Rate of value added tax.

5.11. The group FareProductValidityGroup

FareProductValidityGroup

conditions of use for a particular FARE PRODUCT.

FareProductValidity

FareClass

0:1

siri:FareClassEnumeration

Fare class for which the FareProduct is valid (Transmodel: CLASS OF USE).

RequiredCard

0:*

+EntitlementProduct

One or more ENTITLEMENT PRODUCTs required for the purchase of this FareProduct. In most cases, ENTITLEMENT PRODUCTs offer discounts, e.g., the "BahnCard50" of "Deutsche Bahn".

ValidFor

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories for which this FareProduct is valid.

ValidityDuration

0:1

Maximum duration of FareProduct validity starting with purchase of ticket or begin of journey (ticket validation).

ValidityDurationText

0:1

+InternationalText

Textual description of maximum validity duration.

ValidityTariffZones

0:*

+TariffZoneListInArea

Spatial validity of FareProduct defined as list of fare zones.

ValidityAreaText

0:1

+InternationalText

Textual description of spatial validity.

5.12. The group LegRangeGroup

LegRangeGroup

Range of LEGs (from - to) for which a Fare result (ticket) is valid.

LegRange

FromLegIdRef

1:1

LegObjectIdType

Identifies the "valid from" LEG.

ToLegIdRef

1:1

LegObjectIdType

Identifies the "valid to" LEG.

5.13. The complex type BookingArrangementsContainerStructure

BookingArrangementsContainerStructure

Container for multiple booking arrangements.

BookingArrangement

1:*

+BookingArrangements

[a more generalised form of BOOKING ARRANGEMENTS in TMv6] arrangement for booking any leg or legs of a journey.

Extension

0:1

5.14. The complex type BookingArrangementsStructure

BookingArrangementsStructure

Type for BOOKING ARRANGEMENTs modified from NeTEx.

BookingArrangements

BookingContact

0:1

+ContactDetails

Contact for Booking.

BookingMethods

0:1

+BookingMethodListOfEnumerations

Allowed ways of making a BOOKING.

BookingAccess

0:1

BookingAccessEnumeration

Who can make a booking. Default is public.

BookWhen

0:1

PurchaseWhenEnumeration

When Booking can be made.

BuyWhen

0:1

+PurchaseMomentListOfEnumerations

When purchase can be made.

LatestBookingTime

0:1

Latest time that booking can be made. The exact meaning must be derived also from BookWhen and MinimumBookingPeriod.

MinimumBookingPeriod

0:1

Minimum interval in advance of departure day or time that Service may be ordered.

MaximumBookingPeriod

0:1

Maximum interval in advance of departure day or time that Service may be ordered.

BookingUrl

0:1

+WebLink

URL for booking.

BookingNotes

0:1

+BookingNotes

Notes about booking the LINE.

Extension

0:1

5.15. The complex type BookingMethodListOfEnumerations

BookingMethodListOfEnumerations

List of values for booking values.

BookingMethod

1:*

BookingMethodEnumeration

Booking methods.

5.16. The complex type BookingNotesStructure

BookingNotesStructure

A structure for an ordered list of booking notes.

BookingNote

1:*

+InternationalText

Note about booking the LINE.

5.17. The complex type BookingProcessListOfEnumerations

BookingProcessListOfEnumerations

List of Booking Process values.

BookingProcess

1:*

BookingProcessEnumeration

Ways how to book (UIC 7037 codes).

5.18. The complex type ContactDetailsStructure

ContactDetailsStructure

Type for contact details.

ContactPerson

0:1

+InternationalText

Name of contact person.

Email

0:1

EmailAddressType

The email address of the contact.

Phone

0:1

PhoneType

Contact telephone number.

Fax

0:1

PhoneType

Contact fax number.

Url

0:1

+WebLink

The website address of the contact.

FurtherDetails

0:1

+InternationalText

Further details about contact process.

5.19. The complex type EntitlementProductListStructure

EntitlementProductListStructure

A list of ENTITLEMENT PRODUCTs

EntitlementProduct

1:*

+EntitlementProduct

[a specific form of TRAVEL DOCUMENT in TM and NeTEx] Precondition to access a service or to purchase a FARE PRODUCT issued by an organisation that may not be a PT operator (e.g., military card, concessionary card). In most cases, ENTITLEMENT PRODUCTs offer discounts, e.g., the "BahnCard50" of "Deutsche Bahn".

5.20. The complex type EntitlementProductStructure

EntitlementProductStructure

[a specific form of TRAVEL DOCUMENT in TM and NeTEx] Precondition to access a service or to purchase a FARE PRODUCT issued by an organisation that may not be a PT operator (e.g., military card, concessionary card). In most cases, ENTITLEMENT PRODUCTs offer discounts, e.g., the "BahnCard50" of "Deutsche Bahn".

→‍FareAuthorityRef

1:1

>FareAuthorityRef

Reference to a Fare Authority.

EntitlementProductRef

1:1

EntitlementProductCodeType

Identifier of the ENTITLEMENT PRODUCT (e.g., BahnCard50, BahnCard50First)

ValidityPeriod

0:1

+siri:HalfOpenTimestampOutputRange

Validity period of the ENTITLEMENT PRODUCT

EntitlementProductName

1:1

Name of the ENTITLEMENT PRODUCT

5.21. The complex type FareAuthorityRefStructure

FareAuthorityRefStructure

FareAuthorityCodeType

Identifier of a Fare Authority.

5.22. The complex type FareParamStructure

FareParamStructure

[related to the FARE parameter model in TM and NeTEx] parameters which are used to determine the price to be paid for a FARE PRODUCT by a specific passenger.

FareDataFilter

FareAuthorityFilter

0:*

>FareAuthorityRef

Fare authority for which to retrieve Fare information.

PassengerCategory

0:*

PassengerCategoryEnumeration

sequence of all passenger categories, for which this FareProduct is valid

FareClass

0:1

siri:FareClassEnumeration

Fare class for which to retrieve FareProducts. Refers to TYPE OF FARE CLASS (e.g., first class). Transmodel: CLASS OF USE.

Traveller

0:*

+FarePassenger

Number of travellers that will make the journey and for which Fare information needs to be gathered.

AccessModeList

0:1

+AccessModesListOfEnumerations

ACCESS MODEs to consider (usually only one). This is only used in very special cases. E.g. for carTransportRail. It indicates if one uses a car, truck, motorcycle or bike. The Access mode may result in no transportation being possible.

Extension

0:1

5.23. The complex type FarePassengerStructure

FarePassengerStructure

[a specialised form of USER PROFILE in TM and NeTEx] attributes of a passenger that influence the price to be paid by that passenger for a FARE PRODUCT.

The element contains one of the following elements (a-b)

a

Age

-1:1

Age of the passenger on the day of travel.

b

PassengerCategory

-1:1

PassengerCategoryEnumeration

sequence of all passenger categories, for which this FareProduct is valid

EntitlementProducts

0:1

+EntitlementProductList

A list of ENTITLEMENT PRODUCTs.

The element contains none or one of the following elements (a-b)

a

ZonesAlreadyPaid

-1:1

+TariffZoneRefList

Fare zones for which the passenger already has a valid FareProduct.

b

SalesPackageElementRef

-1:*

>FareProductRef

Id of a FareProduct that the passenger already holds and that may be used for the travel or parts of it.

5.24. The complex type FareProductRefStructure

FareProductRefStructure

FareProductIdType

Identifier of a FareProduct

5.25. The complex type FareProductStructure

FareProductStructure

[related to FARE PRODUCT in TM and NeTEx] different FARE PRODUCTs that may be available with related information

FareProductId

1:1

FareProductIdType

Identifier of a FareProduct

FareProductName

1:1

Printable FareProduct name

FareAuthority

→‍FareAuthorityRef

1:1

>FareAuthorityRef

Reference to a Fare Authority.

FareAuthorityText

1:1

Textual description or name of Fare authority.

ProtoProduct

0:1

Is this product a proto product? Default is false. If true, it should not be shown to the user. In a distributed environment (e.g., EU-Spirit) partial systems may generate incomplete product information (proto product), which has to be processed further and combined with other information before it is a complete fare product and can be shown to the user. See https://eu-spirit.eu/

FareProductPrice

Price

0:1

FareProduct price as decimal number.

NetPrice

0:1

Net FareProduct price as decimal number for accounting purposes.

Currency

0:1

iso 4217 currency code, e.g., EUR for Euro or GBP for Pound Sterling

VatRate

0:1

Percentage

Rate of value added tax.

FareQuota

0:1

Remaining offered tickets in this FARE PRODUCT. When absent, the number of remaining tickets is unknown or not limited. In most cases if the FareQuota is zero then the FareProduct is not shown.

FareProductValidity

FareClass

0:1

siri:FareClassEnumeration

Fare class for which the FareProduct is valid (Transmodel: CLASS OF USE).

RequiredCard

0:*

+EntitlementProduct

One or more ENTITLEMENT PRODUCTs required for the purchase of this FareProduct. In most cases, ENTITLEMENT PRODUCTs offer discounts, e.g., the "BahnCard50" of "Deutsche Bahn".

ValidFor

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories for which this FareProduct is valid.

ValidityDuration

0:1

Maximum duration of FareProduct validity starting with purchase of ticket or begin of journey (ticket validation).

ValidityDurationText

0:1

+InternationalText

Textual description of maximum validity duration.

ValidityTariffZones

0:*

+TariffZoneListInArea

Spatial validity of FareProduct defined as list of fare zones.

ValidityAreaText

0:1

+InternationalText

Textual description of spatial validity.

FareProductBooking

InfoUrl

0:*

+WebLink

URL to information for this FareProduct

SaleUrl

0:*

+WebLink

URL to buy the FareProduct online.

BookingArrangements

0:*

+BookingArrangementsContainer

Multiple sets of multiple booking arrangements for different legs of a journey.

Extension

0:1

5.26. The complex type GroupBookingListOfEnumerations

GroupBookingListOfEnumerations

Possibilities and restrictions for group booking.

GroupBooking

1:*

GroupBookingEnumeration

Group booking policies.

5.27. The complex type PurchaseMomentListOfEnumerations

PurchaseMomentListOfEnumerations

List of Purchase Moment values.

PurchaseMoment

1:*

PurchaseMomentEnumeration

Possibilities when to pay.

5.28. The complex type TariffZoneListInAreaStructure

TariffZoneListInAreaStructure

List of fare zones within the area of a Fare Authority.

FareAuthority

→‍FareAuthorityRef

1:1

>FareAuthorityRef

Reference to a Fare Authority.

FareAuthorityText

1:1

Textual description or name of Fare authority.

TariffZone

1:*

+TariffZone

Fare zone in area.

5.29. The complex type TariffZoneRefListStructure

TariffZoneRefListStructure

List of fare zones references within the area of a Fare Authority.

→‍FareAuthorityRef

1:1

>FareAuthorityRef

Reference to a Fare Authority.

→‍TariffZoneRef

1:*

>TariffZoneRef

Reference to a fare zone.

5.30. The complex type TariffZoneRefStructure

TariffZoneRefStructure

TariffZoneCodeType

Identifier of a fare zone.

5.31. The complex type TariffZoneStructure

TariffZoneStructure

[a more clearly defined equivalent of TARIFF ZONE in TM and NeTEx] A ZONE used to define a zonal fare structure in a zone-counting or zone-matrix system.

→‍TariffZoneRef

1:1

>TariffZoneRef

Reference to a fare zone.

TariffZoneText

1:1

Text describing the fare zone. Passengers will recognize the fare zone by this text. Often published on Fare Zone Maps.

5.32. The complex type TripFareResultStructure

TripFareResultStructure

Structure of a single TripFareResult. This may cover the whole trip or only the part the service can answer. If only partial answers can be delivered, then this must be indicated with FARE_ADDITIONALTICKETS (as a warning). For a given trip multiple FareResults may need to be combined to get the whole tariff. A typical example may be classic public transport and a sharing leg. Some legs, e.g., TransferLegs and walking ContinuousLeg will never have a price. The service may include them in one of the tickets. If the whole trip is for free, then a TripFareResult with a price of 0 is expected. It is possible to have combined FareResults (e.g., for a bundle) and in addition price each leg individually.

ErrorCondition

0:*

+OJPError

Result-specific error messages.

TripId

0:1

TripObjectIdType

BookingId

0:1

BookingObjectIdType

LegRange

FromLegIdRef

1:1

LegObjectIdType

Identifies the "valid from" LEG.

ToLegIdRef

1:1

LegObjectIdType

Identifies the "valid to" LEG.

PassedZones

0:1

+TariffZoneListInArea

The sequence of passed fare zones.

FareProduct

0:*

+FareProduct

One or more FareProducts that are valid for this part of the trip.

StaticInfoUrl

0:*

+WebLink

URL to static information page on the web.

6. OJP/OJP_Lines.xsd - Request and response definitions for information on lines

6.1. Simple type definitions

LineInformationProblemTypeEnumeration

Types of problems that may be returned in responses to LINE INFORMATION requests.

LINEINFORMATION_LINEUNKNOWN

The requested LINE is unknown.

LINEINFORMATION_OTHER

A problem has occurred that does not have a specific problem type.

6.2. The toplevel element LineInformationProblemType

LineInformationProblemType

+LineInformationProblemTypeEnumeration (↔ ojp:ErrorType)

6.3. The group LineInformationResponseGroup

LineInformationResponseGroup

Line Information response group.

LineInformationResponse

LineResult

0:*

+LineResult

6.4. The complex type LineResultStructure

LineResultStructure

-

ErrorCondition

0:*

+OJPError

Problems related to this Line result.

LineRef

1:1

>siri:LineRef

Reference to the LINE.

→‍siri:PublishedLineName

0:1

>siri:NaturalLanguageString

Name or Number by which the LINEis known to the public.

DirectionRef

0:1

>siri:DirectionRef

DIRECTION of LINE.

RouteGeometry

0:*

+LinearShape

The LINE's route geometry. A line can have multiple ROUTEs, and each has its own geometry. The first should be the "main" geometry.

AreaGeometry

0:*

+Area

The LINE's main area. Used for MOBILITY SERVICES that cover one or more areas. The interconnection between the areas is not calculated (e.g., exclusion zones can't be modelled). Don't mix RouteGeometry and AreaGeometry in a response.

Mode

0:*

+Mode

List of transport modes that are supported by this line.

7. OJP/OJP_Locations.xsd - Request and response definitions for location information

7.1. Simple type definitions

PlaceTypeEnumeration

-

stop

stop covers StopPlace and StopPoint. The main reason is that many systems may only return either STOP PLACE/QUAY information or SCHEDULED STOP POINTs.

address

-

poi

-

coord

Deprecated. Use location instead.

location

Geographic position consisting of coordinates. Replaces the deprecated value coord.

topographicPlace

-

PlaceUsageEnumeration

-

origin

-

via

-

destination

-

complexType[ojp:PlaceResultStructure]
  /Probability #simpleType
  (typedef-102.1)

xs:float: range=[0,1]

-

7.2. The group ExchangePointsDataFilterGroup

ExchangePointsDataFilterGroup

-

ExchangePointsDataFilter

Type

0:*

PlaceTypeEnumeration

Allowed location/place object types. If none is given, all types are allowed.

Usage

0:1

PlaceUsageEnumeration

Defines, whether the location/place object of this request acts as origin, via or destination point of the passenger journey.

Modes

0:1

+ModeFilter

Allowed public transport modes. Defines, which public transport modes must be available at the returned location/place objects. Applies only to stops.

OperatorFilter

0:1

+OperatorFilter

Filter for locations/places that are operated by certain organisations.

TopographicPlaceRef

0:*

>TopographicPlaceRef

If at least one is set, only location/place objects within the given localities are allowed.

DestinationSystem

0:1

>siri:ParticipantRef

Reference to system in which the destination (or origin) of the passenger is located.

AdjacentSystem

0:*

>siri:ParticipantRef

One or more adjacent systems to which the exchange points should be retrieved.

7.3. The group ExchangePointsPolicyGroup

ExchangePointsPolicyGroup

-

ExchangePointsPolicy

Language

0:*

Preferred language in which to return text values.

NumberOfResults

0:1

Maximum number of results to be returned. The service is allowed to return fewer objects if reasonable or otherwise appropriate. If the number of matching objects is expected to be large (e.g., in the case that all objects should be delivered) this parameter can be used to partition the response delivery into smaller chunks. The location information service is expected to support a response volume of at least 500 location objects within one single response.

ContinueAt

0:1

Tells the server to skip the mentioned number of results in its response. Can be used in a follow-up request to get further results. The value is usually taken from the previous response.

7.4. The group ExchangePointsRequestGroup

ExchangePointsRequestGroup

-

ExchangePointsRequest

PlaceRef

0:1

+PlaceRef

Location/Place for which exchange points to other "neighbour" systems are to be searched. This location/place is usually the origin/destination of a passenger journey. May be omitted if all exchange points shall be returned.

Params

0:1

+ExchangePointsParam

E.g. location/place types (stops, addresses, POIs) or specific location/place attributes

7.5. The group ExchangePointsResponseGroup

ExchangePointsResponseGroup

-

ExchangePointsResponse

ExchangePointsResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

ContinueAt

0:1

If the response returns fewer results than expected, the value of skip can be used in a follow-up request to get further results. It tells the server to skip the given number of results in its response.

ExchangePointsResult

0:*

+ExchangePointsResult

The exchange points found by the service.

7.6. The group LocationInformationRequestGroup

LocationInformationRequestGroup

-

The element contains one of the following elements (a-b)

LocationInformationRequest

a

InitialInput

-1:1

+InitialLocationInput

Initial input for the location information request. This input defines what is originally looked for. Be aware that this also can contain PLACEs.

b

PlaceRef

-1:1

+PlaceRef

LOCATION / PLACE for further refinement. If a Place in a previous response was marked as not "complete" it can be refined by putting it here. If Places are organised hierarchically, it may be reasonable to identify the Place in a top-down approach with several steps of refining a Place on each level of hierarchy. Following this approach an initial request retrieves a first list of top-level Places (e.g., streets) which are to be refined in a subsequent request to the next level (e.g., house number intervals). The objects of the current level are presented to the user for selection. The object reference of the selected object is then sent in the next request for further refinement.

Restrictions

0:1

+PlaceParam

E.g. place types (stops, addresses, POIs) or specific place attributes

7.7. The group LocationInformationResponseGroup

LocationInformationResponseGroup

-

LocationInformationResponse

LocationInformationResponseContext

0:1

+ResponseContext

Context to hold response objects that occur frequently.

ContinueAt

0:1

If the response returns fewer results than expected, the value of skip can be used in a follow-up request to get further results. It tells the server to skip the given number of results in its response.

PlaceResult

0:*

+PlaceResult

The place/location objects found by the service are ordered in descending order of how well they match the input data. The first result in the list matches best.

7.8. The group PlaceDataFilterGroup

PlaceDataFilterGroup

-

PlaceDataFilter

Type

0:*

PlaceTypeEnumeration

Allowed location/place object types. If none is given, all types are allowed.

Usage

0:1

PlaceUsageEnumeration

Defines, whether location/place objects for origin, via, or destination are searched.

Modes

0:1

+ModeFilter

Allowed public transport modes. Defines, which public transport modes must be available at the returned location/place objects. Applies only to stops.

OperatorFilter

0:1

+OperatorFilter

Filter for locations/places that are operated by certain organisations.

TopographicPlaceRef

0:*

>TopographicPlaceRef

If at least one is set, only location/place objects within the given localities are allowed.

PointOfInterestFilter

0:1

+PointOfInterestFilter

Filter to narrow down POI searches.

7.9. The group PlacePolicyGroup

PlacePolicyGroup

-

PlacePolicy

Language

0:*

Preferred language in which to return text values.

NumberOfResults

0:1

Maximum number of results to be returned. The service is allowed to return fewer objects if reasonable or otherwise appropriate. If the number of matching objects is expected to be large (e.g.: in the case that all objects should be delivered) this parameter can be used to partition the response delivery into smaller chunks. The place information service is expected to support a response volume of at least 500 objects within one single response.

ContinueAt

0:1

Tells the server to skip the mentioned number of results in its response. Can be used in a follow-up request to get further results. The value is usually taken from the previous response.

IncludePtModes

0:1

Tells the service to include the available public transport modes at returned stops.

IncludeOperators

0:1

Tells the service to include the available operators at returned stops.

7.10. The group PlaceSortingGroup

PlaceSortingGroup

-

PlaceSorting

SortingMethod

0:1

If there are multiple sorting methods supported by the system, the client can choose one of the existing. Which methods are available needs to be known to the client and may differ from system to system. Therefore, use with care.

GeoPosition

0:1

+siri:Location

WGS84 coordinates position. Locations closer to this GeoPosition are preferred.

MinimalProbability

0:1

Ignore locations with a lower probability.

7.11. The complex type ExchangePointsParamStructure

ExchangePointsParamStructure

-

ExchangePointsDataFilter

Type

0:*

PlaceTypeEnumeration

Allowed location/place object types. If none is given, all types are allowed.

Usage

0:1

PlaceUsageEnumeration

Defines, whether the location/place object of this request acts as origin, via or destination point of the passenger journey.

Modes

0:1

+ModeFilter

Allowed public transport modes. Defines, which public transport modes must be available at the returned location/place objects. Applies only to stops.

OperatorFilter

0:1

+OperatorFilter

Filter for locations/places that are operated by certain organisations.

TopographicPlaceRef

0:*

>TopographicPlaceRef

If at least one is set, only location/place objects within the given localities are allowed.

DestinationSystem

0:1

>siri:ParticipantRef

Reference to system in which the destination (or origin) of the passenger is located.

AdjacentSystem

0:*

>siri:ParticipantRef

One or more adjacent systems to which the exchange points should be retrieved.

ExchangePointsPolicy

Language

0:*

Preferred language in which to return text values.

NumberOfResults

0:1

Maximum number of results to be returned. The service is allowed to return fewer objects if reasonable or otherwise appropriate. If the number of matching objects is expected to be large (e.g., in the case that all objects should be delivered) this parameter can be used to partition the response delivery into smaller chunks. The location information service is expected to support a response volume of at least 500 location objects within one single response.

ContinueAt

0:1

Tells the server to skip the mentioned number of results in its response. Can be used in a follow-up request to get further results. The value is usually taken from the previous response.

Extension

0:1

7.12. The complex type ExchangePointsResultStructure

ExchangePointsResultStructure

-

ErrorCondition

0:*

+OJPError

Problems related to this EXCHANGE POINTS result.

Place

1:1

+Place

Place object that describes this exchange point.

TravelDurationEstimate

0:1

Rough estimate of the travel duration from the specified reference location/place to this exchange point.

WaitDuration

0:1

Duration needed at this exchange point to change from one service to another. If a journey planning orchestrator puts together a trip at this exchange point, it must take care, that feeding arrival and fetching departure are at least this duration apart.

BorderPoint

0:1

Flag if this exchange point is an administrative border point where timetables are cut off while services still may run through and connect the regions. At this kind of points passengers may continue their journey within the same service. Default is FALSE.

Mode

0:*

+Mode

List of transport modes that call at this place object. This list should only be filled in case of stop points or stop places – and only when explicitly requested.

Priority

0:1

PercentType

The priority of the exchange point. 100 is the maximum. The priority can be used to select given ExchangePoints more often (e.g., because the station is a main hub).

7.13. The complex type GeoAreaStructure

GeoAreaStructure

[specialisation of ZONE in TMv6] a LINK SEQUENCE (one-dimensional) forming the boundary of a ZONE

PolylinePoint

3:*

+siri:Location

Vertices of a polyline defining an area.

7.14. The complex type GeoCircleStructure

GeoCircleStructure

-

Center

1:1

+siri:Location

Centre position of the circle.

Radius

1:1

siri:DistanceType

Radius in metres.

7.15. The complex type GeoRectangleStructure

GeoRectangleStructure

-

UpperLeft

1:1

+siri:Location

Upper-left (north-west) corner of the rectangle.

LowerRight

1:1

+siri:Location

Lower-right (south-east) corner of the rectangle.

7.16. The complex type GeoRestrictionsStructure

GeoRestrictionsStructure

-

The element contains one of the following elements (a-c)

a

Circle

-1:1

+GeoCircle

Area defined by a circle.

b

Rectangle

-1:1

+GeoRectangle

Area defined by a rectangle.

c

Area

-1:1

+GeoArea

Area defined by a polyline.

7.17. The complex type InitialLocationInputStructure

InitialLocationInputStructure

-

Name

0:1

Name of the LOCATION object which is looked for. This is usually the user's input. If not given, the name of the resulting location objects is not relevant.

GeoPosition

0:1

+siri:Location

Coordinate where to look for locations/places. If given, the result should prefer locations/place objects near to this GeoPosition.

GeoRestriction

0:1

+GeoRestrictions

Restricts the resulting location/place objects to the given geographical area.

AllowedSystem

0:*

>siri:ParticipantRef

Used in distributed environments. e.g., EU-Spirit. If none is given, the location/place information request refers to all known systems (in EU-Spirit "passive servers"). If at least one is given, the location/place information request refers only to the given systems (in EU-Spirit "passive servers"). In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

7.18. The complex type PlaceParamStructure

PlaceParamStructure

-

PlaceDataFilter

Type

0:*

PlaceTypeEnumeration

Allowed location/place object types. If none is given, all types are allowed.

Usage

0:1

PlaceUsageEnumeration

Defines, whether location/place objects for origin, via, or destination are searched.

Modes

0:1

+ModeFilter

Allowed public transport modes. Defines, which public transport modes must be available at the returned location/place objects. Applies only to stops.

OperatorFilter

0:1

+OperatorFilter

Filter for locations/places that are operated by certain organisations.

TopographicPlaceRef

0:*

>TopographicPlaceRef

If at least one is set, only location/place objects within the given localities are allowed.

PointOfInterestFilter

0:1

+PointOfInterestFilter

Filter to narrow down POI searches.

PlacePolicy

Language

0:*

Preferred language in which to return text values.

NumberOfResults

0:1

Maximum number of results to be returned. The service is allowed to return fewer objects if reasonable or otherwise appropriate. If the number of matching objects is expected to be large (e.g.: in the case that all objects should be delivered) this parameter can be used to partition the response delivery into smaller chunks. The place information service is expected to support a response volume of at least 500 objects within one single response.

ContinueAt

0:1

Tells the server to skip the mentioned number of results in its response. Can be used in a follow-up request to get further results. The value is usually taken from the previous response.

IncludePtModes

0:1

Tells the service to include the available public transport modes at returned stops.

IncludeOperators

0:1

Tells the service to include the available operators at returned stops.

PlaceSorting

SortingMethod

0:1

If there are multiple sorting methods supported by the system, the client can choose one of the existing. Which methods are available needs to be known to the client and may differ from system to system. Therefore, use with care.

GeoPosition

0:1

+siri:Location

WGS84 coordinates position. Locations closer to this GeoPosition are preferred.

MinimalProbability

0:1

Ignore locations with a lower probability.

Extension

0:1

7.19. The complex type PlaceResultStructure

PlaceResultStructure

-

ErrorCondition

0:*

+OJPError

Problems related to this LOCATION result.

Place

1:1

+Place

The Place / Location object.

Complete

1:1

States whether the included location/place is complete or needs further refinement. Only complete locations/places are fully resolved and can be used in e.g., trip requests. Incomplete locations/places must be refined entering them once again into a LocationInformationRequest.

Probability

0:1

local-type: typedef-102.1

Probability, that this result is the one meant by the user's input. Value should be between 0 and 1.

System

0:1

>siri:ParticipantRef

Stores the system reference, where to ask for actual locations corresponding to this city name result. To get actual locations, a new location information request using the system ID of this result is needed.

Operators

0:1

+OperatorRefs_Rel

List of operators operating at this place object. This list should only be filled if this is explicitly requested.

8. OJP/OJP_PlaceSupport.xsd - Supporting definitions for location information

8.1. Simple type definitions

AddressCodeType

xs:normalizedString: (empty restriction)

Identifier of an Address

ExchangePointsProblemTypeEnumeration

Types of problems that may be returned in responses to EXCHANGE POINTS requests

EXCHANGEPOINTS_NORESULTS

No exchange points could be found that match the query criteria.

EXCHANGEPOINTS_UNKNOWNDESTINATIONSYSTEM

The destination system given in the request parameters is unknown.

EXCHANGEPOINTS_UNKNOWNADJACENTSYSTEM

One or more of the adjacent systems given in the request parameters are unknown.

EXCHANGEPOINTS_OTHER

A problem has occurred that does not have a specific problem type.

LocationProblemTypeEnumeration

Types of problems that may be returned in responses to LOCATION requests.

LOCATION_NORESULTS

No location objects could be found that match the input data.

LOCATION_UNSUPPORTEDTYPE

The requested location types are not supported by the service.

LOCATION_UNSUPPORTEDCOMBINATION

The combination of input data (text string, coordinates, geographical restrictions) cannot be processed by the service.

LOCATION_NOREFINEMENT

The given location object could not be refined.

LOCATION_USAGEIGNORED

The usage type has been ignored.

LOCATION_UNSUPPORTEDPTMODES

The service does not support any restrictions by transport modes.

LOCATION_UNSUPPORTEDLOCALITY

The service does not support any restrictions by localities.

LOCATION_UNSUPPORTEDSORTINGMETHOD

The service does not support the sorting method. The details should provide a list of the allowed methods the service supports.

LOCATION_OTHER

A problem has occurred that does not have a specific problem type.

PlaceObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

PointOfInterestCodeType

xs:normalizedString: (empty restriction)

Identifier of a Point of Interest

StopPlaceCodeType

xs:normalizedString: (empty restriction)

Identifier of a Stop Place

TopographicPlaceCodeType

xs:normalizedString: (empty restriction)

Identifier of a TopographicPlace

8.2. The toplevel element AddressRef

AddressRef

+AddressRef

Reference to an Address

8.3. The toplevel element ExchangePointsProblemType

ExchangePointsProblemType

+ExchangePointsProblemTypeEnumeration (↔ ojp:ErrorType)

8.4. The toplevel element LocationProblemType

LocationProblemType

+LocationProblemTypeEnumeration (↔ ojp:ErrorType)

8.5. The toplevel element PointOfInterestRef

PointOfInterestRef

+PointOfInterestRef

Reference to a Point of Interest

8.6. The toplevel element StopPlaceRef

StopPlaceRef

+StopPlaceRef

Reference to a Stop Place

8.7. The toplevel element TopographicPlaceRef

TopographicPlaceRef

+TopographicPlaceRef

Reference to a TopographicPlace

8.8. The group AddressDetailGroup

AddressDetailGroup

An address with its name entities

AddressDetail

CountryName

0:1

Country of the address.

PostCode

0:1

Postal code of the address.

TopographicPlaceName

0:1

TopographicPlace name of the address. If set it should at least contain the city name.

→‍TopographicPlaceRef

0:1

>TopographicPlaceRef

Reference to a TopographicPlace

Street

0:1

Street name of the address.

HouseNumber

0:1

House number of the address. If none is given, either a crossing street can be given, or the whole street is meant.

CrossRoad

0:1

Crossing. This can be used to be more specific without using house numbers.

8.9. The group PlaceRefGroup

PlaceRefGroup

Group for reference to a geographic PLACE of any type which may be specified as the origin or destination of a trip.

The element contains one of the following elements (a-f)

PlaceRef

a

→‍siri:StopPointRef

-1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

b

→‍StopPlaceRef

-1:1

>StopPlaceRef

Reference to a Stop Place

c

GeoPosition

-1:1

+siri:Location

WGS84 coordinates position.

d

→‍TopographicPlaceRef

-1:1

>TopographicPlaceRef

Reference to a TopographicPlace

e

→‍PointOfInterestRef

-1:1

>PointOfInterestRef

Reference to a Point of Interest

f

→‍AddressRef

-1:1

>AddressRef

Reference to an Address

Name

1:1

+InternationalText

Public name of the place.

AllowedSystemId

0:*

Used in distributed environments. e.g., EU-Spirit. If none is given, the place information request refers to all known systems (in EU-Spirit "passive servers"). If at least one is given, the place information request refers only to the given systems (in EU-Spirit "passive servers"). In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

8.10. The group StopAttributesGroup

StopAttributesGroup

[properties of a SCHEDULED STOP POINT or STOP PLACE in TMv6] selection of attributes of ACCESSIBIITY LIMITATION related to a SCHEDULED STOP POINT extended by attributes referring to some equipment.

StopAttributes

WheelchairAccessible

0:1

Whether this stop is accessible for wheelchair users.

Lighting

0:1

Whether this stop is lit.

Covered

0:1

Whether this stop offers protection from weather conditions like rain, snow, storm etc.

8.11. The group StopPlaceGroup

StopPlaceGroup

A stop place with id and name

StopPlace

→‍StopPlaceRef

1:1

>StopPlaceRef

Reference to a Stop Place

StopPlaceName

1:1

+InternationalText

Name of this stop place for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop place that may be appended to the name if enough space is available. E.g. "Exhibition Center".

8.12. The group StopPointGroup

StopPointGroup

A stop point with id and name

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

8.13. The complex type AccessModesListOfEnumerations

AccessModesListOfEnumerations

List of Access Modes.

AccessMode

0:*

ifopt:AccessModesEnumeration

Access mode that should be considered.

8.14. The complex type AddressRefStructure

AddressRefStructure

AddressCodeType

Identifier of an Address

8.15. The complex type AddressStructure

AddressStructure

descriptive data associated with a PLACE that can be used to describe the unique geographical context of a PLACE for the purposes of identifying it. May be refined as either a ROAD ADDRESS, a POSTAL ADDRESS or both

PublicCode

1:1

AddressCodeType

ID of this address.

PrivateCode

0:*

+PrivateCode

Code of this address in private/foreign/proprietary coding schemes.

Name

1:1

+InternationalText

Name or description of address for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the address that may be appended to the name if enough space is available. E.g. "Crossing with Peterstraße".

AddressDetail

CountryName

0:1

Country of the address.

PostCode

0:1

Postal code of the address.

TopographicPlaceName

0:1

TopographicPlace name of the address. If set it should at least contain the city name.

→‍TopographicPlaceRef

0:1

>TopographicPlaceRef

Reference to a TopographicPlace

Street

0:1

Street name of the address.

HouseNumber

0:1

House number of the address. If none is given, either a crossing street can be given, or the whole street is meant.

CrossRoad

0:1

Crossing. This can be used to be more specific without using house numbers.

8.16. The complex type CategoryKeyValueType

CategoryKeyValueType

Category Key Value triplets. Category can be empty. Several such elements form the information necessary for a given category.

Category

0:1

Key

1:1

Value

1:1

8.17. The complex type OsmTagStructure

OsmTagStructure

Structure of an OpenStreetMap tag.

Tag

1:1

Name of OpenStreetMap tag (amenity, leisure, tourism, bike, ...)

Value

1:1

Value for OpenStreetMap tag (charging_station, hostel, yes, ...)

8.18. The complex type PlaceRefStructure

PlaceRefStructure

Reference to a geographic PLACE of any type which may be specified as the origin or destination of a trip.

The element contains one of the following elements (a-f)

PlaceRef

a

→‍siri:StopPointRef

-1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

b

→‍StopPlaceRef

-1:1

>StopPlaceRef

Reference to a Stop Place

c

GeoPosition

-1:1

+siri:Location

WGS84 coordinates position.

d

→‍TopographicPlaceRef

-1:1

>TopographicPlaceRef

Reference to a TopographicPlace

e

→‍PointOfInterestRef

-1:1

>PointOfInterestRef

Reference to a Point of Interest

f

→‍AddressRef

-1:1

>AddressRef

Reference to an Address

Name

1:1

+InternationalText

Public name of the place.

AllowedSystemId

0:*

Used in distributed environments. e.g., EU-Spirit. If none is given, the place information request refers to all known systems (in EU-Spirit "passive servers"). If at least one is given, the place information request refers only to the given systems (in EU-Spirit "passive servers"). In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

8.19. The complex type PlaceStructure

PlaceStructure

geographic PLACE of any type which may be specified as the origin or destination of a trip

The element contains none or one of the following elements (a-e)

a

StopPoint

-1:1

+StopPoint

Model of a stop point

b

StopPlace

-1:1

+StopPlace

Model of a stop place

c

TopographicPlace

-1:1

+TopographicPlace

TopographicPlace. Region, village, or city.

d

PointOfInterest

-1:1

+PointOfInterest

Model of a POI

e

Address

-1:1

+Address

Model of an address

Name

1:1

+InternationalText

Public name of the place.

GeoPosition

1:1

+siri:Location

Position using WGS84/EPSG:4326 coordinates.

Mode

0:*

+Mode

List of transport modes that call at this place object. This list should only be filled in case of stop points or stop places – and only when explicitly requested.

AccessModeList

0:1

+AccessModesListOfEnumerations

Access modes that are supported by this place.

SituationFullRefs

0:1

+SituationRefList

SITUATION reference. Mostly used for STOP PLACE, SCHEDULED STOP POINT (StopPoint). However, in future a situation reference may occur on many geographic elements (e.g., roads) as well.

Attribute

0:*

+GeneralAttribute

Attributes associated with this place. This is used, e.g., for details, OSM attributes or key/value descriptions. Most of them will be implementation dependent (except OSM). From Transmodel, TYPE OF POINT might be an attribute.

Extension

0:1

8.20. The complex type PointOfInterestAdditionalInformationStructure

PointOfInterestAdditionalInformationStructure

Generic structure for additional information on POIs.

POIAdditionalInformation

1:*

+CategoryKeyValueType

POI additional information is a set of key/value pairs that are associated with defined categories.

8.21. The complex type PointOfInterestCategoryStructure

PointOfInterestCategoryStructure

[a view of POINT OF INTEREST CLASSIFICATION in TMv6] categorisation of POINTs OF INTEREST in respect of the activities undertaken at them (defined by key-value-pairs).

The element contains one of the following elements (a-b)

a

OsmTag

-1:*

+OsmTag

OpenStreetMap tag structure (key-value)

b

PointOfInterestClassification

-1:*

Classification of the POI (when it is not from OSM). The codification of the classification id may include de codification source (for example "IGN:[classificationCode]")

8.22. The complex type PointOfInterestFilterStructure

PointOfInterestFilterStructure

Filter POIs by category.

Exclude

0:1

Whether categories in list are to include or exclude from search. Default is FALSE.

PointOfInterestCategory

0:*

+PointOfInterestCategory

These POI categories can be used to filter POIs. If more than one is given the filtering is by logical "OR" (when Exclude=FALSE) and logical "AND" (when Exclude=TRUE).

8.23. The complex type PointOfInterestRefStructure

PointOfInterestRefStructure

PointOfInterestCodeType

Identifier of a Point of Interest

8.24. The complex type PointOfInterestStructure

PointOfInterestStructure

[corresponds to POINT OF INTEREST in TMv6 with related information] type of PLACE to or through which passengers may wish to navigate as part of their journey and which is modelled in detail by journey planners.

PublicCode

1:1

PointOfInterestCodeType

ID of this Point of Interest.

Name

1:1

+InternationalText

Name or description of point of interest for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the point of interest that may be appended to the name if enough space is available. E.g. "Exhibition Center".

PointOfInterestCategory

0:*

+PointOfInterestCategory

Categories this POI is associated with. Order indicates descending relevance.

PrivateCode

0:*

+PrivateCode

Code of this point of interest in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

>TopographicPlaceRef

Reference to a TopographicPlace

POIAdditionalInformation

0:1

+PointOfInterestAdditionalInformation

Additional information for this POI (e.g., information on available parking slots, charging infrastructure, sharing vehicles).

8.25. The complex type StopPlaceRefStructure

StopPlaceRefStructure

StopPlaceCodeType

Identifier of a Stop Place

8.26. The complex type StopPlaceStructure

StopPlaceStructure

[an extended view of STOP PLACE in TMv6] a PLACE extended by ACCESSIBILITY LIMITATION properties and some attributes of the associated equipment, comprising one or more locations where vehicles may stop and where passengers may board or leave vehicles or prepare their trip, and which will usually have one or more well-known names

StopPlace

→‍StopPlaceRef

1:1

>StopPlaceRef

Reference to a Stop Place

StopPlaceName

1:1

+InternationalText

Name of this stop place for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop place that may be appended to the name if enough space is available. E.g. "Exhibition Center".

PrivateCode

0:*

+PrivateCode

Code of this stop place in private/foreign/proprietary coding schemes.

→‍TopographicPlaceRef

0:1

>TopographicPlaceRef

Reference to a TopographicPlace

StopAttributes

WheelchairAccessible

0:1

Whether this stop is accessible for wheelchair users.

Lighting

0:1

Whether this stop is lit.

Covered

0:1

Whether this stop offers protection from weather conditions like rain, snow, storm etc.

8.27. The complex type StopPointStructure

StopPointStructure

[an extended view of SCHEDULED STOP POINT in TMv6] a SCHEDULED STOP POINT extended by ACCESSIBILITY LIMITATION attributes and with identifier and name where passengers can board or alight from vehicles

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

PrivateCode

0:*

+PrivateCode

Code of this stop point in private/foreign/proprietary coding schemes.

ParentRef

0:1

>StopPlaceRef

Reference to the stop place to which this stop point belongs.

→‍TopographicPlaceRef

0:1

>TopographicPlaceRef

Reference to a TopographicPlace

StopAttributes

WheelchairAccessible

0:1

Whether this stop is accessible for wheelchair users.

Lighting

0:1

Whether this stop is lit.

Covered

0:1

Whether this stop offers protection from weather conditions like rain, snow, storm etc.

8.28. The complex type TopographicPlaceRefStructure

TopographicPlaceRefStructure

TopographicPlaceCodeType

Identifier of a TopographicPlace

8.29. The complex type TopographicPlaceStructure

TopographicPlaceStructure

[TMv6] A type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g., County,City, Town, Village) and of different specificity (e.g., Greater London, London, West End, Westminster, St James's).

TopographicPlaceCode

1:1

TopographicPlaceCodeType

TopographicPlace ID.

TopographicPlaceName

1:1

+InternationalText

Name or description of TopographicPlace for use in passenger information.

PrivateCode

0:*

+PrivateCode

Code of this TopographicPlace in private/foreign/proprietary coding schemes.

ParentRef

0:1

>TopographicPlaceRef

Reference to a parent TopographicPlace.

ReferredSystem

0:1

>siri:ParticipantRef

Used in distributed environments (e.g., EU-Spirit). If set, this topographic place resides within the given system (in EU-Spirit "passive server"). This system can be queried for actual places within this topographic place. This is used in a distributed environment for a two-steps place identification. In EU-Spirit the system IDs were previously called "provider code". See https://eu-spirit.eu/

Area

0:1

+Area

Area covered by the locality described as a polygon.

9. OJP/OJP_StopEvents.xsd - Request and response definitions for arrivals and departures of public transport services at stops

9.1. Simple type definitions

HierarchyEnumeration

Indicates for which parts of the hierarchy of the StopPlace(s) stop events should be provided (if known by the server). "local" (default) is the local server setting. "no" will include no hierarchy and only provide the given StopPlace / StopPoint. "down" will include all lower StopPoints/StopPlaces in the hierarchy, if such a hierarchy exists. "all" does include all StopPoints/StopPlaces for the meta station if it is known. How to use this: if you indicate the reference to a train station and the parameter is set to "down", the departures/ arrivals at the associated bus stations will show as well. If you have the ScheduledStopPoint of platform B of the local bus and it is associated with 3 other stations, you will get all these arrivals/departures as well, if the parameter is set to "all".

local

-

no

-

down

-

all

-

StopEventProblemTypeEnumeration

Types of problems that may be returned in responses to STOPEVENT requests.

STOPEVENT_NOEVENTFOUND

No departure/arrival could be found within the requested period that meets the given restrictions.

STOPEVENT_LOCATIONUNSERVED

At the locations (address, stop, etc.) for which stop events have been requested, there is no public transport service at all.

STOPEVENT_LOCATIONUNKNOWN

The location (address, stop, etc.) for which stop events were requested is unknown.

STOPEVENT_DATEOUTOFRANGE

There are no timetables available for the requested date.

STOPEVENT_LASTSERVICEOFTHISLINE

This departure/arrival event is the last one of this line for this operating day.

STOPEVENT_NOREALTIME

There is no real-time or forecast data available for this departure/arrival event.

STOPEVENT_OTHER

A problem has occurred that does not have a specific problem type.

StopEventResultObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

StopEventTypeEnumeration

Departure or arrival events or both

departure

-

arrival

-

both

-

9.2. The toplevel element StopEventProblemType

StopEventProblemType

+StopEventProblemTypeEnumeration (↔ ojp:ErrorType)

9.3. The group StopEventContentFilterGroup

StopEventContentFilterGroup

Content filters which data is expected in the response

StopEventContentFilter

IncludePreviousCalls

0:1

Whether the previous calls of each vehicle journey should be included in the response.

IncludeOnwardCalls

0:1

Whether the onward calls of each vehicle journey should be included in the response.

IncludeOperatingDays

0:1

Whether operating day information of this stop event should be included in the response.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

Whether real-time information of this stop event should be used in the response. Default is "full"

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true

IncludeStopHierarchy

0:1

HierarchyEnumeration

Indicates for which parts of the hierarchy of the StopPlace(s) stop events should be provided (if known by the server). "local" (default) is the local server setting. "no" will include no hierarchy and only provide the given StopPlace / StopPoint. "down" will include all lower StopPoints/ StopPlaces in the hierarchy, if such a hierarchy exists. "all" does include all StopPoints/StopPlaces for the meta station if it is known. How to use this: if you indicate the reference to a train station and the parameter is set to "down", the departures/arrivals at the associated bus stations will show as well. If you have the ScheduledStopPoint of platform B of the local bus and it is associated with 3 other stations, you will get all these arrivals/departures as well if the parameter is set to "all".

9.4. The group StopEventDataFilterGroup

StopEventDataFilterGroup

Request data filters

StopEventDataFilter

ModeFilter

0:1

+ModeFilter

MODEs to be excluded or included in stop events. We on purpose don't use ModeOfOperationFilter in the stop event service.

LineFilter

0:1

+LineDirectionFilter

Lines/Directions to include/exclude.

OperatorFilter

0:1

+OperatorFilter

Transport operators to include/exclude.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements.

9.5. The group StopEventPolicyGroup

StopEventPolicyGroup

Request policies

StopEventPolicy

NumberOfResults

0:1

parameter to control the number of TRIP results before/after a point in time. May NOT be used when departure time at origin AND arrival time at destination are set

TimeWindow

0:1

Time window events should lie within. Starting from time given in PlaceContext.

StopEventType

0:1

StopEventTypeEnumeration

Only departures or arrivals or both.

9.6. The group StopEventRequestGroup

StopEventRequestGroup

Request structure for departure and arrival events at stops

StopEventRequest

Location

1:1

+PlaceContext

LOCATION / PLACE for which to obtain stop event information. If a coordinate or an address is used, then the result may depend on other parameters: All stops in reasonable walking distance and stops that are within range of limitations of the IndividualTransportOptions should be shown. If the next stop is too far away, then no result is shown. "Reasonable" is usually defined as part of the server configuration.

Params

0:1

+StopEventParam

Request parameter

9.7. The group StopEventResponseGroup

StopEventResponseGroup

Response structure for departure and arrival events at stops

StopEventResponse

StopEventResponseContext

0:1

+ResponseContext

Container for data that is referenced multiple times.

StopEventResult

0:*

+StopEventResult

Enclosing element for stop event data.

9.8. The complex type CallAtNearStopStructure

CallAtNearStopStructure

indication of the walk distance and time to a nearby stop where relevant.

CallAtStop

1:1

+CallAtStop

[same as CALL in SIRI] the meeting of a VEHICLE JOURNEY with a specific SCHEDULED STOP POINT.

WalkDistance

0:1

siri:DistanceType

Distance from request LOCATION / PLACE (e.g., address) to this stop in metres.

WalkDuration

0:1

Walking duration from request LOCATION / PLACE (e.g., address) to this stop. All user options considered (e.g., walk speed).

9.9. The complex type StopEventParamStructure

StopEventParamStructure

Request specific parameters (parameters which define what is to be included in a Stop Event result)

StopEventDataFilter

ModeFilter

0:1

+ModeFilter

MODEs to be excluded or included in stop events. We on purpose don't use ModeOfOperationFilter in the stop event service.

LineFilter

0:1

+LineDirectionFilter

Lines/Directions to include/exclude.

OperatorFilter

0:1

+OperatorFilter

Transport operators to include/exclude.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements.

StopEventPolicy

NumberOfResults

0:1

parameter to control the number of TRIP results before/after a point in time. May NOT be used when departure time at origin AND arrival time at destination are set

TimeWindow

0:1

Time window events should lie within. Starting from time given in PlaceContext.

StopEventType

0:1

StopEventTypeEnumeration

Only departures or arrivals or both.

StopEventContentFilter

IncludePreviousCalls

0:1

Whether the previous calls of each vehicle journey should be included in the response.

IncludeOnwardCalls

0:1

Whether the onward calls of each vehicle journey should be included in the response.

IncludeOperatingDays

0:1

Whether operating day information of this stop event should be included in the response.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

Whether real-time information of this stop event should be used in the response. Default is "full"

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true

IncludeStopHierarchy

0:1

HierarchyEnumeration

Indicates for which parts of the hierarchy of the StopPlace(s) stop events should be provided (if known by the server). "local" (default) is the local server setting. "no" will include no hierarchy and only provide the given StopPlace / StopPoint. "down" will include all lower StopPoints/ StopPlaces in the hierarchy, if such a hierarchy exists. "all" does include all StopPoints/StopPlaces for the meta station if it is known. How to use this: if you indicate the reference to a train station and the parameter is set to "down", the departures/arrivals at the associated bus stations will show as well. If you have the ScheduledStopPoint of platform B of the local bus and it is associated with 3 other stations, you will get all these arrivals/departures as well if the parameter is set to "all".

Extension

0:1

9.10. The complex type StopEventResultStructure

StopEventResultStructure

Wrapper element for a single stop event result.

Id

1:1

StopEventResultObjectIdType

ID of this result.

ErrorCondition

0:*

+OJPError

Problems related to this STOPEVENT result.

StopEvent

1:1

+StopEvent

Stop event data element.

9.11. The complex type StopEventStructure

StopEventStructure

Stop event structure.

PreviousCall

0:*

+CallAtNearStop

Calls at stops that happen before this stop event (service pattern of this vehicle journey before this stop event).

ThisCall

1:1

+CallAtNearStop

The call of this vehicle journey at this stop.

OnwardCall

0:*

+CallAtNearStop

Calls at stops that happen after this stop event (rest of the service pattern of the vehicle journey).

Service

1:1

+DatedJourney

Service that calls at this stop.

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

SituationFullRefs

0:1

+SituationRefList

For SITUATIONs that affect the whole StopEvent. Otherwise, references for SITUATIONs can be added at the different CALL elements

Extension

0:1

10. OJP/OJP_TripInfo.xsd - Request and response definitions for information on a single trip

10.1. Simple type definitions

IncludeFormationEnumeration

Possible values how to include formations in the basic filters

none

-

vehiclefeature

The response should include VehicleFeatureRef (from SIRI).

full

Besides VehicleFeatureRefs also Formation, ArrivalFormation and DepartureFormation can be used. This is the full SIRI formation experience. Refer to the SIRI documentation for details. The specification document and the examples may show simpler ways of doing things. For full accessibility many features are needed. It is recommended to always also use VehicleFeatureRef (for people not processing SIRI formation and because buses and the like don't need Formation in most cases).

TripInfoProblemTypeEnumeration

Types of problems that may be returned in responses to TripInfo requests.

TRIPINFO_JOURNEYREFUNKNOWN

The journey reference used in the request is unknown.

TRIPINFO_VEHICLEUNKNOWN

The vehicle reference used in the request is unknown.

TRIPINFO_NOJOURNEYFOUND

No matching journey could be found for the requested time and journey/vehicle identifiers.

TRIPINFO_NOGEOINFO

No geographic information available for this vehicle journey.

TRIPINFO_NOREALTIME

No real-time information available.

TRIPINFO_OTHER

A problem has occurred that does not have a specific problem type.

10.2. The toplevel element TripInfoProblemType

TripInfoProblemType

+TripInfoProblemTypeEnumeration (↔ ojp:ErrorType)

10.3. The group TripInfoContentFilterGroup

TripInfoContentFilterGroup

Parameters that control the level of detail to be returned in the results.

TripInfoContentFilter

IncludeCalls

0:1

Whether call information is to be included. Default is true.

IncludePosition

0:1

Whether current position is to be included. Default is true.

IncludeService

0:1

Whether service information is to be included. Default is true.

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of this vehicle journey.

IncludeTrackProjection

0:1

Whether the result should include the geographic projection (coordinates) of this vehicle journey.

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeFormation

0:1

IncludeFormationEnumeration

Whether the formation should be included. With "simple" only VehicleFeature is used. "full" may unleash the full power of the SIRI formation model (especially for trains). The OJP specification document gives hints on how to limit oneself as a server to the most important aspects. Default is none.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true

10.4. The group TripInfoPolicyGroup

TripInfoPolicyGroup

Parameters that control the response behaviour.

TripInfoPolicy

UseRealTimeData

0:1

UseRealtimeDataEnumeration

Use real-time data. Default is "full"

10.5. The group TripInfoRequestGroup

TripInfoRequestGroup

TripInfo request structure.

The element contains one of the following element sequences (a-c)

DatedJourneyRef

a

→‍JourneyRef

-1:1

>JourneyRef

Reference to a Journey

a

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

DatedTrainNumberRef

b

TrainNumber

-1:1

b

OperatorRef

-1:1

>siri:OperatorRef

b

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

TimedVehicleRef

c

→‍siri:VehicleRef

-1:1

>siri:VehicleRef

Reference to a VEHICLE.

c

TimeOfOperation

-1:1

Time stamp when the vehicle is operating. In most use cases equal to "now".

TripInfoRequest

Params

0:1

+TripInfoParam

Request parameter.

10.6. The group TripInfoResponseGroup

TripInfoResponseGroup

TripInfo response structure.

TripInfoResponse

TripInfoResponseContext

0:1

+ResponseContext

Response context.

TripInfoResult

0:1

+TripInfoResult

Result structure.

10.7. The complex type TripInfoParamStructure

TripInfoParamStructure

TripInfo request parameter structure.

TripInfoPolicy

UseRealTimeData

0:1

UseRealtimeDataEnumeration

Use real-time data. Default is "full"

TripInfoContentFilter

IncludeCalls

0:1

Whether call information is to be included. Default is true.

IncludePosition

0:1

Whether current position is to be included. Default is true.

IncludeService

0:1

Whether service information is to be included. Default is true.

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of this vehicle journey.

IncludeTrackProjection

0:1

Whether the result should include the geographic projection (coordinates) of this vehicle journey.

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeFormation

0:1

IncludeFormationEnumeration

Whether the formation should be included. With "simple" only VehicleFeature is used. "full" may unleash the full power of the SIRI formation model (especially for trains). The OJP specification document gives hints on how to limit oneself as a server to the most important aspects. Default is none.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true

Extension

0:1

10.8. The complex type TripInfoResultStructure

TripInfoResultStructure

TripInfo result structure containing the status of a trip.

ErrorCondition

0:*

+OJPError

Problems related to this TripInfo result.

PreviousCall

0:*

+CallAtStop

The stops this service already has called at. Including the current stop if service is currently at stop.

CurrentPosition

0:1

+VehiclePosition

Current position of this service.

OnwardCall

0:*

+CallAtStop

The stops this service still has to call at.

Service

0:1

+DatedJourney

Description of the service.

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

siri:CommonFacility

→‍siri:FareClassFacility

0:*

siri:FareClassFacilityEnumeration

Classification of FareClass Facility type - Tpeg pti23.

→‍siri:TicketingFacility

0:*

siri:TicketingFacilityEnumeration

Classification of Ticketing Facility type - Tpeg pti23.

→‍siri:NuisanceFacility

0:*

siri:NuisanceFacilityEnumeration

Classification of Nuisance Facility type - Tpeg pti23.

→‍siri:MobilityFacility

0:*

siri:MobilityFacilityEnumeration

Classification of Mobility Facility type - Tpeg pti23.

→‍siri:PassengerInformationFacility

0:*

siri:PassengerInformationFacilityEnumeration

Classification of PassengerInfo Facility type - Tpeg pti23.

→‍siri:PassengerCommsFacility

0:*

siri:PassengerCommsFacilityEnumeration

Classification of PassengerComms Facility type - Tpeg pti23.

→‍siri:RefreshmentFacility

0:*

siri:RefreshmentFacilityEnumeration

Classification of Refreshment Facility type - Tpeg pti23.

siri:AccessFacility

0:*

siri:AccessFacilityEnumeration

Classification of Access Facility.

→‍siri:SanitaryFacility

0:*

siri:SanitaryFacilityEnumeration

Classification of Sanitary Facility type - Tpeg pti23.

→‍siri:LuggageFacility

0:*

siri:LuggageFacilityEnumeration

Classification of Luggage Facility type - Tpeg pti23.

siri:ServiceFacility

→‍siri:AccommodationFacility

0:*

siri:AccommodationFacilityEnumeration

Classification of Accomodation Facility type - Tpeg pti23.

JourneyTrack

0:1

+LegTrack

Geographic embedding of this journey. The entire journey is regarded as one leg.

Extension

0:1

11. OJP/OJP_Trips.xsd - Request and response definitions for trip requests and distributed journey planning

11.1. Simple type definitions

AccessFeatureStatusEnumeration

Allowed values for status of the access feature.

unknown

-

available

-

partiallyAvailable

If partiallyAvailable is used, then some note should be provided in one of the descriptive elements of the containing PathLink

notAvailable

-

AccessFeatureTypeEnumeration

Allowed values for a AccessFeature.

elevator

-

stairs

-

seriesOfStairs

-

singleStep

-

seriesOfSingleSteps

-

escalator

-

travelator

-

ramp

-

footpath

-

shuttle

-

other

-

unknown

-

AccessibilityFeatureTypesEnumeration

Allowed values for AccessibilityFeature (for mobility and sensory impairments, assistance and crucial elements to pay attention to).

lowFloorAccess

-

stepFreeAccess

-

accessWithSteps

-

slidingStep

-

raisedKerb

-

narrowEntrance

-

wheelchairLift

-

manualRamp

-

automaticRamp

-

suitableForWheelchairs

-

suitableForUnassistedWheelchairs

-

suitableForSeverelyDisabled

-

suitableForPushchairs

-

suitableForBicycles

-

tactilePlatformEdges

-

tactileGuidingStrips

-

tactileOrAuditorySigns

-

visualSigns

-

elevatorWithTactileButtons

-

elevatorWithAcousticAnnouncements

-

audioInformation

-

audioForHearingImpaired

-

visualDisplays

-

displaysForVisuallyImpaired

-

largePrintTimetables

-

boardingAssistance

-

onboardAssistance

-

unaccompaniedMinorAssistance

-

barrier

-

validator

-

ExtendToFrontOrBackType

Prefer earlier or later times.

extendToFront

-

extendToBack

-

FeasibilityEnumeration

Allowed values for the feasibility of a TRIP or part of a TRIP.

allAccessFeaturesAvailable

-

accessFeatureNotAvailable

-

accessFeaturePartiallyAvailable

-

accessFeatureWithUnknownAvailability

-

seeSituations

-

GuidanceAdviceEnumeration

Several types of guidance advice given to traveller. Suitable values may differ by MODE (e.g., a car driver needs different advice than a person walking for a transfer.

origin

Defining origin.

destination

Defining a destination.

continue

Continue on the same street/road/path.

keep

Keep going on the same street/road/path.

turn

When this value is used, you always must consider the value in TurnAction as well. There must be a TurnAction present if "turn" is used.

leave

Can be something like an elevator or a vehicle.

enter

Can be something like an elevator or a vehicle.

enter_roundabout

Entering a roundabout.

stay_in_roundabout

Staying in the roundabout.

leave_roundabout

Leave the roundabout.

enter_builtup_area

Entering a built-up area / community.

leave_builtup_area

Leave the built-up area / community.

freewayAccessRamp

Access lane to highway or the like.

unknown_lane_choice

If it is unclear which lane to choose.

left_lane

If there are more than 2 lanes, then TurnAction half_left, left, sharp_left may help decide.

middle_lane

If there are more than 3 lanes, then Turnaction straight defines the middle one.

right_lane

If there are more than 2 lanes, then TurnAction half_right, right, sharp_right may help decide.

unknown_turning_kind

-

LegObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

MultiPointTripResultObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

MultiPointTypeEnumeration

Defines how the router should handle requests with multiple origins and destinations. MultiPointType is more important than NumberOfResults in the sense that if 10 results are needed to fulfill the MultiPointType, then it is 10, even when NumberOfResults was set to 1.

anyPoint

Returning results for a single origin and destination (hopefully the best ones). As this element was not sufficiently defined in the past, some implementations may behave differently.

eachOrigin

At least a distinct solution for each of the origin points must be delivered.

eachDestination

At least a distinct solution for each of the destination points must be delivered.

eachOriginDestination

At least one result for each origin/destination pair must be delivered.

somePoints

Clarifies that some (probably the "best") origin-destination pairs should be returned. How many are to be used is not defined.

OptimisationMethodEnumeration

The types of algorithms that can be used for planning a journey (fastest, least walking, etc.). Only one method can be used. Each one really is a whole set of a policy, which is defined below. E.g., "fastest" also includes "least transfers" as a second criteria, some modes are excluded usually by default. Implementations might differ (slightly). Also, some strategies might not be implemented. The most important strategies are marked.

fastest

Shortest duration somewhere in the future. This may present a shorter trip than the next earliest arrival (with latest departure). Expected strategy.

minChanges

Minimise the number of interchanges as the first criterion. Expected strategy.

leastWalking

Shortest walking distance in meters, summed over all legs.

leastCost

Cheapest fare, considering the applicable reductions. Might not be based on actual cost, but an estimation. Expected strategy.

leastDistance

Least distance in metres. Mostly used for ALTERNATIVE MODE OF OPERATION and for ItModesToCover.

earliestArrival

Earliest possible arrival time respecting the time constraints (forward search).

latestDeparture

Latest departure time for a given arrival time (backward search).

earliestArrivalAndLatestDeparture

Combines earliestArrival and latestDeparture, allowing to compress the departure time (forward-backward-forward search).

minNonLevelEntrances

The user wants to minimize non-level entrances on the trip. this is useful for PRM who still can use some non-level entrances.

minStairs

The user wants to minimize stairs and steps on the trip. This is useful for PRM who still can use some steps/stairs.

bestForVisualImpairment

The user wants to avoid transfers without tactile guidance, as well as platforms and vehicles without auditory signals.

bestForAuditoryImpairment

The user wants to avoid transfers without guidance for people with auditory impairment, as well as platforms and vehicles without visual signs.

environmentalSafety

If set, favour "green" modes/lines such as bike sharing and (electric) trains, avoid or restrict modes/lines known for higher CO2 emissions such as (conventional) taxi, ride-hailing or coach.

extraSafe

High level of safety (referring to crime, hazards or prone to accidents). If used, certain modes, lines or zones/districts known for lower safety, i.e. higher risk of accidents and crime, may be avoided, others may be preferred. This may depend on the actual, local or time of day situation. E.g. bike or scooter may be considered unsafe in some cities/districts while safe in others.

extraReliable

Low probability of delays, cancellations etc. If used, modes known for their (un)reliability may be avoided/preferred, and extra time added for transfers. This may depend on the actual, local or time of day situation, based on punctuality statics, traffic jam statistics or rush hours. E.g. taxis in a given city might be known to be unreliable during at 8-10 and 16-19 hours, otherwise reliable.

scenic

Scenic (or touristic) travel. Different by modes or by the surrounding.

quietTravel

E.g. first class or quiet compartments preferred. Journeys that are with low occupancy.

TransitionEnumeration

Transition types for interchanges.

up

-

down

-

level

-

upAndDown

-

downAndUp

-

TripChangeProblemTypeEnumeration

Types of problems that may be returned in responses to TRIPCHANGE requests.

TRIPCHANGE_NOLATERTRIPFOUND

No later option for the requested part of the TRIP could be found.

TRIPCHANGE_NOEARLIERTRIPFOUND

No earlier option for the requested part of the TRIP could be found.

TRIPCHANGE_INVALIDLEGREF

Requested leg ref is invalid.

TRIPCHANGE_INVALIDOPERATOR

Requested operator is invalid.

TRIPCHANGE_NOVEHICLEAVAILABLE

No vehicle is available for the requested leg.

TRIPCHANGE_OTHER

A problem has occurred that does not have a specific problem type.

TripObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a TRIP Object.

TripProblemTypeEnumeration

Types of problems that may be returned in responses to Trip requests.

TRIP_NOTRIPFOUND

No trip plan could be found that meets all the parameters as they have been set by the user (start and end locations, departure/arrival time and further options possibly set by the user).

TRIP_ORIGINUNKNOWN

The start location (address, stop place, …) for the requested trip is unknown.

TRIP_DESTINATIONUNKNOWN

The end location (address, stop place, …) for the requested trip is unknown.

TRIP_VIAUNKNOWN

One of the via points is unknown.

TRIP_NOTVIAUNKNOWN

One of the not-via points is unknown.

TRIP_NOCHANGEATUNKNOWN

One of the no-change-at stations is unknown.

TRIP_NOORIGIN

No start location has been defined for the trip.

TRIP_NODESTINATION

No end location has been defined for the trip.

TRIP_ORIGINDESTINATIONIDENTICAL

Start and end of the trip are identical.

TRIP_DATETIMEERROR

The requested date and/or time do not make sense.

TRIP_TIMEWINDOWTOOLARGE

The requested time window is too large.

TRIP_DEPARTUREAFTERARRIVAL

The requested departure time at each origin is after the requested arrival time at any destination.

TRIP_DATEOUTOFRANGE

There is no timetable data available for the requested date.

TRIP_ORIGINEQUIVALENT

The requested origin stop place has been replaced by an equivalent stop place.

TRIP_DESTINATIONEQUIVALENT

The requested destination stop place has been replaced by an equivalent stop place.

TRIP_VIAEQUIVALENT

One of the requested via stop places has been replaced by an equivalent stop place.

TRIP_REALTIMEINCOMPLETE

There is no real-time information available for at least one of the services within this trip result.

TRIP_ITTIMEEXTENDED

The maximum time allowed for using modes of individual transport (mostly walking or cycling) has been extended by the system because otherwise no trip could be found.

TRIP_ITMODECHANGED

The mode of individual transport specified by the user has been replaced by the system because otherwise no trip could be found. Usually, this means taking a taxi instead of walking.

TRIP_INCONVENIENTWAITING

The trip plan in this trip result contains a long waiting time.

TRIP_RESTRICTEDRESULTSDROPPED

Used for warnings, when possible/better results were dropped, because of the criteria were not used (e.g., private services, offer only available for seniors).

TRIP_MULTIPOINT_NOTALLPOINTSCOVERED

No trip solution was found covering each of the requested points.

TRIP_MULTIPOINT_TOOMANYPOINTS

Too many points have been requested as departure or arrival.

TRIP_MULTIPOINT_TYPE_NOT_SUPPORTED

The indicated multipoint type is not supported.

TRIP_REFINE_LEG_UNKNOWN

Indicated legs do not exist.

REFINE_OBJECTNOTFOUND

The object to be refined could not be found in the database of the responding system or could not be found unequivocally.

REFINE_PROFILENOTSUPPORTED

Refinement does not support the hiking or cycling profile.

TRIP_OTHER

A problem has occurred that does not have a specific problem type.

TripResultObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

TurnActionEnumeration

The range of possible turns that can be described.

straight_on

338-21 degrees

half_right

22-67 degrees

right

68-111 degrees

sharp_right

112-157 degrees

uturn

158-201 degrees

sharp_left

202-247 degrees

left

248-291 degrees

half_left

292-337 degrees

up

Upwards, the target level is in the PathLink structure.

down

Downwards, the target level is in the PathLink structure.

unknown_turn_action

-

group[ojp:TripMobilityFilterGroup]
  /HikingProfile #simpleType
  (typedef-90.1)

-

easy

Regular hiking/walking in valleys and plains and easy mountain trails e.g., yellow hiking signs in Switzerland or blue in Germany.

medium

Medium difficulty mountain trails. E.g. white-red-white hiking signs in Switzerland or red in Germany.

difficult

Difficult mountain trails. E.g. white-blue-white hiking signs in Switzerland or black in Germany.

group[ojp:TripMobilityFilterGroup]
  /CyclingProfile #simpleType
  (typedef-90.2)

-

fast

Fastest cycle route

green

Greenest cycle route

comfortable

Family friendly and leisurely route

11.2. The toplevel element TripChangeProblemType

TripChangeProblemType

+TripChangeProblemTypeEnumeration (↔ ojp:ErrorType)

11.3. The toplevel element TripProblemType

TripProblemType

+TripProblemTypeEnumeration (↔ ojp:ErrorType)

11.4. The group InterchangeGroup

InterchangeGroup

Adding interchange elements from SIRI to a transfer leg.

Interchange

InterchangeRef

0:1

>siri:InterchangeRef

Reference of an INTERCHANGE.

ExtraInterchange

0:1

Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1)

InterchangeCancellation

0:1

Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1)

siri:InterchangeProperty

siri:StaySeated

0:1

Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection.

siri:Guaranteed

0:1

Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed.

siri:Advertised

0:1

Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'.

11.5. The group MultiPointTripPolicyGroup

MultiPointTripPolicyGroup

Policies that control the multipoint trip search behaviour.

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

MultiPointTripPolicy

MultiPointType

0:1

MultiPointTypeEnumeration

Defines how the router should handle requests with multiple origins and destinations. As it is important for the strategy of the distributed trip planning the MultiPointType should be set. If the type is not supported a TRIP_MULTIPOINT_TYPE_NOT_SUPPORTED warning or error must be returned. Default is anyPoint.

11.6. The group MultiPointTripRequestGroup

MultiPointTripRequestGroup

Multi-point trip request structure.

MultiPointTripRequest

Origin

1:*

+PlaceContext

Specifies the origin situation from where the user wants to start.

Destination

1:*

+PlaceContext

Specifies the destination situation where the user is heading to.

Via

0:*

+TripVia

Ordered series of points where the journey must pass through. If more than one via point is given all of them must be obeyed - in the correct order. The server is allowed to replace a via stop by equivalent stops (in Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia).

NotVia

0:*

+NotVia

Not-via restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs that the TRIP is not allowed to pass through. If more than one not via point is given all of them must be obeyed.

NoChangeAt

0:*

+NoChangeAt

no-change-at restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs at which no TRANSFER is allowed within a TRIP (in Transmodel this would be an extension to TRIP MOBILITY FILTER).

Params

0:1

+MultiPointTripParam

Options to control the search behaviour and response contents.

11.7. The group MultiPointTripResponseGroup

MultiPointTripResponseGroup

Multi-point trip response structure.

MultiPointTripResponse

MultiPointType

0:1

MultiPointTypeEnumeration

The MultiPointType should be returned because it may differ from the one asked. Many systems will support only a subset of the MultiPointTypes, and it is important to know what the result is based on.

MultiPointTripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

MultiPointTripResult

0:*

+MultiPointTripResult

The trip results found by the server.

11.8. The group MultiPointWaitTimeGroup

MultiPointWaitTimeGroup

Group for wait times at origin/destination.

MultiPointWaitTime

OriginWaitTime

0:1

Additional wait time at origin of this trip.

DestinationWaitTime

0:1

Additional wait time at destination of this trip.

11.9. The group TransferDurationGroup

TransferDurationGroup

[an attribute of a CONNECTION (not INTERCHANGE) in TMv6] calculated duration in a response taking into account the request parameters. TransferDuration plus waiting time is the minimum interval between arrival and departure time.

TransferDuration

Duration

1:1

Overall duration of this interchange (Transmodel: PT CONNECTION LEG.MEAN INTERCHANGE TIME).

WalkDuration

0:1

Walk time as part of the overall interchange duration (in Transmodel might be modelled as TRANSFER.CONNECTION.DefaultDuration).

BufferTime

0:1

Buffer time as part of the overall interchange duration. Buffer times, e.g., check in/out times, sometimes are mandatory for using certain services as e.g., airplanes, ferries or highspeed trains.

11.10. The group TripChangeRequestGroup

TripChangeRequestGroup

Trip change request structure.

TripChangeRequest

ChangeParams

0:1

+TripChangeParam

Options to control the change.

TripResult

1:1

+TripResult

The trip result to be changed by the server.

TripResponseContext

0:1

+ResponseContext

Context to hold objects, which are referenced within the response.

11.11. The group TripChangeResponseGroup

TripChangeResponseGroup

Trip change response structure.

TripChangeResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

TripResult

0:1

+TripResult

The trip results refined by the server.

11.12. The group TripContentFilterGroup

TripContentFilterGroup

Parameters that control the level of detail of the trip results.

BaseTripContentFilter

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of each journey leg.

IncludeLegProjection

0:1

Whether the result should include the geographic projection (coordinates) of each journey leg.

IncludeTurnDescription

0:1

Whether the result should include turn-by-turn instructions for each journey leg.

IncludeAccessFeatures

0:1

Whether the result should include the access features (stairs, elevator, etc.) on each path link.

IncludeAccessFeaturesStatus

0:1

Whether the result should include real time status of access features to indicate broken equipment.

IncludeAccessibilityDetails

0:*

AccessibilityDetailsProfileEnumeration

Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.

TripContentFilter

IncludeIntermediateStops

0:1

Whether the result should include intermediate stops (between the passenger's board and alight stops).

IncludeFare

0:1

Whether the result should include fare information.

IncludeOperatingDays

0:1

Whether the result should include operating day information - as encoded bit string and in natural language.

TripSummaryOnly

0:1

If true, then the response will contain only summaries of the found trips. Default is false.

11.13. The group TripDataFilterGroup

TripDataFilterGroup

Data to be included/excluded from search, e.g., modes, operators (Transmodel: TRIP REQUEST FILTER).

TripDataFilter

ModeAndModeOfOperationFilter

0:*

+ModeAndModeOfOperationFilter

MODEs and MODEs OF OPERATION to be considered in trip calculation. If only MODE is used, then it is for all MODE OF OPERATION. If combinations of MODE and MODE OF OPERATION are used (multiples), then all combinations are to be considered.

LineFilter

0:1

+LineDirectionFilter

Lines/Directions to include/exclude.

OperatorFilter

0:1

+OperatorFilter

Transport operators to include/exclude.

VehicleFilter

0:1

+VehicleFilter

Filter for VEHICLE and TRAIN NUMBERs.

TariffzoneFilter

0:1

+TariffzoneFilter

Filter for trips using only specific tariff zones.

11.14. The group TripMobilityFilterGroup

TripMobilityFilterGroup

Parameters the user can set to restrict the mobility options - particularly for interchanging.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

11.15. The group TripPolicyGroup

TripPolicyGroup

Policies that control the trip search behaviour.

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

The element contains one of the following elements (a) or element sequences (b)

TripPolicy

a

MotorisedMainTravelMode

-0:1

The MotorisedMainTravelMode defines whether the trip planner works in PT mode (or pure IT mode) or includes carTransportRail and the like. If set to true (e.g., because one travels by car, truck or motorcycle), then carTransportRail, ferry are used together with roads.

b

ItModeToCover

-0:*

+ItModes

For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.

b

IncludeAlternativeOptions

-0:1

Whether alternative options should be presented as well. Mainly important for dominated journeys or in the case of ContinuousLegs the second-best route. Should be optimised for user expectations (see. e.g https://theses.hal.science/tel-01848737). However, what the alternative options are may vary widely depending on the optimisation methods and filters.

11.16. The group TripRefineRequestGroup

TripRefineRequestGroup

Trip refinement request structure.

TripRefineRequest

RefineParams

0:1

+TripRefineParam

Options to control the refine

TripResult

1:1

+TripResult

The trip result to be refined by the server.

TripResponseContext

0:1

+ResponseContext

Context to hold objects, which are referenced within the response.

11.17. The group TripRefineResponseGroup

TripRefineResponseGroup

Trip refinement response structure.

TripRefineResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

UnknownLegRef

0:*

LegObjectIdType

Refers to a leg that was not found in the data of the server. If the to be refined TripResult could not be found or unequivocally determined, all RefineLegRefs are returned as UnknownLegRefs.

TripResult

0:*

+TripResult

The trip results refined by the server.

11.18. The group TripRequestGroup

TripRequestGroup

Trip request structure.

TripRequest

Origin

1:*

+PlaceContext

Specifies the origin situation from where the user wants to start.

Destination

1:*

+PlaceContext

Specifies the destination situation where the user is heading to.

Via

0:*

+TripVia

Ordered series of points where the journey must pass through. If more than one via point is given all of them must be obeyed - in the correct order. The server is allowed to replace a via stop by equivalent stops. Note: Systems may support only one.

ViaSystem

0:*

>siri:ParticipantRef

With this parameter a distributing system is asked to build a trip using a given System to pass through. This helps in selecting Exchange Points for this trip. ViaSystem is also used in sequence. Note: Systems may support only one.

NotVia

0:*

+NotVia

Not-via restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs that the TRIP is not allowed to pass through. If more than one not via point is given all of them must be obeyed.

NoChangeAt

0:*

+NoChangeAt

no-change-at restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs at which no TRANSFER is allowed within a TRIP.

Params

0:1

+TripParam

Options to control the search behaviour and response contents.

11.19. The group TripResponseGroup

TripResponseGroup

Trip response structure.

TripResponse

TripResponseContext

0:1

+ResponseContext

Context to hold trip response objects that occur frequently.

TripResult

0:*

+TripResult

The trip results found by the server.

11.20. The group TripStatusGroup

TripStatusGroup

Parameters which describe the status of a TRIP (will be added to MONITORED TRIP in Transmodel).

TripStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

Delayed

0:1

Whether this trip is delayed. Default is false.

Infeasible

0:1

Whether this trip cannot be used, due to operational delays and impossible transfers. Default is false.

11.21. The complex type ContinuousLegStructure

ContinuousLegStructure

[relates to a specific type of RIDE LEG with Timed=false or an ACCESS LEG in TM and NeTEx] leg of a journey that is not bound to a timetable.

LegStart

1:1

+PlaceRef

PLACE where the leg starts (can be a PLACE, SCHEDULED STOP POINT or a VEHICLE MEETING POINT) with time information.

LegEnd

1:1

+PlaceRef

PLACE to alight (can be a SCHEDULED STOP POINT or a VEHICLE MEETING POINT) with time information.

Service

1:1

+ContinuousService

Service of this leg.

TimeWindow

TimeWindowStart

0:1

Time at which window begins.

TimeWindowEnd

0:1

Time at which window ends.

Duration

1:1

Duration of this leg according to user preferences like walking speed.

LegDescription

0:1

+InternationalText

Title or summary of this leg for overview.

Length

0:1

LengthType

Length of the leg.

LegTrack

0:1

+LegTrack

Detailed description of each element of this leg including geometric projection.

PathGuidance

0:1

+PathGuidance

Structured model further describing this interchange, its geographic embedding and accessibility (LEG.PATH GUIDANCE).

Feasibility

0:*

FeasibilityEnumeration

Information about the feasibility of the ContinuousLeg, in particular with respect to the access features used.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Sustainability

EmissionCO2

0:1

+EmissionCO2

Estimation of CO2 emissions.

Extension

0:1

11.22. The complex type FollowStructure

FollowStructure

-

The element contains one of the following elements (a-d)

a

FollowSignName

-1:1

+InternationalText

Follow a sign.

b

FollowRoadName

-1:1

+InternationalText

Follow a road/route.

c

FollowDirectionName

-1:1

+InternationalText

Follow a direction.

d

FollowExit

-1:1

+InternationalText

Follow an exit.

11.23. The complex type LegAlightStructure

LegAlightStructure

Describes the situation at a stop or station at which the passenger alights from a Leg of a trip including time-related information

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

ServiceArrival

1:1

+ServiceArrival

describes the arrival situation at the leg alight stop point (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME)

ServiceDeparture

0:1

+ServiceDeparture

describes the departure situation at this leg alight stop point (empty for last leg) (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME)

FeederInterchangeId

0:1

Interchange identifier of the feeding line/service at its alighting. This is not a reference. This identifier is used to recognize in a distributed environment (e.g., EU-Spirit), that two systems refer to the same line (or service) while using their own internal references. In EU-Spirit this is used to decide whether an interchange is in fact a stay-seated scenario (aka "line id"). See https://eu-spirit.eu/

MeetsViaRequest

0:1

This stop fulfils one of the via requirements stated in the request data.

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

11.24. The complex type LegBoardStructure

LegBoardStructure

Describes the situation at a stop or station at which the passenger boards a Leg of a trip including time-related information.

The element contains one of the following elements (b) or element sequences (a)

StopPoint

a

→‍siri:StopPointRef

-1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

a

StopPointName

-1:1

+InternationalText

Name or description of stop point for use in passenger information.

a

NameSuffix

-0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

a

PlannedQuay

-0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

a

EstimatedQuay

-0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

b

GeoPosition

-1:1

+siri:Location

ServiceArrival

0:1

+ServiceArrival

Contains ARRIVAL times (timetable, recorded, estimated, timing bands estimated) and the ARRIVAL formation.

ServiceDeparture

1:1

+ServiceDeparture

Contains DEPARTURE times (timetable, recorded, estimated, timing bands estimated) and the DEPARTURE formation.

DistributorInterchangeId

0:1

Interchange identifier of the distributing line/service at its boarding. This is not a reference. This identifier is used to recognize in a distributed environment (e.g., EU-Spirit), that two systems refer to the same line (or service) while using their own internal references. In EU-Spirit this is used to decide whether an interchange is in fact a stay-seated scenario (aka "line ID"). See https://eu-spirit.eu/

MeetsViaRequest

0:1

This stop fulfils one of the via requirements stated in the request data.

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

11.25. The complex type LegIntermediateStructure

LegIntermediateStructure

Describes the situation at a stop or station that lies between the LegBoard and LegAlight stop or station including time-related information.

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

ServiceArrival

1:1

+ServiceArrival

describes the arrival situation at this leg board stop point (empty for first leg) (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME)

ServiceDeparture

1:1

+ServiceDeparture

describes the departure situation at this leg board stop point (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME)

MeetsViaRequest

0:1

This stop fulfils one of the via requirements stated in the request data.

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

11.26. The complex type LegStructure

LegStructure

A single stage of a TRIP that is made without change of MODE or service (e.g., between each interchange). Implements LEG from TM 6.2.

Id

1:1

LegObjectIdType

Id of this leg. Unique within trip result.

ParticipantRef

0:1

>siri:ParticipantRef

[equivalent of PARTICIPANT in SIRI] IT system that is participating in a communication with other participant(s)

Duration

0:1

The duration of the LEG (e.g., from Transmodel PT RIDE LEG.Duration).

The element contains one of the following elements (a-c)

a

TimedLeg

-1:1

+TimedLeg

Corresponds to a RIDE or PT RIDE LEG in TM 6.2 with the attribute Timed (with related information). Passenger LEG with timetabled schedule.

b

TransferLeg

-1:1

+TransferLeg

TRANSFER LEG or CONNECTION LEG according to TM 6.2. Description of a LEG which links other LEGs where a TRANSFER or CONNECTION between different LOCATIONs is required.

c

ContinuousLeg

-1:1

+ContinuousLeg

A specialised type of RIDE LEG in with Timed=false, a PERSONAL LEG or an ACCESS LEG TM 6 and NeTEx. LEG of a TRIP that is not bound to a timetable.

Sustainability

EmissionCO2

0:1

+EmissionCO2

Estimation of CO2 emissions.

Changed

0:1

TRUE if leg got changed by TripChange-Request.

11.27. The complex type MultiPointTripParamStructure

MultiPointTripParamStructure

Multi-point trip request parameter structure.

TripDataFilter

ModeAndModeOfOperationFilter

0:*

+ModeAndModeOfOperationFilter

MODEs and MODEs OF OPERATION to be considered in trip calculation. If only MODE is used, then it is for all MODE OF OPERATION. If combinations of MODE and MODE OF OPERATION are used (multiples), then all combinations are to be considered.

LineFilter

0:1

+LineDirectionFilter

Lines/Directions to include/exclude.

OperatorFilter

0:1

+OperatorFilter

Transport operators to include/exclude.

VehicleFilter

0:1

+VehicleFilter

Filter for VEHICLE and TRAIN NUMBERs.

TariffzoneFilter

0:1

+TariffzoneFilter

Filter for trips using only specific tariff zones.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

MultiPointTripPolicy

MultiPointType

0:1

MultiPointTypeEnumeration

Defines how the router should handle requests with multiple origins and destinations. As it is important for the strategy of the distributed trip planning the MultiPointType should be set. If the type is not supported a TRIP_MULTIPOINT_TYPE_NOT_SUPPORTED warning or error must be returned. Default is anyPoint.

BaseTripContentFilter

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of each journey leg.

IncludeLegProjection

0:1

Whether the result should include the geographic projection (coordinates) of each journey leg.

IncludeTurnDescription

0:1

Whether the result should include turn-by-turn instructions for each journey leg.

IncludeAccessFeatures

0:1

Whether the result should include the access features (stairs, elevator, etc.) on each path link.

IncludeAccessFeaturesStatus

0:1

Whether the result should include real time status of access features to indicate broken equipment.

IncludeAccessibilityDetails

0:*

AccessibilityDetailsProfileEnumeration

Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.

TripContentFilter

IncludeIntermediateStops

0:1

Whether the result should include intermediate stops (between the passenger's board and alight stops).

IncludeFare

0:1

Whether the result should include fare information.

IncludeOperatingDays

0:1

Whether the result should include operating day information - as encoded bit string and in natural language.

TripSummaryOnly

0:1

If true, then the response will contain only summaries of the found trips. Default is false.

FareParam

0:1

+FareParam

Parameters for fare calculation. Only used if IncludeFare is set (TripContentFilterGroup).

Extension

0:1

11.28. The complex type MultiPointTripResultStructure

MultiPointTripResultStructure

Structure for a multipoint trip result and associated problems

Id

1:1

MultiPointTripResultObjectIdType

Id of this trip result for referencing purposes. Unique within multipoint-trip response.

ErrorCondition

0:*

+OJPError

Problems related to this trip result.

The element contains one of the following elements (a-b)

a

Trip

-1:1

+Trip

Information on the trip.

b

TripSummary

-1:1

+TripSummary

Summary on trip. Only if requestor set TripSummaryOnly in request.

MultiPointWaitTime

OriginWaitTime

0:1

Additional wait time at origin of this trip.

DestinationWaitTime

0:1

Additional wait time at destination of this trip.

TripFare

0:*

+TripFareResult

Fare and fare product information for this trip as a whole or parts of it.

11.29. The complex type NoChangeAtStructure

NoChangeAtStructure

No-change-at restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs at which no TRANSFER is allowed within a TRIP.

The element contains one of the following elements (a-b)

a

→‍siri:StopPointRef

-1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

b

→‍StopPlaceRef

-1:1

>StopPlaceRef

Reference to a Stop Place

11.30. The complex type NotViaStructure

NotViaStructure

Not-via restrictions for a TRIP, i.e. SCHEDULED STOP POINTs or STOP PLACEs that the TRIP is not allowed to pass through

The element contains one of the following elements (a-b)

a

→‍siri:StopPointRef

-1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

b

→‍StopPlaceRef

-1:1

>StopPlaceRef

Reference to a Stop Place

11.31. The complex type PathGuidanceSectionStructure

PathGuidanceSectionStructure

An extended definition of a NAVIGATION PATH in TMv6 and PATH GUIDANCE to include the textual navigation instructions. Description of a part of a TRIP. May include geographic information, turn instructions and accessibility information.

TrackSection

0:1

+TrackSection

An aggregate of information that may be leaning on LEG TRACK together with duration and length that can be used for representing the leg on a map. The points may be STOP PLACE, SCHEDULED STOP POINT, coordinates, or ADDRESSes.

TurnDescription

0:1

+InternationalText

Textual description of a traveller manoeuvre. Contains information from manoeuvre, TurnAction, and TrackSection.RoadName.

GuidanceAdvice

0:1

GuidanceAdviceEnumeration

Several types of guidance advice given to traveller (according to Transmodel a view of a LEG TRACK and PATH GUIDANCE).

TurnAction

0:1

TurnActionEnumeration

The range of possible turns that can be described (according to Transmodel a view of a LEG TRACK and PATH GUIDANCE).

RoadName

0:1

+InternationalText

Road name

Follow

0:*

+Follow

Signs, roads, POI to follow.

DirectionHint

0:1

+InternationalText

Textual direction hint for better understanding, e.g., "follow signs to Hamburg" (according to Transmodel a view of a LEG TRACK and PATH GUIDANCE).

AbsoluteBearing

0:1

siri:AbsoluteBearingType

Absolute bearing (sky direction) after the described manoeuvre.

PathLink

0:1

+PathLink

Description of the type of accessibility on this navigation section. This view is simplified in comparison to the NeTEx PathLink structure.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

11.32. The complex type PathGuidanceStructure

PathGuidanceStructure

Description of a piece of a TRIP. May include geographic information, turn instructions and accessibility information.

PathGuidanceSection

1:*

+PathGuidanceSection

A view of LEG TRACK including PATH JUNCTION information, PATH LINK information and PATH GUIDANCE. One or more path guidance sections that form the LEG. For a good PATH GUIDANCE, a fine granularity of the sections may be needed. This may also depend on the MODE and the type of guidance required.

11.33. The complex type PathLinkEndStructure

PathLinkEndStructure

Designations of a floor/level.

LevelPublicCode

0:1

Public identifier of the level as found on elevators and signs.

LevelName

0:1

+InternationalText

Official name of the level.

Id

0:1

PlaceObjectIdType

Id of the element at this end of the PathLink (typically a PLACE, e.g., where the elevator is located).

11.34. The complex type PathLinkStructure

PathLinkStructure

[TMv6] a link within a PLACE of or between two PLACEs (that is STOP PLACEs, ACCESS SPACEs or QUAYs, BOARDING POSITIONs, POINTs OF INTEREST etc. or PATH JUNCTIONs) that represents a step in a possible route for pedestrians, cyclists, or other out-of-vehicle passengers within or between a PLACE. Here we use a reduced form of a PATH LINK containing the description of the type of accessibility on this navigation section.

Transition

0:1

TransitionEnumeration

Whether path is up, down, or level.

AccessFeatureType

0:1

AccessFeatureTypeEnumeration

Type of physical feature of PATH LINK.

Count

0:1

Number indicating how often the access feature occurs in this PathLink

AccessFeatureStatus

0:1

AccessFeatureStatusEnumeration

Whether the access feature is available or out of service.

AccessFeatureStatusText

0:1

+InternationalText

Textual information about reduced availability of the access feature, in particular if AccessFeatureStatus is partiallyAvailable.

AccessibilityFeature

0:*

AccessibilityFeatureTypesEnumeration

Presence of an accessibility feature on the PathLink.

→‍SituationFullRef

0:*

+SituationFullRef

Reference to situation message. Message details might be found in response context or through other communication channels.

From

0:1

+PathLinkEnd

Designations of level and place where this PathLink starts.

To

0:1

+PathLinkEnd

Designations of level and place where this PathLink ends.

11.35. The complex type TariffzoneFilterStructure

TariffzoneFilterStructure

-

Exclude

0:1

Whether to include or exclude given tariff zones in the list from the search. Default is to include.

TariffZones

1:1

+TariffZoneListInArea

List of fare zones to include or exclude.

11.36. The complex type TimedLegStructure

TimedLegStructure

Corresponds to a RIDE or PT RIDE LEG in TM 6.2 with the attribute Timed (with related information). Passenger LEG with timetabled schedule.

LegBoard

1:1

+LegBoard

Stop/Station where boarding is done

LegIntermediate

0:*

+LegIntermediate

Information about the intermediate passed stop points.

LegAlight

1:1

+LegAlight

Stop/Station to alight

Service

1:1

+DatedJourney

Service that is used for this leg.

LegAttribute

0:*

+LegAttribute

Attributes that are not valid on the whole service, but only on parts of the journey leg.

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

LegTrack

0:1

+LegTrack

Geographic embedding of this leg.

ParallelService

0:*

+ParallelService

Services running combined with at least parts of this journey, e.g., wing trains. The contained stop sequence interval refers to the original journey.

Sustainability

EmissionCO2

0:1

+EmissionCO2

Estimation of CO2 emissions.

Extension

0:1

11.37. The complex type TransferLegStructure

TransferLegStructure

TRANSFER LEG or CONNECTION LEG according to TM 6.2. Description of a LEG which links other LEGs where a TRANSFER or CONNECTION between different LOCATIONs is required.

TransferType

1:*

TransferTypeEnumeration

TYPE that is used for this interchange between public services (TYPE OF TRANSFER, but also ACCESS MODE and PERSONAL MODE as far as a TRANSFER is concerned). In some constellations multiple TransferType are possible.

LegStart

1:1

+PlaceRef

Stop/Station/Place where boarding is done (can be a PLACE, SCHEDULED STOP POINT or a VEHICLE MEETING POINT)

LegEnd

1:1

+PlaceRef

Stop/Station/Place to alight (can be a PLACE, SCHEDULED STOP POINT or a VEHICLE MEETING POINT).

TimeWindow

TimeWindowStart

0:1

Time at which window begins.

TimeWindowEnd

0:1

Time at which window ends.

TransferDuration

Duration

1:1

Overall duration of this interchange (Transmodel: PT CONNECTION LEG.MEAN INTERCHANGE TIME).

WalkDuration

0:1

Walk time as part of the overall interchange duration (in Transmodel might be modelled as TRANSFER.CONNECTION.DefaultDuration).

BufferTime

0:1

Buffer time as part of the overall interchange duration. Buffer times, e.g., check in/out times, sometimes are mandatory for using certain services as e.g., airplanes, ferries or highspeed trains.

Interchange

InterchangeRef

0:1

>siri:InterchangeRef

Reference of an INTERCHANGE.

ExtraInterchange

0:1

Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1)

InterchangeCancellation

0:1

Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1)

siri:InterchangeProperty

siri:StaySeated

0:1

Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection.

siri:Guaranteed

0:1

Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed.

siri:Advertised

0:1

Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'.

LegDescription

0:1

+InternationalText

Text that describes this interchange.

Length

0:1

LengthType

Length of this interchange path.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

PathGuidance

0:1

+PathGuidance

Structured model further describing this interchange, its geographic embedding and accessibility (LEG.PATH GUIDANCE).

Feasibility

0:*

FeasibilityEnumeration

Information about the feasibility of the TransferLeg, in particular with respect to the access features used.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Extension

0:1

11.38. The complex type TripChangeParamStructure

TripChangeParamStructure

Trip change request parameter structure.

ChangeLegRef

1:1

LegObjectIdType

Refers to the leg to be adapted by the server. Typical usage: either a transfer leg representing an interchange that is considered too short or a sharing leg for which the exact times shall be retrieved for a specific operator.

SystemId

0:1

System reference to use for the refinement. If not specified, the origin systems of each leg are used for the refinement.

ExtendToFrontOrBack

0:1

ExtendToFrontOrBackType

Whether to extend the initial time interval of the ChangeLeg towards the front or the back of the trip (earlier respectively later times).

AdditionalWaitingTime

0:1

Absolute time in minutes the passenger wants additionally to make the interchange. If another TransferLeg is needed (e.g., since another quay is used for the found arrival/departure) this is taken into account. If not passed, the next best arrival/departure is requested.

TripParams

0:1

+TripParam

Options to control the search behaviour and response contents. They should be largely the same as used as in the initial OJPTripRequest.

Extension

0:1

11.39. The complex type TripParamStructure

TripParamStructure

Trip request parameter structure.

TripDataFilter

ModeAndModeOfOperationFilter

0:*

+ModeAndModeOfOperationFilter

MODEs and MODEs OF OPERATION to be considered in trip calculation. If only MODE is used, then it is for all MODE OF OPERATION. If combinations of MODE and MODE OF OPERATION are used (multiples), then all combinations are to be considered.

LineFilter

0:1

+LineDirectionFilter

Lines/Directions to include/exclude.

OperatorFilter

0:1

+OperatorFilter

Transport operators to include/exclude.

VehicleFilter

0:1

+VehicleFilter

Filter for VEHICLE and TRAIN NUMBERs.

TariffzoneFilter

0:1

+TariffzoneFilter

Filter for trips using only specific tariff zones.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

The element contains one of the following elements (a) or element sequences (b)

TripPolicy

a

MotorisedMainTravelMode

-0:1

The MotorisedMainTravelMode defines whether the trip planner works in PT mode (or pure IT mode) or includes carTransportRail and the like. If set to true (e.g., because one travels by car, truck or motorcycle), then carTransportRail, ferry are used together with roads.

b

ItModeToCover

-0:*

+ItModes

For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.

b

IncludeAlternativeOptions

-0:1

Whether alternative options should be presented as well. Mainly important for dominated journeys or in the case of ContinuousLegs the second-best route. Should be optimised for user expectations (see. e.g https://theses.hal.science/tel-01848737). However, what the alternative options are may vary widely depending on the optimisation methods and filters.

BaseTripContentFilter

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of each journey leg.

IncludeLegProjection

0:1

Whether the result should include the geographic projection (coordinates) of each journey leg.

IncludeTurnDescription

0:1

Whether the result should include turn-by-turn instructions for each journey leg.

IncludeAccessFeatures

0:1

Whether the result should include the access features (stairs, elevator, etc.) on each path link.

IncludeAccessFeaturesStatus

0:1

Whether the result should include real time status of access features to indicate broken equipment.

IncludeAccessibilityDetails

0:*

AccessibilityDetailsProfileEnumeration

Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.

TripContentFilter

IncludeIntermediateStops

0:1

Whether the result should include intermediate stops (between the passenger's board and alight stops).

IncludeFare

0:1

Whether the result should include fare information.

IncludeOperatingDays

0:1

Whether the result should include operating day information - as encoded bit string and in natural language.

TripSummaryOnly

0:1

If true, then the response will contain only summaries of the found trips. Default is false.

FareParam

0:1

+FareParam

Parameters for fare calculation. Only used if IncludeFare is set (TripContentFilterGroup).

Extension

0:1

11.40. The complex type TripRefineParamStructure

TripRefineParamStructure

Trip refinement request parameter structure.

ForeignObjectRefs

0:1

If true, then the request may contain object references from another system. Default is FALSE.

RefineLegRef

0:*

LegObjectIdType

Refers to the legs to be refined by the server. If none is specified, all legs are open for refinement (depending on whether the system in question can refine them).

SystemId

0:1

System reference to use for the refinement. If not specified, the origin systems of each leg are used for the refinement.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

The element contains one of the following elements (a) or element sequences (b)

TripPolicy

a

MotorisedMainTravelMode

-0:1

The MotorisedMainTravelMode defines whether the trip planner works in PT mode (or pure IT mode) or includes carTransportRail and the like. If set to true (e.g., because one travels by car, truck or motorcycle), then carTransportRail, ferry are used together with roads.

b

ItModeToCover

-0:*

+ItModes

For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.

b

IncludeAlternativeOptions

-0:1

Whether alternative options should be presented as well. Mainly important for dominated journeys or in the case of ContinuousLegs the second-best route. Should be optimised for user expectations (see. e.g https://theses.hal.science/tel-01848737). However, what the alternative options are may vary widely depending on the optimisation methods and filters.

BaseTripContentFilter

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of each journey leg.

IncludeLegProjection

0:1

Whether the result should include the geographic projection (coordinates) of each journey leg.

IncludeTurnDescription

0:1

Whether the result should include turn-by-turn instructions for each journey leg.

IncludeAccessFeatures

0:1

Whether the result should include the access features (stairs, elevator, etc.) on each path link.

IncludeAccessFeaturesStatus

0:1

Whether the result should include real time status of access features to indicate broken equipment.

IncludeAccessibilityDetails

0:*

AccessibilityDetailsProfileEnumeration

Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.

TripContentFilter

IncludeIntermediateStops

0:1

Whether the result should include intermediate stops (between the passenger's board and alight stops).

IncludeFare

0:1

Whether the result should include fare information.

IncludeOperatingDays

0:1

Whether the result should include operating day information - as encoded bit string and in natural language.

TripSummaryOnly

0:1

If true, then the response will contain only summaries of the found trips. Default is false.

FareParam

0:1

+FareParam

Parameters for fare calculation. Only used if IncludeFare is set (TripContentFilterGroup).

Extension

0:1

11.41. The complex type TripResultStructure

TripResultStructure

Structure for a single trip result and associated problems.

Id

1:1

TripResultObjectIdType

Id of this trip result for referencing purposes. Unique within trip response.

ErrorCondition

0:*

+OJPError

Problems related to this Trip result.

The element contains one of the following elements (a-b)

a

Trip

-1:1

+Trip

Detailed information on trip.

b

TripSummary

-1:1

+TripSummary

Summary on trip. Only if requestor set TripSummaryOnly in request.

TripFare

0:*

+TripFareResult

Fare and fare product information for this trip as a whole or parts of it.

IsAlternativeOption

0:1

When the result is an alternative option from IncludeAlternativeOptions, then the flag should be set to true. If it is an alternative option this means that the server decided to add this result for its own reasons: e.g., to push a certain trip leg, because it believes that it might better suit at least some possible customers. Such options are not an optimal fit to the criteria that were in the request. The client may therefore disregard such results depending on the use case.

11.42. The complex type TripStructure

TripStructure

[an extended form of PT TRIP in TM and NeTEx as it also includes the initial and final access legs to and from public transport] whole journey from passenger origin to passenger destination in one or more LEGs

Id

1:1

TripObjectIdType

Id of this trip for referencing purposes. Unique within trip response.

Duration

1:1

Overall duration of the trip (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

StartTime

1:1

Departure time at origin (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

EndTime

1:1

Arrival time at destination (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

Transfers

1:1

Number of interchanges.

Distance

0:1

siri:DistanceType

Trip distance (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

Leg

1:*

+Leg

Legs of the trip (Transmodel: LEG or MONITORED LEG). Note: There is always a TransferLeg between two TimedLegs. There can be a TransferLeg between two ContinuousLegs (e.g., because some special time-consuming action is necessary like a car hire). There can be a TransferLeg between a ContinuousLeg and a TimedLeg for the same reason. There aren't two consecutive TransferLegs.

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

TripStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

Delayed

0:1

Whether this trip is delayed. Default is false.

Infeasible

0:1

Whether this trip cannot be used, due to operational delays and impossible transfers. Default is false.

Feasibility

0:*

FeasibilityEnumeration

Information about the feasibility of the TRIP, in particular with respect to the access features used.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Extension

0:1

11.43. The complex type TripSummaryStructure

TripSummaryStructure

Structure for trip overview information (only implementation related and therefore not modelled in Transmodel).

TripId

1:1

TripObjectIdType

Id of this trip for referencing purposes. Unique within trip response.

Origin

0:1

+PlaceRef

Describes the origin situation of this trip.

Destination

0:1

+PlaceRef

Describes the arrival situation of this trip.

Duration

0:1

Overall duration of the trip (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

StartTime

0:1

Departure time at origin (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

EndTime

0:1

Arrival time at destination (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

PTLegs

0:1

Number of public transport legs.

Distance

0:1

siri:DistanceType

Trip distance (TRIP attribute, not detailed in Transmodel, available from constituting LEGs).

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

Feasibility

0:*

FeasibilityEnumeration

Information about the feasibility of the TRIP, in particular with respect to the access features used.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Extension

0:1

12. OJP/OJP_JourneySupport.xsd - Supporting definitions for journeys on public transport vehicles

12.1. Simple type definitions

AccessibilityDetailsProfileEnumeration

Allowed values for AccessibilityDetails.

visualImpairment

-

auditoryImpairment

-

mobilityImpairment

-

bicycle

-

general

-

ReservationNeededEnumeration

Possible types of reservation needed for services.

none

-

service

A reservation/booking is required for the service to operate. BookingArrangement should then be used and contain more details.

stop

A reservation/booking is required for the service to call at the stop for boarding and alighting. BookingArrangement should then be used and contain more details.

UseRealtimeDataEnumeration

-

full

Full use of real-time information, including removal of SERVICE JOURNEYS (TRIP REQUEST POLICY.UseRealTime is only a boolean in Transmodel).

explanatory

Cancelled and delayed SERVICE JOURNEYs are still returned, but an additional explanatory textual information is provided to describe their current real-time status.

none

Only based on timetable data

VehicleProgressEnumeration

Vehicle progress relative to timetable service pattern.

Not yet operated

-

Operation finished

-

At stop

-

Between stops

-

12.2. The group BaseTripContentFilterGroup

BaseTripContentFilterGroup

Parameters to control the level of detail of both public and individual transport journey results.

BaseTripContentFilter

IncludeTrackSections

0:1

Whether the result should include TrackSection elements to describe the geographic route of each journey leg.

IncludeLegProjection

0:1

Whether the result should include the geographic projection (coordinates) of each journey leg.

IncludeTurnDescription

0:1

Whether the result should include turn-by-turn instructions for each journey leg.

IncludeAccessFeatures

0:1

Whether the result should include the access features (stairs, elevator, etc.) on each path link.

IncludeAccessFeaturesStatus

0:1

Whether the result should include real time status of access features to indicate broken equipment.

IncludeAccessibilityDetails

0:*

AccessibilityDetailsProfileEnumeration

Which accessibility features and other accessibility-related information to retrieve (e.g., guidance text for the visually impaired).

IncludePlacesContext

0:1

Whether the place context is needed. If a requestor has that information already, the response can be made slimmer, when set to false. Default is true.

IncludeSituationsContext

0:1

Whether the situation context is needed. If a requestor has that information by other means or can't process it, the response can be made slimmer, when set to false. Default is true.

12.3. The group BaseTripMobilityFilterGroup

BaseTripMobilityFilterGroup

Base mobility options to be applied for both public and individual transport.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

12.4. The group BaseTripPolicyGroup

BaseTripPolicyGroup

Policies that control the trip search behaviour for both public and individual transport.

The element contains none or one of the following elements (a) or element sequences (b)

BaseTripPolicy

a

NumberOfResults

-0:1

The number of trip results that the user wants to see at least. Be aware that some implementations will deliver one of the TripResults before the indicated departure time. This means that you can't assume that you get the exact number of results that you asked for in the request from the server.

NumberOfResults

b

NumberOfResultsBefore

-0:1

The desired number of trip results before the given time (at origin or destination).

b

NumberOfResultsAfter

-0:1

The desired number of trip results after the given time (at origin or destination).

BaseTripPolicy

TimeWindow

0:1

Time window in which the trips should be, starting from the time specified in PlaceContext. Implements TRIP REQUEST.FlexibilityWindow. All trips within the window should be provided by the implementation.

UseRealtimeData

0:1

UseRealtimeDataEnumeration

The way real-time data should be used in the calculation of the trip.

ImmediateTripStart

0:1

Whether the trip calculation should find a solution that starts immediately (e.g., because the user is already on the way) instead of finding the latest possible start opportunity. Default is FALSE.

TransferLimit

0:1

The maximum number of interchanges the user will accept per trip.

OptimisationMethod

0:1

OptimisationMethodEnumeration

The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).

ConsiderElevationData

0:1

Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.

IncludeAllRestrictedLines

0:1

There might exist lines that have special restrictions and are not generally available to the public. E.g. school buses, company shuttles. dragLifts need to have an ACCESS MODE ski. Lines with ACCESS MODE bicycle will be included as well. If this flag is set, then existing restricted lines are considered by the router, irrespective of the selected passenger categories or the MotorisedMainTravelMode. The results are marked as restricted in the ServiceGroup. The usage could also be detailed with Attribute elements. Restricted trumps PassengerCategory, for example. If Restricted is set to true, all services are displayed.

PassengerCategory

0:*

PassengerCategoryEnumeration

Sequence of all passenger categories, for which this search shall be conducted. In rare cases additional offerings may be available (e.g., demand responsive service with certain areas being reserved for seniors). If multiple PassengerCategories are provided, then Services are shown when they are available for at least one PassengerCategory.

12.5. The group DatedJourneyGroup

DatedJourneyGroup

Vehicle journey that runs at a specific date.

DatedJourney

ConventionalModeOfOperation

0:1

ConventionalModesOfOperationEnumeration

MODE OF OPERATION for scheduled and flexible services (NeTEx).

→‍OperatingDayRef

1:1

>OperatingDayRef

Reference to an Operating Day

Service

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

PublicCode

0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

siri:LineRef

1:1

>siri:LineRef

Line Reference.

siri:DirectionRef

0:1

>siri:DirectionRef

Direction Reference.

Service

Mode

1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

ProductCategory

0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

PublishedServiceName

1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

TrainNumber

0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

→‍siri:VehicleRef

0:1

>siri:VehicleRef

Reference to a VEHICLE.

OperatorRefs

0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

RouteDescription

0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

Via

0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

siri:OperatorRef

0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

siri:ProductCategoryRef

0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

→‍siri:ServiceFeatureRef

0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

siri:VehicleFeatureRef

0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

JourneyRelations

0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

12.6. The group EstimatedTimeBandGroup

EstimatedTimeBandGroup

Range for estimated time.

EstimatedTimeBand

EstimatedTimeLow

0:1

Estimated lower limit for time.

EstimatedTimeHigh

0:1

Estimated upper limit for time.

12.7. The group NumberOfResultsGroup

NumberOfResultsGroup

parameter to control the number of TRIP results before/after a point in time. May NOT be used when departure time at origin AND arrival time at destination are set

NumberOfResults

NumberOfResultsBefore

0:1

The desired number of trip results before the given time (at origin or destination).

NumberOfResultsAfter

0:1

The desired number of trip results after the given time (at origin or destination).

12.8. The group RouteDescriptionGroup

RouteDescriptionGroup

Descriptive text for a route, e.g., "Airport via City Centre".

RouteDescription

RouteDescriptionText

1:1

+InternationalText

12.9. The group ScheduledJourneyGroup

ScheduledJourneyGroup

Vehicle journey (not dated).

Service

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

PublicCode

0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

siri:LineRef

1:1

>siri:LineRef

Line Reference.

siri:DirectionRef

0:1

>siri:DirectionRef

Direction Reference.

Service

Mode

1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

ProductCategory

0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

PublishedServiceName

1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

TrainNumber

0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

→‍siri:VehicleRef

0:1

>siri:VehicleRef

Reference to a VEHICLE.

OperatorRefs

0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

RouteDescription

0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

Via

0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

siri:OperatorRef

0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

siri:ProductCategoryRef

0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

→‍siri:ServiceFeatureRef

0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

siri:VehicleFeatureRef

0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

JourneyRelations

0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

12.10. The group ServiceDestinationGroup

ServiceDestinationGroup

Last serviced stop of a vehicle journey (also VEHICLE MEETING POINT or ADDRESSABLE PLACE).

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

12.11. The group ServiceGroup

ServiceGroup

Properties of a service (line and direction): attributes of Continuous Journey Structure or Dated Journey Structure.

Service

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

PublicCode

0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

siri:LineRef

1:1

>siri:LineRef

Line Reference.

siri:DirectionRef

0:1

>siri:DirectionRef

Direction Reference.

Service

Mode

1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

ProductCategory

0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

PublishedServiceName

1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

TrainNumber

0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

→‍siri:VehicleRef

0:1

>siri:VehicleRef

Reference to a VEHICLE.

OperatorRefs

0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

RouteDescription

0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

Via

0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

siri:OperatorRef

0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

siri:ProductCategoryRef

0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

→‍siri:ServiceFeatureRef

0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

siri:VehicleFeatureRef

0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

JourneyRelations

0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

12.12. The group ServiceOriginGroup

ServiceOriginGroup

First serviced stop of a vehicle journey (also VEHICLE MEETING POINT or ADDRESSABLE PLACE).

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

12.13. The group ServiceStatusGroup

ServiceStatusGroup

parameters which describe the status of a DATED VEHICLE JOURNEY

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

12.14. The group ServiceTimeGroup

ServiceTimeGroup

Contains at least scheduled time, but can contain real time and estimated times

ServiceTime

TimetabledTime

1:1

time at point as it is published

RecordedAtTime

0:1

time as it was recorded

EstimatedTime

0:1

estimated time (for prognosis)

EstimatedTimeBand

EstimatedTimeLow

0:1

Estimated lower limit for time.

EstimatedTimeHigh

0:1

Estimated upper limit for time.

12.15. The group StopCallStatusGroup

StopCallStatusGroup

Status properties for the vehicle call at this stop.

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

12.16. The group StopSequenceIntervalGroup

StopSequenceIntervalGroup

Interval of stop sequence numbers of a given TimedLeg which may be one or multiple VEHICLE JOURNEYs. The numbering starts with 1. An example is the train from Bern to Zweisimmen that is split in Spiez. The sequence 1-3 is the first sequence, 3-9 the second.

StopSequenceInterval

FromStopSequenceNumber

0:1

Stop sequence number, where the interval begins (inclusive). If missing, the interval begins at the beginning of the leg (or at the beginning of the journey for uses in StopEvents and TripInfo).

ToStopSequenceNumber

0:1

Stop sequence number, where the interval ends (inclusive). If missing, the interval ends at the end of the leg (or at the end of the journey for uses in StopEvents and TripInfo).

12.17. The group TimeWindowGroup

TimeWindowGroup

The window of opportunity that the traveller has to perform this leg of the journey (e.g., a bridge is only open during a given interval).

TimeWindow

TimeWindowStart

0:1

Time at which window begins.

TimeWindowEnd

0:1

Time at which window ends.

12.18. The complex type CallAtStopStructure

CallAtStopStructure

[same as CALL in SIRI] the meeting of a VEHICLE JOURNEY with a specific SCHEDULED STOP POINT

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

ServiceArrival

0:1

+ServiceArrival

Arrival times of the service at this stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME).

ServiceDeparture

0:1

+ServiceDeparture

Departure times of the service at this stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME).

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

12.19. The complex type ContinuousServiceStructure

ContinuousServiceStructure

[a special form of SERVICE JOURNEY in TMv6] a vehicle movement on a continuous, non-timetabled service.

The element contains one of the following elements (a-b)

a

AlternativeModeOfOperation

-1:1

AlternativeModesOfOperationEnumeration

Alternative transport options.

b

PersonalModeOfOperation

-0:1

PersonalModesOfOperationEnumeration

Personal transport options.

The element contains one of the following element sequences (a-b)

DatedJourney

a

ConventionalModeOfOperation

-0:1

ConventionalModesOfOperationEnumeration

MODE OF OPERATION for scheduled and flexible services (NeTEx).

a

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

Service

a

→‍JourneyRef

-1:1

>JourneyRef

Reference to a Journey

a

PublicCode

-0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

a

siri:LineRef

-1:1

>siri:LineRef

Line Reference.

a

siri:DirectionRef

-0:1

>siri:DirectionRef

Direction Reference.

Service

a

Mode

-1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

a

ProductCategory

-0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

a

PublishedServiceName

-1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

a

TrainNumber

-0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

a

→‍siri:VehicleRef

-0:1

>siri:VehicleRef

Reference to a VEHICLE.

a

OperatorRefs

-0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

a

RouteDescription

-0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

a

Via

-0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

a

Restricted

-0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

a

RestrictionNote

-0:1

+InternationalText

Information about the restriction.

a

Attribute

-0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

a

OriginStopPointRef

-0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

a

OriginText

-1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

a

siri:OperatorRef

-0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

a

siri:ProductCategoryRef

-0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

a

→‍siri:ServiceFeatureRef

-0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

a

siri:VehicleFeatureRef

-0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

a

DestinationStopPointRef

-0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

a

DestinationText

-0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

a

Unplanned

-0:1

Whether this trip is an additional one that has not been planned. Default is false.

a

Cancelled

-0:1

Whether this trip is cancelled and will not be run. Default is false.

a

Deviation

-0:1

Whether this trip deviates from the planned service pattern. Default is false.

a

UndefinedDelay

-0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

a

Occupancy

-0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

a

JourneyRelations

-0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

b

PersonalMode

-1:1

PersonalModesEnumeration

PERSONAL MODE used either for PERSONAL MODE OF OPERATION or in ALTERNATIVE MODE OF OPERATION.

b

AlternativeService

-0:1

+AlternativeService

Shared mobility offer.

BookingArrangements

0:1

+BookingArrangementsContainer

Container with information on booking possibilities for this service.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Extension

0:1

12.20. The complex type DatedJourneyStructure

DatedJourneyStructure

[equivalent to DATED VEHICLE JOURNEY in TMv6] passenger carrying VEHICLE JOURNEY for one specified DAY TYPE for which the pattern of working is in principle defined by a SERVICE JOURNEY PATTERN. DatedJourney details of a service include its operating days.

The element contains one of the following element sequences (a)

DatedJourney

a

ConventionalModeOfOperation

-0:1

ConventionalModesOfOperationEnumeration

MODE OF OPERATION for scheduled and flexible services (NeTEx).

a

→‍OperatingDayRef

-1:1

>OperatingDayRef

Reference to an Operating Day

Service

a

→‍JourneyRef

-1:1

>JourneyRef

Reference to a Journey

a

PublicCode

-0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

a

siri:LineRef

-1:1

>siri:LineRef

Line Reference.

a

siri:DirectionRef

-0:1

>siri:DirectionRef

Direction Reference.

Service

a

Mode

-1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

a

ProductCategory

-0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

a

PublishedServiceName

-1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

a

TrainNumber

-0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

a

→‍siri:VehicleRef

-0:1

>siri:VehicleRef

Reference to a VEHICLE.

a

OperatorRefs

-0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

a

RouteDescription

-0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

a

Via

-0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

a

Restricted

-0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

a

RestrictionNote

-0:1

+InternationalText

Information about the restriction.

a

Attribute

-0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

a

OriginStopPointRef

-0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

a

OriginText

-1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

a

siri:OperatorRef

-0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

a

siri:ProductCategoryRef

-0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

a

→‍siri:ServiceFeatureRef

-0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

a

siri:VehicleFeatureRef

-0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

a

DestinationStopPointRef

-0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

a

DestinationText

-0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

a

Unplanned

-0:1

Whether this trip is an additional one that has not been planned. Default is false.

a

Cancelled

-0:1

Whether this trip is cancelled and will not be run. Default is false.

a

Deviation

-0:1

Whether this trip deviates from the planned service pattern. Default is false.

a

UndefinedDelay

-0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

a

Occupancy

-0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

a

JourneyRelations

-0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

siri:JourneyFormation

siri:TrainElements

0:1

+local-type: typedef-25.2

siri:Trains

0:1

+local-type: typedef-25.3

siri:CompoundTrains

0:1

+local-type: typedef-25.4

BookingArrangements

0:1

+BookingArrangementsContainer

Container with information on booking possibilities for this service.

ReservationNeeded

0:1

ReservationNeededEnumeration

Indicates whether this service needs some kind of reservation or booking to run.

SituationFullRefs

0:1

+SituationRefList

A list of references to SITUATIONs.

Extension

0:1

12.21. The complex type LegAttributeStructure

LegAttributeStructure

GeneralAttribute

Structured attribute classification with associated text. If URL is given, it refers to the whole attribute text.

The element content starts with items inherited from the base type:

UserText

1:1

+InternationalText

Text of the attribute to be shown to the user.

Code

1:1

Internal code of the attribute. Can be used for detection of double occurrences.

Key

0:1

Key if the attribute is used as a key/value pair.

Value

0:1

Value if the attribute is used as a key/value pair.

Facility

0:*

+siri:AllFacilitiesFeature

Facilities associated with this attribute.

Mandatory

0:1

Defines whether the attribute has to be shown to the user.

Importance

0:1

PercentType

Importance of the attribute.

WebLink

Url

1:1

URL to resource on web.

MimeType

0:1

MIME type of the referenced resource. To which kind of resource does the URL point to?

Embeddable

0:1

Is the referenced resource meant to be embedded as a webview in a surrounding context, e.g., app or web page? If yes, the resource has to be fully responsive. Default is false.

Inherited content is followed by own content:

FromStopSeqNumber

0:1

The attribute is valid from the stop point with this sequence number within the leg. If missing it is valid from the beginning of the leg.

ToStopSeqNumber

0:1

The attribute is valid to the stop point (inclusively) with this sequence number within the leg. If missing it is valid to the end of the leg.

12.22. The complex type LegTrackStructure

LegTrackStructure

The LINK PROJECTION of a Leg onto the topography of the route being followed.

TrackSection

1:*

+TrackSection

A geographical view of a Transmodel LEG TRACK together with duration and length that can be used for representing the leg on a map. The points may be STOP PLACE, SCHEDULED STOP POINT, coordinates, or ADDRESSes. Specialisation of SECTION.

12.23. The complex type ParallelServiceStructure

ParallelServiceStructure

Services running combined with at least parts of this journey, e.g., wing trains. The contained stop sequence interval refers to the original journey.

StopSequenceInterval

FromStopSequenceNumber

0:1

Stop sequence number, where the interval begins (inclusive). If missing, the interval begins at the beginning of the leg (or at the beginning of the journey for uses in StopEvents and TripInfo).

ToStopSequenceNumber

0:1

Stop sequence number, where the interval ends (inclusive). If missing, the interval ends at the end of the leg (or at the end of the journey for uses in StopEvents and TripInfo).

Service

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

PublicCode

0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

siri:LineRef

1:1

>siri:LineRef

Line Reference.

siri:DirectionRef

0:1

>siri:DirectionRef

Direction Reference.

Service

Mode

1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

ProductCategory

0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

PublishedServiceName

1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

TrainNumber

0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

→‍siri:VehicleRef

0:1

>siri:VehicleRef

Reference to a VEHICLE.

OperatorRefs

0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

RouteDescription

0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

Via

0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

siri:OperatorRef

0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

siri:ProductCategoryRef

0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

→‍siri:ServiceFeatureRef

0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

siri:VehicleFeatureRef

0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

JourneyRelations

0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

12.24. The complex type PlaceContextStructure

PlaceContextStructure

[a view of PLACE in TMv6] a PLACE and access to it by individual transport

The element contains one of the following elements (a-b)

a

PlaceRef

-1:1

+PlaceRef

Static place.

b

TripLocation

-1:1

+TripLocation

Location within a (moving) vehicle.

The element contains none or one of the following elements (a-b)

a

DepArrTime

-0:1

Time when departure/arrival from/to location is required.

b

TimeAllowance

-0:1

Extra time needed before reaching/after leaving this location (an example of a TRIP ACCESS CONSTRAINT. In Transmodel it is modelled more extensively and could relate to ACCESS MODE e.g., walk max. 5 minutes, but cycle 10 minutes).

IndividualTransportOption

0:*

+IndividualTransportOption

Options how to access/leave the place by individual transport.

12.25. The complex type ProductCategoryStructure

ProductCategoryStructure

Product category based on NeTEx/SIRI. A product category is a classification for VEHICLE JOURNEYs to express some common properties of journeys for marketing and fare products.

Name

0:1

+InternationalText

Full name of this product category, e.g., "Autoreisezug" in Switzerland or "Dampfschiff"

ShortName

0:1

+InternationalText

Short name or acronym of the product category, likely to be published, e.g., "BAV", "ARZ", "TGV". The product category is more important for publication in Switzerland than Mode / Submode.

→‍ProductCategoryRef

0:1

>siri:ProductCategoryRef

Reference to a product category. Product categories should be defined once and used uniformly in all channels (e.g., NeTEx, SIRI, OJP).

12.26. The complex type ServiceArrivalStructure

ServiceArrivalStructure

Arrival times of a service at a stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME, equals MONITORED LEG ARRIVAL).

ServiceTime

TimetabledTime

1:1

time at point as it is published

RecordedAtTime

0:1

time as it was recorded

EstimatedTime

0:1

estimated time (for prognosis)

EstimatedTimeBand

EstimatedTimeLow

0:1

Estimated lower limit for time.

EstimatedTimeHigh

0:1

Estimated upper limit for time.

→‍siri:ArrivalFormationAssignment

0:*

+siri:FormationAssignment

Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1)

12.27. The complex type ServiceDepartureStructure

ServiceDepartureStructure

Departure times of a service at a stop (group of attributes of TIMETABLED PASSING TIME, ESTIMATED PASSING TIME, OBSERVED PASSING TIME, equals MONITORED LEG DEPARTURE).

ServiceTime

TimetabledTime

1:1

time at point as it is published

RecordedAtTime

0:1

time as it was recorded

EstimatedTime

0:1

estimated time (for prognosis)

EstimatedTimeBand

EstimatedTimeLow

0:1

Estimated lower limit for time.

EstimatedTimeHigh

0:1

Estimated upper limit for time.

→‍siri:DepartureFormationAssignment

0:*

+siri:FormationAssignment

Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1)

12.28. The complex type ServiceViaPointStructure

ServiceViaPointStructure

[a specialisation of VIA in TMv6] STOP PLACE or SCHEDULED STOP POINT as a VIA for a particular SERVICE PATTERN. Specialisation of a VIA.

StopPoint

→‍siri:StopPointRef

1:1

>siri:StopPointRef

Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT.

StopPointName

1:1

+InternationalText

Name or description of stop point for use in passenger information.

NameSuffix

0:1

+InternationalText

Additional description of the stop point that may be appended to the name if enough space is available. E.g. "opposite main entrance".

PlannedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. According to planned timetable.

EstimatedQuay

0:1

+InternationalText

Name of the bay where to board/alight from the vehicle. As to the latest real-time status.

DisplayPriority

0:1

PriorityType

Priority of this via point to be displayed when space is limited.

12.29. The complex type TrackSectionStructure

TrackSectionStructure

SECTION of a LEG TRACK on the infrastructure network of the LEG together with time information.

TrackSectionStart

0:1

+PlaceRef

Start place of this track section (Start of a SECTION of a LEG.TRACK).

TrackSectionEnd

0:1

+PlaceRef

End place of this track section (End of a SECTION of a LEG.TRACK).

LinkProjection

0:1

+LinearShape

An oriented correspondence from one LINK of a source layer, onto an entity in a target layer: e.g., LINK SEQUENCE.

RoadName

0:1

Name of the road this track section is attached to (LEG TRACK.SECTION NAME, may also be something like "bicycle line along Tellstrasse").

Duration

0:1

Duration the passenger needs to travel through this track section.

Length

0:1

siri:DistanceType

Length of this track section.

Extension

0:1

12.30. The complex type TripLocationStructure

TripLocationStructure

A trip location represents the current logical position of a journey service. It can be used similarly to a place e.g., for starting a new trip request from within this service. A trip location does not(!) describe the relative position of a traveller within a vehicle, e.g., the seat.

→‍OperatingDayRef

1:1

>OperatingDayRef

Reference to an Operating Day

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

siri:LineIdentity

siri:LineRef

1:1

>siri:LineRef

Reference to a LINE.

siri:DirectionRef

1:1

>siri:DirectionRef

Reference to a LINE DIRECTION DIRECTION, typically outward or return.

12.31. The complex type TripViaStructure

TripViaStructure

VIA restrictions for a TRIP.

ViaPoint

1:1

+PlaceRef

Reference to specify the via place.

DwellTime

0:1

Duration the passenger wants to stay at the via place. Default is 0.

12.32. The complex type VehiclePositionStructure

VehiclePositionStructure

Geographical and logical position of a vehicle.

GeoPosition

0:1

+siri:Location

Geographic position of vehicle.

Progress

0:1

VehicleProgressEnumeration

Logical progress of vehicle relative to service pattern.

Bearing

0:1

siri:AbsoluteBearingType

Bearing in compass degrees in which vehicle is heading (expected to be consistent with Transmodel ROUTE or LEG TRACK and PATH GUIDANCE).

ProgressBetweenStops

0:1

+siri:ProgressBetweenStops

Provides information about the progress of the vehicle along its current link, that is link from previous visited top to current position.

12.33. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)

group[siri:JourneyFormationGroup]
  /TrainElements #complexType
  (typedef-25.2)

-

The element contains one or more of the following elements (a-b)

a

→‍siri:TrainElementRef

-1:1

>siri:TrainElementRef

Reference to a TRAIN ELEMENT. (since SIRI 2.1)

b

→‍siri:TrainElement

-1:1

+siri:TrainElement

An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1)

12.34. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)

group[siri:JourneyFormationGroup]
  /Trains #complexType
  (typedef-25.3)

-

The element contains one or more of the following elements (a-b)

a

siri:TrainRef

-1:1

b

→‍siri:Train

-1:1

+siri:Train

A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1)

12.35. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)

group[siri:JourneyFormationGroup]
  /CompoundTrains #complexType
  (typedef-25.4)

-

The element contains one or more of the following elements (a-b)

a

siri:CompoundTrainRef

-1:1

b

→‍siri:CompoundTrain

-1:1

+siri:CompoundTrain

Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation.

13. OJP/OJP_Availability.xsd - Request and response definitions for availability of tickets and services on a journey leg.

13.1. Simple type definitions

AvailabilityProblemTypeEnumeration

Types of problems that may be returned in responses to AVAILABILITY requests.

AVAILABILITY_NOSERVICEFOUND

No SERVICE (VEHICLE JOURNEY or VEHICLE) could be found for this request.

AVAILABILITY_LOCATIONUNSERVED

At the locations (address, stop, etc.) for which the availability has been requested, there is no public transport service at all. E.g. outside the area.

AVAILABILITY_LOCATIONUNKNOWN

The location (address, stop, etc.) for which availability was requested is unknown.

AVAILABILITY_OUTSIDERULES

The vehicle is not available due to existing rules like operating hours or not competing against an existing public transport line. In the details of the problem there should be information indicating which rules were violated: e.g., The desired MOBILITY SERVICE can't be provided because there exists a regular line for this TRIP.

AVAILABILITY_SERVICEDISRUPTED

The MOBILITY SERVICE is disrupted.

AVAILABILITY_UNAVAILABLE

There is no VEHICLE available at the current time.

AVAILABILITY_OTHER

A problem has occurred that does not have a specific problem type.

BookableServiceItemTypeEnumeration

Types of bookable service items.

wheelchair

Space for a wheelchair.

motorisedWheelchair

Space for a motorised wheelchair.

foldableWheelchair

Space for storing a foldable wheelchair.

walkingFrame

Place suitable for a person with a walking frame.

pram

Space for a pram or pushchair.

heavyLuggage

Space for storing heavy luggage.

childSeatTakenAlong

Seat suitable for attaching a child seat taken along by the passengers.

childSeatSupplied

Child seat provided in the vehicle.

babyCarrierTakenAlong

Seat suitable for attaching a baby carrier taken along by the passengers.

babyCarrierSupplied

Baby carrier provided in the vehicle.

seatBoosterSupplied

Seat booster provided in the vehicle.

bicycle

Space for a bicycle.

guideDog

Place suitable when accompanied by a guide dog.

dog

Place suitable when accompanied by a dog.

boardingAssistance

Assistance for boarding.

alightingAssistance

Assistance for alighting.

onboardAssistance

Assistance available on board, during the journey.

unassistedMinorAssistance

Assistance for a minor travelling alone.

group[ojp:TripMobilityFilterGroup]
  /HikingProfile #simpleType
  (typedef-90.1)

-

easy

Regular hiking/walking in valleys and plains and easy mountain trails e.g., yellow hiking signs in Switzerland or blue in Germany.

medium

Medium difficulty mountain trails. E.g. white-red-white hiking signs in Switzerland or red in Germany.

difficult

Difficult mountain trails. E.g. white-blue-white hiking signs in Switzerland or black in Germany.

group[ojp:TripMobilityFilterGroup]
  /CyclingProfile #simpleType
  (typedef-90.2)

-

fast

Fastest cycle route

green

Greenest cycle route

comfortable

Family friendly and leisurely route

13.2. The toplevel element AvailabilityProblemType

AvailabilityProblemType

+AvailabilityProblemTypeEnumeration (↔ ojp:ErrorType)

13.3. The group AvailabilityRequestGroup

AvailabilityRequestGroup

Availability request. Used to check the availability of a MOBILITY SERVICE, a VEHICLE, SERVICE JOURNEY or SINGLE JOURNEY. Be aware that usually after the response arrives, the rest of the TRIP must be recalculated. As especially pick-up and drop-off locations may have shifted from where they were in the previously calculated TRIP.

The element contains one of the following elements (a)

AvailabilityRequest

a

PublicTransport

-1:1

+BookingPTLeg

Definition of the journey leg to be covered by public transport. Other mobility services can be added later.

MobilityUser

1:*

+BookingUser

Passenger(s) for whom the service needs to be booked, one MobilityUser per passenger.

MinMaxTimeBand

EarliestDepartureTime

0:1

Earliest possible departure time from start location.

LatestArrivalTime

0:1

Latest possible arrival time at destination location.

AvailabilityRequest

Extension

0:1

13.4. The group AvailabilityResponseGroup

AvailabilityResponseGroup

Availability response.

AvailabilityResponse

AvailabilityResponseContext

0:1

+ResponseContext

Context to hold availability response objects that occur frequently.

AvailabilityResult

0:1

+AvailabilityResult

Indication of the availability of the requested service.

Extension

0:1

13.5. The group BookableTicketAndServiceInformationGroup

BookableTicketAndServiceInformationGroup

Lists those tickets or surcharges and service characteristics such as the transportation of wheelchairs, prams, luggage etc. or the provision of required child seats or booster seats that are offered in the trips transport company to be booked for the trip.

BookableTicketAndServiceInformation

BookableTicket

0:*

+FareProduct

Sequence of bookable tickets or surcharges for this part of the trip. If ticket price is zero: an already purchased/virtual ticket of this type presented to the driver would be accepted.

BookableServiceItem

0:*

+BookableServiceItem

Sequence of bookable service items for this part of the trip.

13.6. The group DriverAssistanceGroup

DriverAssistanceGroup

Requirements for the driver/staff to assist the passenger when boarding/alighting.

DriverAssistance

BoardingAssistance

0:1

Whether assistance is required for boarding. Could be offered by the driver or station staff. Default is FALSE.

AlightingAssistance

0:1

Whether assistance is required for alighting. Could be offered by the driver or station staff. Default is FALSE.

13.7. The group MinMaxTimeBandGroup

MinMaxTimeBandGroup

Earliest possible departure time from a start location and latest possible arrival at a different destination location.

MinMaxTimeBand

EarliestDepartureTime

0:1

Earliest possible departure time from start location.

LatestArrivalTime

0:1

Latest possible arrival time at destination location.

13.8. The group PassengerProfileGroup

PassengerProfileGroup

Profile of the passenger's abilities.

PassengerProfile

WheelchairUser

0:1

Passenger uses a wheelchair. Default is FALSE.

WalkingFrame

0:1

Passenger uses a walking frame. Default is FALSE.

WalkingStick

0:1

Passenger uses a walking stick. Default is FALSE.

WalkingImpaired

0:1

Passenger is (maybe temporarily) walking impaired. Default is FALSE.

Pram

0:1

Passenger has a pram with him/her. Default is FALSE.

HeavyLuggage

0:1

Passenger has got heavy luggage. Default is FALSE.

VisuallyImpaired

0:1

Passenger is visually impaired.

HearingImpaired

0:1

Passenger is hearing impaired.

ReadingImpaired

0:1

Passenger is reading impaired.

13.9. The group PassengerRequirementsGroup

PassengerRequirementsGroup

Description of passenger's accessibility requirements

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

DriverAssistance

BoardingAssistance

0:1

Whether assistance is required for boarding. Could be offered by the driver or station staff. Default is FALSE.

AlightingAssistance

0:1

Whether assistance is required for alighting. Could be offered by the driver or station staff. Default is FALSE.

13.10. The complex type AvailabilityResultStructure

AvailabilityResultStructure

Availability result structure.

ErrorCondition

0:*

+OJPError

Problems related to this AVAILABILITY result.

The element contains one of the following elements (a)

a

PublicTransport

-1:1

+BookingPTLeg

Definition of the journey leg that should be made by public transport. Other mobility services may be added later.

BookableTicketAndServiceInformation

BookableTicket

0:*

+FareProduct

Sequence of bookable tickets or surcharges for this part of the trip. If ticket price is zero: an already purchased/virtual ticket of this type presented to the driver would be accepted.

BookableServiceItem

0:*

+BookableServiceItem

Sequence of bookable service items for this part of the trip.

Extension

0:1

13.11. The complex type BookableServiceItemStructure

BookableServiceItemStructure

Possible service items that can be booked in the actual booking system (defined by the traffic company of charge). Only those elements with value greater 0 are bookable. The indicated capacity corresponds to the maximum number that can be booked in one booking. This number does not have to be available for the specific booking and may result in booking failure. Caution: list can vary widely from one traffic company to another.

Type

1:1

BookableServiceItemTypeEnumeration

The type of bookable service.

MaxBookableCapacity

1:1

Maximum number of service items that can be booked in one booking transaction. Default is 0.

13.12. The complex type BookingPTLegStructure

BookingPTLegStructure

Journey leg by public transport.

PickUpLocation

1:1

+ProvisionedCallAtPlace

Location where passenger intends to enter the service.

SetDownLocation

1:1

+ProvisionedCallAtPlace

Location where passenger intends to leave the service.

Service

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

PublicCode

0:1

Public code of the SERVICE JOURNEY (same meaning as in NeTEx). Examples: "512", "S8" or "Circle Line" or "ICE 488".

siri:LineDirection

siri:LineRef

1:1

>siri:LineRef

Line Reference.

siri:DirectionRef

0:1

>siri:DirectionRef

Direction Reference.

Service

Mode

1:1

+Mode

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

ProductCategory

0:1

+ProductCategory

A product category for the service. This is a classification defined in NeTEx/SIRI used to identify groups of journeys with some special properties for marketing and fare products, e.g., "TE2" for SNCF or a special panorama train "PE" in Switzerland.

PublishedServiceName

1:1

+InternationalText

Line name or service description as known to the public, e.g., "512", "S8" or "Circle Line" or "ICE 488".

TrainNumber

0:1

Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes will use TrainNumber.

→‍siri:VehicleRef

0:1

>siri:VehicleRef

Reference to a VEHICLE.

OperatorRefs

0:1

+OperatorRefs_Rel

References to the OPERATORS. Multiple OPERATORS in case a ContinuousLeg can be operated by more than one operator, especially in the ALTERNATIVE MODE OF OPERATION where there can be dozens of taxi companies and many free-floating sharing companies.

RouteDescription

0:1

+InternationalText

Descriptive text for a route, e.g., "Airport via City Centre".

Via

0:*

+ServiceViaPoint

Via points of the service that may help identify the vehicle to the public (In Transmodel modelled as TRIP REQUEST PLACE.TRIP VIA PLACE.GoVia; it will also most probably be detailed as a VIA and associated DESTINATION DISPLAY in the ROUTE description).

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

Attribute

0:*

+GeneralAttribute

Note or service attribute.

ServiceOrigin

OriginStopPointRef

0:1

>siri:StopPointRef

First stop of the vehicle journey; origin stop point.

OriginText

1:1

+InternationalText

Label for first stop.

siri:BasicServiceInfo

siri:OperatorRef

0:1

>siri:OperatorRef

OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.

siri:ProductCategoryRef

0:1

>siri:ProductCategoryRef

Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.

→‍siri:ServiceFeatureRef

0:*

>siri:ServiceFeatureRef

Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged.

siri:ServiceInfo

siri:VehicleFeatureRef

0:*

>siri:VehicleFeatureRef

Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.

ServiceDestination

DestinationStopPointRef

0:1

>siri:StopPointRef

Last stop of vehicle journey; destination stop point.

DestinationText

0:1

+InternationalText

Label for last stop. Should be set for classic public transport. Demand responsive and newer modes of operation will often not have a destination text.

ServiceStatus

Unplanned

0:1

Whether this trip is an additional one that has not been planned. Default is false.

Cancelled

0:1

Whether this trip is cancelled and will not be run. Default is false.

Deviation

0:1

Whether this trip deviates from the planned service pattern. Default is false.

UndefinedDelay

0:1

Whether this trip may have an undefined delay. Default is false. More details could be provided in a PtSituation.

Occupancy

0:1

siri:OccupancyEnumeration

[equivalent to OCCUPANCY in SIRI] passenger load status of a VEHICLE. If omitted, not known.

Service

JourneyRelations

0:1

+siri:JourneyRelations

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.

Extension

0:1

13.13. The complex type BookingUserStructure

BookingUserStructure

Passenger(s) for whom the service needs to be booked.

Age

0:1

Age of the passenger on the day of travel.

PassengerProfile

WheelchairUser

0:1

Passenger uses a wheelchair. Default is FALSE.

WalkingFrame

0:1

Passenger uses a walking frame. Default is FALSE.

WalkingStick

0:1

Passenger uses a walking stick. Default is FALSE.

WalkingImpaired

0:1

Passenger is (maybe temporarily) walking impaired. Default is FALSE.

Pram

0:1

Passenger has a pram with him/her. Default is FALSE.

HeavyLuggage

0:1

Passenger has got heavy luggage. Default is FALSE.

VisuallyImpaired

0:1

Passenger is visually impaired.

HearingImpaired

0:1

Passenger is hearing impaired.

ReadingImpaired

0:1

Passenger is reading impaired.

BaseTripMobilityFilter

NoSingleStep

0:1

The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded.

NoStairs

0:1

The user is not able to walk up/downstairs.

NoEscalator

0:1

The user is not able to use an escalator.

NoElevator

0:1

The user is not able to use an elevator.

NoRamp

0:1

The user is not able to use a ramp.

NoSight

0:1

The user is not able to see.

NoTravelator

0:1

The user is not able to use a travelator.

LevelEntrance

0:1

The user needs vehicles with level entrance between platform and vehicle.

LevelEntranceOrBoardingAid

0:1

The user needs vehicles with level entrance between platform and vehicle, an appropriate ramp, or assistance for boarding or alighting (for assisted and unassisted wheelchairs, or similar constraints).

TripMobilityFilter

BikeTransport

0:1

The user wants to carry a bike on public transport (could be extended in future to transporting big luggage / animals / etc.).

WalkSpeed

0:1

OpenPercentType

Deviation from average walking speed in percent. 100% percent is average speed. Less than 100 % slower, Greater than 150% faster.

AdditionalTransferTime

0:1

Additional time added to all transfers (also to transfers between individual to public transport, not modelled in Transmodel).

HikingProfile

0:1

local-type: typedef-90.1

Users hiking profile. The main element to control general walking behaviour is WalkSpeed (together with accessibility constraints). Note: explanations in German can be found here: https://akademie.alpinewelten.com/bergwandern/klassifizierung-von-wanderwegen

CyclingProfile

0:1

local-type: typedef-90.2

Cycling profile of the user (especially for sportive activities).

DriverAssistance

BoardingAssistance

0:1

Whether assistance is required for boarding. Could be offered by the driver or station staff. Default is FALSE.

AlightingAssistance

0:1

Whether assistance is required for alighting. Could be offered by the driver or station staff. Default is FALSE.

13.14. The complex type ProvisionedCallAtPlaceStructure

ProvisionedCallAtPlaceStructure

Provisioned vehicle call at a general location.

DatedJourneyRef

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

→‍OperatingDayRef

1:1

>OperatingDayRef

Reference to an Operating Day

CallPlace

1:1

+PlaceRef

More general location for a call than stop points. May be used with flexible services or "Area Dial-A-Ride".

ServiceArrival

0:1

+ServiceArrival

Arrival times of the service at this stop.

ServiceDeparture

0:1

+ServiceDeparture

Departure times of the service at this stop.

StopCallStatus

Order

0:1

Sequence number of this stop in the service pattern of the journey.

RequestStop

0:1

The vehicle journey calls at this stop only on demand.

UnplannedStop

0:1

This stop has not been planned by the planning department.

NotServicedStop

0:1

The vehicle will not call at this stop despite earlier planning.

NoBoardingAtStop

0:1

Boarding will not be allowed at this stop of this journey.

NoAlightingAtStop

0:1

Alighting will not be allowed at this stop of this journey.

→‍siri:ExpectedDepartureOccupancy

0:*

+siri:VehicleOccupancy

Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)

→‍siri:ExpectedDepartureCapacities

0:*

+siri:PassengerCapacity

Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)

Attribute

0:*

+GeneralAttribute

Note or attribute.

14. OJP/OJP_Common.xsd - Supporting definitions of common structures

14.1. Simple type definitions

JourneyCodeType

xs:NMTOKEN: (empty restriction)

Identifier of a Journey

ObjectIdType

xs:normalizedString: (empty restriction)

Type for identifier of a NeTEx Object.

OperatingDayCodeType

xs:NMTOKEN: (empty restriction)

Identifier of an Operating Day

OwnerCodeType

xs:NMTOKEN: (empty restriction)

identifier of ORGANISATION with ownership as the RESPONSIBILITY ROLE

Percentage

xs:decimal: range=[0,100]

A percentage value between 0 and 100

WeekdayTypeEnumeration

[a specialisation of DAY OF WEEK in TMv6] enumeration of individual the seven DAYs OF WEEK, along with public holidays

Sunday

-

Monday

-

Tuesday

-

Wednesday

-

Thursday

-

Friday

-

Saturday

-

PublicHoliday

-

complexType[ojp:EmissionCO2Structure]
  /KilogramPerPersonKm #simpleType
  (typedef-92.1)

xs:float: value>=0

-

14.2. The toplevel element ErrorType

ErrorType

xs:string

14.3. The toplevel element JourneyRef

JourneyRef

+JourneyRef

Reference to a Journey

14.4. The toplevel element OJPError

OJPError

+OJPError (↔ siri:OtherError)

Error: All OJP related errors.

14.5. The toplevel element OperatingDayRef

OperatingDayRef

+OperatingDayRef

Reference to an Operating Day

14.6. The toplevel element OperatorRef

OperatorRef

+siri:OperatorRef

Reference to an Operator ([TMv6] company providing public transport services.)

14.7. The toplevel element OwnerRef

OwnerRef

+OwnerRef

Reference to an ORGANISATION with ownership as the RESPONSIBILITY ROLE

14.8. The toplevel element ParticipantRef

ParticipantRef

+siri:ParticipantRef

Reference to a Participant ([equivalent of PARTICIPANT in SIRI] IT system that is participating in a communication with other participant(s))

14.9. The toplevel element ProductCategoryRef

ProductCategoryRef

+siri:ProductCategoryRef

Reference to a product category. Product categories should be defined once and used uniformly in all channels (e.g., NeTEx, SIRI, OJP).

14.10. The group AlternativeServiceUsageGroup

AlternativeServiceUsageGroup

Usage parameters of a sharing service.

AlternativeServiceUsage

TimeBufferBefore

0:1

Typical time a user will need to check in and unlock the vehicle.

TimeBufferAfter

0:1

Typical time a user will need to lock the vehicle and check out.

14.11. The group DatedJourneyRefGroup

DatedJourneyRefGroup

Reference to a DATED VEHICLE JOURNEY (Reference to a journey on a specific operating day).

DatedJourneyRef

→‍JourneyRef

1:1

>JourneyRef

Reference to a Journey

→‍OperatingDayRef

1:1

>OperatingDayRef

Reference to an Operating Day

14.12. The group DatedTrainNumberRefGroup

DatedTrainNumberRefGroup

Reference to a TRAIN NUMBER of an OPERATOR at a given OPERATING DAY.

DatedTrainNumberRef

TrainNumber

1:1

OperatorRef

1:1

>siri:OperatorRef

→‍OperatingDayRef

1:1

>OperatingDayRef

Reference to an Operating Day

14.13. The group OperatingDaysGroup

OperatingDaysGroup

Coded as bit pattern

OperatingDays

OperatingDays

0:1

+OperatingDays

Bit string definition of operating days.

OperatingDaysDescription

0:1

+InternationalText

Textual description of the operation days, e.g., "Monday to Friday" or "not on holidays".

14.14. The group ProblemDetailGroup

ProblemDetailGroup

Detailed description of the problem.

ProblemDetail

Details

0:1

+InternationalText

Explanation of the problem.

LogData

0:1

Additional log data.

14.15. The group SustainabilityGroup

SustainabilityGroup

Elements about sustainability. Primarily for TRIPs and LEGs.

Sustainability

EmissionCO2

0:1

+EmissionCO2

Estimation of CO2 emissions.

14.16. The group TimedVehicleRefGroup

TimedVehicleRefGroup

Reference to a vehicle for a specific point in time.

TimedVehicleRef

→‍siri:VehicleRef

1:1

>siri:VehicleRef

Reference to a VEHICLE.

TimeOfOperation

1:1

Time stamp when the vehicle is operating. In most use cases equal to "now".

14.17. The complex type AlternativeServiceStructure

AlternativeServiceStructure

Service that provides shared vehicles (The Transmodel MODE OF OPERATION is VEHICLE SHARING; other related Transmodel concepts: ALTERNATIVE MODE LEG.SINGLE JOURNEY.COMMON.VEHICLE SERVICE.TRANSPORT ORGANISATION).

OperatorRef

1:1

>siri:OperatorRef

Identifier of the operator of the sharing service

Name

0:1

Public name of the service.

AlternativeServiceUsage

TimeBufferBefore

0:1

Typical time a user will need to check in and unlock the vehicle.

TimeBufferAfter

0:1

Typical time a user will need to lock the vehicle and check out.

InfoUrl

0:1

+WebLink

Link to the web page providing more details on the service.

Restricted

0:1

This flag is set if the service can only be used in a restricted way. For example, a specific ACCESS MODE is required (e.g., dragLift) or the LINE is only made available to certain passenger groups (e.g., school buses, hotel shuttles).

RestrictionNote

0:1

+InternationalText

Information about the restriction.

14.18. The complex type AreaStructure

AreaStructure

Area described as a polygon.

Points

3:*

+siri:Location

Ordered list of geographic locations describing the polygon of the area.

14.19. The complex type EmissionCO2Structure

EmissionCO2Structure

Estimation of CO2 emissions.

KilogramPerPersonKm

1:1

local-type: typedef-92.1

Kilograms of CO2 emission by person and by kilometre.

ConfidenceLevel

0:1

Percentage

Confidence level of the emission value in percent.

14.20. The complex type GeneralAttributeStructure

GeneralAttributeStructure

Structured attribute classification with associated text. If URL is given, it refers to the whole attribute text.

UserText

1:1

+InternationalText

Text of the attribute to be shown to the user.

Code

1:1

Internal code of the attribute. Can be used for detection of double occurrences.

Key

0:1

Key if the attribute is used as a key/value pair.

Value

0:1

Value if the attribute is used as a key/value pair.

Facility

0:*

+siri:AllFacilitiesFeature

Facilities associated with this attribute.

Mandatory

0:1

Defines whether the attribute has to be shown to the user.

Importance

0:1

PercentType

Importance of the attribute.

WebLink

Url

1:1

URL to resource on web.

MimeType

0:1

MIME type of the referenced resource. To which kind of resource does the URL point to?

Embeddable

0:1

Is the referenced resource meant to be embedded as a webview in a surrounding context, e.g., app or web page? If yes, the resource has to be fully responsive. Default is false.

14.21. The complex type JourneyRefStructure

JourneyRefStructure

JourneyCodeType

Identifier of a Journey

14.22. The complex type LinearShapeStructure

LinearShapeStructure

An oriented correspondence from one LINK or ROUTE of a source layer, onto an entity in a target layer: e.g., LINK SEQUENCE. As OJP is reduced in relation to NeTEx, we use a simple general structure.

Position

2:*

+siri:Location

Ordered list of locations representing the geometry of the link or route.

14.23. The complex type LineDirectionFilterStructure

LineDirectionFilterStructure

Filter for in/exclusion of lines (and directions).

Line

1:*

+siri:LineDirection

Reference to a GROUP of DIRECTIONs of the ROUTEs belonging to the same LINE created for the purpose of filtering and organising timetables.

Exclude

0:1

Whether lines in list are to include or exclude from search. Default is exclude.

14.24. The complex type OJPErrorStructure

OJPErrorStructure

siri:OtherError

Type for Error Code.

The element content starts with items inherited from the base type:

@number

1:1

Error code number associated with error.

siri:ErrorText

0:1

Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition.

Inherited content is followed by own content:

→‍ErrorType

1:1

ProblemDetail

Details

0:1

+InternationalText

Explanation of the problem.

LogData

0:1

Additional log data.

14.25. The complex type OperatingDayRefStructure

OperatingDayRefStructure

OperatingDayCodeType

Identifier of an Operating Day

14.26. The complex type OperatingDaysStructure

OperatingDaysStructure

[TMv6] day of public transport operation of which the characteristics are defined in a specific SERVICE CALENDAR and which may last more than 24 hours. This is useful, when the trip can be made during several days. Often users search in "general" without setting a date and then refine with the actual date. By using OperatingDaysStructure the result can directly be reused without an additional OJPTripRequest.

From

1:1

Start date of period.

To

1:1

End date of period.

Pattern

1:1

ValidDayBitType

Bit pattern for operating days between start date and end date. The length of the pattern is equal to the number of days from start date to end date. A bit value of "1" indicates that an event happens on the day that is represented by the bit position.

14.27. The complex type OperatorFilterStructure

OperatorFilterStructure

Filter for in/exclusion of transport operators.

Exclude

0:1

Whether operators in list are to include or exclude from search. Default is exclude.

OperatorRef

0:*

>siri:OperatorRef

Reference to transport operator

14.28. The complex type OperatorRefs_RelStructure

OperatorRefs_RelStructure

-

OperatorRef

1:*

>siri:OperatorRef

14.29. The complex type OwnerRefStructure

OwnerRefStructure

OwnerCodeType

identifier of ORGANISATION with ownership as the RESPONSIBILITY ROLE

14.30. The complex type PrivateCodeStructure

PrivateCodeStructure

Code within scope of a private referential system

System

1:1

Code of the foreign referential system.

Value

1:1

Object code within this private/foreign system.

14.31. The complex type VehicleFilterStructure

VehicleFilterStructure

Filter for Vehicles

Exclude

0:1

Whether to include or exclude given VehicleRefs and TRAIN NUMBERS in the list from the search. Default is exclude.

VehicleRef

0:*

>siri:VehicleRef

Reference to VEHICLE

TrainNumber

0:*

TRAIN NUMBERs

14.32. The complex type WeekdayTimePeriodStructure

WeekdayTimePeriodStructure

[a specialisation of TIME BAND in TMv6] aggregation of TIME BAND and DAY OF WEEK (Time period on a weekday).

Weekday

0:*

WeekdayTypeEnumeration

[a specialisation of DAY OF WEEK in TMv6] enumeration of individual the seven DAYs OF WEEK, along with public holidays

StartTime

1:1

Start time of period.

Duration

1:1

Time duration of period.

15. OJP/OJP_FacilitySupport.xsd - Supporting definitions for facilities containing wrappers for SIRI

15.1. The group ServiceFacilityGroup

ServiceFacilityGroup

Wrapper for SIRI service facilities.

siri:CommonFacility

→‍siri:FareClassFacility

0:*

siri:FareClassFacilityEnumeration

Classification of FareClass Facility type - Tpeg pti23.

→‍siri:TicketingFacility

0:*

siri:TicketingFacilityEnumeration

Classification of Ticketing Facility type - Tpeg pti23.

→‍siri:NuisanceFacility

0:*

siri:NuisanceFacilityEnumeration

Classification of Nuisance Facility type - Tpeg pti23.

→‍siri:MobilityFacility

0:*

siri:MobilityFacilityEnumeration

Classification of Mobility Facility type - Tpeg pti23.

→‍siri:PassengerInformationFacility

0:*

siri:PassengerInformationFacilityEnumeration

Classification of PassengerInfo Facility type - Tpeg pti23.

→‍siri:PassengerCommsFacility

0:*

siri:PassengerCommsFacilityEnumeration

Classification of PassengerComms Facility type - Tpeg pti23.

→‍siri:RefreshmentFacility

0:*

siri:RefreshmentFacilityEnumeration

Classification of Refreshment Facility type - Tpeg pti23.

siri:AccessFacility

0:*

siri:AccessFacilityEnumeration

Classification of Access Facility.

→‍siri:SanitaryFacility

0:*

siri:SanitaryFacilityEnumeration

Classification of Sanitary Facility type - Tpeg pti23.

→‍siri:LuggageFacility

0:*

siri:LuggageFacilityEnumeration

Classification of Luggage Facility type - Tpeg pti23.

siri:ServiceFacility

→‍siri:AccommodationFacility

0:*

siri:AccommodationFacilityEnumeration

Classification of Accomodation Facility type - Tpeg pti23.

15.2. The group StopFacilityGroup

StopFacilityGroup

Wrapper for SIRI stop facilities.

siri:CommonFacility

→‍siri:FareClassFacility

0:*

siri:FareClassFacilityEnumeration

Classification of FareClass Facility type - Tpeg pti23.

→‍siri:TicketingFacility

0:*

siri:TicketingFacilityEnumeration

Classification of Ticketing Facility type - Tpeg pti23.

→‍siri:NuisanceFacility

0:*

siri:NuisanceFacilityEnumeration

Classification of Nuisance Facility type - Tpeg pti23.

→‍siri:MobilityFacility

0:*

siri:MobilityFacilityEnumeration

Classification of Mobility Facility type - Tpeg pti23.

→‍siri:PassengerInformationFacility

0:*

siri:PassengerInformationFacilityEnumeration

Classification of PassengerInfo Facility type - Tpeg pti23.

→‍siri:PassengerCommsFacility

0:*

siri:PassengerCommsFacilityEnumeration

Classification of PassengerComms Facility type - Tpeg pti23.

→‍siri:RefreshmentFacility

0:*

siri:RefreshmentFacilityEnumeration

Classification of Refreshment Facility type - Tpeg pti23.

siri:AccessFacility

0:*

siri:AccessFacilityEnumeration

Classification of Access Facility.

→‍siri:SanitaryFacility

0:*

siri:SanitaryFacilityEnumeration

Classification of Sanitary Facility type - Tpeg pti23.

→‍siri:LuggageFacility

0:*

siri:LuggageFacilityEnumeration

Classification of Luggage Facility type - Tpeg pti23.

siri:StopFacility

→‍siri:AssistanceFacility

0:*

siri:AssistanceFacilityEnumeration

Classification of Assistance Facility.

→‍siri:HireFacility

0:*

siri:HireFacilityEnumeration

Classification of Hire Facility.

16. OJP/OJP_ModesSupport.xsd - Supporting definitions for the classification of modes of transport

16.1. Simple type definitions

AlternativeModesOfOperationEnumeration

ALTERNATIVE MODE OF OPERATION offered.

sharing

Using a sharing as an ALTERNATIVE MODE OF OPERATION. Only if one of the specialisations doesn't apply.

stationLessSharing

ALTERNATIVE MODE OF OPERATION. station less sharing.

stationBasedSharing

ALTERNATIVE MODE OF OPERATION. Based on fix stations (VEHICLE MEETING POINT).

singleStationBasedSharing

ALTERNATIVE MODE OF OPERATION. Based on single fix station (VEHICLE MEETING POINT).

multipleStationBasedSharing

ALTERNATIVE MODE OF OPERATION. Based on multiple fix stations (VEHICLE MEETING POINT).

peerToPeerSharing

ALTERNATIVE MODE OF OPERATION. Specialised sharing between people.

parkAndRideSharing

ALTERNATIVE MODE OF OPERATION. Specialised sharing in the context of a park and ride situation.

sharingClubSharing

ALTERNATIVE MODE OF OPERATION. Sharing organised as a club.

prM

ALTERNATIVE MODE OF OPERATION. In relation to a conventional SERVICE JOURNEY, but when pick-up and drop-off are not associated with SCHEDULED STOP POINTs.

pooling

General pooling ALTERNATIVE MODE OF OPERATION. Only use this enum when no specialisation applies. In some cases, where the pooling is very "scheduled" use the pooling in ConventionalModeOfOperation.

taxi

Taxi MODE OF OPERATION.

shuttle

Shuttle MODE OF OPERATION, when not associated with SCHEDULED STOP POINTs.

dynamicPooling

ALTERNATIVE MODE OF OPERATION. A pooling that is dynamic, usually local, and not long-term planned.

longDistancePooling

ALTERNATIVE MODE OF OPERATION. A pooling for long distances, mostly for a SINGLE JOURNEY.

commuterPooling

ALTERNATIVE MODE OF OPERATION. A pooling to go to workplaces and related things. Usually, in a regular interval with the same people.

parkAndRidePooling

ALTERNATIVE MODE OF OPERATION. A pooling in relation to park and ride.

chauffeured

ALTERNATIVE MODE OF OPERATION for SINGLE JOURNEY with a paid driver. Often more than a single SINGLE JOURNEY.

demandResponsive

ALTERNATIVE MODE OF OPERATION demand responsive is used when there is no SCHEDULED STOP POINTs involved and the timetable component is weak. Otherwise, use the demandResponsive in ConventionalModeOfOperation.

flexibleArea

Specialisation of the demand responsive ALTERNATIVE MODE OF OPERATION for AREA related offers. Otherwise, use the demandResponsive in ConventionalModeOfOperation.

companyShuttle

ALTERNATIVE MODE OF OPERATION. To specifically state that it is a company related. Specialisation of demand responsive.

hotelShuttle

ALTERNATIVE MODE OF OPERATION. To specifically state that it is hotel related. Specialisation of demand responsive.

hire

Using a hired VEHICLE.

other

Only use this value when no other applies.

ConventionalModesOfOperationEnumeration

Types of MODES OF OPERATION are scheduled, classic and flexible. From NeTEx.

scheduled

Regular MODE OF OPERATION for CONVENTIONAL MODE OF OPERATION. Based on SCHEDULED STOP POINTs and timetables.

demandResponsive

Demand responsive services. General term when nothing else is known. Requires SCHEDULED STOP POINTs. The more taxi-like a demand responsive service becomes the more probable it is better to use ALTERNATIVE MODE OF OPERATION.

flexibleRoute

Specialisation of demand responsive MODE OF OPERATION. The service is still based on a ROUTE.

flexibleArea

Specialisation of demand responsive MODE OF OPERATION. The service is based on AREAs, but still SCHEDULED STOP POINTs are used. Sometimes the characteristics of a given demand responsive service makes it mor of an ALTERNATIVE MODE OF OPERATION (e.g., pure area service). A conventional mode of operation is more indicated, when there is a limited list of stops within the area.

shuttle

If the service is provided as a form of shuttle.

pooling

In some cases, pooling is not an ALTERNATIVE MODE OF OPERATION, but is better served with a TimedLeg. Then this MODE OF OPERATION is to be used.

replacement

The service is provided as a replacement of a SCHEDULED service.

school

MODE OF OPERATION that specifically states that it is school related. Specialisation of demand responsive or scheduled.

pRM

If for a scheduled, conventional service a special additional vehicle is needed to provide for special PRM needs. This kind of MODE OF OPERATION is to be used.

PersonalModesEnumeration

TYPE OF MODE that can be used in an individual context. PERSONAL MODE in TM 6.2.

foot

-

bicycle

-

car

-

motorcycle

-

truck

-

scooter

-

other

Only to be used when no other type applies.

PersonalModesOfOperationEnumeration

PERSONAL MODE OF OPERATION

self

Without a VEHICLE.

own

Using an owned VEHICLE.

otherOwned

Using a VEHICLE owned by a different private person without a commercial context.

privateLift

Other driver without commercial interest is driving. Typical case of being picked up or dropped off at a stop e.g., by a friend, relative. If the offer is advertised or commercial, then pooling from ALTERNATIVE MODE OF OPERATION should be chosen.

lease

Using a leased VEHICLE.

TransferTypeEnumeration

TYPE OF TRANSFER. It is a mix between MODE information, MODE OF OPERATION information and a more stringent TYPE OF TRANSFER.

walk

The "normal" TransferType. Indicates that the traveler walks to the next LEG.

shuttle

Indicates that a shuttle service is used for the TRANSFER LEG. E.g. between gates in an airport.

taxi

Indicates that the transfer is done by taxi. This type should be avoided and the taxi leg should be modelled as a ContinuousLeg.

protectedConnection

Indicates that the connection to the next leg is specially monitored and usually kept (depending on agreements between the operators). Usually, it is used in combination with walk.

guaranteedConnection

The connection is guaranteed. This doesn't apply very often, but e.g., a bus has to bring people from the last train to a different destination. Then it will not depart before the train has arrived and the passengers have changed. In some cases, guaranteedConnection might be used with less strictness.

remainInVehicle

The next leg is in the same VEHICLE and there is no need to change it.

changeWithinVehicle

If trains are split, it may be necessary to change to the correct part of the train. Usage of changeWithinVehicle is preferred over remainInVehicle if it is unclear whether the traveller is in the correct part of the train.

checkIn

Means that a checkin operation is necessary. This usually results in a longer time that can't be justified by the length of the transfer leg.

checkOut

Means that a checkout operation is necessary. This usually results in a longer time that can't be justified by the length of the transfer leg

parkAndRide

This does not model the car ride. But parking the car and getting to the stop may take way longer e.g., in a big parking garage. This is a special type of checkIn or checkOut.

bikeAndRide

In the transfer leg additional time may be needed to get or stow a bike (e.g., because the BIKE PARKING is at a special place). this can be seen as a special type of checkIn or checkOut.

carHire

Time for a car hire is needed. This will make the transfer leg to take longer than expected. Can be seen as a special case of checkIn.

bikeHire

Time for a bike hire is needed. This will make the transfer leg to take longer than expected. Can be seen as a special case of checkIn.

other

Only to be used when no other type applies.

16.2. The group ModeGroup

ModeGroup

Elements for a Transport Mode

Mode

PtMode

1:1

siri:VehicleModesOfTransportEnumeration

Categorisation of a (conventional) PUBLIC TRANSPORT MODE. We use the SIRI 2.1 element which allows for many values in the enumeration. In OJP we don't use the following enumeration values: "pti1_xxx", "xxxServices" when a value without the "Service" exists for the same MODE, "allServicesExcept", "selfDrive", "taxi". Also, in cases where only a "xxxService" exists in the enumeration, it should be avoided. "other" or "unknown" should only be used if no other value applies.

The element contains one of the following elements (a-i)

siri:PtModeChoice

a

→‍siri:AirSubmode

-1:1

siri:AirSubmodesOfTransportEnumeration

TPEG Pti08 and Pts108 "AirService" submodes.

b

→‍siri:BusSubmode

-1:1

siri:BusSubmodesOfTransportEnumeration

TPEG Pti05 and Pts105 "BusService" submodes.

c

→‍siri:CoachSubmode

-1:1

siri:CoachSubmodesOfTransportEnumeration

TPEG Pti03 and Pts103 "CoachService" submodes.

d

→‍siri:FunicularSubmode

-1:1

siri:FunicularSubmodesOfTransportEnumeration

TPEG pti10 Funicular submodes.

e

→‍siri:MetroSubmode

-1:1

siri:MetroSubmodesOfTransportEnumeration

TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes.

f

→‍siri:TramSubmode

-1:1

siri:TramSubmodesOfTransportEnumeration

TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes.

g

→‍siri:TelecabinSubmode

-1:1

siri:TelecabinSubmodesOfTransportEnumeration

TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes.

h

→‍siri:RailSubmode

-1:1

siri:RailSubmodesOfTransportEnumeration

TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes.

i

→‍siri:WaterSubmode

-1:1

siri:WaterSubmodesOfTransportEnumeration

TPEG Pti07 and Pts107 "WaterTransportService" submodes.

16.3. The complex type IndividualTransportOptionStructure

IndividualTransportOptionStructure

Individual modes and their usage limits as stated by the passenger (TRIP ACCESS CONSTRAINT).

ItModeAndModeOfOperation

1:1

+ItModes

Combinations of MODE and MODE OPERATION for ACCESS LEG. If no MODE OF OPERATION is given, then all can be used. Usually, the result will be the own vehicle.

MaxDistance

0:1

siri:DistanceType

Maximum distance in meters. If given, it restricts the maximum distance of routes with the given mode.

MaxDuration

0:1

Maximum duration. If given, it restricts the maximum time of routes with the given mode.

MinDistance

0:1

siri:DistanceType

Minimum distance in meters. If given, it restricts the minimum distance of routes with the given mode.

MinDuration

0:1

Minimum duration. If given, it restricts the minimum time of routes with the given mode.

Speed

0:1

OpenPercentType

Relative speed in percent. If given slows the standard speed (below 100) or fasten it (above 100).

AdditionalTime

0:1

Additional time added to the actual traveling time needed to use a specific mode.

16.4. The complex type ItModesStructure

ItModesStructure

Combinations of MODE and MODE OF OPERATION that should be covered as monomodal trips (or for the ACCESS LEGs). If no MODE OF OPERATION is added usually "own" is assumed. But the trip planner may add other relevant results (e.g., sharing, if sensible trips are possible).

PersonalMode

1:1

PersonalModesEnumeration

Relevant PERSONAL MODE to be used for the monomodal trip.

PersonalModeOfOperation

0:*

PersonalModesOfOperationEnumeration

List of personal mobility offers for this MODE.

AlternativeModeOfOperation

0:*

AlternativeModesOfOperationEnumeration

List of alternative mobility offers for this MODE.

16.5. The complex type ModeAndModeOfOperationFilterStructure

ModeAndModeOfOperationFilterStructure

List of MODE and MODE OF OPERATION filter offers to include or exclude.

Exclude

0:1

Whether MODE and MODE OF OPERATION combination in list are to include or exclude from search. Default is exclude.

PtMode

0:*

siri:VehicleModesOfTransportEnumeration

List of PT Transport modes to include/exclude. We use the SIRI 2.1 element which allows for many values in the enumeration. In OJP we don't use the following enumeration values: "pti1_xxx", "xxxServices" when a value without the "Service" exists for the same MODE, "allServicesExcept", "selfDrive", "taxi". Also, in cases where only a "xxxService" exists in the enumeration, it should be avoided. "other" or "unknown" should only be used if no other value applies.

PersonalMode

0:*

PersonalModesEnumeration

List of personal transport modes to include/exclude. Those are also used in many of the ALTERNATIVE MODES OF OPERATION.

The element contains one of the following elements (a-i)

siri:PtModeChoice

a

→‍siri:AirSubmode

-1:1

siri:AirSubmodesOfTransportEnumeration

TPEG Pti08 and Pts108 "AirService" submodes.

b

→‍siri:BusSubmode

-1:1

siri:BusSubmodesOfTransportEnumeration

TPEG Pti05 and Pts105 "BusService" submodes.

c

→‍siri:CoachSubmode

-1:1

siri:CoachSubmodesOfTransportEnumeration

TPEG Pti03 and Pts103 "CoachService" submodes.

d

→‍siri:FunicularSubmode

-1:1

siri:FunicularSubmodesOfTransportEnumeration

TPEG pti10 Funicular submodes.

e

→‍siri:MetroSubmode

-1:1

siri:MetroSubmodesOfTransportEnumeration

TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes.

f

→‍siri:TramSubmode

-1:1

siri:TramSubmodesOfTransportEnumeration

TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes.

g

→‍siri:TelecabinSubmode

-1:1

siri:TelecabinSubmodesOfTransportEnumeration

TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes.

h

→‍siri:RailSubmode

-1:1

siri:RailSubmodesOfTransportEnumeration

TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes.

i

→‍siri:WaterSubmode

-1:1

siri:WaterSubmodesOfTransportEnumeration

TPEG Pti07 and Pts107 "WaterTransportService" submodes.

PersonalModeOfOperation

0:*

PersonalModesOfOperationEnumeration

List of personal mobility offers to include/exclude.

AlternativeModeOfOperation

0:*

AlternativeModesOfOperationEnumeration

List of alternative mobility offers to include/exclude.

ConventionalModeOfOperation

0:*

ConventionalModesOfOperationEnumeration

List of conventional mobility offers to include/exclude.

16.6. The complex type ModeFilterStructure

ModeFilterStructure

List of MODE to exclude or include.

Exclude

0:1

Whether MODEs in list are to be excluded or included from search. Default is to exclude.

PtMode

0:*

siri:VehicleModesOfTransportEnumeration

List of PT Transport modes to include/exclude. We use the SIRI 2.1 element which allows for many values in the enumeration. In OJP we don't use the following enumeration values: "pti1_xxx", "xxxServices" when a value without the "Service" exists for the same MODE, "allServicesExcept", "selfDrive", "taxi". Also, in cases where only a "xxxService" exists in the enumeration, it should be avoided. "other" or "unknown" should only be used if no other value applies.

PersonalMode

0:*

PersonalModesEnumeration

List of personal transport modes to include/exclude. Those are also used in many of the ALTERNATIVE MODES OF OPERATION.

The element contains one of the following elements (a-i)

siri:PtModeChoice

a

→‍siri:AirSubmode

-1:1

siri:AirSubmodesOfTransportEnumeration

TPEG Pti08 and Pts108 "AirService" submodes.

b

→‍siri:BusSubmode

-1:1

siri:BusSubmodesOfTransportEnumeration

TPEG Pti05 and Pts105 "BusService" submodes.

c

→‍siri:CoachSubmode

-1:1

siri:CoachSubmodesOfTransportEnumeration

TPEG Pti03 and Pts103 "CoachService" submodes.

d

→‍siri:FunicularSubmode

-1:1

siri:FunicularSubmodesOfTransportEnumeration

TPEG pti10 Funicular submodes.

e

→‍siri:MetroSubmode

-1:1

siri:MetroSubmodesOfTransportEnumeration

TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes.

f

→‍siri:TramSubmode

-1:1

siri:TramSubmodesOfTransportEnumeration

TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes.

g

→‍siri:TelecabinSubmode

-1:1

siri:TelecabinSubmodesOfTransportEnumeration

TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes.

h

→‍siri:RailSubmode

-1:1

siri:RailSubmodesOfTransportEnumeration

TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes.

i

→‍siri:WaterSubmode

-1:1

siri:WaterSubmodesOfTransportEnumeration

TPEG Pti07 and Pts107 "WaterTransportService" submodes.

16.7. The complex type ModeStructure

ModeStructure

[a specialisation of MODE in TMv6] an extended range of VEHICLE MODEs, aggregating them with some SUBMODEs

Mode

PtMode

1:1

siri:VehicleModesOfTransportEnumeration

Categorisation of a (conventional) PUBLIC TRANSPORT MODE. We use the SIRI 2.1 element which allows for many values in the enumeration. In OJP we don't use the following enumeration values: "pti1_xxx", "xxxServices" when a value without the "Service" exists for the same MODE, "allServicesExcept", "selfDrive", "taxi". Also, in cases where only a "xxxService" exists in the enumeration, it should be avoided. "other" or "unknown" should only be used if no other value applies.

The element contains one of the following elements (a-i)

siri:PtModeChoice

a

→‍siri:AirSubmode

-1:1

siri:AirSubmodesOfTransportEnumeration

TPEG Pti08 and Pts108 "AirService" submodes.

b

→‍siri:BusSubmode

-1:1

siri:BusSubmodesOfTransportEnumeration

TPEG Pti05 and Pts105 "BusService" submodes.

c

→‍siri:CoachSubmode

-1:1

siri:CoachSubmodesOfTransportEnumeration

TPEG Pti03 and Pts103 "CoachService" submodes.

d

→‍siri:FunicularSubmode

-1:1

siri:FunicularSubmodesOfTransportEnumeration

TPEG pti10 Funicular submodes.

e

→‍siri:MetroSubmode

-1:1

siri:MetroSubmodesOfTransportEnumeration

TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes.

f

→‍siri:TramSubmode

-1:1

siri:TramSubmodesOfTransportEnumeration

TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes.

g

→‍siri:TelecabinSubmode

-1:1

siri:TelecabinSubmodesOfTransportEnumeration

TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes.

h

→‍siri:RailSubmode

-1:1

siri:RailSubmodesOfTransportEnumeration

TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes.

i

→‍siri:WaterSubmode

-1:1

siri:WaterSubmodesOfTransportEnumeration

TPEG Pti07 and Pts107 "WaterTransportService" submodes.

Name

0:1

+InternationalText

Name of the mode.

ShortName

0:1

+InternationalText

Short name or acronym of the mode.

Description

0:1

+InternationalText

Additional text that further describes the mode.

17. OJP/OJP_SituationSupport.xsd - Supporting definitions for situations containing wrappers for SIRI Situation Exchange service (SIRI SX)

17.1. The toplevel element SituationFullRef

SituationFullRef

+SituationFullRef

Reference to situation message. Message details might be found in response context or through other communication channels.

17.2. The complex type SituationFullRefStructure

SituationFullRefStructure

siri:SituationFullRef

Type for reference to a SITUATION.

The element content starts with items inherited from the base type:

siri:SituationFullIdentity

siri:VersionCountryRef

0:1

>ifopt:CountryRef

Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as.

siri:ParticipantRef

1:1

>siri:ParticipantRef

Unique identifier of a Participant. Provides namespace for SITUATION.

→‍siri:SituationNumber

1:1

>siri:EntryQualifier

Identifier of SITUATION within a Participant. Exclude versionr.

siri:SituationUpdateIdentity

siri:UpdateCountryRef

0:1

>ifopt:CountryRef

Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as.

siri:UpdateParticipantRef

0:1

>siri:ParticipantRef

Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context.

siri:Version

0:1

>siri:SituationVersion

Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION.

17.3. The complex type SituationRefList

SituationRefList

List of references to SITUATIONs.

→‍SituationFullRef

1:*

+SituationFullRef

Reference to situation message. Message details might be found in response context or through other communication channels.

17.4. The complex type SituationsStructure

SituationsStructure

Wrapper type for SIRI PtSituationsElementStructure

PtSituation

0:*

+siri:PtSituationElement

SIRI situation details in public transport, see CEN/TS 15531-5.

RoadSituation

0:*

+siri:RoadSituationElement

SIRI situation details in individual transport, see CEN/TS 15531-5.

18. OJP/OJP_Utility.xsd - Support definitions not specifically related to the public transport domain

18.1. Simple type definitions

EmailAddressType

xs:normalizedString: (empty restriction)

Type definition for email addresses.

LengthType

xs:nonNegativeInteger: (empty restriction)

Data type for lengths, in meters.

OpenPercentType

xs:nonNegativeInteger: (empty restriction)

Percent value as integer, no upper limit.

PercentType

xs:nonNegativeInteger: value<=100

Percent value as integer, limited to max value 100.

PhoneNumberType

xs:normalizedString: (empty restriction)

Type definition for phone numbers

PriorityType

xs:nonNegativeInteger: range=[1,5]

Data type for priority values, from 1 (highest) to 5 (lowest).

ValidDayBitType

xs:string: pattern=#[01]*#

sequence of bits (values 0 or 1) coded as a text string and representing days

18.2. The group WebLinkGroup

WebLinkGroup

URL of a web resource including type of resource.

WebLink

Url

1:1

URL to resource on web.

MimeType

0:1

MIME type of the referenced resource. To which kind of resource does the URL point to?

Embeddable

0:1

Is the referenced resource meant to be embedded as a webview in a surrounding context, e.g., app or web page? If yes, the resource has to be fully responsive. Default is false.

18.3. The complex type InternationalTextStructure

InternationalTextStructure

[a restricted view of ALTERNATIVE NAME in TMv6] alternative identified text to be used in specified languages.

Text

1:*

>siri:NaturalLanguageString

Text content.

TextId

0:1

Id of this text. May be used for matching to pre-recorded audio files.

18.4. The complex type WebLinkStructure

WebLinkStructure

URL of a web resource with label.

Label

1:1

+InternationalText

Label for link description.

WebLink

Url

1:1

URL to resource on web.

MimeType

0:1

MIME type of the referenced resource. To which kind of resource does the URL point to?

Embeddable

0:1

Is the referenced resource meant to be embedded as a webview in a surrounding context, e.g., app or web page? If yes, the resource has to be fully responsive. Default is false.

19. OJP/OJP_Status.xsd - OJP Status request and response

19.1. Simple type definitions

StatusProblemTypeEnumeration

Types of problems that may be returned in responses to status requests.

STATUS_INSTANCE_USAGE_DEPRECATED

Usage of this instance is deprecated. Contact the provider for more information.

STATUS_OTHER

A problem has occurred that does not have a specific problem type.

19.2. The toplevel element OJPStatusResponse

OJPStatusResponse

+OJPStatusResponse (↔ siri:AbstractFunctionalServiceCapabilitiesResponse)

19.3. The toplevel element StatusProblemType

StatusProblemType

+StatusProblemTypeEnumeration (↔ ojp:ErrorType)

19.4. The group OJPStatusResponseGroup

OJPStatusResponseGroup

Status response group.

OJPStatusResponse

ServiceStarted

0:1

Time when the service was started.

ServiceReady

0:1

Time when the service started responding to queries.

LastTimetableUpdate

0:1

Time when the timetable was last updated.

ServerBuildVersion

0:1

Information about the server build.

19.5. The complex type OJPStatusResponseStructure

OJPStatusResponseStructure

siri:AbstractServiceCapabilitiesResponse

General Type for General SIRI Response.

The element content starts with items inherited from the base type:

→‍siri:ResponseTimestamp

1:1

Time individual response element was created.

siri:ContextualisedResponseEndpoint

siri:RequestMessageRef

0:1

>siri:MessageRef

Arbitrary unique reference to the request which gave rise to this message.

siri:DelegatorEndpoint

siri:DelegatorAddress

0:1

siri:EndpointAddress

Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0)

siri:DelegatorRef

0:1

>siri:ParticipantRef

Identifier of delegating system that originated message. (since SIRI 2.0)

siri:CapabilityStatus

→‍siri:Status

0:1

Whether the request was processed successfully or not. Default is 'true'.

siri:ErrorCondition

0:1

+siri:ServiceDeliveryErrorCondition

Description of any error or warning condition.

Inherited content is followed by own content:

ServiceResponseContext

DataFrameRef

0:1

>siri:DataFrameRef

identifier of the set of data being used by an information system, which allows a comparison to be made with the versions of data being used by overlapping systems.

CalcTime

0:1

CalcTimeType

Calculation time.

ErrorCondition

0:*

+OJPError

OJP generic problem for the whole delivery.

OJPStatusResponse

ServiceStarted

0:1

Time when the service was started.

ServiceReady

0:1

Time when the service started responding to queries.

LastTimetableUpdate

0:1

Time when the timetable was last updated.

ServerBuildVersion

0:1

Information about the server build.

→‍siri:Extensions

0:1

+siri:Extensions

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).