<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 14, 2020 at 7:46 AM Greg Troxel <<a href="mailto:gdt@lexort.com">gdt@lexort.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">...<br><br>
As for access=private 'breaking' routing, this discussion feels very<br>
much like tagging for the router, instead of tagging what is and fixing<br>
the router. If you are driving someplace and you have permission, then<br>
it should be expected that you can use access=private ways to get to<br>
your destination. Humans konw this, and while most people wouldn't<br>
randomly drive down other people's driveways, it's obvious that if you<br>
are invited to a house it's ok to use their driveway.<br>
<br>
So a router that does not allow use of access=private for a final<br>
segment, by default, is broken.<br></blockquote><div><br></div><div>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 <i>are</i> gated/posted. <br></div><div><br></div><div>As an example, a local airport has <a href="https://www.openstreetmap.org/way/310385892#map=17/44.46348/-73.14431">gated service roads and driveways</a> 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.<br></div></div></div>