Proposed features/wait
| Lanes with give_way/stop/traffic_signals | |
|---|---|
| Status: | Voting (under way) |
| Proposed by: | AntMadeira, L___I |
| Tagging: | wait=none/give_way/stop/traffic_signals |
| Applies to: | 
|
| Definition: | Define the lane(s) where stop/give_way/traffic_signals apply |
| Drafted on: | 2020-11-20 |
| Vote start: | 2021-01-27 |
| Vote end: | 2021-02-10 |
Proposal
This proposal introduces the key wait, which specifies the lanes where give_way/stop/traffic_signals apply. This key is only useful if used together with at least one of the suffixes :lanes, :forward or :backward or on one-ways.
Rationale
At the date of this proposal, there's no easy or straightforward procedure to tell routing apps when a driver has to stop or give way on a certain lane. Adding a stop or give way sign to a way doesn't solve this, because there could be several different signs affecting several lanes on the same road. Adding to the :lanes scheme, this proposal aims at introducing a key which identifies a specific lane where a give_way/stop/traffic_signals is applied, while the others on the same carriageway are not affected. This can be used by routing applications to inform drivers that they have to wait on a certain lane.
Tagging
Lane-specific information can be expressed in a way by suffixing the key with :lanes, as with other keys in the same scheme, like maxspeed=*, destination=*, turn=*, change=*, etc. The value of that key then contains the values for each lane separated by a | (vertical bar) in left-to-right order as viewed in the respective driving direction of those lanes (resp. in the osm-way direction in case of lanes running in both directions).
The selected portion of the affected way, must be cut in the following way:
- from the first indication via road markings, signposts or similar indications which clearly divide the lanes in a particular direction
- to the junction or the completion of merge.
This key would have four different possible values: none, give_way, stop or traffic_signals.
| Value | Action |
|---|---|
| none | The lane is not affected by this key. The driver doesn't need to wait on the affected lane. |
| give_way | Driver must give way on the affected lane. |
| stop | Driver must stop on the affected lane. |
| traffic_signals | Driver must obey to traffic signals on the affected lane. |
A simple example with wait key on a one-way street:
lanes=3 turn:lanes=left|through|right wait:lanes=stop|none|give_way
This would be a road with three lanes, with a stop applied only to the leftmost lane, none to the centre lane, and a give way sign on the rightmost lane. For a driver, this means he/she has to stop on the left lane to turn left or give way on the right lane to turn right, while the centre lane has no restrictions.
The direction of the lane change is usually viewed in the direction of the OSM way. If the key is used together with the suffix lanes:backward (i.e. as wait:lanes:backward=*) the direction is viewed in the opposite direction of the OSM way.
Examples
These are some examples of places where the wait key could be helpful.
| Images | Tags | In OSM |
|---|---|---|
lanes=2 turn:lanes=merge_to_right|through;right wait:lanes=give_way|none |
776323611 776323611
| |
lanes=3 lanes:forward=1 lanes:backward=2 turn:lanes:forward=left;through turn:lanes:backward=left|through wait:lanes:backward=stop|none |
776617389 776617389
| |
lanes=3 lanes:forward=2 lanes:backward=1 turn:lanes:forward=left|right wait:lanes:forward=traffic_signals|give_way |
875250330 875250330
|
Applies to
This key applies to ways only, as in the lanes scheme.
Related keys
- turn=*
- destination=*
External discussions
See also
Comments
Please comment on the discussion page.
Voting
- Log in to the wiki if you are not already logged in.
- Scroll down to voting and click 'Edit source'. Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
| To get this output | you type | Description |
|---|---|---|
|
{{vote|yes}} --~~~~
| |
|
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. |
|
{{vote|abstain}} comments --~~~~
|
If you don't want to vote but have comments. Replace comments with your comments. |
Note: The ~~~~ automatically inserts your name and the current date.
I approve this proposal. --AntMadeira (talk) 01:42, 27 January 2021 (UTC)- I approve this proposal. --HedgiePT (talk) 03:09, 27 January 2021 (UTC)
- I approve this proposal. --Aharvey (talk) 03:20, 27 January 2021 (UTC)
- I approve this proposal. --ForgottenHero (talk) 07:09, 27 January 2021 (UTC)
I have comments but abstain from voting on this proposal. one thing seems missing - an explicit mention that it applies on the end of last way with the same tagging (so splitting way requires no special functionality - to avoid Proposed features/transit fiasco). Sorry for not noticing it earlier. Mateusz Konieczny (talk) 07:11, 27 January 2021 (UTC)
I oppose this proposal. Critical issues as in Talk:Proposed_features/wait#Point-like_features_should_not_be_tagged_on_ways not addressed. This dissociates necessary information from the location-relevant highway=* feature. -- Kovposch (talk) 07:20, 27 January 2021 (UTC)
- To be more specific, there was response but you and proposal author disagreed whatever such info should be mapped on nodes or on ways Mateusz Konieczny (talk) 07:47, 27 January 2021 (UTC)