Not sure what you mean by “the software” but the Renderer’s designers choose
what is displayed by the Renderer. The standard OSM rendering of the OSM
database shows objects that are marked as access=private as well as access=yes.
As mentioned below only Public objects should be added to the DB unless they
are physically noticeable such as private roads or property and they will be
given an access tag of private to show they are not public. access=private
indicates the right of access to an object not that the object should be kept
hidden from public disclosure.
Everything in OSM is visible to all Renderer's to display or not display aas
they choose.
The OSM database is not the place for private individuals or organisations to
store private data.
Hope this helps to clarify things.
Jonathan
http://bigfatfrog67.me
From: John F. Eldredge
Sent: Tuesday, 17 March 2015 22:20
To: [email protected], Tag discussion, strategy and related tools
What I mean is, does the software allow you to specify that only objects with
access permitting the general public, or access=private with only specified
values of the operator tag, be rendered?
--
John F. Eldredge -- [email protected]
"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.
On March 17, 2015 4:43:07 PM <[email protected]> wrote:
Not sure what you mean by “Private Objects”, anything in the DB is capable of
being displayed, depending on whether the Renderer wants to. Nothing is
Private in OSM.
Jonathan
-----------------------
http://bigfatfrog67.me
From: John F. Eldredge
Sent: Tuesday, 17 March 2015 20:44
To: Tag discussion, strategy and related tools
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.
--
John F. Eldredge -- [email protected]
"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.
On March 16, 2015 7:08:34 PM Warin <[email protected]> wrote:
On 17/03/2015 10:46 AM, Bryce Nesbitt wrote:
"Please do not map private objects in private space. In general if
the object could create a privacy concern, or is just not useful to
a member of the public, please don't add it to the database. Note
it is fully OK to map facilities within membership or fee based venues,
as long as the facilities are reasonably available to members of the public."
Examples not to map: toilets in homes, employee only toilets in businesses,
private recycling bins, playgrounds in private homes or day care facilities.
Examples to map: toilets inside DisneyLand, buildings visible from air photos,
private facilities with a history of public "permissive" use.
If OSM encourages others to use the OSM data base.. why cannot they add data
that is 'private' to them?
If renderers were not to render any access=private object then the general
public would not be aware of these 'private' objects and
those who want them may enter them and configure there own render to show
'their' data alongside OSM data.
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.
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.
And then the definition of 'private' is?
Are Universities 'private'? Are bicycle repair stations inside university
grounds private?
Are private swimming pools in backyards to be mapped as they may be used in an
emergency to fight fires?
The boundaries between private and public are grey ... and then their is
community emergency use. Murky waters.
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
