ср, 14 февр. 2018 г. в 17:47, Christoph Hormann <o...@imagico.de>:

> On Wednesday 14 February 2018, Michael Reichert wrote:
> >
> > All challenges are run four times, one iteration with full metadata,
> > one with timestamp and version fields, one with version field only
> > and one without any metadata. [...]
> While this seems a useful test to do i wonder how the timestamp and
> version fields are relevant regarding privacy and personal data
> protection?

If OSM API were fast enough, it would allow to rather easily group changes
back to changesets. Number of changesets gets you back number of mappers.
Classifying a returning mapper by edit pattern would allow to get back the
geometric median of their edits, which brings you to knowing where they

(To make OSM API upload faster don't forget to join the efforts in

> I know a possible answer could be that in combination with personal data
> (like user names or ids) it would provide additional information on
> people.  But this argument applies to *any data* including the geometry
> (i.e. coordinates) and tags.
> So what is the special thing from a legal standpoint about versions and
> timestamps compared to geometries and tags?
dev mailing list

Reply via email to