Address autocompletion query should use GET and not POST

Shouldn’t autocompletion queries use GET instead of POST? That would (e.g.) permit browser and reverse proxy cache.

[patrickallaert]

We use the user ip when he refused the precise geolocation or when it’s not available for various reasons. Then using that ip we can approximately locate the user.

I would use the following logic at HTTP caching level: IF (HTTP query contains coordinates) THEN: use an Expire header to indicate intermediate caches (reverse proxies/browser) that it can be cached for a certain amount of time ELSE no Expire header.

I have no idea how rounding would work, if it provide a good HIT ratio then why not. But if it degrades the relevancy of the API then that would be a nogo.

A simplistic approach would be to round latitude/longitude coordinates to a specific number of decimals. In the worst case (at equator), 1° is: EarthCircumference / 360 = 40075.16 km / 360 ≃ 111.32 km. Rounding latitude/longitude coordinates using 3 digits (1/1000 precision) would be rouding to 111.32 m in the worst case. I guess that this kind of service wouldn’t suffer of 1 km precision in terms of relevancy which would therefore be achieved rounding coordinates to 0.01°.

[vvo]

Hi @patrickallaert thanks for all the suggestions here, we currently think this is not a critical issue and so will close this issue.

If in the future we identify this as being realy critical we will surely need your help and advice thought. Thanks!