Issue 79: "blurred" position in get parameter
Project Member Reported by mixare.org, Mar 4, 2011
As User i would like to see something like a "blurred" Position (exact
Position via GET-Parameters could be fetched by anyone!).

(mail from Chris of 2011.02.14)

Mar 4, 2011
Project Member #1 mixare.org
I find that the GPS is already adding enough noise to the requests :-)

Jokes apart, this can be added in the settings...
May 8, 2011
#2 stiller....@googlemail.com
If you want do that, i found a neat way to do that blurring:
OSM needs some Math for Tile-Numers:
http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames
just do Math.round instead of Math.floor at the right place and you are done :-) 

Instead of latitude, longitude and radius a query could use z, x, y.
Lower zoom-level means a bigger bounding-box and more blurring.
the bounding-box consists of 4 "Tiles" where the lower right "Tile" is defined by x/y.

This way, your data could easily be cached (and re-mapped serverside)!

chris

Apr 23, 2012
Project Member #3 mixare.org
(No comment was entered for this change.)
Status: Accepted
Owner: daniele.gobbetti
Labels: Version-AndroidRelease0.9
Jun 20, 2012
Project Member #4 daniele.gobbetti
 Issue 128  has been merged into this issue.
Jun 20, 2012
Project Member #5 daniele.gobbetti
Hi. A very first prototype is available in this branch:
https://github.com/mixare/mixare/tree/feature/issue79

The latitude and longitude are truncated to the second decimal position (i.e. roughly 250 meters from my empirical tests) before being transmitted.

This affects *only* the data that are transmitted to the servers, hence the markers are placed in the right spot even with this patch.

Please let me know whether you know more sophisticated rounding algorithms (the tiles approach would unfortunately break all the existing implementations of data providers!).

What's still missing is a toggle for the user.