brycenesbitt wrote > 5. There are concerns that iD makes deletion of features more prominent > in the UI, compared to prior editors.
In all this discussion if the delete feature, or rectanglify is too prominent, I always wonder why people don't just undo the accidental mistake? Even as an "experienced mapper" I have made enough accidental mistakes by e.g. deleting the wrong thing, or moving whole land areas instead of just a node, or the editor did something I did not expect it to do or I did something else destructively by mistake. And I have done this in all the editors I have used including JOSM. However, I hope that I have always noticed that what I just did was unintentional and hit the undo button. (In that respect I am rather glad OSM got rid of the "live edit mode" of Potlatch where the option of undo, or in the worst case just close the editor without saving, was not possible) So one line of questioning should be: Do people not notice what they have done? Do people intend to do those actions, because they did not understand that this was wrong? Do people not find the undo button? Does the editor too often do things they didn't expect and got so frustrated that they saved the broken result anyway? Apart from in the last case, reducing the prominence of the delete and rectanglify buttons likely won't really help. Both delete and rectanglify really are pretty basic functions that any new user is likely to seek out, so hiding it isn't going to help. Amongst the people who do new user training and therefore have a great opportunity to observe newbies and understand where they go wrong, has anyone observed this specific issue of unintended deletions getting into the DB? Do they have any insights as to what went wrong in the human-editor interaction? Are there other user interface changes possible to make people more aware of what they are doing? I.e. make sure that e.g. deleting something is visually obvious? Perhaps the currently selected object needs to be "bright yellow", in which case any changes to that object becomes much more prominent and you can't just accidentally do something to the object without noticing? This may well even be helpful to experienced mappers to make sure they know what is going on. Particularly if you have an "inteligent" editor which tries to guess what you wanted to do and automatically do it for you. On the other hand, is this really an issue with iD? Or does it happen just as much in other editors and a small error rate is simply inevitable in a collaborative project like OSM? Kai -- View this message in context: http://gis.19327.n5.nabble.com/Making-iD-the-default-editor-on-osm-org-tp5773770p5774154.html Sent from the General Discussion mailing list archive at Nabble.com. _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
