Then, the element contains one of the following elements:
a
NumberOfResultsBefore
0:1
xs:nonNegativeInteger
The desired number of trip results before the given time (at origin or destination).
a
NumberOfResultsAfter
0:1
xs:nonNegativeInteger
The desired number of trip results after the given time (at origin or destination).
b
NumberOfResults
-0:1
xs:positiveInteger
The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them.
b
NumberOfResults
-0:1
xs:positiveInteger
The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them.
TimeWindow
0:1
xs:duration
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
The way real-time data should be used in the calculation of the trip.
ImmediateTripStart
0:1
xs:boolean
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
xs:nonNegativeInteger
The maximum number of interchanges the user will accept per trip.
OptimisationMethod
0:1
The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).
ConsiderElevationData
0:1
xs:boolean
Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.
IncludeAllRestrictedLines
0:1
xs:boolean
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:*
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.
Then, the element contains one of the following elements:
The element contains a sequence of the following elements:
ItModeToCover
-0:*
For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.
IncludeAlternativeOptions
-0:1
xs:boolean
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 the user expectance (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.
IncludeAllRestrictedLines
-0:1
xs:boolean
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:*
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.
b
MotorisedMainTravelMode
-0:1
xs:boolean
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.
Then, the element contains one of the following elements:
The element contains a sequence of the following elements:
ItModeToCover
-0:*
For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.
IncludeAlternativeOptions
-0:1
xs:boolean
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 the user expectance (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.
b
MotorisedMainTravelMode
-0:1
xs:boolean
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.
IncludeTrackSections
0:1
xs:boolean
Whether the result should include TrackSection elements to describe the geographic route of each journey leg.
The element contains one of the following elements:
a
NumberOfResultsBefore
0:1
xs:nonNegativeInteger
The desired number of trip results before the given time (at origin or destination).
a
NumberOfResultsAfter
0:1
xs:nonNegativeInteger
The desired number of trip results after the given time (at origin or destination).
b
NumberOfResults
-0:1
xs:positiveInteger
The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them.
b
NumberOfResults
-0:1
xs:positiveInteger
The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them.
TimeWindow
0:1
xs:duration
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
The way real-time data should be used in the calculation of the trip.
ImmediateTripStart
0:1
xs:boolean
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
xs:nonNegativeInteger
The maximum number of interchanges the user will accept per trip.
OptimisationMethod
0:1
The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.).
ConsiderElevationData
0:1
xs:boolean
Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE.
IncludeAllRestrictedLines
0:1
xs:boolean
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:*
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:
The element contains a sequence of the following elements:
ItModeToCover
-0:*
For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.
IncludeAlternativeOptions
-0:1
xs:boolean
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 the user expectance (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.
IncludeAllRestrictedLines
-0:1
xs:boolean
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:*
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.
b
MotorisedMainTravelMode
-0:1
xs:boolean
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.
The element contains one of the following elements:
The element contains a sequence of the following elements:
ItModeToCover
-0:*
For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions.
IncludeAlternativeOptions
-0:1
xs:boolean
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 the user expectance (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.
b
MotorisedMainTravelMode
-0:1
xs:boolean
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.
TripMobilityFilterGroup
group
| Parameters the user can set to restrict the mobility options - particularly for interchanging. | ||||
BaseTripMobilityFilter |
| 0:1 | xs:boolean | The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded. | |
Then, the element contains one of the following elements: | |||||
NumberOfResults | a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results before the given time (at origin or destination). |
a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results after the given time (at origin or destination). | |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
| 0:1 | xs:duration | 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. | ||
| 0:1 | The way real-time data should be used in the calculation of the trip. | |||
| 0:1 | xs:boolean | 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. | ||
| 0:1 | xs:nonNegativeInteger | The maximum number of interchanges the user will accept per trip. | ||
| 0:1 | The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.). | |||
| 0:1 | xs:boolean | Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE. | ||
| 0:1 | xs:boolean | 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. | ||
| 0:* | 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 |
| 1:1 | If a solution for any one of multiple origin/destination points is sufficient. Or a distinct solution for each of the origin/destination points has to be found. | ||
The element contains one of the following elements: | |||||
NumberOfResults | a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results before the given time (at origin or destination). |
a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results after the given time (at origin or destination). | |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
| 0:1 | xs:duration | 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. | ||
| 0:1 | The way real-time data should be used in the calculation of the trip. | |||
| 0:1 | xs:boolean | 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. | ||
| 0:1 | xs:nonNegativeInteger | The maximum number of interchanges the user will accept per trip. | ||
| 0:1 | The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.). | |||
| 0:1 | xs:boolean | Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE. | ||
| 0:1 | xs:boolean | 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. | ||
| 0:* | 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 |
| 1:1 | If a solution for any one of multiple origin/destination points is sufficient. Or a distinct solution for each of the origin/destination points has to be found. |
MultiPointTripResponseGroup
group
| Multi-point trip response structure. | ||||
Then, the element contains one of the following elements: | |||||
NumberOfResults | a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results before the given time (at origin or destination). |
a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results after the given time (at origin or destination). | |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
| 0:1 | xs:duration | 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. | ||
| 0:1 | The way real-time data should be used in the calculation of the trip. | |||
| 0:1 | xs:boolean | 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. | ||
| 0:1 | xs:nonNegativeInteger | The maximum number of interchanges the user will accept per trip. | ||
| 0:1 | The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.). | |||
| 0:1 | xs:boolean | Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE. | ||
| 0:1 | xs:boolean | 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. | ||
| 0:* | 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. | |||
Then, the element contains one of the following elements: | |||||
The element contains a sequence of the following elements: | |||||
TripPolicy |
| -0:* | For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions. | ||
| -0:1 | xs:boolean | 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 the user expectance (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. | ||
| -0:1 | xs:boolean | 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. | ||
| -0:* | 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. | |||
b |
| -0:1 | xs:boolean | 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. | |
Then, the element contains one of the following elements: | |||||
The element contains a sequence of the following elements: | |||||
TripPolicy |
| -0:* | For each MODE or MODE OF OPERATION combination in this list a separate monomodal trip shall be found - in addition to inter-modal solutions. | ||
| -0:1 | xs:boolean | 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 the user expectance (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. | ||
b |
| -0:1 | xs:boolean | 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. | |
BaseTripContentFilter |
| 0:1 | xs:boolean | Whether the result should include TrackSection elements to describe the geographic route of each journey leg. | |
The element contains one of the following elements: | |||||
NumberOfResults | a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results before the given time (at origin or destination). |
a |
| 0:1 | xs:nonNegativeInteger | The desired number of trip results after the given time (at origin or destination). | |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
BaseTripPolicy | b |
| -0:1 | xs:positiveInteger | The number of trip results that the user wants to see at least (TRIP REQUEST POLICY.maximumNumberofJourneys). Be aware that some implementatins will deliver one of the TripResults before the indicated departure time. This means one always has to check the results against the parameters before using them. |
| 0:1 | xs:duration | 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. | ||
| 0:1 | The way real-time data should be used in the calculation of the trip. | |||
| 0:1 | xs:boolean | 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. | ||
| 0:1 | xs:nonNegativeInteger | The maximum number of interchanges the user will accept per trip. | ||
| 0:1 | The type of algorithm to be used in the calculation of the trip (fastest, least walking, etc.). | |||
| 0:1 | xs:boolean | Whether the trip calculation should take elevation data into account (bike, foot). Default is FALSE. | ||
| 0:1 | xs:boolean | 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. | ||
| 0:* | 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. |
BaseTripMobilityFilterGroup
group
| Base mobility options to be applied for both public and individual transport. | ||||
BaseTripMobilityFilter |
| 0:1 | xs:boolean | The user is not able to pass over (or wants to avoid) single steps. Stairs and non-level entrances are not excluded. | |
| 0:1 | xs:boolean | The user is not able to walk up/down stairs. |