[Tagging] The direction=* tag

John F. Eldredge john at jfeldredge.com
Sun Mar 19 20:01:27 UTC 2017

This has the added complication that the way may have two-way traffic, but 
the sign doesn't apply to both directions. In fact, most signs don't apply 
to both sides of a roadway; instead, there will usually be a separate sign 
for both directions of travel.

On March 19, 2017 2:56:02 PM yo paseopor <yopaseopor at gmail.com> wrote:

>> yes, it is important to be able to understand to which way (and traveling
>> direction) a sign applies, but nodes do not have a forward or backward
>> direction
> but the way the node is in yes it does. Node it is not independent. It is
> in a way. with a specific direction (you can revert the direction if you
> need it, rivers only flow forward-downward). Wiki says "(i.e., draw the way
> in the direction that the river flows)."[1]
>> , at most they can have an upwards or downwards direction. They also have
>> a front side and a back side
> , but generally I'd assume the tagging is about the front side, without
>> specifying it.
> In OSM mappers assume something until this thing has become more important
> and then need to redefine the way the key is applied with subkeys and other
> values.Think about bus stops for example [2] [3]...
>> One way to map the direction in an easy way is to map the sign at the side
>> of the road.(requires post processing to use the information in a graph
>> model).
> To avoid this complication I can assume the direction of the way the node
> it is in. JOSM style recognise it, Kendzi3D plug-in also does with
> direction key or :forward/:backward subkey. [4]
>> For a stop sign you could also make a short way for the part from the stop
>> line to the actual crossing node, and add stop sign information there
>> (either with a relation similar to turn restrictions or with direction
>> dependent tags on the _way_)
> Why you accept a line and not a dot in the same place knowing the
> information of the way the node it is [5]? Reading OSM wiki Why is possible
> to do with traffic lights [6] (you have to put in a way - wiki says "Thus,
> because traffic signals can affect routing decisions, it is important that
> they are attached to the ways to which they apply, and not placed beside
> the way" [5] , you have a specific subkey) or city_limit [7] but not with
> the other traffic signs? Do we have to erase and delete all the traffic
> signals (907 256) [8] because they are not correct? If we can do with a
> traffic light I am sure we can do with other nodes with no lights there but
> so important. If traffic signs were not so important governments did not
> put in at the roads.
> Mapillary and OSC will give us this information through their plug-ins.
> Mapillary has a complete scheme of traffic signs recognition [9]. OSC has
> an inside editor [10]. Spanish government open a file with more than
> 500,000 traffic signs relative to the way...and with a specific permission
> to use it with OpenStreetMaps [11]. Are we telling other organizations can
> give us this data, with this specific information but OSM can't accept it?
> Taginfo says it is possible  [12][13]
> Salut i senyals de trĂ nsit (Health and traffic signs )
> yopaseopor
> [1] https://wiki.openstreetmap.org/wiki/Tag:waterway%3Driver
> [2] https://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dstop_position
> [3] https://wiki.openstreetmap.org/w/index.php?title=Tag:
> highway%3Dbus_stop&offset=&limit=500&action=history
> [4] https://wiki.openstreetmap.org/wiki/Proposed_features/
> Extended_traffic_signs_tagging#Renders
> [5] https://wiki.openstreetmap.org/wiki/Tag:highway%3Dstop#How_to_map
> [6] https://wiki.openstreetmap.org/wiki/Tag:highway%
> 3Dtraffic_signals#Traffic_signals_for_cars
> [7] https://wiki.openstreetmap.org/wiki/Tag:traffic_sign%3Dcity_limit
> [8] https://taginfo.openstreetmap.org/tags/?key=highway&
> value=traffic_signals
> [9] https://www.mapillary.com/developer/api-documentation/#traffic-signs
> [10]
> http://blog.improve-osm.org/en/2016/11/a-glimpse-into-the-future-of-mapmaking-with-osm-2/
> [11]
> https://wiki.openstreetmap.org/wiki/File:Resoluci%C3%B3n_se%C3%B1ales_de_tr%C3%A1fico_verticales_RCE.pdf
> [12] https://taginfo.openstreetmap.org/keys/traffic_sign%3Aforward
> [13] https://taginfo.openstreetmap.org/keys/traffic_sign%3Abackward
> ----------
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20170319/731e691e/attachment.html>

More information about the Tagging mailing list