Peter Johnson

I'm a little rusty on this myself so forgive me as I remember how it's configured. If you have a look in debug mode at a query such as `/v1/reverse?size=40&point.lat=0&point.lon=0&debug=1`...

Try this elasticsearch query on a fairly large Pelias index (with a few hundred million records) and see what the performance is like, I could be wrong 🤷 ``` POST...

Hi @Cerrebos, There is currently a limitation in Pelias that reverse queries for `LineString` based geometries are calculated based on distance from their midpoint (ie. a point 50% along the...

Also worth considering a routing engine such as Valhalla or Graphhopper for this task, those tools are more suited to your requirements. Pelias is capable of doing this although its...

Last year I added the ability for the interpolation service to return the nearest linestring: https://github.com/pelias/interpolation/pull/261 That functionality isn't currently being utilized in the `/v1/reverse` endpoint of `pelias/api` but it...

https://github.com/pelias/interpolation#get-streetneargeojson

Yes the interpolation service doesn't store the extended information that's available when querying the main pelias/API server. It's not a perfect solution but the IDs should line up between the...

Both these links seem to be working for me? 

woah Apr 29, 2016 :) nothing I can think of, we haven't been working on autocomplete much, at least nothing that's made it to production in the last few months.

A test-case mentioning this issue changed from fail->pass due to https://github.com/pelias/api/pull/1370 The following query now returns `New York, NY` in position 1 https://pelias.github.io/compare/#/v1/autocomplete?focus.point.lat=41.05343&focus.point.lon=-73.53873&text=New+York%2C+NY