OJPTripRequest

#AutoTranslate

Brief Description

TripRequest is the main service. A trip can be planned by specifying the origin and destination.

A trip has multiple legs (sections).

Functional Description

The modelling of a journey consists of the following components:

Stops: The data sets are also available for this purpose Departments.
Journeys: A journey is the transport of customers on a specific route, a specific timetable connection, with a specific means of transport (vehicle), at a specific time, in a specific direction.
Timetable: A timetable defines the route of a means of transport in local and long-distance public passenger transport and in rail freight transport. The necessary information includes train number, days of operation, route, arrival, departure and transit times at stops as well as the permissible speeds in the individual sections of the route.
Forecast: Forecasts are the future travel times of a journey based on the vehicle’s current location. Established algorithms are used to calculate forecasts in the near future, taking many factors into account. As the forecast proceeds, fewer factors are taken into account.

Technical Description

API Explorer

You can try out your own requests – direct link to API Explorer.

Request

<?xml version="1.0" encoding="UTF-8"?>
<OJP xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns="http://www.siri.org.uk/siri" version="1.0" 
xmlns:ojp="http://www.vdv.de/ojp" xsi:schemaLocation="http://www.siri.org.uk/siri ../ojp-xsd-v1.0/OJP.xsd">
    <OJPRequest>
        <ServiceRequest>
			<RequestTimestamp>2020-01-31T12:30:00Z</RequestTimestamp>
            <RequestorRef>3CC3C04A-20A0-4B12-AC46-5A7843E328A7</RequestorRef>
            <ojp:OJPTripRequest>
				<RequestTimestamp>2020-01-31T12:30:00Z</RequestTimestamp>
                <ojp:Origin>
                    <ojp:PlaceRef>
                        <ojp:StopPlaceRef>ch:1:sloid:3000</ojp:StopPlaceRef>
                        <ojp:LocationName>
                            <ojp:Text>Bern</ojp:Text>
                        </ojp:LocationName>
                    </ojp:PlaceRef>
                </ojp:Origin>
                <ojp:Destination>
                    <ojp:PlaceRef>
                        <ojp:StopPlaceRef>ch:1:sloid:5000</ojp:StopPlaceRef>
                        <ojp:LocationName>
                            <ojp:Text>Luzern</ojp:Text>
                        </ojp:LocationName>
                    </ojp:PlaceRef>
                </ojp:Destination>
                <ojp:Params>
                    <ojp:NumberOfResults>10</ojp:NumberOfResults>
                    <ojp:OptimisationMethod>fastest</ojp:OptimisationMethod>
                </ojp:Params>
            </ojp:OJPTripRequest>
        </ServiceRequest>
    </OJPRequest>
</OJP>

Item	Cardinality	Description	Example
`RequestTimestamp`	1:1	The Timestamp of the request in ISO 8601 format. Preferably in UTC.	<RequestTimestamp>2020-01-31T12:30:00Z</RequestTimestamp>
`MessageIdentifier`	0:1	The Identifier the message. Preferably strictly monotonically increasing.	<MessageIdentifier>756</MessageIdentifier>
`ojp:Origin`	1:*	The starting point of the trip request. OJP offers several ways to describe this element. More information in the relevant section	<ojp:Origin> <ojp:PlaceRef> <ojp:StopPlaceRef>ch:1:sloid:3000</ojp:StopPlaceRef> <ojp:LocationName> <ojp:Text>Bern</ojp:Text> </ojp:LocationName> </ojp:PlaceRef> <ojp:DepArrTime>2020-01-20T12:00:00Z</ojp:DepArrTime> </ojp:Origin>
`ojp:Destination`	1:*	The destination of the journey request. OJP offers several ways to describe this element. More information can be found in the relevant section.	<ojp:Destination> <ojp:PlaceRef> <ojp:StopPlaceRef>ch:1:sloid:5000</ojp:StopPlaceRef> <ojp:LocationName> <ojp:Text>Luzern</ojp:Text> </ojp:LocationName> </ojp:PlaceRef> <ojp:DepArrTime>2020-01-20T12:00:00Z</ojp:DepArrTime> </ojp:Destination>
`ojp:Via`	0:1	A single ‘via’ is supported. If several via points have to be included or a round trip has to be calculated, the request must be divided into several trips for the request.	<ojp:Via> <ojp:ViaPoint> <StopPointRef>ch:1:sloid:6000</StopPointRef> <ojp:LocationName> <ojp:Text>Winterthur</ojp:Text> </ojp:LocationName> </ojp:ViaPoint> </ojp:Via>
`ojp:Params`	0:1	The other parameters. See the corresponding section.	<ojp:Params> <ojp:IncludeTrackSections>true</ojp:IncludeTrackSections> <ojp:IncludeLegProjection>true</ojp:IncludeLegProjection> <ojp:IncludeTurnDescription>true</ojp:IncludeTurnDescription> <ojp:IncludeAccessibility>true</ojp:IncludeAccessibility> <ojp:IncludeIntermediateStops>true</ojp:IncludeIntermediateStops> <ojp:IncludeFare>true</ojp:IncludeFare> </ojp:Params>

