perhaps use the =destination tag instead of =private on the road you are supposed to use. http://wiki.openstreetmap.org/wiki/Key:access <http://wiki.openstreetmap.org/wiki/Key:access>
I think that unless you are an invited guest and have a drawn map and permission from the owner, a private place that provides access on a certian way to visitors would use a different tag than access=private - they expect visitors to use that particular way to visit the facility - so access=destination seems correct. If the other access roads have gates/bollards/rope, tag them as access=no or private as well. it will further discourage visitors from using that road. http://wiki.openstreetmap.org/wiki/Key:barrier <http://wiki.openstreetmap.org/wiki/Key:barrier> javbw > On Dec 25, 2014, at 10:34 AM, Richard Welty <[email protected]> wrote: > > we were using the old skobbler app to get us to the biltmore estate in > Ashville, NC today, and an issue came up with access tagging. specifically, > there are multiple roads that can access biltmore but only one official > entrance. > the current tagging in OSM labels all the roads as private, with the result > that > an OSM based GPS app can't distinguish what the correct roads to use > actually are. we ended up at the wrong entrance. > > i'm pondering how to tag to distinguish between the preferred private and > the ones that aren't supposed to be used. any suggestions? > > richard > > -- > [email protected] > Averill Park Networking - GIS & IT Consulting > OpenStreetMap - PostgreSQL - Linux > Java - Web Applications - Search > > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
