Proposal:Opening hours extension 2019-03-14
| Proposal status: | Draft (under way) |
|---|---|
| Proposed by: | C933103 |
| Tagging: | opening_hours=* |
| Applies to: | |
| Definition: | extend the opening_hours key syntax. |
| Statistics: |
|
| Draft started: | 2019-03-14 |
[[Category:Proposals with "Draft" status|]][[Category:Proposed features under way|]]
Proposal
Expand the syntax of opening_hours=* with the following elements:
Part A
times: Extend the maximum range for hours to 30 so that valid time could be up to 30:59. Useful when shops and such are printing time over 24 hours on their official notice, and might also carry different meanings when DST switch are involved. It also mean that Sa 24:00 will be an acceptable alternative representation Su 00:00, or Fr 27:00 can be interpreted as Sa 03:00 in most usual cases.
Simultaneously, specify that even if a time range is marked in the current way like Sa 22:00-06:00, The day variable given before only applies to the opening time, and that it would automatically lapse into Sunday for the part after the day change even if only "Sa" was specified. In other words, Sa 22:00-06:00 would mean (Sa 22:00)-(Su 06:00). This is actually the way people are now inputting such time, but it seems like it would be better if it can be spelled out on the wiki page.
Part B.1
holidays: Add BH to represent Bank Holiday.
Part B.2
offset_time: sign wd weeks, for example +3weeks to represent 3 weeks after a specific day.
Part C
Mth: Add L01/L02/L03/L04/L05/L06/L07/L08/L09/L10/L11/L12/L01leap/L02leap/L03leap/L04leap/L05leap/L06leap/L07leap/L08leap/L09leap/L10leap/L11leap/L12leap to represent Lunar month in East Asia Lunar (Lunisolar) Calendar using local time zone (Each lunar month start on the day when the new moon occur, and the time new moon occur will be different at different place because of time zone, so same lunar date might correspond to different days in different part of the earth simultaneously.
Solar Term: term1/term2. Use together with western Mth. For example Dec term2 represent winter solstice. Dec term2 +105 represent Hansik festival. Again depend on timezone.
tz identifier: Seems like it won't work and need to be defined via other ways. Leave it for further proposal in the future.
{@tz identifier}/{@UTC sign hh:mm}, for example {@Asia/Shanghai}, used to represent the basis for time calculation that is different from the local timezone, for example L01 01 {@Asia/Shanghai} for Chinese New Year outside Chinese timezone, or L01 01 {@UTC+07:46} for those who are still using old Beijing local mean solar time to calculate the date. Use combined syntax like L01 01 -1 {@Asia/Shanghai} 16:00-21:00 off {@America/New_York} to express a shop located at somewhere using New York timezone would close at 4-9pm on the day before Chinese New Year.
This proposed expansion still couldn't cover some Asian way of date keeping, for example Doyo ushi no hi day that's defined as "ushi" days (2nd day in 12-days week) after the "doyo" solar term (cannot be defined from the above solar term tagging scheme because it is a "miscellaneous" solar term defined as when the sun's ecliptic longitude reached 117 degree) but before risshu (Aug term1), or the Chinese/Korean version of dog days, which are defined as starting from the 7th day on the third 10-days week after Jun term2, and end on the 7th day on the second 10-day week after Aug term1. It might be better to expand the yearly_fest section of the scheme for these festivals instead when the need to represent features that dependent on these festivals arise.
Part D
Add unspecified word event that told users/applications further details can be seen in comments within "".
Rationale
There are currently no simple way to represent these proposed conditions in OSM, adding support for these would allow representing them in OSM
Examples
- Opening time of a restaurant: 18:00-28:00
- Opening time of a bank: Mo-Fr 09:00-12:30,13:00-17:00; BH off
- Operational days of a bus route that operate during the Qing Ming festival and the Double Nine festival, and weekends that envelop the two festivals, can be expressed as following:
Apr term1;(Apr term1 -4weeks Su, PH)-(Apr term1 +3weeks Su, PH);(Apr term1 -2weeks Sa)-(Apr term1 +1weeks Sa);L09 09;(L09 09 -2weeks Su, PH)-(L09 09 +2weeks Su, PH);(L09 09 term1 -2weeks Sa)-(L09 09 term1 +1weeks Sa)
Tagging
Applies to
Nodes, ways or areas
Rendering
Features/Pages affected
External discussions
- Talk:Key:opening_hours#Proposed_extension_to_supported_syntax_in_the_page.
- https://lists.openstreetmap.org/pipermail/tagging/2019-March/043818.html
Comments
Please comment on the discussion page.