Mateusz Konieczny via Tagging <tagging@openstreetmap.org> writes: > Feb 25, 2023, 19:58 by g...@lexort.com: > >> I am assuming -- but the wiki is unclear -- that >> >> access=private, tagged on barrier=gate >> >> means that all modes of travel have a right of access only with >> permission >> > note that some may not physically fit (even with permission your elephant > may be still not fitting some entrances)
Good point; I was sloppy. It implies that a mode phsyically fits if it fits on the ways on either side of the barrier. >> and that >> >> access=private >> foot=yes >> >> means that all modes need permission except for foot which has a legal >> right to pass. >> > note that often foot=permissive would be more accurate > but foot=yes is used > (especially common in areas where legal right of way is rare or not > existing and basically all =yes are actually =permissive) A fair comment about typical. I am thinking of a specific place in my town where the road/track is privately owned, the gate is locked, motor_vehicle=private but it is actualy true that foot=yes because the town paid for a deeded easement to the public. >> With >> >> access=private >> foot=yes >> locked=no >> >> then it's clear that physical passage is possible for all modes. >> > not entirely > > for example if tagged on highway=footway line then I would > not assume that car would fit there A fair complaint; I meant but did not say that it is possible if the rules would say it works if the barrier were not there. > what worse, even if tagged in say highway=service this gate may > be not large enough to fit a car highway=service by definition is enough for cars so if there is a gate on a highway=service that does admit cars on both sides, but is not wide enough for a car, then I would say this is mistagged and there should be a short way that is path or whatever. >> With >> >> access=private >> foot=yes >> locked=yes >> >> then it says that phsical passage is not possible and hence if people >> can walk around then it needs a way representing walking around. >> > this one is tricky and expecting that it will be used consistently > will not work well True, but we have to guess at what is right, and then when users do it wrong explain and fix. > +1 to separate bypass ways if matching reality > not sure how to handle cases where bypass way does not work > (for example you can crawl under lift gate, it is allowed, you cannot get > around it) I guess that's still a separate way that's path with a height restriction, even if it overlaps. >> I realize there have been "but we can invent complicated bypass tags" >> but those seem to not interact well with existing data consumers and it >> does not seem we have consensus. >> > +1 though some cases where bypass way does not work are annoying I think if we let it overlap it's ok. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
