[Tagging] Feature Proposal - Voting - Toll Gantry
jerome.seigneuret at gmail.com
Wed Sep 19 19:30:47 UTC 2018
In fact, this is a problem with software solution not a tag. the
interpretation is a toll access need to wait a part of time. But if you
have badge access you don't wait... and if there is lot of traffic you are
depandent of traffic... waiting time is not for me an argument and a
limitation caused by existing key value but just the interpretation. My 2
cents comment is in relation with toll because i have an rfid badge and I
don't wait a minute. I just slow down to 30km/h to cross the toll booth.
problem is on micro-mapping schema and specifing object with speed crossing
badge, crossing with credit card, crossing with money...
That same problem with traffic transport. If you pocess an abonment you can
save time, more than else if it payed with CD and more than other if it
payed with money.
An other work is the number of rapid access because if there only one speed
toll an lot of traffic you need wait a time anyway.
In my opinion, the best solution is on number of rapid access toll vs
classic access in same solution of parking numbers of places for specific
for information barrier <https://wiki.openstreetmap.org/wiki/Key:barrier>=
lift_gate <https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dlift_gate> and
<https://wiki.openstreetmap.org/wiki/Tag:fee%3Dyes> can be set on paint and
barrier=toll_booth can be a polygon with intersection on your highway.
In fact the problem is only an parent key of toll because it's assimilate
to a barrier but this is just an obligatory access point for users
I think it's better solution to set toll_booth in highway because it's
In railway you payed with resevation on railway track between to point A to
B on time. Did you learn about toll_booth on railway???
historically there is also barrier=entrance but you can understand in this
case there is no physical object. so barrier or not??? That same with
barrier=no Isn't it?
Other problem are using lift_gate and toll_booth with same point... that
schema is problematic.
Can you proposed solution with twice type access
exemple for french access to A709 in France
you can see 1 rapid access right and left
in opposite direction there is 3 speed access left (for vehicule with
specifi maxheight) and 2 speed access on right (for increase traffic speed
that is just my reflection on toll_booth.
For you proposed key, I think you can cut element in twice
highway=grantry+toll=yes and add you speed conditon or stop conditon and it
respond to your case.
grantry is also a proposal
you can set all you need on point in intersection with gantry
*gantry *can be also use for direction information or message with
The problem, and I think you understand where I want go, would be on
combination of information on object in same position.
Le mer. 19 sept. 2018 à 19:33, Jonathon McClung <jonathon at kaartgroup.com> a
> The issue is mostly with how the current standard (as stated here
> <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/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.
> At the end of your email you talk about alternate names. We discussed many
> names, but ultimately landed on toll_gantry because the meaning of the word
> toll is immediately apparent. The term gantry was chosen because it’s
> meaning is specific and less ambiguous than “toll bridge" the other common
> name for these fixtures. Much of this is discussed on the proposal’s page
> <https://wiki.openstreetmap.org/wiki/Proposed_Features/Toll_Gantry> and discussion
> Jonathon McClung | Kaart | jonathon at kaartgroup.com
> On Sep 19, 2018, at 10:59 AM, Jérôme Seigneuret <
> jerome.seigneuret at gmail.com> wrote:
> I don't really understand the difference
> toll_both is a vending machine (or human) with lift gate barrier. It is
> just an other type of object because in other case you can set really the
> gantry as line and set on point type camera or other information object.
> camera as set in relation there is an other subject in France "Ecotaxe
> highway can be set with fee=yes if this is just that you wan't
> there is also speed tall access with RFID toll badge ("Télépéage" for
> in other way if it's a camera you can set camera type
> there is speed_camera why not simply highway=atc_camera
> I think this is only in relation with highway. Isn't It?
> Le mer. 19 sept. 2018 à 17:55, Jonathon McClung <jonathon at kaartgroup.com>
> a écrit :
>> Hello OSM Tagging List!
>> Two weeks have come and gone and now the proposal for highway=toll_gantry
>> is up for vote!
>> Please visit
>> https://wiki.openstreetmap.org/wiki/Proposed_Features/Toll_Gantry and
>> cast your vote. If you missed this proposal the first time, still have
>> concerns, or still have questions, please join the discussion. Otherwise,
>> we look forward to seeing your votes!
>> Jonathon McClung | Kaart | jonathon at kaartgroup.com
>> Tagging mailing list
>> Tagging at openstreetmap.org
> Jérôme Seigneuret
> Tagging mailing list
> Tagging at openstreetmap.org
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging