andyb109 blocked by SomeoneElse
- Created:
- Duration:
- 0 hours
- Status:
- Ended .
- Reason for block:
Hello andyb109,
Since you started editing OpenStreetMap six weeks ago you’ve added a lot of “natural=peak” data to OpenStreetMap. Unfortunately quite a lot of them seem to be:
-
duplicates of existing data,
-
misnamed, or
-
in the wrong place
As an example, a few days ago you added:
osm.org/node/3371183186/history#map=16/52.9431/-3.2090
This is an almost exact duplicate of:
which has been in the database for over two years. I’m sending you this message as one that you have to read before continuing editing because previous attempts at communication have failed. I’ve previously added to changeset discussions to the following changesets:
osm.org/changeset/28284143 osm.org/changeset/28433302 osm.org/changeset/28503017 osm.org/changeset/28504411 osm.org/changeset/28506109 osm.org/changeset/28506129 osm.org/changeset/28508130 osm.org/changeset/28511355 osm.org/changeset/28651871 osm.org/changeset/28688379 osm.org/changeset/28735192 osm.org/changeset/28735244 osm.org/changeset/28735381
but haven’t heard anything back. It’s possible that your email is misconfigured, which is why I’m sending this message like in this way.
OpenStreetMap is a shared database. We all collectively benefit from the data that we all individually add to it. Unfortunately, if people add duplicates, misnamed or misplaced things, it devalues the hard work of the people who have previously added valid data. I’ve deleted some of the duplicates above already; other mappers have deleted some of the others.
It’s therefore important that we all take care to get things right. It’s not good enough to pick some text on an OS OpenData or out-of-copyright map, find a nearby area of high ground, and assign that name to it regardless of whether in real life it’s likely to be called that or not. For example, at this location:
osm.org/node/3295427561/history#map=16/52.9261/-3.5377
there is a name “Lily’s Wood” on both the OS OpenData and NLS 1:25k OOC maps. However, in this case it is likely that it applies to the wood in which the name occurs:
which was added to OpenStreetMap some time ago (the clue is in the word “wood”).
The NLS 1:25k contours do show a local maximum in the ground level within the wood, but no name distinct name appears to be assigned to it - and therefore no name should be made up for it within OSM. It’s also important that meaningful changeset comments are used to help communicate to other mappers how the data was added and why it is valid. In this case (changeset comment “Added new peak”) this was not done.
So, once you’ve read this message please do continue editing OpenStreetmap, but please do make sure that:
-
You don’t duplicate existing data that has already been added.
-
You only add data that is valid, correctly named and in the correct location.
-
You don’t make up names because you think “this ought to be a named peak” where in reality it is not.
-
You use meaningful changeset comments explaining how any why you know that the edits are valid. Not just something like “Added peak name from OS data”, but: which OS data? OS OpenData or an out of copyright map? If an out of copyright map which one, and how do you know that that name is still valid now? If you don’t abide by these rules you will be stopped from editing OpenStreetMap.
If you’ve got any questions please don’t hesitate to contact me or anyone else in OSM’s data working group by email to data@osmfoundation.org .
Best Regards,
Andy Townsend, on behalf of the OSM Data Working Group.
-