| 8 | | Because there are hundreds of mappers publishing their geo-data on the OSM server it is important to track who published what data in which context. It would be tedious for mappers to describe for every single node and every single way why it is published. A more convenient approach is to package a group of related objects and assign the package a comment, not the individual objects. This way, if a mapper maps his or her neighborhood, he or she can upload a package of nodes and ways and assign it a comment "`mapped and reviewed some ways in foo city`". |
| | 8 | Because there are hundreds of mappers publishing their geo-data on the OSM server it is important to track who published what data in which context. |
| | 9 | |
| | 10 | Changesets simply group data creations, modifications and deletions - with additional properties {{{comment}}}, {{{created_by}}}, {{{imagery_used}}} [osmwiki:Proposed_features/changeset_tags and several others] (this information stored as simple tags). Similar to other wiki software, one changeset can affect one object (a single character edit in the text), but may contain big changes (removals of paragraphs, partial or complete rewrite of the text) with the only difference that geo information is edited instead of text. Investigating history of one character is equally hard to comparing text at given point in time. Since [osmwiki:Planet.osm complete "text" in OSM is 30-600GB big] therefore users speak of history within several changesets and not about complete history every time. |
| | 11 | |
| | 12 | A more convenient approach is to package a group of related objects and assign the package a comment, not the individual objects. This way, if a mapper maps his or her neighborhood, he or she can upload a package of nodes and ways and assign it a comment "`mapped and reviewed some ways in foo city`". |
