Re: [Tagging] Expand the key:opening_hours

On 14/03/19 11:30, Sergio Manzi wrote: On 2019-03-14 01:28, Warin wrote: Think best to separate it from the present opening hours. Perhaps   opening_hours:persian=* (example - where the Persian calendar is in use).??? Good idea! Happy Nowruz, Persian year 1398. _

Re: [Tagging] Expand the key:opening_hours

Of course such shop will also need to indicate the closing date in Gregorian calendar fashion, but as those date are not fixed, if you are typing that information in Gregorian calendar into OSM then you're effectively inputting one-off event into OSM that needs to be changed every year to match the

Re: [Tagging] Expand the key:opening_hours

Am 14.03.2019 um 23:18 schrieb Phake Nick: > > > 在 2019年3月14日週四 20:38，Simon Poole > 寫道： > > Some more comments: > > - the OH values are currently always evaluated in the local time zone > (or to go even a bit further in a local context as the location they >

Re: [Tagging] Expand the key:opening_hours

在 2019年3月14日週四 20:38，Simon Poole 寫道： > Some more comments: > > - the OH values are currently always evaluated in the local time zone > (or to go even a bit further in a local context as the location they > apply to is always known), so a time zone indicator would be only needed > in the cases tha

Re: [Tagging] Expand the key:opening_hours

Some more comments: - the OH values are currently always evaluated in the local time zone (or to go even a bit further in a local context as the location they apply to is always known), so a time zone indicator would be only needed in the cases that require different processing, the question is if

Re: [Tagging] Expand the key:opening_hours

Separating it from the current system might have the advantage that it will not need to use the same syntax to support all regional specific methods of day counting and time counting at once, but even after separated it will still need to support the full set of current opening_time specification i

Re: [Tagging] Expand the key:opening_hours

On 2019-03-14 01:28, Warin wrote: > Think best to separate it from the present opening hours. > > Perhaps   opening_hours:persian=* (example - where the Persian calendar is in > use).??? Good idea! Sergio smime.p7s Description: S/MIME Cryptographic Signature _

Re: [Tagging] Expand the key:opening_hours

On 14/03/19 10:52, Simon Poole wrote: Just a PS: any grammar extension need to be compatible with the use of OH strings in conditional restrictions too, see https://wiki.openstreetmap.org/wiki/Conditional_restrictions . While I haven't looked at in detail your proposal for a timezone extensio

Re: [Tagging] Expand the key:opening_hours

Just a PS: any grammar extension need to be compatible with the use of OH strings in conditional restrictions too, see https://wiki.openstreetmap.org/wiki/Conditional_restrictions . While I haven't looked at in detail your proposal for a timezone extension might have difficulties with that. Am 14.

Re: [Tagging] Expand the key:opening_hours

The basic problem with proposing an extension to the current OH grammar is that it is already far too complicated and full of ambiguities, there are afaik currently only two parsers that handle > 90% of the grammar and most of the other ones are rather broken, adding more stuff is definitely not go

[Tagging] Expand the key:opening_hours

I found that the current way of mapping opening time of features in OSM map are too limiting, and the opening time of some features cannot be properly represented with only the current syntax, therefore I have written a brief idea about how the syntax in key opening_hours could have been expanded t