Find a location

VERSION 0.48.0
PUBLIC PREVIEW

Fuzzy search is the default, generic search service. It can handle vague and imprecise inputs and supply results for:

  • Areas on the map (countries, states, cities).
  • Specific addresses with a street name and number (2501 Soquel Drive, Kalverstraat 23).
  • Address ranges on streets where address points are interpolated along the length of the street.
  • Streets.
  • Junctions, places where two streets intersect.
  • Point of interest (Restaurant, Sports Center).

Fuzzy search requests are built using the SearchOptions class. You can take advantage of the default parameters in Kotlin to choose the properties that you need. The only required parameter for fuzzy search is the query parameter. The other parameters are optional.

1val query = "TomTom"
2val searchOptions =
3 SearchOptions(query, countryCodes = setOf("NLD", "PLD"), limit = 5)

To get the best experience, consider:

  • Using geoBias to perform geo-biasing, which boosts the priority of results relevant to the user’s current location.
  • Using searchAreas if geo-biasing is not strong enough to keep your results local to the user.
  • Using categoryIds to limit results to specific categories, e.g.: POIs or addresses only

More information about best practices are described here. A detailed description of fuzzy search and its parameters can be found in the Search API Fuzzy Search documentation.

Once you have a SearchOptions object, provide it to the fuzzy search request. This can be done asynchronously using the SearchCallback, or synchronously as described in Synchronous search call. If the call succeeds, the returned result is in SearchResponse. If an error occurred, it is in SearchFailure.

1search.search(
2 searchOptions,
3 object : SearchCallback {
4 override fun onSuccess(result: SearchResponse) {
5 /* YOUR CODE GOES HERE */
6 }
7
8 override fun onFailure(failure: SearchFailure) {
9 /* YOUR CODE GOES HERE */
10 }
11 }
12)

Search along the route

Search along the route allows you to perform a POI search along a specified route. This search is constrained by specifying a limit on the amount of time detours can take. If the route that passes through the found point is faster than the original one, the detour time value is negative.

The proposed detour may alter the original route, because the best detour may skip some of the original points.

To specify the request parameters, use the SearchOptions class.

1val query = "ATM"
2val searchOptions = SearchOptions(
3 query = query,
4 route = route.geometry,
5 maxDetourDuration = 600.seconds,
6 sortOrder = SortOrder.ByDetourDistance,
7 limit = 10
8)

The request can be performed synchronously or asynchronously. If you use an asynchronous call, provide an SearchCallback. A successful request returns SearchResponse. If the request fails, SearchFailure is returned.

1search.search(
2 searchOptions,
3 object : SearchCallback {
4 override fun onFailure(failure: SearchFailure) {
5 /* YOUR CODE GOES HERE */
6 }
7
8 override fun onSuccess(result: SearchResponse) {
9 /* YOUR CODE GOES HERE */
10 }
11 }
12)
center

Autocomplete

Autocomplete helps users make more effective searches. It recognizes entities inside an input query and offers them as query terms. This improves the accuracy of the search results.

Autocomplete requests are built using the AutocompleteOptions class. The required parameter is the query for which autocomplete results should be returned. You can also provide optional parameters to perform a more accurate search, following similar recommendation as for fuzzy search. See the Search API Autocomplete documentation for more information.

1val query = "Sport"
2val amsterdam = GeoPoint(52.379189, 4.899431)
3val autocompleteOptions = AutocompleteOptions(
4 query = query,
5 locale = Locale("en", "US"),
6 position = amsterdam,
7 radius = Distance.meters(5000)
8)

Once you have a AutocompleteOptions object, provide it to the autocomplete search request. This can be done asynchronously using the AutocompleteCallback, or synchronously as described in Synchronous search call. If the call succeeds, the returned result is in AutocompleteResponse. If an error occurred, it is in SearchFailure.

1search.autocompleteSearch(
2 autocompleteOptions,
3 object : AutocompleteCallback {
4 override fun onSuccess(result: AutocompleteResponse) {
5 /* YOUR CODE GOES HERE */
6 }
7
8 override fun onFailure(failure: SearchFailure) {
9 /* YOUR CODE GOES HERE */
10 }
11 }
12)

Search with geographical filter

The search with geographical filter for search results allows you to perform a free-form search inside one or more defined geographic areas (geometries).

The following types of geometries are supported:

  • PolygonGeometry - A polygon defined by an array of coordinates representing the vertices of the polygon.
    1val vertices = listOf(
    2 GeoPoint(52.372069, 4.893175),
    3 GeoPoint(52.370225, 4.895390),
    4 GeoPoint(52.372790, 4.899520),
    5 GeoPoint(52.374656, 4.896207),
    6 GeoPoint(52.372069, 4.893175)
    7)
    8val polygonGeometry = PolygonGeometry(vertices)
  • CircleGeometry - A circle defined by a center coordinate and its radius in meters.
    1val center = GeoPoint(52.214555, 5.188332)
    2val radius = Distance.meters(1000)
    3val circleGeometry = CircleGeometry(center, radius)
  • RectangleGeometry - A rectangle defined by its top left and bottom right coordinates.
    1val rectangleGeometry = RectangleGeometry(
    2 boundingBox = GeoBoundingBox(
    3 topLeft = GeoPoint(52.269216, 4.723318),
    4 bottomRight = GeoPoint(52.235761, 4.810460)
    5 )
    6)

Provide the geometries and query to the constructor of the SearchOptions by defining the searchAreas parameter. You can also define optional parameters such as the number of results to return, language, and various search constraints. More information about optional parameters and the geometry search can be found in the Search API Geometry Search documentation.

1val query = "Restaurant"
2val geometrySearchOptions = SearchOptions(
3 query = query,
4 searchAreas = setOf(polygonGeometry, circleGeometry, rectangleGeometry)
5)

The search call can be done synchronously or asynchronously. Calling it asynchronously requires a SearchCallback, to handle the response. If the search is successful, the response is a SearchResponse object. Otherwise, error information is returned as a SearchFailure.

1search.search(
2 geometrySearchOptions,
3 object : SearchCallback {
4 override fun onSuccess(result: SearchResponse) {
5 /* YOUR CODE GOES HERE */
6 }
7
8 override fun onFailure(failure: SearchFailure) {
9 /* YOUR CODE GOES HERE */
10 }
11 }
12)

Search with geometry data request

A Geometry data request is used to obtain geometries that represent the outline of a city, county, or land area. The request supports batch requests for up to twenty (20) identifiers per call. The request with more then twenty (20) identifiers will fail. To build the geometry data request, use the GeometryDataOptions class. The only required parameter is a list of identifiers for which you want geometry. To obtain these identifiers, you must first get the SearchResultId of a fuzzy search. Then use its geometryId property to get the geometry ID.

Not every SearchResult has a geometry ID.

val geometries = fuzzySearchResponse.results.mapNotNull { it.searchResultId.geometryId }

You can provide an optional zoom level parameter, which defines the precision of the returned geometries. For more information about the additional data search, go to the Search API Additional Data Search documentation.

1val geometryDataOptions = GeometryDataOptions(
2 geometryIds = geometries,
3 geometryZoom = null
4)

Once the GeometryDataOptions object is built, you can perform either a synchronous or asynchronous request. The call returns an GeometryDataResponse object, or a SearchFailure if the request was unsuccessful.

1search.requestGeometryData(
2 geometryDataOptions,
3 object : GeometryDataCallback {
4 override fun onSuccess(result: GeometryDataResponse) {
5 /* YOUR CODE GOES HERE */
6 }
7
8 override fun onFailure(failure: SearchFailure) {
9 /* YOUR CODE GOES HERE */
10 }
11 }
12)

Next steps

Since you have learned how to work with search, here are recommendations for the next steps: