Proposed features/Extended conditions for access tags
|This proposal is now abandoned since Conditional restrictions has been approved by vote.|
|Extended conditions for access tags|
|Proposal status:||Abandoned (inactive)|
|Definition:||an access tag only applies if all conditions are fulfilled|
This proposal presents the idea of adding conditions to existing keys (such as maxspeed, access ...). A tag with conditions will only have an effect if all conditions are valid. Something like this is necessary to describe many traffic restrictions encountered in reality.
Conditions are appended after the base key. Conditions are separated from the base key and each other using colons (":"). Brackets around conditions should be used to improve readability or to avoid ambiguities.
A list of conditions can be found here: Conditions
|Maxspeed is 100 km/h for most vehicles, but 60 km/h for hgv traffic.|
|Maxspeed is 120 km/h under normal conditions, but 80 km/h when the road is wet.|
|Bicycles are permitted to use this street outside 10AM-6PM.|
|access:(weight>5.5)=destination||Vehicles over 5.5t are only allowed for destination traffic.|
|Maxspeed for hgv is limited to 80 on weekends, but 120 otherwise.|
|Maxspeed limited to 30 on 7AM-5PM weekdays, but 50 otherwise.|
Usage and evaluation details
- More specific information overrides more general information. For example, on a wet road, maxspeed:wet=* overrides maxspeed=*; maxspeed:wet:hgv=* overrides both maxspeed:wet=* and maxspeed:hgv=* for hgv.
- If there are conflicting tags without a "specificness" hierarchy, the most restrictive rule (e.g. lowest maxspeed) is to be chosen.
Specificness is defined as follows: a key A is more specific than a key B if the set of conditions in A, including implied conditions, is a superset of the set of conditions in B, including implied conditions. The following conditions are implied:
- transportation modes imply all ancestor transportation modes (e.g. "motorcar" implies "motor_vehicle" and "vehicle")
Way direction dependency
The following tags affected by this proposal depend on way direction:
- tags with ":forward" or ":backward" as part of the key
- tags starting with direction-dependent base keys (e.g. "oneway:...")
Editors should include those tags in their way reversal safety checks.
Please use the talk page.
See /First voting.