Re: "Try to keep changesets to a manageable size, both in number of changes and geographical scope."
This would be good to add to "Good changeset comments" https://wiki.openstreetmap.org/wiki/Good_changeset_comments If a changeset covers a huge are or too many changes, it won't be easy to understand the comments in the future. It's not usually a problem for iD users, since you get a warning when over 100 objects have been edited and it's hard to scroll around too far, but it happens with JOSM and imports. Many of the issues with too large changesets are related to imports and mechanical edits, which are not currently discussed on this Good_practice page but have separate pages: https://wiki.openstreetmap.org/wiki/Automated_edits https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct https://wiki.openstreetmap.org/wiki/Import https://wiki.openstreetmap.org/wiki/Import/Guidelines On 7/5/19, Warin <61sundow...@gmail.com> wrote: > On 05/07/19 05:54, Jmapb wrote: >> On 7/4/2019 12:40 AM, Warin wrote: >>> On the order of things. >>> >>> Best to tell them what to do first. This provides some motivation. >>> >>> Leave 'what not to do' for last, these tend to turn people away. >>> >>> So I would do: >>> >>> 1 One feature, one OSM element >>> >>> 2 Good changeset comments (+Keep the history) >>> >>> 3 Editing Standards: (Align aerial imagery before tracing, Do not >>> trace from outdated imagery... Keep straight ways straight ... Mark >>> estimations with FIXME ... etc.) >>> >>> 4 Do correct errors >>> >>> 5 Verifiability (+Map what's on the ground, Don't map: historic >>> events, temporary features, local legislation etc) >>> >>> 6 Document your custom-tags (Don't remove tags that you don't >>> understand... >>> >>> 7 Don't map for the renderer (+ Don't misuse name tag) >> >> I'd personally advocate for one more "don't" -- But it can be phrased as >> a "do" if that helps the psychology: >> >> "Try to keep changesets to a manageable size, both in number of changes >> and geographical scope." >> >> I believe this is commonly understood best practice, but it's only >> vaguely documented. > > +1 .. and guilty of it too (in my early days). > > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
