In the German category, a video was shared, where a mapper put a gap into a path, because the path crossed a 1m wide gap (a Kluft in German, maybe abyss in English?) This is very word for word mapping. (I only see that now, as I write these words.)
I’d prefer to have a node barrier=gap; width=1 e.g. A renderer could draw an icon there, a router could warn of the necessity to jump the gap. Of course no renderer nor router will support that within 25 years as of today. Would a proposal help speed that up? I’d say, the concept quite concise?
I really think the safety of the general public should be considered here - there is no path, there isn’t even ground. How does one convey this to the public? What next, mapping paths through minefields?
Think about other situations where you don’t have a “ground”. Like if you need to jump from stone to stone to cross a waterway, we would not leave a gap either, but call it ford=yes. If there is a block on the road where you need to climb/jump over, we would call it barrier=block. If a wooden plank is missing on a pier, we might not even map it at all.
Also our wiki is suggesting already that anyone should treat barrier=* as access=no and treat only known values differently.
Overall I don’t see any concerns of public safety besides the normal.
I think, the safety of the General Public stopped being an issue since the introduction of sac_scale.
Having read about the term chasm, from looking at the video in the German topic above, I’m gonna stay with “gap”. Might not be what the British saying “mind the gap” has in mind (pun not intended), but nevertheless, OSMisms abound?
Nevertheless: My question also about, whether the proposal process be a means of conveying something to prospective users?
Just from a linguistic point of view, barrier sounds like there is an object blocking something, where here there is something missing. Hazard might be a better fitting key, though then we would be back to the public safety topic I believe.
I would agree, that gap sounds odd in that context, but maybe it’s better to have something more generic. Just thinking about the above mentioned pier with some missing planks. It’s kind of the same “barrier”, but you wouldn’t call it chasm.
Functionally, it’s not much different from a barrier=cattle_grid, which is kind of a gap as well, and longitudinal grids present a major obstacle for bicycles.
That being said, I agree this gap should be an obstacle rather than a barrier. I don’t see a fitting value either on Wiki or taginfo, though. obstacle=crevice?
1 Like
Mammi71
(One feature, Six mappers and still More ways to map it)
20
Londoners and tourists alike should have no confusion about the gap: