Changeset Best Practices - TelenavMapping/Telenav_mapping_team_practices_and_workflow GitHub Wiki

What are changesets?

A changeset consists of a group of changes made by a single user over a short period of time. One changeset may include additions of new elements to OSM, the addition of new tags to existing elements, changes to tag values of elements, deletion of tags and also deletion of elements. ch5

Changeset comments

Why do we use changeset comments?

  • It makes it easier to other mappers to understand what you have done
  • To avoid misunderstandings and get mistakes fixed quickly
  • Comments help you remember what you did, why and when

Examples

ch3

Changeset source

Why do we use changeset source?

  • Fellow mappers can clearly see the source for the edits that have been made in the changeset
  • Fellow mappers can double check the source if any doubts should appear

Examples

ch4

Golden rules

  • Please remember that your changeset will remain in the OSM database for as long as the project lives! Don’t use them to vent anger at your fellow mappers who might have prompted you to fix something or might have questioned your edits.
  • Keep them as tidy as possible, minimising the geographic area you’re editing in. Try to avoid to edit in Canada and then edit in Europe in the same changeset. So upload often. This helps with avoiding editing conflicts and makes changesets easier to 'read' by others. There are no 'hard' rules but here are some guidelines:
    • Changeset bounding box < 1km x 1km.
    • No more than 100 edits in one changeset.
    • Changesets should cover the same types of edits (for example only TR, only new roads, etc)
  • Always add a comment and a source for your changesets.
  • Try to be as explicit as possible about your edits by taking full advantage of the changeset comment and changeset source.