Closed jqnatividad closed 1 year ago
it's is good option. I will take it to implement soon. But how about to build index only for set of countries? Less index size is better choice for concrete use cases.
Awesome!
IMHO, its a must have for suggest
to reduce the false positive matches.
Apart from country, you may want to also implement filters for CitiesRecord fields like admin_division, admin1_names, timezone and population while you're at it.
And I agree building an index for a set of countries is required as well.
Insofar as my use cases are concerned, I'd vote for the suggest filters over index optimization.
done. release v0.4.0 it wasn't elegant to apply new logic for suggest/reverse. especial for reverse
Thanks sooo much @estin !
geosuggest is sooo fast and its utility is far higher than the reverse-geocoder crate I was using before!
BTW @estin,, for reverse, I just realized that the country filter doesn't really make sense.
You may want to remove support for country filtering for reverse. Sorry 😦
@jqnatividad Thanks!
You may want to remove support for country filtering for reverse. Sorry 😦
No. It's may be useful to filter by countries on reverse where location nearest for country bounds.
It'd be great if both suggest and reverse results can be constrained to a provided list of countries.
This will greatly increase usability, especially for
suggest
, as it will markedly reduce false positive suggestions.