[Tagging] emergency bays - which side?

[Volker Schmidt]

Emergency bays and bus bays are physically very similar, i.e. a short piece
of an additional lane on a road.

Unfortunately the two tags highway=emergency_bay and
bus_bay=both|left|right use very different approaches to describing
essential the same physical arrangement.


bus_bay=both|left|right

highway=emergency_bay

wiki page

https://wiki.openstreetmap.org/wiki/Key:bus_bay

http://wiki.openstreetmap.org/wiki/Tag:highway%3Demergency_bay

node

no (according to the wiki page)
yes (in reality there are few cases of bus_bay=yes with highway=bus_stop)

yes

node example

http://www.openstreetmap.org/node/2134413721

http://www.openstreetmap.org/node/1690562827

http://www.openstreetmap.org/node/4892296128

http://www.openstreetmap.org/node/3246948212


way

yes

yes

way example

http://www.openstreetmap.org/way/253182588

http://www.openstreetmap.org/way/460019134

left|right|both

yes (mandatory)

not foreseen in the wiki page


node: 55

way: 1715

node: 3710

way: 642

I personally like the bus_bay approach better, but I see the drawback of
having to split the road way twice for every occurrence, when you use the
type:way approach

The emergency_bay approach is easier to map if you only consider the node
approach and only on one-way streets, assuming that  you can define the
default as being on the right-hand side for right-hand-drive countries (and
symmetrically for the left-hand ones). For dual lane traffic or for
emergency bays on the "wrong" side of the road you need an agreed way to
define which side of the road. I do not like the way approach of the
emergency_bay tagging, as it actually requires a separate way, which does
not reflect the reality on the ground.

As both tags are so far relatively low-use, it may not be too late to unify
the bus_bay and emergency_bay mapping approaches.

Volker



>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20180101/7f0d73eb/attachment.html>