Re: [OSM-dev] 0.6 - older trackpoints /was: Re: 0.6
On Wed, May 07, 2008 at 08:47:29AM +0200, Stefan Baebler wrote: I propose to introduce the ability to limit the age of trackpoints downloaded into the client by introducing an extra parameter age, eg: GET /api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber +1! Although it might be easier on the database if the age is replaced by a cutoffdate instead? cu bart ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
Re: [OSM-dev] 0.6 - older trackpoints /was: Re: 0.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Stubbs schrieb: On Wed, May 7, 2008 at 8:17 AM, bvh [EMAIL PROTECTED] wrote: On Wed, May 07, 2008 at 08:47:29AM +0200, Stefan Baebler wrote: I propose to introduce the ability to limit the age of trackpoints downloaded into the client by introducing an extra parameter age, eg: GET /api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber +1! Although it might be easier on the database if the age is replaced by a cutoffdate instead? Can we fix this to whole days, and make it use the calendar day, instead of the last 24 hour period? Otherwise you might get to know which track was created exactly when by repeatedly downloading an area and watching the differences. - -- Dirk-Lüder Deelkar Kreie Bremen - 53.0952°N 8.8652°E -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIa+kFUbODdpRVDwRArlxAKCOZ3MYzz/B8NflZeygaGeXMRS9rACgoKok 5be9oN0glsJte4rhSNm1EKU= =3lW+ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
Re: [OSM-dev] 0.6 - older trackpoints /was: Re: 0.6
Dirk-Lüder Kreie wrote: I propose to introduce the ability to limit the age of trackpoints downloaded into the client by introducing an extra parameter age, eg: GET /api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber +1! Although it might be easier on the database if the age is replaced by a cutoffdate instead? Can we fix this to whole days, and make it use the calendar day, instead of the last 24 hour period? Otherwise you might get to know which track was created exactly when by repeatedly downloading an area and watching the differences As said the time would be the time when the trace was imported into the db, so this wouldn't give out personal moving patterns, but time of upload patterns (delayed by the time gpx spends in the queue), which isn't such an issue i believe. Think of a situation when someone uploads 7 month old traces and users choose to see only the last 6 months worth of traces. Such traces would still be visible for 6 months after being uploaded to allow some time for them to be traced. But it makes sense that such precision (with decimals) is not needed. Whole days is good enough, heck, the age unit could also be weeks or even months to further lower the precision to provide some more obfuscation for traces that might not be public (linked to user and downloadable as raw gpx), but i don't think this level of additional privacy would be necesarry. Midnight (GMT?) seems ok for a cutoff step (in case of weeks it would need to be a fixed day of week and in case of month a fixed day in month, which could be strange to get used to) Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
