id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23445	Support traffic_signals=*	daganzdaanda	team	"Recently there was a discussion at https://community.openstreetmap.org/t/fussgangerampeln-als-triplet-gemappt/107802 where flohoff argued that the detailed mapping of simple (pedestrian) crossings with a `highway=traffic_signals`, then a `highway=crossing` and then again a `highway=traffic_signals` breaks routers which should give a penalty to a regular `highway=traffic_signals` but should not do so for a crossing. 
During the discussion I noticed https://wiki.openstreetmap.org/wiki/Key:traffic_signals for the first time, and thought using this could solve the routing problem. 

I think JOSM should add support for `traffic_signals=*` to the dialogue for traffic lights. It's already in use quite a bit, and it could be useful. 

Maybe talk with the iD people, to establish a common understanding for the best value(s) in cases like a crossing for pedestrians and bikes (mentioned in https://josm.openstreetmap.de/ticket/22611 which asks for a validator test). Right now, I guess a light for pedestrian and cyclist crossing could also be done with `traffic_signals=pedestrian_crossing` and `bicycle=yes`.

See also the previous https://josm.openstreetmap.de/ticket/17808 (wontfix, but 3 years ago when the tagging was not yet that common)"	enhancement	new	normal		Internal preset