Proposal:Time restricted tags
| Time restricted tags | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | Driver2 |
| Tagging: | tag.time=specified time |
| Applies to: | Tags |
| Definition: | Restricts a given tag to a certain time |
| Statistics: |
|
| Rendered as: | * |
| Draft started: | |
| Proposed on: | * |
| RFC start: | * |
| Vote start: | * |
| Vote end: | * |
Summary
There are day_on=*, day_off=* etc. tags, but they are not flexible enough. Firstly they only turn on/off general access and secondly they only allow a single combination of days and hours. The syntax used for opening_hours=* appears to be much more suitable for this. Also there is no way to make single tags only active during a specified time.
Of course this is only for simple cases. Advanced access-restrictions or something like that probably need a more complex syntax or technique, as it is being developed on the Access restrictions proposal.
Tagging
- key=value (any key=value combination)
- key.time=time (specify the time in that the key=value combination above will apply)
It should probably be defined for what tags you should expect a time-parameter, since users of the data would have to check for it's existence all the time. Else there could be misunderstandings, like assuming a road is closed all the time, while it is only once a year. (Maybe there is a better solution for that?)
Examples
A time restricted parking area, but only on workdays from 8:00 to 18:00.
A parking area with a fee, that allows free parking at night.
A residential street that is closed for cars on weekends (except destination traffic).
Comments
Please use the talk page for discussion.