[Tagging] Extended tagging schema - my thoughts
rob.j.nickerson at gmail.com
Fri Aug 10 16:19:50 BST 2012
>* > - you lose backward compatibility*>* *>* The proposal falls back to existing tag schemas therefore providing*>* backwards compatability.*
No, it doesn't. If you set maxspeed=120; wet 80, then none of the
existing routing programs can use this tag anymore. The Extended
Conditions proposal uses the tagging maxspeed=120, maxspeed:wet=80,
which allows existing routing programs to still use the maxspeed key.
>* > - you run into the (real) risk of exceeding the 255 byte limit imposed on values*>* *>* That would have to be one hell of a complicated access rule!!*
Oh, you haven't seen anything. German inner city pedestrian zones are
infamous for complex access restrictions (taking into account
bicycles, delivery traffic, destination traffic, taxis, all of them
depending on the day of week and the time of the day, and sometimes
even on the direction).
Apologies. What was meant was that software need only cut off the
extended values to return to existing systems (and thus
compatibility). For example "maxspeed=120; wet 80" is chopped down to
". As there are lots of tags in use, it will be tricky to find a
schema that is both liked and does not break a single thing.
As for 255 bytes. All vehicles have their own tag, so would be tricky
to hit 255 bytes.
p.s. I am trying to suggest an alternative that does not put all the
conditions in the tag key (as this was one of the big criticisms).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging