| 3 | | IMHO it is detrimental to OSM to have such changesets; one simple example (I am sure there are better ones): a changeset introducing lots of address data, |
| 4 | | no source given - has the address data been copied from a map which is considered a fallback/secondary source only and should thus be checked doing a |
| 5 | | survey or has the data actually been collected during a survey? Similarly, empty changeset comments are obviously not helpful for deciding if a changeset |
| 6 | | should be checked for quality assurance etc. |
| | 3 | IMHO it is detrimental to OSM to have such changesets; one simple example (I am sure there are better ones): a changeset introducing lots of address data, no source given - has the address data been copied from a map which is considered a fallback/secondary source only and should thus be checked doing a survey or has the data actually been collected during a survey? Similarly, empty changeset comments are obviously not helpful for deciding if a changeset should be checked for quality assurance etc. |
