Michael Barabanov wrote:
Seems like double work to me. Ross's suggestion may just work. If
there're no objections, I'll update the wiki.
Please not, this is a crude hack. Why not use the opening_hours syntax?
This should be standard.
hours=6:00-9:00,15:00-19:00
Sebastian
On 17 August 2010 17:44, Sebastian Klein basti...@googlemail.com wrote:
Michael Barabanov wrote:
Seems like double work to me. Ross's suggestion may just work. If
there're no objections, I'll update the wiki.
Please not, this is a crude hack. Why not use the opening_hours syntax? This
On Tue, 17 Aug 2010 18:04:21 +1000
John Smith deltafoxtrot...@gmail.com wrote:
On 17 August 2010 17:44, Sebastian Klein basti...@googlemail.com wrote:
Michael Barabanov wrote:
Seems like double work to me. Ross's suggestion may just work. If
there're no objections, I'll update the
John Smith wrote:
On 17 August 2010 17:44, Sebastian Klein basti...@googlemail.com wrote:
Michael Barabanov wrote:
Seems like double work to me. Ross's suggestion may just work. If
there're no objections, I'll update the wiki.
Please not, this is a crude hack. Why not use the opening_hours
Ross Scanlon wrote:
And also a semi-colon ; between the times as per the rest of multiple values
for one key.
No, quoting [1]:
a break on days separated by , · ( e.g. Mo,We,Fr )
a break on hours separated by , · ( e.g. 08:30-14:00,16:30-20:00 )
different hours on different days are
2010/8/17 Michael Barabanov michael.baraba...@gmail.com:
Seems like double work to me. Ross's suggestion may just work. If there're
no objections, I'll update the wiki.
There is already a proposal for this kind of stuff, which would be
possible to apply here as well:
On 17 August 2010 18:52, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
2010/8/17 Michael Barabanov michael.baraba...@gmail.com:
Seems like double work to me. Ross's suggestion may just work. If there're
no objections, I'll update the wiki.
There is already a proposal for this kind of
On 17/08/2010 05:29, John Smith wrote:
On 17 August 2010 13:14, Michael Barabanovmichael.baraba...@gmail.com wrote:
I agree. But I'm not in the mood to start a voting process on changing
hour_on to access:time.
We keep getting told this is a do-ocracy, so if you find something
more
2010/8/17 John Smith deltafoxtrot...@gmail.com:
You were the one complaining about amenity=school being widely used so
we should sub-tag it, I don't think we should do any of the above for
similar reasons, leave the restriction stuff alone and dump
dates/times into their own key pair.
On 17 August 2010 22:27, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
If a restriction is valid only for some time, I would like to see this
in one tag and not in 2 for several reasons:
I think you are over engineering, in any case my previous point still
stands, there is no less than 3
M∡rtin Koppenhoefer wrote:
2010/8/17 John Smith deltafoxtrot...@gmail.com:
You were the one complaining about amenity=school being widely used so
we should sub-tag it, I don't think we should do any of the above for
similar reasons, leave the restriction stuff alone and dump
dates/times into
2010/8/17 John Smith deltafoxtrot...@gmail.com:
On 17 August 2010 23:44, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
Oops, so sorry, I wasn't aware that there is already a time syntax in
the restrictions relation :(
I your suggestion conflicts with the restriction=* values, so any
2010/8/17 Sebastian Klein basti...@googlemail.com:
I don't really like the Extended_conditions_for_access_tags proposal for
reasons mentioned in the above sites and their talk pages. Basically it
violates (or gives up) the principle that keys are simple atomic identifiers
that you can query
2010/8/17 John Smith deltafoxtrot...@gmail.com:
I'm not talking about hour_on, I'm talking specifically about your suggestion:
restriction=[6:00-9:00;15:00-18:00]only_right_turn
Which breaks restriction=*
IMHO it doesn't. It is justified that a restriction that is valid
_only 6-9 or 15-18_
On 18 August 2010 00:03, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
2010/8/17 John Smith deltafoxtrot...@gmail.com:
I'm not talking about hour_on, I'm talking specifically about your
suggestion:
restriction=[6:00-9:00;15:00-18:00]only_right_turn
Which breaks restriction=*
IMHO it
2010/8/17 John Smith deltafoxtrot...@gmail.com:
Your suggestion would require a regex, the time information should be
in it's own key to prevent this.
I'm not a programmer but I think that some substring-parsing would be
sufficient (do you mean this?). For the evaluation of the term you
will
On 18 August 2010 00:06, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
I'm not a programmer but I think that some substring-parsing would be
substring/regex is essentially the same end result.
sufficient (do you mean this?). For the evaluation of the term you
will in all cases need a
2010/8/17 John Smith deltafoxtrot...@gmail.com:
On 18 August 2010 00:03, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
2010/8/17 John Smith deltafoxtrot...@gmail.com:
I'm not talking about hour_on, I'm talking specifically about your
suggestion:
On 18 August 2010 00:08, M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
It is much more elegant on the other hand not to have to create
separate restrictions for all times, but deal in one restriction with
it. The more these things are in use, the more apps will be able to
understand them.
2010/8/17 John Smith deltafoxtrot...@gmail.com:
That's the point, if you are looking for a limited set of values you
can do a complete match, you don't need to try and do anything as
complex or resource intensive as a regular expression *UNLESS* you
know explicitly that key would need to be
On Mon, 16 Aug 2010 18:30:26 -0700
Michael Barabanov michael.baraba...@gmail.com wrote:
Hi,
How would one tag a turn restriction (
http://wiki.openstreetmap.org/wiki/Turn_restrictions) which is active say
6-9AM and 3-6PM every day? hour_on/hour_off seem to only be sufficient for
one time
On Mon, Aug 16, 2010 at 9:30 PM, Michael Barabanov
michael.baraba...@gmail.com wrote:
Hi,
How would one tag a turn restriction
(http://wiki.openstreetmap.org/wiki/Turn_restrictions) which is active say
6-9AM and 3-6PM every day? hour_on/hour_off seem to only be sufficient for
one time
Thanks. BTW, tagwatch does have those:
http://tagwatch.stoecker.eu/Planet/En/keystats_hour_on.html
On Mon, Aug 16, 2010 at 6:47 PM, Ross Scanlon i...@4x4falcon.com wrote:
On Mon, 16 Aug 2010 18:30:26 -0700
Michael Barabanov michael.baraba...@gmail.com wrote:
Hi,
How would one tag a
On 17 August 2010 12:18, Michael Barabanov michael.baraba...@gmail.com wrote:
Seems like double work to me. Ross's suggestion may just work. If there're
no objections, I'll update the wiki.
That would probably be fine for every day of the week, and yes I
noticed day_on/off, but that seems to
I agree. But I'm not in the mood to start a voting process on changing
hour_on to access:time.
On Mon, Aug 16, 2010 at 7:58 PM, John Smith deltafoxtrot...@gmail.comwrote:
On 17 August 2010 12:18, Michael Barabanov michael.baraba...@gmail.com
wrote:
Seems like double work to me. Ross's
On 17 August 2010 13:14, Michael Barabanov michael.baraba...@gmail.com wrote:
I agree. But I'm not in the mood to start a voting process on changing
hour_on to access:time.
We keep getting told this is a do-ocracy, so if you find something
more useful, just do it? :)
I will, once I see a restriction that doesn't fit:)
On Mon, Aug 16, 2010 at 8:29 PM, John Smith deltafoxtrot...@gmail.comwrote:
On 17 August 2010 13:14, Michael Barabanov michael.baraba...@gmail.com
wrote:
I agree. But I'm not in the mood to start a voting process on changing
hour_on to
27 matches
Mail list logo
