On Tue, Jul 14, 2020 at 7:46 AM Greg Troxel <g...@lexort.com> wrote: > ... > > As for access=private 'breaking' routing, this discussion feels very > much like tagging for the router, instead of tagging what is and fixing > the router. If you are driving someplace and you have permission, then > it should be expected that you can use access=private ways to get to > your destination. Humans konw this, and while most people wouldn't > randomly drive down other people's driveways, it's obvious that if you > are invited to a house it's ok to use their driveway. > > So a router that does not allow use of access=private for a final > segment, by default, is broken. >
There is a big problem with this interpretation of tagging ways with access=private that are not posted/gated to prevent access but are not used by convention/norm: Doing this makes it impossible to distinguish these from roads that *are* gated/posted. As an example, a local airport has gated service roads and driveways <https://www.openstreetmap.org/way/310385892#map=17/44.46348/-73.14431> to get to a variety of maintenance and airline buildings. These are appropriately access=private because they are gated and only employees can use them. Routers need to be able to direct customers/public via the close-by access=public/destination/customers roads and not try to use the access=private roads. If access=private is used for most residential driveways and routers need to treat access=private as a thing to be ignored for final routing, they will get this airport situation wrong.
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
