Open GoogleCodeExporter opened 9 years ago
I find that the GPS is already adding enough noise to the requests :-)
Jokes apart, this can be added in the settings...
Original comment by mixare.org
on 4 Mar 2011 at 3:39
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
Original comment by stiller....@googlemail.com
on 8 May 2011 at 4:28
Original comment by mixare.org
on 23 Apr 2012 at 7:51
Issue 128 has been merged into this issue.
Original comment by daniele.gobbetti
on 20 Jun 2012 at 3:43
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.
Original comment by daniele.gobbetti
on 20 Jun 2012 at 4:21
[deleted comment]
https://github.com/KlemensE/mixare/commit/a87485742cd2c88d7762d80608208c46dcafa0
54
Original comment by klemens....@gmail.com
on 7 Aug 2012 at 8:35
Original issue reported on code.google.com by
mixare.org
on 4 Mar 2011 at 3:38