On Fri, Aug 7, 2009 at 4:22 PM, John Smith<[email protected]> wrote: > It's going to get very messy very quickly if you are trying to shoe horn > general time limits in with school zones, but you could do: > > maxspeed=80 > maxspeed:time_1=school;07:00-09:00,14:30-15:30;mon-fri;40 > maxspeed:time_2=all;16:00-19:00;mon-fri;60
I was not proposing that a school zone restriction must be shoe horn'ed in with a general time limit - you could have: maxspeed=80 maxspeed:school_zone=07:00-09:00,14:30-15:30;40 maxspeed:time_1=07:00-09:00;40 maxspeed:time_2=16:00-19:00;60 I don't like the _1 and _2, but I guess you're saying that's the only way to make sure you keep ALL the values in the value field (which you seem to be advocating)? > Actually the whole idea of getting all values into a single line probably > will only serve to make a mess of it completely. Perhaps, though IMHO the multi-tag school_zone proposal is 1) not entirely un-messy, 2) more importantly, does not seem to fit into any sort of existing or proposed framework for other access tags. > So now we're at this: > > maxspeed:time=reason;hh:mm-hh:mm[,hh:mm-hh:mm]*;[dd-dd|dd,dd,dd];xxx More like: maxspeed:school_zone=hh:mm-hh:mm[,hh:mm-hh:mm]*;[dd-dd|dd,dd,dd];xxx and maxspeed:time=hh:mm-hh:mm[,hh:mm-hh:mm]*;[dd-dd|dd,dd,dd];xxx Keep in mind that this format is actually quite simple and intuitive, and I would argue gives a good framework for other access tags with conditions: <X>:<K> = <L>;<V>, where the format of <L> depends only on <K>. I'm gonna leave this thread be for now, I've said enough. What do others think? _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
