OTP simple built-in geocoder. Client geocoder modules usually read XML, but GeocoderBuiltin reads JSON.

The following resources are applicable:



Geocode using data using the OTP graph for stops, clusters and street names


name description type default
query The query string we want to geocode query
autocomplete Whether we should use the query string to do a prefix match query false
stops Search for stops, either by name or stop code query true
clusters Search for clusters by their name query false
corners Search for street corners using at least one of the street names query true

Response Body

element: (custom)
media types: application/json

list of results in in the format expected by GeocoderBuiltin.js in the OTP Leaflet client