Autocomplete returns by text priority

aesculus · February 3, 2019, 9:15pm

Is there any way to prioritize the results based on the text given? For example if I enter “york” I get back a bunch of New York reponses before any York* responses. I would like the responses to favor returning names that match foremost and add the additional ones after if very few of the primary are returned.

nils · February 4, 2019, 7:02am

Hi,
We use Pelias geocoding engine.

There’s quite a few ways to limit your search:

github.com

pelias/documentation/blob/master/search.md#available-search-parameters

# Pelias: Finding places

Geocoding is the process of matching an address or other text to its corresponding geographic coordinates.

All Pelias requests share the same format:

```
   https://search.mapzen.com/v1/search?text=London
   \___/   \_______________/\__/\_____/\_________/
     |            |          /     |        |
  scheme       domain   version  path     query
```

## Search the world

![Searching globally](/images/world_all.png)

In the simplest search, you can provide only one parameter, the text you want to match in any part of the location details. To do this, build a query where the `text` parameter is set to the item you want to find.

For example, if you want to find a [YMCA](https://en.wikipedia.org/wiki/YMCA) facility, here's what you'd need to append to the base URL of the service.

This file has been truncated. show original

aesculus · February 10, 2019, 12:59am

Thank you for the reply but I was asking more about the use and returns of the text. For example entering “york” should return items starting with “york” first and then when exhausted move on to returning items like “new york”.

I can sort the returns that way but I suspect there is a limit to how deep the returns are processed and perhaps many “new yorks” are getting returned in place of “york …” places.

nils · February 10, 2019, 9:03am

Yes, that’s a known issue in Pelias. They’re working towards making autocomplete work more like the search endpoint.

aesculus · February 12, 2019, 11:41pm

Cool. Looking forward to an update.