As far as I understand (I’ve never used the tag myself), the purpose of crossing=no (and it’s always used without a highway=crossing tag) is to make it clear that a node that based on context might be mistaken for a pedestrian crossing is not actually one.
e.g. if you have a highway=traffic_signals on a road node, but the signals are specifically only for road traffic, there are no pedestrian signals, and it is in some way indicated that pedestrian crossing is not allowed here, then you could tag that node with crossing=no As for your specific example, I would draw the fence (as barrier=fence) and add the crossing=no tag to the road itself. From: Graeme Fitzpatrick <graemefi...@gmail.com> Sent: Monday, 20 May 2019 07:57 To: Tag discussion, strategy and related tools <tagging@openstreetmap.org> Subject: Re: [Tagging] "Unambiguous crossings" proposals and related questions On Mon, 20 May 2019 at 02:32, <osm.tagg...@thorsten.engler.id.au <mailto:osm.tagg...@thorsten.engler.id.au> > wrote: Pretty well agree with everything you said, Thorsten, but I'd like to clarify one point thanks. no - there is no crossing possible/legal here Understand the idea, but how do we actually use it? The fence here https://www.google.com/maps/@-28.0725198,153.4441123,3a,75y,182.92h,70.96t/data=!3m6!1e1!3m4!1spYYE39O0IZ2ymA7Jh-D-5g!2e0!7i13312!8i6656 is "supposed" to stop people crossing the highway (it doesn't!) & extends for several k, broken only by cross-streets, turning lanes & pedestrian crossings. So how do we mark crossing=no along this entire stretch? Draw the fence in & add a crossing tag to that? Would anything / anyone read it? Crossing=no added to the road itself? Same thing applies. Any other thoughts? (Or is there an obvious, simple solution that I'm missing :-)) Thanks Graeme
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