Origin/Destination structure

Elements	Cardinality	Description	Example
`ojp:PlaceRef/siri:StopPointRef`	0:1	Reference to StopPoint. Only SLOID will be used; for foreign StopPoints, the BPUIC number can still be used in the request and in the response. More Information.	<ojp:PlaceRef> <StopPointRef>ch:1:sloid:30813</StopPointRef> <ojp:LocationName> <ojp:Text>Zürich Kreuzplatz</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:PlaceRef/ojp:StopPlaceRef`	0:1	Reference to a stop. Only the SLOID will be used; for foreign StopPoints, the BPUIC number can still be used in the request and in the response. More Information.	<ojp:PlaceRef> <StopPointRef>ch:1:sloid:30813</StopPointRef> <ojp:LocationName> <ojp:Text>Zürich Kreuzplatz</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:PlaceRef/ojp:GeoPosition`	0:1	WGS84 coordinates	<ojp:PlaceRef> <ojp:GeoPosition> <Longitude>8.484003</Longitude> <Latitude>47.386135</Latitude> </ojp:GeoPosition> <ojp:LocationName> <ojp:Text>Altstetten</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:PlaceRef/ojp:TopographicPlaceRef`	0:1	Reference to a Location. Difficult because the values cannot be guessed	<ojp:PlaceRef> <ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef> <ojp:LocationName> <ojp:Text>Bern (Bern)</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:PlaceRef/ojp:PointOfInterestRef`	0:1	Reference to a Point of Interest. The Location Name is ignored.	<ojp:PlaceRef> <ojp:PointOfInterestRef>1</ojp:PointOfInterestRef> <ojp:LocationName> <ojp:Text>unbekannt</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:PlaceRef/ojp:AddressRef`	0:1	Reference to an address.	<ojp:PlaceRef> <ojp:AddressRef> <ojp:AddressCode>streetID:1500000041::23020227:-1:Via al Dosso:Torricella-Taverne:Via al Dosso::Via al Dosso: 6807:ANY:DIVA_STREET:994668:6208464:MRCV:sbb</ojp:AddressCode> </ojp:>AddressRef </ojp:PlaceRef>
`ojp:PlaceRef/ojp:LocationName`	1:1	Public name of the place Please note: The name is ignored. First perform a LocationRequest, which will return a reference or coordinate!	<ojp:PlaceRef> <StopPointRef>ch:1:sloid:3003</StopPointRef> <ojp:LocationName> <ojp:Text>Zürich Stadelhofen</ojp:Text> </ojp:LocationName> </ojp:PlaceRef>
`ojp:DepArrTime`	0:1	Time to be used. ‘Z’ stands for Zulu Time (independent of any time zone). For Z, the seconds must also be specified. If the format is not correct or if there is no Z, the system tries to interpret the time as local time.	<ojp:DepArrTime>2020-01-20T12:00:00Z</ojp:DepArrTime>
`ojp:TimeAllowance`	0:1	Instead of DepArrTime. Additional time required to reach and leave the location.	<ojp:TimeAllowance>PT2H</ojp:TimeAllowance>
`IndividualTransportOptions`	0:*	Options for travelling to and from the stops See separate table	<ojp:IndividualTransportOptions> <ojp:Mode>walk</ojp:Mode> <ojp:MaxDistance>5000</ojp:MaxDistance> <ojp:MaxDuration>PT1H</ojp:MaxDuration> <ojp:Speed>120</ojp:Speed> </ojp:IndividualTransportOptions>

IndividualTransportOptions

Elements	Cardinality	Description	Example
`ojp:Mode`	1:1	The mode to be used to reach the origin. At the moment, only walk is supported. Other values: walk cycle taxi self-drive-car others-drive-car motorcycle truck	<ojp:Mode>walk</ojp:Mode>
`ojp:MaxDistance`	0:1	Maximum distance in metres. This minimises the routes.	<ojp:MaxDistance>10000</ojp:MaxDistance>
`ojp:MaxDuration`	0:1	Maximum duration. Indicates the maximum duration of the router. Please note the format. It is xs:duration.	<ojp:MaxDuration>PT2H</ojp:MaxDuration>
`ojp:MinDistance`	0:1	Minimum distance in metres. This minimises the routes. This feature is not supported.	<ojp:MinDistance>1</ojp:MinDistance>
`ojp:MinDuration`	0:1	Minimum duration. Indicates the minimum duration of the router. Please note the format. It is xs:duration. This feature is not supported.	<ojp:MinDuration>PT1S</ojp:MinDuration>
`ojp:Speed`	0:1	Relative speed in percent. Normal is 100%.	<ojp:Speed>100</ojp:Speed>

Params

Elements	Cardinality	Description	Example
`ojp:PtModeFilter`	0:1	The filter indicates which modes are to be taken into account. The mode lists are given in the XSD. Filtering for submodes has no effect.	<ojp:PtModeFilter> <ojp:Exclude>true</ojp:Exclude> <ojp:PtMode>rail</ojp:PtMode> </ojp:PtModeFilter>
`ojp:LineFilter`	0:1	Lines to be included or excluded.	<ojp:LineFilter> <ojp:Line> <LineRef>sbb:92080::R</LineRef> </ojp:Line> <ojp:Line> <LineRef>sbb:91012:B:H</LineRef> </ojp:Line> <ojp:Exclude>true</ojp:Exclude> </ojp:LineFilter>
`ojp:OperatorFilter`	0:1	Operators to be included or excluded.	<ojp:OperatorFilter> <ojp:Exclude>false</ojp:Exclude> <ojp:OperatorRef>sbb:11:SchweizerischeBundesbahnenSBB</ojp:OperatorRef> </ojp:OperatorFilter>
`ojp:PrivateModeFilter`	0:1	Use private modes or not. This feature is not available.	n/a
`ojp:NoSingleStep`	0:1	The user cannot cross a paragraph. This feature is not available.	n/a
`ojp:NoStairs`	0:1	The user cannot navigate stairs. This feature is not available.	n/a
`ojp:NoEscalator`	0:1	The user cannot navigate an escalator. This feature is not available.	n/a
`ojp:NoElevator`	0:1	The user cannot use an elevator. This feature is not available.	n/a
`ojp:NoRamp`	0:1	The user cannot navigate a ramp This feature is not available.	n/a
`ojp:LevelEntrance`	0:1	The user requires entrances/transitions at ground level This feature is not available.	n/a
`ojp:BikeTransport`	0:1	The user wants to take a bicycle with him This feature is not available.	n/a
`ojp:WalkSpeed`	0:	Deviation from normal running speed. 100% normal. This feature is not available.	n/a
`ojp:NumberOfResults`	0:1	If results are weighted equally by the search algorithm, more results are returned. If the desired number of connections cannot be found, fewer results are returned. Otherwise, the desired number of results is returned.	<ojp:NumberOfResults>10</ojp:NumberOfResults>
`ojp:NumberOfResultsBefore`	0:1	Number of results before a given time (at the finish line or at the start). If an OJP client wishes to receive an earlier departure time for the journeys it has received, it must send a new request stating NumberOfResultsBefore=n and Destination.DepArrTime = earliest EndTime found in the last response minus 1 minute.	<ojp:NumberOfResultsBefore>4</ojp:NumberOfResultsBefore>
`ojp:NumberOfResultsAfter`	0:1	Number of results after a given time (at the finish line or at the start). If an OJP client wishes to receive a later date in relation to the journeys already received, it must send a new request with NumberOfResultsAfter=n and Origin.DepArrTime = latest StartTime found in the last response, plus 1 minute.	<ojp:NumberOfResultsAfter>6</ojp:NumberOfResultsAfter>
`ojp:IgnoreRealtimeData`	0:1	Do you want to include real-time data?	<ojp:IgnoreRealtimeData>true</ojp:IgnoreRealtimeData>
`ojp:ImmediateTripStart`	0:1	Assume that the user is already on the way? Not supported.	n/a
`ojp:TransferLimit`	0:1	Maximum number of changes	<ojp:TransferLimit>3</ojp:TransferLimit>
`ojp:OptimisationMethod`	0:1	Which optimization method should be used? fastest, least walking, etc. This feature is not available.	n/a
`ojp:ItModesToCover`	0:*	Find a separate monomodal trip for each mode in the list, in addition to the intermodal trips. Supported for sharing services since August 2022.	See section on sharing below.
`ojp:IncludeTrackSection`	0:1	Whether the result should contain TrackSection elements to describe the geographic course of this vehicle journey.	<ojp:IncludeTrackSections>true</ojp:IncludeTrackSections>
`ojp:IncludeLegProjection`	0:1	Include the geographical presentation of a leg in the result.	<ojp:IncludeLegProjection>true</ojp:IncludeLegProjection>
`ojp:IncludeTurnDescription`	0:1	A detailed description of the route for each leg is provided in the PathGuidance.	<ojp:IncludeTurnDescription>true</ojp:IncludeTurnDescription>
`ojp:IncludeAccessibility`	0:1	Include disability information.	<ojp:IncludeAccessibility>true</ojp:IncludeAccessibility>
`ojp:IncludeIntermediateStops`	0:1	Indicates whether stops should also be specified along the individual trip, i.e. all the intermediate stops.	<ojp:IncludeIntermediateStops>true</ojp:IncludeIntermediateStops>
`ojp:IncludeFare`	0:1	Include price information. This feature is currently not supported.	<ojp:IncludeFare>true</ojp:IncludeFare>
`ojp:Extension`	0:1	Used for certain sharing modes.	See section on sharing below.

Response

An example of a whole answer: tripresponse

First, ojp:TripResponseContext is returned. It contains information on all the places used (stops, locations, addresses, etc.) in the ojp:Places element:

<ojp:Location>
	<ojp:StopPlace>
		<ojp:StopPlaceRef>8591252</ojp:StopPlaceRef>
		<ojp:StopPlaceName>
			<ojp:Text>Zürich, Letzigrund</ojp:Text>
		</ojp:StopPlaceName>
		<ojp:TopographicPlaceRef>23026261:27</ojp:TopographicPlaceRef>
	</ojp:StopPlace>
	<ojp:LocationName>
		<ojp:Text xml:lang="de">Zürich, Letzigrund</ojp:Text>
	</ojp:LocationName>
	<ojp:GeoPosition>
		<siri:Longitude>8.50373</siri:Longitude>
		<siri:Latitude>47.38124</siri:Latitude>
	</ojp:GeoPosition>
</ojp:Location>

In future, the context may also include the situations (faults).

This is followed by 0:* TripResult. After the header

<ojp:TripResult>
	<ojp:ResultId>ID-153A06C3-1F00-4048-9141-A217840479A6</ojp:ResultId>
	<ojp:Trip>
		<ojp:TripId>ID-153A06C3-1F00-4048-9141-A217840479A6</ojp:TripId>
		<ojp:Duration>PT29M</ojp:Duration>
		<ojp:StartTime>2020-01-20T11:57:00Z</ojp:StartTime>
		<ojp:EndTime>2020-01-20T12:26:00Z</ojp:EndTime>
		<ojp:Transfers>1</ojp:Transfers>
<!-- ... -->

individual trips will follow.

If the route to and from a stop is not routed, the continuous legs leading to the stop are shown first.

Otherwise, a TimedLeg comes.

<ojp:TripLeg>
	<ojp:LegId>1</ojp:LegId>
	<ojp:TimedLeg>
		<ojp:LegBoard>
			<siri:StopPointRef>ch:1:sloid:91252</siri:StopPointRef>
				<ojp:StopPointName>
					<ojp:Text>Zürich, Letzigrund</ojp:Text>
				</ojp:StopPointName>
				<ojp:ServiceDeparture>
					<ojp:TimetabledTime>2020-01-20T11:57:00Z</ojp:TimetabledTime>
				</ojp:ServiceDeparture>
				<ojp:Order>1</ojp:Order>
		</ojp:LegBoard>
		<ojp:LegIntermediates>
			<siri:StopPointRef>ch:1:sloid:91038</siri:StopPointRef>
			<ojp:StopPointName>
				<ojp:Text>Zürich, Albisriederplatz</ojp:Text>
			</ojp:StopPointName>
			<ojp:ServiceArrival>
				<ojp:TimetabledTime>2020-01-20T11:59:00Z</ojp:TimetabledTime>
			</ojp:ServiceArrival>
			<ojp:ServiceDeparture>
				<ojp:TimetabledTime>2020-01-20T11:59:00Z</ojp:TimetabledTime>
			</ojp:ServiceDeparture>
			<ojp:Order>2</ojp:Order>
		</ojp:LegIntermediates>
<!-- weitere LegIntermediate --->
		<ojp:LegAlight>
			<siri:StopPointRef>ch:1:sloid:91105</siri:StopPointRef>
			<ojp:StopPointName>
				<ojp:Text>Zürich, Bürkliplatz</ojp:Text>
			</ojp:StopPointName>
			<ojp:ServiceArrival>
				<ojp:TimetabledTime>2020-01-20T12:13:00Z</ojp:TimetabledTime>
			</ojp:ServiceArrival>
			<ojp:Order>11</ojp:Order>
		</ojp:LegAlight>
		<ojp:Service>
			<ojp:OperatingDayRef>2020-01-20</ojp:OperatingDayRef>
			<ojp:JourneyRef>sbb:91002::H:j20:1253</ojp:JourneyRef>
			<siri:LineRef>sbb:91002:</siri:LineRef>
			<siri:DirectionRef>H</siri:DirectionRef>
			<ojp:Mode>
				<ojp:PtMode>tram</ojp:PtMode>
				<siri:TramSubmode>cityTram</siri:TramSubmode>
				<ojp:Name>
					<ojp:Text xml:lang="de">Tram</ojp:Text>
				</ojp:Name>
			</ojp:Mode>
			<ojp:PublishedLineName>
				<ojp:Text>2</ojp:Text>
			</ojp:PublishedLineName>
			<ojp:OperatorRef>sbb:3849</ojp:OperatorRef>
			<ojp:Attribute>
				<ojp:Text>
					<ojp:Text xml:lang="de">Niederflureinstieg</ojp:Text>
				</ojp:Text>
				<ojp:Code>A__NF</ojp:Code>
			</ojp:Attribute>
			<ojp:DestinationStopPointRef>de:00000:-1</ojp:DestinationStopPointRef>
			<ojp:DestinationText>
				<ojp:Text xml:lang="de">Zürich Tiefenbrunnen, Bahnhof</ojp:Text>
			</ojp:DestinationText>
		</ojp:Service>
	</ojp:TimedLeg>
</ojp:TripLeg>

Comments:

All XXXRefs are being gradually updated with the new stable Swiss identifiers SID4PT.
The attributes are formed from the known attributes from HRDF starting with A__ . The names are derived from the Traffic notices derived. In some cases, these also correspond to a combination of SIRI facilities. The mapping is carried out in accordance with Notes2FacilitiesMappingFile not all are present in OJP 1.0. In such cases, no mapping is carried out.

Some points are realized by means of extensions:

Name for the (e.g. ‘train’) transport mode (transport category, download from https://data.opentransportdata.swiss/dataset/vm-liste)
ShortName (e.g. ‘IC’) Transport submode Abbreviation (offer category short reference., download at https://data.opentransportdata.swiss/dataset/vm-liste)
PublishedLineName (e.g. ‘IC8’ or ‘S1’) passenger relevant route text
TimedLeg.Extension.TransportTypeName (e.g. ‘InterCity’) Transport submode name (offer category name, download at https://data.opentransportdata.swiss/dataset/vm-liste)
TimedLeg.Extension.PublishedJourneyNumber (e.g. ‘829’) Train number
TimedLeg.Extension.OperatorName (e.g. ‘Swiss Federal Railways SBB’) OperatorName

When changing TransferLegs used:

<ojp:TransferLeg>
	<ojp:TransferMode>walk</ojp:TransferMode>
	<ojp:LegStart>
		<siri:StopPointRef>ch:1:sloid:91105</siri:StopPointRef>
		<ojp:LocationName>
			<ojp:Text xml:lang="de">Zürich, Bürkliplatz</ojp:Text>
		</ojp:LocationName>
	</ojp:LegStart>
	<ojp:LegEnd>
		<siri:StopPointRef>ch:1:sloid:91105</siri:StopPointRef>
		<ojp:LocationName>
			<ojp:Text xml:lang="de">Zürich, Bürkliplatz</ojp:Text>
		</ojp:LocationName>
	</ojp:LegEnd>
	<ojp:TimeWindowStart>2020-01-20T12:13:00Z</ojp:TimeWindowStart>
	<ojp:TimeWindowEnd>2020-01-20T12:15:00Z</ojp:TimeWindowEnd>
	<ojp:Duration>PT2M</ojp:Duration>
	<ojp:WalkDuration>PT2M</ojp:WalkDuration>
	<ojp:BufferTime>PT0M</ojp:BufferTime>
</ojp:TransferLeg>

Improvements will be needed especially for transfers in line with the Disability Discrimination Act.

Geographical information used

The footpath routing is based on OpenStreetMap (OSM). The following parts are currently based on OSM only:

In ContinuousLeg and TransferLeg (TransferMode=walk):

TrackSection
TurnAction
in TimedLeg
Leg intermediate
IncludeAccessibility

OSM data are available at Open Data Commons Open Database License (ODbL). Applications that use OSM must cite OSM as the source. How this should be done is set out in the policy below OSM Attribution Guidelines.

OJP TripRequest with sharing providers

Since August 2022, OJP TripRequest can be used to calculate travel chains with sharing vehicles (bicycles, e-scooters, rental bikes or carshares) at the start and/or end (first and/or last mile).

General information

For the time being, the functionality is experimental in nature. This may result in unexpected or impractical travel chains. The SKI+ team will be happy to receive feedback.

As far as possible, elements of the OJP-1.0 standard were used. However, some extensions had to be implemented using extensions. With the introduction of the OJP 2.0 protocol, multi- and intermodality will be implemented as defined in the standard.

The calculations are based on this Data source.

The locations of the sharing vehicles can also be accessed using the following service: OJPLocationInformationRequest

Parameters to control TripRequest

The query in TripRequest is controlled by parameters (additional XML elements) at four possible places:

1. Monomodal travel by bicycle

According to OJP-1.0 standard for this purpose <ojp:Params> is supplemented with the <ojp:ItModesToCover> element, with the value ‘cycle’:

<ojp:ItModesToCover>cycle</ojp:ItModesToCover>

2. Monomodal travel by e-scooter, rental bike or car sharing

<ojp:Params> is used with a Extension expanded:

<ojp:Extension> ...
  <ojp:ItModesToCover>escooter_rental</ojp:ItModesToCover> ...
</ojp:Extension>

with ‘escooter_rental,’ ‘bicycle_rental’ or ‘car_sharing,’ or

3. Intermodal journeys by public transport and by bike at the start and/or end

According to OJP-1.0 standard <ojp:Origin> and/or <ojp:Destination> are given the element <ojp:IndividualTransportOptions>. It defines the mode (cycle), min/max duration in minutes and min/max distance in metres, as shown in the example below.

<ojp:IndividualTransportOptions>
  <ojp:Mode>cycle</ojp:Mode> <!--Fahrrad am Anfang -->
  <ojp:MaxDuration>PT30M</ojp:MaxDuration> <!--Optional: maximale Dauer -->
  <ojp:MinDuration>PT2M</ojp:MinDuration> <!--Optional: minimale Dauer -->
  <ojp:MaxDistance>20000</ojp:MaxDistance> <!--Optional: maximale Fahrdistanz -->
  <ojp:MinDistance>100</ojp:MinDistance> <!--Optional: minimale Fahrdistanz -->
</ojp:IndividualTransportOptions>

4. Intermodal journeys by public transport and with e-scooters, rental bikes or car sharing to start and/or end

<ojp:Params> is used with a Extension extended, analogously with <ojp:Origin> and/or <ojp:Destination> and with the modes escooter_rental, bicycle_rental or car_sharing, or as shown in the following example:

<ojp:Extension>
  <ojp:Origin>
    <ojp:Mode>escooter_rental</ojp:Mode> <!--eScooter zu Beginn-->
    <ojp:MaxDuration>PT30M</ojp:MaxDuration> <!--Optional: maximale Dauer-->
    <ojp:MinDuration>PT2M</ojp:MinDuration> <!--Optional: minimale Dauer-->
    <ojp:MaxDistance>20000</ojp:MaxDistance> <!--Optional: maximale Fahrdistanz-->
    <ojp:MinDistance>100</ojp:MinDistance> <!--Optional: minimale Fahrdistanz-->
  </ojp:Origin>
</ojp:Extension>

Overview of possible combinations

The following table shows which combinations are useful for monomodal and multimodal journeys. (Please note: public transport is considered as one mode here, even if it involves different means of transport and changes):

Combination	Monomodal journey	Multimodal — Mode at the start	Multimodal — End mode	Start & End Mode
*public transport*	`(default)`	—	—	—
*on foot*	`ItModesToCover=walk oder IndividualTransportOptions=walk (Wanderungen, s. oben)`	`(default)`	`(default)`	`(default)`
*with your own bike*	`ItModesToCover= cycle`	`IndividualTransportOptions ... Mode=cycle`	—	—
*with your own car*	`ItModesToCover= self-drive-car`	—	—	—
*Bicycle Sharing*	`Ext./ItModesToCover= bicycle_rental`	`Ext./Origin/Mode= bicycle_rental`	`Ext./Destin./Mode= bicycle_rental`	possible if Origin and Destin are the same. Modes
*e-Scooter Sharing*	`Ext./ItModesToCover= escooter_rental`	`Ext./Origin/Mode= escooter_rental`	`Ext./Destin./Mode= escooter_rental`	possible if Origin and Destin are the same. Modes
*Car Sharing*	`Ext./ItModesToCover= car_sharing`	—	`Ext./Destin./Mode= car_sharing`	—

Search for car tunnel hoists

Example of a request for a car tunnel drawbar (ATZ):

<siri:OJP xmlns="http://www.vdv.de/ojp" xmlns:siri="http://www.siri.org.uk/siri" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://www.vdv.de/ojp" version="1.0">  <siri:OJPRequest>
    <siri:ServiceRequest>
      <siri:RequestTimestamp>2024-03-21T16:22:30.112Z</siri:RequestTimestamp>
      <siri:RequestorRef>OJP_JS_SDK_v0.9.31</siri:RequestorRef>
      <OJPTripRequest>
        <siri:RequestTimestamp>2024-03-21T16:22:30.112Z</siri:RequestTimestamp>
        <Origin>
          <PlaceRef>
            <StopPlaceRef>ch:1:sloid:11171</StopPlaceRef>
            <LocationName>
              <Text>Kandersteg Autoverlad</Text>
            </LocationName>
          </PlaceRef>
        </Origin>
        <Destination>
          <PlaceRef>
            <StopPlaceRef>ch:1:sloid:19655</StopPlaceRef>
            <LocationName>
              <Text>Goppenstein Autoverlad</Text>
            </LocationName>
          </PlaceRef>
        </Destination>
      <ojp:Params>
            <ojp:PrivateModeFilter>
                  <ojp:Exclude>false</ojp:Exclude>
            </ojp:PrivateModeFilter>
            <ojp:NumberOfResults>3</ojp:NumberOfResults>
      <ojp:IncludeTrackSections>false</ojp:IncludeTrackSections>
      <ojp:IncludeLegProjection>false</ojp:IncludeLegProjection>
      <ojp:IncludeTurnDescription>false</ojp:IncludeTurnDescription>
      <ojp:IncludeIntermediateStops>true</ojp:IncludeIntermediateStops>
      </ojp:Params>
      </OJPTripRequest>
    </siri:ServiceRequest>
  </siri:OJPRequest>
</siri:OJP>

Table of contents

Search on the page