RfC: barrier=gap

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?

1 Like

The topic in question:

can you attach photo of such place or similar to it?

I think it is about case where in mountains you jump across narrow crevice but…

1 Like

Why not? There are 68 barrier=gap already in use ans another couple of gap anything, see
barrier | Keys | OpenStreetMap Taginfo.

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?

I think chasm might be more appropriate. Kluft berg - Google Search

With a chasm, you might have to cut your arm off: 127 Hours (2010) - IMDb with an abyss, they don’t find the body. :face_with_peeking_eye:

4 Likes

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.

2 Likes

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?

It’s at 19:25 in the above liked video.

1 Like

This really looks like no big deal. I have seen paths tagged T4 present more hazardous sections.

1 Like

barrier=chasm ?

barrier=gap sounds to me like a gap in fence or wall (barrier=entrance)

EDIT: see confusion in action few posts lower

EDIT2: barrier=abyss ? But that seems stronger and more obscure word.

6 Likes

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.

2 Likes

I might be oversimplifying this, but if there’s a gap, just draw a gap in the wall or fance or whatever and then run the path through the gap.

barrier=gap is a trolltag.

Edit: I misunderstood what is being described here. It’s a path that goes over some kind of an abyss, not a path through a gap in the barrier.

this seems distinct to me from jumping over/stepping over chasm and would be fine with different tagging for them

1 Like

So maybe barrier=vertical_gap would be more precise… :wink:

To throw another idea into the mix:

Draw a way perpendicular to the path and tag it

natural=gorge + width=1 + depth=…

The crossing node could be tagged:

hazard=hole or cliff or … + sac_scale=… + bridge=no (to make it clear for absolutely everyone)

hazard= was supposed to be used for signed cases, right? Not all of them depending on what mapper feels is hazardous?

3 Likes

me dont’t know and the wiki seems to me not to require it 100%. Alternatives:

add furtherly hazard:signed=no or

replace hazard by obstacle

the definition of the barrier key is not compatible with a “gap”, because a gap is not a physical structure on the ground.

+1 for obstacle

2 Likes

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

Londoners and tourists alike should have no confusion about the gap:

On its origin:
‘Please mind the gap between the train and the platform’

The slogan has become so well known that you can now buy all sorts of London Underground merchandise featuring this phrase.

And yes, ‘gap’ here refers precisely to the sort of gaps that can be dangerous if you accidentally step into them or fail to jump over them.

2 Likes