[Tagging] Feature Proposal - Voting - Toll Gantry

Tom Pfeifer t.pfeifer at computer.org
Wed Sep 19 23:26:59 UTC 2018

On 19.09.2018 19:31, Jonathon McClung wrote:
> The issue is mostly with how the current standard (as stated here 
> https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dtoll_booth 
> <https://wiki.openstreetmap.org/wiki/Tag:barrier=toll_booth>) impacts routing. This is said on the 
> proposal page here "Many current routing softwares add a delay to trip time when encountering the 
> tag barrier <https://wiki.openstreetmap.org/wiki/Key:barrier>=toll_booth 
> <https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dtoll_booth>. However, the delay on these more 
> modern toll collection systems is significantly less; not requiring the driver to stop in most 
> cases. In effect, this means that many drivers will be routed onto a slower route.” This is the 
> major difference. Of course the way itself should be tagged toll=yes. This is a clean way to a) show 
> where the toll begins and b) give the routing software something to account for on the way.

First, how much of a delay is added by the routing engines, have you investigated this? If so, this 
would be a few seconds once-per trip, not every 500m like a traffic light. Thus the difference on 
the calculated overall travel time would be insignificant.

Second, the problems described would be more easily and more elegantly solved with subtagging the 
existing barrier=toll_booth, instead of inventing a new first level tag. Subtagging preserves 
backward compatibility, while a new tag has to be implemented everywhere,


More information about the Tagging mailing list