hi, On Sat, 22 Aug 2009, Tobias Knerr wrote:
>> I listed :backward and :forward postfixes for access keys > > What you are doing here seems like picking raisins from conditional > tagging and trying to handle it as a special case. I'm not sure whether > you are aware of my proposal? > > http://wiki.openstreetmap.org/wiki/Proposed_features/Conditions_for_access_tags I didn't really answer this question yet. My idea with :forward and :backward was to group all access restrictions - keys that take yes/no/destination/private/etc. - with the access key. So I also sometimes write e.g. access:vehicle:forward=no . But time restrictions should also be included, e.g. as :T<from>-<to>, so one could write (crazy) things like: access:vehicle:forward:Tmo-fr=destination access:vehicle:forward:Tsa-su=yes access:vehicle:backward:Tmo-fr=delivery access:vehicle:backward:Tsa-su=no A problem with oneway= is that it cannot accept the whole range of access values - only yes/no. So the above cannot be done with :oneway AFAICT. (max)height/weight/width/speed could maybe also be included with access, but I think it is better to treat them as "access limits" and keep them separate. Then the conditions proposal looks good for these keys. Christiaan _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
