<html>
<head>
</head>
<body>
<div style="color: black;">
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black;">Does the default rendering on
the slippy map on OSM's main page show private objects? If it does, then
there is a loss of privacy. If it doesn't, then there is a loss of feedback
to mappers.</p>
<p style="margin: 0 0 1em 0; color: black;">-- <br>
John F. Eldredge -- john@jfeldredge.com<br>
"Darkness cannot drive out darkness; only light can do that. Hate cannot drive out hate; only love can do that."
Dr. Martin Luther King, Jr.<br>
</p>
</div>
<div style="color: black;">
<p
style="color: black; font-size: 10pt; font-family: Arial, sans-serif; margin: 10pt 0;">On
March 16, 2015 7:08:34 PM Warin <61sundowner@gmail.com> wrote:</p>
<blockquote type="cite" class="gmail_quote"
style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<div class="moz-cite-prefix">On 17/03/2015 10:46 AM, Bryce Nesbitt
wrote:<br>
</div>
<blockquote
cite="mid:CAC9LFPetO0beLkL08610GrqUtedGNB8dZx69geqXEsmLtV5jig@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
"Please do not map private objects in private space. In general
if
<div>the object could create a privacy concern, or is just not
useful to </div>
<div>a member of the public, please don't add it to the
database. Note</div>
<div>it is fully OK to map facilities within membership or fee
based venues,</div>
<div>as long as the facilities are reasonably available to
members of the public."</div>
<div><br>
</div>
<div><b>Examples not to map</b>: toilets in homes, employee only
toilets in businesses, private recycling bins, playgrounds in
private homes or day care facilities.</div>
<div><br>
</div>
<div><b>Examples to map: </b>toilets inside DisneyLand,
buildings visible from air photos, private facilities with a
history of public "permissive" use.</div>
</div>
<br>
</blockquote>
<br>
<br>
If OSM encourages others to use the OSM data base.. why cannot they
add data that is 'private' to them? <br>
<br>
If renderers were not to render any access=private object then the
general public would not be aware of these 'private' objects and <br>
those who want them may enter them and configure there own render to
show 'their' data alongside OSM data. <br>
<br>
One idea is to only map stuff that is 'publicly viewable'. Some
define this as 'from a public place' such as a street. However with
satellite views being publicly available then mapping things that
are not viewable from a public street becomes possible with more
accuracy than that of a visual estimation from a public street. <br>
<br>
I think that mapping stuff that is not usefull, in some way, is a
waste of time, public stuff or private stuff. If a person with
authority wants to map private stuff .. then I think that is OK. The
key is the authority. <br>
<br>
And then the definition of 'private' is? <br>
Are Universities 'private'? Are bicycle repair stations inside
university grounds private? <br>
Are private swimming pools in backyards to be mapped as they may be
used in an emergency to fight fires? <br>
The boundaries between private and public are grey ... and then
their is community emergency use. Murky waters. <br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
Tagging@openstreetmap.org<br>
<a class="aqm-autolink aqm-autowrap"
href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a><br></blockquote>
</div>
</div>
</body>
</html>