If I may add my 2ยข here. Apply the KISS principle (Keep It Short and Simple). PS: I know that KISS initialy stands for keep it simple stupid but I don't want to be rude ;-)
I am a newbie. I am not a map specialist. I love to do cycling. And Openstreetmap can help me practicing my activity. And I am willing to collaborate to the project, marking cycleways, as long as I understand how I can do it. If you complexify things too much, you will lose your collaborators. You will lose me. You count on a lot of collaborators to map the world, aren't you? I have discover Openstreetmap about 2 weeks ago. I use the native openstreetmap.org interface with the "Overlays/Data" function to see details of road I am planning to use for my cycling ride. Surface=Paved/Unpaved is what is most interesting for me at this time and I can see it that way. Great. It is readable. If your tag pattern gets too complicated, (1) it won't be followed by "ordinary" collaborator and (2) it might become unreadable for ordinary people. I would add that it might also become more complex for "rendering-map maker" ... But that, I don't know. I've suggested a shoulder=yes/no tag. Somebody came out with a complex structure (probably valid) for shoulders. Does it really have to be that complicated? I don't know. You, speclists, know better than me. What are the objective of the openstreetmap project? Identify everthing on earth? Or provide a complete free map of the world? Maybe I don't get it right... But don't kill the project with unfollowable and incomprehensive rules / tags. KISS. Daniel Tremblay
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
