Location Information Service

<RequestTimestamp>2020-01-09T08:00:00Z</RequestTimestamp>

<MessageIdentifier>4711</MessageIdentifier>

Where different terms are common, you can search for all of them. For example, you can search for both ‘Basel’ and ‘Bâle CFF’. For stops that have information in multiple languages, it also works if you search in only one language. For example, ‘Biel’ can be found with a request for ‘Biel’ or ‘Bienne’.

<ojp:InitialInput>
	<ojp:LocationName>Bern</ojp:LocationName>
</ojp:InitialInput>

<ojp:InitialInput>
	<ojp:GeoPosition>
		<Longitude>8.5545</Longitude>
		<Latitude>47.365</Latitude>
	</ojp:GeoPosition>
</ojp:InitialInput>

<ojp:GeoRestriction>
	<ojp:Circle>
		<ojp:Center>
			<Longitude>8.5545</Longitude>
			<Latitude>47.365</Latitude>
		</ojp:Center>
		<ojp:Radius>500</ojp:Radius>
	</ojp:Circle>
</ojp:GeoRestriction>

<ojp:InitialInput>
	<ojp:GeoRestriction>
		<ojp:Rectangle>
			<ojp:UpperLeft>
				<Longitude>8.54</Longitude>
				<Latitude>47.37</Latitude>
			</ojp:UpperLeft>
			<ojp:LowerRight>
				<Longitude>8.57</Longitude>
				<Latitude>47.36</Latitude>
			</ojp:LowerRight>
		</ojp:Rectangle>
	</ojp:GeoRestriction>
</ojp:InitialInput>

There are the following types:

• stop
• address
• poi
• coord
• topographicPlace

The main uses are stop and coordination. POIs will become more important over time, such as multi-storey car parks or charging stations.

Sharing vehicles (e-scooters, bicycles, cars) and charging stations can now be queried as POIs (see ojp:PointOfInterestFilter below).

For address, first use the general input to determine the exact LocationName. Then search with this exact name and the type ‘address’. Only then does the address code come back. However, this is a special case and should not normally be used. Neither the address code nor TopographicPlaceRef have any meaning outside of OJP searches.

<ojp:Type>stop</ojp:Type>

There are the following values:

• origin
• via
• destination

This feature is not supported.

See also section for PtMode

<ojp:PtModes>
	<ojp:Exclude>true</ojp:Exclude>
	<ojp:PtMode>bus</ojp:PtMode>
	<siri:BusSubmode>localBusService</siri:BusSubmode>
</ojp:PtModes>

This feature is not supported.

<ojp:TopographicPlaceRef>23011901:2</ojp:TopographicPlaceRef>

• On ojp:Tag, always amenity
• Optional for ojp:Value escooter_rental, bicycle_rental, car_sharing or charging_station.

Please note: The query should be combined with a GeoRestriction (Circle or Rectangle), not with the LocationName, GeoPosition or PlaceRef.

<ojp:PointOfInterestFilter>
  <ojp:PointOfInterestCategory>
    <ojp:OsmTag>
      <ojp:Tag>amenity</ojp:Tag>
      <ojp:Value>escooter_rental</ojp:Value>
    </ojp:OsmTag>
  </ojp:PointOfInterestCategory>
</ojp:PointOfInterestFilter>

Not implemented in current version 1.0, planned for a later version

Important: Strings such as ‘St. Gallen Haggen’ and ‘St. Gallen, Haggen’ are equivalent for the search.

If a result group is trimmed with an equal probability (>0.5), the server returns all results. I.e. the actual number of results may differ from the desired result. The reason for this is that if NumberOfResults=1 and ‘St. Gallen, Haggen’ are entered, 2 stops must be returned: ‘St. Gallen, Haggen’ and ‘St. Gallen Haggen’.

<NumberOfResults>10</NumberOfResults>

<IncludePtModes>true</IncludePtModes>

<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>ch:1:sloid:30813</ojp:StopPlaceRef>
	<ojp:LocationName>
		<ojp:Text>Zürich Kreuzplatz</ojp:Text>
	</ojp:LocationName>
</ojp:PlaceRef>

<ojp:PlaceRef>
	<ojp:GeoPosition>
		<Longitude>8.5545</Longitude>
		<Latitude>47.365</Latitude>
	</ojp:GeoPosition>
	<ojp:LocationName>
		<ojp:Text>Zürich Kreuzplatz</ojp:Text>
	</ojp:LocationName>
</ojp:PlaceRef>

<siri:ResponseTimestamp>2020-04-03T14:47:59Z</siri:ResponseTimestamp>

<siri:RequestMessageRef>756</siri:RequestMessageRef>

<siri:Status>true</siri:Status>

