Talk:Key:cycle barrier
"Handlebar height"
"Handlebar height" doesn’t seem explicit enough given the context. Are we talking about common adult mountain bike handlebar height (~ 1 m), roadbike (slightly lower), recumbent, kids ? --Lejun (talk) 05:47, 22 August 2021 (UTC)
- Yes, this problem with squeezed/tilted barriers is not well worked out yet. I see these two solutions:
- Either using maxwidth:physical=* at a defined height (1 m) - this would be relatively easy to survey and interpret. tilt=* could be specified additionally.
- Or alternatively a specification of opening=* at the ground and the additional specification of the tilt=* angle, then one can derive the distance at all heights (depending on exact layout/geometry of the barrier bars). This variant could be more accurate if the values are accurate, but more difficult to determine on the ground and complex to evaluate.
- The two variants do not exclude each other, so they could exist in parallel.
- Or are there other thoughts/suggestions on this?
- --Supaplex030 (talk) 12:04, 22 August 2021 (UTC)
height at tilted structures
Just to follow up now that tilt=* has been added: How should height=* be measured for a tilted structure? Should it be the length of the structure or the vertical height? --Lejun (talk) 06:10, 25 August 2021 (UTC)
- height=* means the vertical height. --Supaplex030 (talk) 19:47, 25 August 2021 (UTC)
- Imagine a ladder: The height is the tallest it reaches. The ladder itself would be a "length" (or some other dimension) to it. ---- Kovposch (talk) 05:05, 26 August 2021 (UTC)
- Fine with me. Keeping this idea implies that anyone measuring height for a tilted structure would need to somehow measure the vertical height at the peak of the barrier and not only put a ruler along it. It would be on consumer side’s too to process the exact length (Can’t see any reason to do that apart from 3D rendering). That being said, How would this scheme applies to non-straight barriers (e.g. hourglass shaped)? Would it be too nitpicky for now? --Lejun (talk) 06:03, 26 August 2021 (UTC)
Oscillating barriers
I would suggest adding another type of barriers which is quite developed here in France (and particularly annoying when you have bags or a cargo bike). It is composed with a classic pivoting barrier and an oscillating one such as this : https://wiklou.org/w/images/thumb/3/3f/Barriere_dacces_selectif.jpg/360px-Barriere_dacces_selectif.jpg --Biologeek (talk) 07:43, 28 August 2021 (UTC)
- I’d rather map this kind of barrier as two elements with barrier=kissing_gate on the left (the wiki page suggests further precision with kissing_gate=square_profile). As for the right side, I suggest using :
- barrier=cycle_barrier as barrier=motorcycle_barrier isn’t seeing much use
- cycle_barrier=single is the more fitting as there’s only a single barrier "layer"
- cycle_barrier:installation=fixed
- bicycle=dismount
- maxheight=* for the upper flag part
- opening=* for the lower bottleneck
- min_height=* for the height needed (e.g. for a cargobike) to clear the lower part
- maxwidth:physical=* for the width between the flag pole and the left pole
- To add some more context, those are (exclusively ?) sold by SEMCO® and named Pass’Vélo™ which could lead to others tags such as:
- manufacturer=*
- model=*
- wheelchair=designated (on the pedestrian barrier as stated on the manufacturer website)
- If there’s no objection then I’ll go fetch some standard values as a proof of concept (GeoVelo’s router announced cargobike support earlier this month, may be interesting to testing purposes) and add it in the examples. --Lejun (talk) 15:49, 20 November 2022 (UTC)
- A french specific section has been added to barrier=cycle_barrier. --Lejun (talk) 06:37, 28 November 2022 (UTC)