Peter Johnson

Hi @mihneadb, I think it's better to leave it as configurable on startup. Having it variable per-request could cause quality-of-service issues for cloud providers like ourselves as there would be...

Thanks @Joxit, interesting feedback, that's certainly unexpected behaviour.

Yes, please build a docker project from [pelias/docker](https://github.com/pelias/docker) and compare the differences in result quality between `pelias/api:master` and `pelias/api:fuzzy_autocomplete`. https://hub.docker.com/layers/pelias/api/fuzzy_autocomplete/images/sha256-9da0db501c473a7079e1df26569657d0bca89a3c97e0976f01a183a92b7a4f9d Let us know what's better/worse

This branch also needs to rebase `master`, I had a quick look at it and it's not a trivial task.

I'm not sure if follow, why would that be an issue? Are you saying the queries are not compatible with ES7?

The technical answer is that fuzziness increases recall at the cost of precision, and this alone does not increase relevance. The main issue is the way Lucene implements edit-distance queries...

Hi @YanDjin, this behavior is intentional. It's fairly common around the world (ie. NY county, city, state), Luxemburg, Singapore etc. We've had numerous issued filed over the years about insufficient...

wow looks cool, we will need a bit of time to test and review it! @gibranparvez would it be possible to change the links from the `venicegeo` org to something...

Hi @zeevogels thanks for writing up the feature requests for this. It's actually an interesting proposal. The 'filtering' API params (such as `boundary.rect`) apply what elasticsearch calls a "MUST" condition....

hey @dianashk I was thinking about this again and I thought I should mention that although we match on all `name.*` fields only `name.default` is returned to the user and...