[OSM-newbies] Do, then document, or ask first?

[Randy]

Alan Mintz wrote:

>For several months, I've been doing a lot of mapping on OSM in southern
>California.
>
>In general, when there is not a direct answer for something in the wiki,
>I've tried to come up with one from logic and similar documented
>situations, tagged that way, and then added it to my list of issues, which
>has grown to several dozen now, instead of bombarding the mailing list with
>questions.
>
>What do I do now? Do I edit the wiki to reflect what I've done, and maybe
>send a list of links to the list so people can review/comment/object, or
>should I send the issues one by one to the mailing list and then fix if
>necessary and document afterwards, or some other method?

You can find many different threads in the various talk lists about how to 
handle changes, from the "only use approved tags" to the "tag it anyway 
you want and forget about it". But based on my very limited experience, a 
middle of the road approach to answer your question is "It depends."

If you are adding a simple expansion to an existing tag, (such as my 
addition of number as an additional tag for addr:interpolation), or maybe 
the addition of "culvert" as an additional tag for waterways, then go 
ahead and use it. But, bring it to the masses in talk-tagging. You may 
find that you have missed an existing tag, or others may have ideas for 
improvement. Then, when the dust settles, add it to Map Features if 
appropriate, and go back and tweak your tags, if necessary.

For more extensive changes, which might require a significant description, 
and may impact existing tagging methods (such as my proposal to add 
"covered" as a property to tag various nodes/ways/areas) it may be better 
to create a formal proposal page and add it to Proposed Features, and 
announce it in both tagging and talk-main. If you're unsure about the 
approach, bring it to talk. Someone will tell you which way to go (but be 
prepared for conflicting responses).

Then there are the simple little things like adding a new amenity or shop 
tag. Personally, if I can't find an existing tag that fits, I just come up 
with the best description I can, and press on. You may (or may not) want 
to announce that you've added one. Amenities and shops are of such wide 
variety that it is hardly worth announcing them. It is, however, a good 
idea to check TagWatch, to see if you can find something similar that 
works rather than adding a new tag.

Final caveat: I'm a relative newbie, so take what I say with a grain of 
salt, and listen to the more experienced.

-- 
Randy