<ojp:CalcTime>939</ojp:CalcTime>

<ojp:Location>
	<ojp:StopPlace>
		<ojp:StopPlaceRef>ch:1:sloid:8052</ojp:StopPlaceRef>
		<ojp:StopPlaceName>
			<ojp:Text>Bern Tiefenau</ojp:Text>
		</ojp:StopPlaceName>
		<ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef>
	</ojp:StopPlace>
	<ojp:LocationName>
		<ojp:Text xml:lang="de">Bern Tiefenau (Bern)</ojp:Text>
	</ojp:LocationName>
	<ojp:GeoPosition>
		<siri:Longitude>7.45020</siri:Longitude>
		<siri:Latitude>46.97274</siri:Latitude>
	</ojp:GeoPosition>
</ojp:Location>

<ojp:Complete>true</ojp:Complete>

The results are sorted in descending order by probability (most relevant first).

The selection of the best candidates for the list of hits is determined after the input text matches the entire database. The probability is determined by the number of matching trigrams into which the terms can be broken down and the remainder that does not match. If there is a complete match, i.e. no remainder, there is a perfect match and the candidate receives the maximum probability 1. If there is still a remainder, points are deducted. The hits found in this way can then be influenced by various evaluation criteria and by quality and sorting order. Hits can be changed based on the region (municipality code), type (stop, address, location, POI, …), serving means of transport or a relevance value.

<ojp:Probability>0.927999973</ojp:Probability>

<ojp:Mode>
	<ojp:PtMode>rail</ojp:PtMode>
	<siri:RailSubmode>unknown</siri:RailSubmode>
</ojp:Mode>
<ojp:Mode>
	<ojp:PtMode>bus</ojp:PtMode>
	<siri:BusSubmode>localBusService</siri:BusSubmode>
</ojp:Mode>

<ojp:StopPlace>
	<ojp:StopPlaceRef>ch:1:sloid:8052</ojp:StopPlaceRef>
	<ojp:StopPlaceName>
		<ojp:Text>Bern Tiefenau</ojp:Text>
	</ojp:StopPlaceName>
	<ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef>
</ojp:StopPlace>

<ojp:StopPoint>
	<siri:StopPointRef>ch:1:sloid:76558:1:3</siri:StopPointRef>
	<ojp:StopPointName>
		<ojp:Text xml:lang="de">Thun, Marktgasse</ojp:Text>
	</ojp:StopPointName>
	<ojp:PrivateCode>
		<ojp:System>EFA</ojp:System>
		<ojp:Value>119107:0:10000</ojp:Value>
	</ojp:PrivateCode>
	<ojp:ParentRef>ch:1:sloid:76558</ojp:ParentRef>
	<ojp:TopographicPlaceRef>23006942:9</ojp:TopographicPlaceRef>
</ojp:StopPoint>

<ojp:TopographicPlace>
	<ojp:TopographicPlaceCode>suburbID:8136088:6:Bernhardsdorf:5439812:10881110:MRCV</ojp:TopographicPlaceCode>
	<ojp:TopographicPlaceName>
		<ojp:Text xml:lang="de">Bernhardsdorf</ojp:Text>
	</ojp:TopographicPlaceName>
</ojp:TopographicPlace>

<ojp:Address>
	<ojp:AddressCode>streetID:382:13:23006351:1:Sempachstrasse:Bern:Sempach-strasse::Sempachstrasse:3014:ANY:DIVA_SINGLEHOUSE:830639:6064058:MRCV:sbb</ojp:AddressCode>
	<ojp:AddressName>
		<ojp:Text xml:lang="de">Bern, Sempachstrasse 13</ojp:Text>
	</ojp:AddressName>
	<ojp:PostCode>3014</ojp:PostCode>
	<ojp:TopographicPlaceName>Bern</ojp:TopographicPlaceName>
	<ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef>
	<ojp:Street>Sempachstrasse</ojp:Street>
	<ojp:HouseNumber>13</ojp:HouseNumber>
</ojp:Address>

<ojp:LocationName>
	<ojp:Text xml:lang="de">Bernina Suot (Pontresina)</ojp:Text>
</ojp:LocationName>

The example shows what comes back when there are no coordinates. The precision is then set to half the circumference of the world. Of course, we try to avoid such cases.

<ojp:GeoPosition>
	<siri:Longitude>0.0</siri:Longitude>
	<siri:Latitude>0.0</siri:Latitude>
	<siri:Precision>20000000</siri:Precision>
</ojp:GeoPosition>

<ojp:StopPlaceRef>ch:1:sloid:8052</ojp:StopPlaceRef>

<ojp:StopPlaceName>
	<ojp:Text>Bern Tiefenau</ojp:Text>
</ojp:StopPlaceName>

<ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef>