The figures below show various search texts entered by the end user and the list of suggestions in the Geocoder Autocomplete API response. The highlights mark the parts of the suggestions that match the search text. The highlighting shown here is based on the mark-up provided with each request for suggestions (in the beginHighlight and endHighlight request parameters). Client applications can implement their own highlighting, modify the mark-up, or simply ignore it.
Requesting Suggestions without Spatial Filtering
Figure 1. With a Partial NameFigure 2. With a Street Name and a Partial District NameFigure 3. With a Preposition Omitted in the Street NameFigure 4. With Special Characters: è vs e ...Figure 5. With Special Characters: ß vs ss ...Figure 6. With an Intersection Query: (query=5th ave @ 9th)
The service returns intersections for queries containing a street name followed by and, at, & or @. Currently, intersection queries are supported for queries on USA only.
Figure 7. With an Intersection Query Using "at" as a Separator: (query=Haight at Ma)
Requesting Suggestions with Spatial Filtering
You can use various types of spatial filtering to specify a context for the suggestions.
The figure below illustrates a request made without the country filter. Figure 8. Without a Country Filter
The figure below illustrates the same request, but this time with the request parameter country set to France (country=FRA). Figure 9. With a Country Filter
The figure below illustrates a request made without the mapview filter. Figure 10. Without a Mapview Filter
The figure below illustrates the same request, but this time with the mapview parameter set to Montréal, Québec(mapview=46.0346628,-74.3384855;45.2173875,-73.043472). Figure 11. With a Mapview Filter