Location Information Service

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

<MessageIdentifier>4711</MessageIdentifier>

Where different designations are common, it is possible to search for any of them. For example, it is possible to search for “Basel” as well as “Bâle CFF”. For stops that have names in multiple languages, it also works if searching in only one language. For example, “Biel/Bienne” 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>

The following types exist:

• stop
• address
• poi
• coord
• topographicPlace

The main uses are stop and coord. poi will become more important over time (namely for car parks and sharers).

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

For address, the exact location name must first be determined with general input. Then exactly this name and the type “address” must be searched for. Only then will the address code be returned. However, this is a special case that should not normally be used. Neither address code nor TopographicPlaceRef have any meaningful meaning outside the searches in OJP.

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

The following values exist:

• origin
• via
• destination

This feature is not supported.

See also section on PtMode.

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

Not planned

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

Structure as shown in the example on the right:

• ojp:Tag: always amenity
• For ojp:Value: use one of escooter_rental, bicycle_rental, car_sharing or charging_station.

Note: The query should be combined with a GeoRestriction (Circle or Rectangle) and not with 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>

Planned for a future release.

Important: If a result group is cut with equal probability (>0.5), the server returns all results. This means that the actual number of results can deviate from the desired result. The reason for this is that with NumberOfResults=1 and input “St. Gallen, Haggen”, two stops must actually be returned: “St. Gallen, Haggen” and “St. Gallen Haggen”.

<NumberOfResults>10</NumberOfResults>

<IncludePTModes>true</IncludePTModes>

We do not recommend using this element because there is uncertainty about which ID is required.

<ojp:PlaceRef>
	<StopPointRef>8530813</StopPointRef>
	<ojp:LocationName>
		<ojp:Text>Zürich Kreuzplatz</ojp:Text>
	</ojp:LocationName>
</ojp:PlaceRef>

<ojp:PlaceRef>
	<ojp:StopPlaceRef>8530813</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>8508052</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 hit list is determined after the input text matches the entire dataset. 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, the candidate has a perfect match and receives the maximum probability 1. If there is still a remainder, this leads to a deduction of points. The hits found in this way can then be influenced by various evaluation criteria and quality and sorting order. Hits can be modified by region (municipality code), type (stop, address, city, 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>8508052</ojp:StopPlaceRef>
	<ojp:StopPlaceName>
		<ojp:Text>Bern Tiefenau</ojp:Text>
	</ojp:StopPlaceName>
	<ojp:TopographicPlaceRef>23006351:1</ojp:TopographicPlaceRef>
</ojp:StopPlace>

None of these should currently be returned.

This feature is currently not supported.

<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>

TODO: PointOfInterest is not currently supported.

<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 if no coordinates are available. The precision is then set to half the world circumference. 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>8508052</ojp:StopPlaceRef

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

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

<ojp:TopographicPlaceCode>suburbID:8136088:6:Bernhardsdorf:5439812:10881110:MRCV
</ojp:TopographicPlaceCode>

<ojp:TopographicPlaceName>
	<ojp:Text xml:lang="de">Bernhardsdorf</ojp:Text>
</ojp:TopographicPlaceName>