Proposed features/traffic signals group
| traffic signals group | |
|---|---|
| Status: | Proposed (under way) |
| Proposed by: | Sanderd17 |
| Tagging: | type=traffic signals group |
| Applies to: | relation |
| Definition: | Use when you have to stop only once for a group of traffic lights |
| Rendered as: | hidden |
| Draft start: | 2010-12-27 |
| RFC start: | 2010-12-27 |
| Vote start: | * |
| Vote end: | * |
Contents |
Rationale
A router could (or should) give a time penalty for passing traffic lights since sometimes you have to stop. How heavy the penalty is depends on the type of roads that cross. But big roads have normally two separated sets of lanes, sometimes a separated cycleway and all those crossings have a tag highway=traffic_signals. The router shouldn't give a penalty for each traffic light, but only one penalty.
Proposal
To know which traffic signals fit in one group, a relation could be used with as members the traffic signal nodes. The roles could be set to the type of vehicle that has to stop for a traffic light. e.g. a role "pedestrian;all" would indecate that the lights are meant for pedestians vs all the rest. A role "bicycle" would mean that it's a crossing between cycle lanes. That way, routers will know at which traffic light the car/bicycle/... will have to stop.
Examples
http://www.openstreetmap.org/?lat=50.938743&lon=3.099462&zoom=18&layers=M
Tagging
| Tags | Notes |
|---|---|
| type=traffic_signals_group |
See also
- Proposed_features/Set_of_Traffic_Signals
- traffic_signals:sound=*
- traffic_signals:vibration=*
- traffic_signals:arrow=*
- traffic_signals:minimap=*
Vote
- ...
