Robin `ypid` Schneider
ypid23 at aol.de
Wed Feb 26 12:24:42 UTC 2014
On 26.02.2014 12:45, André Pirard wrote:
> On 2014-02-25 15:24, Peter Wendorff wrote :
>> Hi André,
>> as far as I know, the same would be possible with
>> opening_hours="24/7, Fr 14:00-22:00 off"
> Oh no, please please please, let us not start that same thread all over again.
> (opening-hours: how to code "always but..."?)
> What you say has already been said, amended, denied, rejected in every way etc.
> It's a tagging that I originally proposed and the comments were ("inside quotes")
> -1 24/7 : "it's wrong", "is used for a rendering icon"
> -1 ,; : ,
> -1 off : "is not used", "is used, but not like that"
> On 2014-02-25 15:33, Martin Koppenhoefer wrote :
> On 2014-02-25 15:49, Robin `ypid` Schneider wrote :
>> opening_hours="open; Fr 14:00-22:00 off"
> -1 : open : "it's an invention"
It was introduced by Netzwolf some years ago because it is needed as
<rule_modifier> (when used together with a comment). It is now used over 150
times to do exactly that (regex: /open\s+"/). Of course it is an invention but
one which is required.
> So ... your contradictory replies are the exact proof that closing-hours is
> badly needed.
I do not think that it is needed …
> Failing that, the chaos that you demonstrate will continue.
> And that means a useless database.
I agree. It is a bit difficult but semicolon is the default rule separator and
comma should only be used as needed.
> Only closing-hours=Fr 14:00-22:00 cannot be disputed.
>> no need for an extra tag.
>> Also keep in mind that two tags opening_hours and closing_hours are
>> error prone when used both together at the same object.
>> Am 25.02.2014 14:50, schrieb André Pirard:
>>> I had to tag several parking lots closed on times such as *Fr 14:00-22:00* when
>>> the market took place there.
>>> I raised a convoluted discussion: everyone had a different opinion about that
>>> tagging, plus strange comments (*).
>>> After more than 10 hours spent in research and collaboration, I had to conclude
>>> with the inability of the Key:Opening_hours
>>> <http://wiki.osm.org/wiki/Opening_hours> specification to express that timing,
>>> or explain it, at least simply.
>>> I finally used a vary straightforward and clear:
>>> *closing-hours=Fr 14:00-22:00*
>>> and I suggest that you use it too and that you add that key to the specification.
>>> It can be clearly explained, once won't hurt, as follows:
>>> As often funnily put, /*closing-hours*/ is the same as /*opening-hours*/ except
>>> that it is exactly the opposite :-)
>>> Seriously: use /*closing-hours*/ with the same rules as *opening-hours* and
>>> invert the result: opening time becomes closing time and conversely.
>>> It couldn't be more simple, obvious and understandable. Quite the opposite of
>>> that story.
>>> May this be helpful,
Live long and prosper
More information about the Tagging