[Tagging] [OSM-talk] "Limitations on mapping private information" - wiki page

Paul Allen pla16021 at gmail.com
Wed Sep 16 14:35:27 UTC 2020


On Wed, 16 Sep 2020 at 14:47, bkil <bkil.hu+Aq at gmail.com> wrote:

>
> Private swimming pools aren't that interesting but people seem to
> enjoy tracing them. Maybe in case of emergency they could be used as a
> nearby water source by the fire brigade?
>

Depending on the terrain, they may be visible and serve as navigational
references.  "If I'm where I think I am, there should be a house with a
swimming pool in that direction."

Also, swimming pools are not people and have no right to privacy under
the GDPR.

Also, aerial imagery exists.  People can look at such imagery in Google
Maps, Bing Maps, etc.  If you don't want people knowing you have
a swimming pool then build a cover over it or bribe all the aerial imagery
companies to doctor their images so your swimming pool isn't visible.

>
> From the privacy section, am I reading correctly that you suggest that
> you find it acceptable to map each tomb in a cemetery by name?
>

I've mapped a few tombs by name.  They're large, elaborate, and
(most importantly) are "listed buildings" meaning they are of
cultural significance and protected by law.  I wouldn't bother
mapping any other tombs in a cemetery, not unless I ran out
of things to map (that isn't going to happen).

I think you are trying to basically gather "mapping ethics", and maybe
> this should be better be done in Wikipedia because it does not only
> concern OpenStreetMap, but any mapping provider.
>

And what if OSM feels those generic mapping ethics are too lax?
We'll end up with our own, one way or another.  Even if it's only
guidance as to how to interpret generic ethics in the context of
the OSM mapping model.

-- 
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20200916/e5ac55bb/attachment.htm>


More information about the Tagging mailing list