Bus:lanes:forward or lanes🚌forward?

Help and support Tagging help & support
, , ,
1

I’m facing a dilemma: Is it better (as in, most recent, accepted and expressive standard) to use bus:lanes:forward or lanes:bus:forward in the following scenario?

||               ||                            |                    ||
|| \/ bwd lane 1 || /\ fwd lane 1, vehicle+bus | /\ fwd lane 2, bus ||
||               ||                            |                    ||

My best solution so far is

highway=...
lanes=3
lanes:forward=2
lanes:backward=1
bus:lanes:forward=yes|designated

And since the outer-most lane later develops into a full-fledged bus stop with a platform, I tag that next segment with bus_bay=right.

Is this correct and expressive enough?
Thanks in advance! :slight_smile:

2

I virtually never used lanes:bus because that lacks the position of bus lanes and it’s always better to be explicit about this.

On that aside, I wouldn’t use bus_bay over bus:lanes for when a bus stop exists because the lane still continues in that situation, it doesn’t suddenly disappear, just because a bus stop is nearby. It’s basically the difference between parking=lane and parking_street=side i.e. the former takes a lane away from the road, the latter takes form of cutting into kerb (among other things) or between a double-tracked railway[1] and a passing loop using railway analogy[2].

  1. allows two trains to pass in-motion, particularly at regular speed ↩︎

  2. requires the other train to park to safely let the other train go through or if they can do it in motion, one if not both of the trains have to (significantly) slow down ↩︎

1 Like
3

Thank you, the railway analogy sure helps! So bus_bay has no place in this context because we already have a full-fledged bus lane and it’s not just carved into the side of the lane.
Regarding the lanes, I think I’ll stick with bus:lanes instead of lanes:bus.
Thank you for your answer!