[OSM-talk] New OSM Quick-Fix service

[Martin Koppenhoefer]

Frederik:

> I am appalled that after your abysmal OSM editing history where you more
> often than not ignored existing customs rules, while *claiming* to
> follow them, you're now building a service that entices others to do the
> same.
>



> On Sat, Oct 14, 2017 at 6:09 AM Christoph Hormann <osm at imagico.de> wrote:
>> This is a tool to perform automated edits as per the automated edits
>> policy.  A resposible developer of such a tool should inform its users
>> that making automated edits comes with certain requirements and that
>> not following these rules can result in changes being reverted and user
>> accounts being blocked.
>>
>
2017-10-14 13:06 GMT+02:00 Yuri Astrakhan <yuriastrakhan at gmail.com>:

> Christoph, I looked around Osmose and MapRoulette, and I don't see any
> such warnings . Could you elaborate how you would like these kinds of tools
> to promote good editing practices? Any UI ideas? I'll be happy to improve
> our tools on making sure they meet community expectations.
>


I agree with Christoph and Frederik, that this is oviously a tool to
perform (crowdsourced) automated edits, and although it is designed in a
way to make them look like individual contributions, the automated editing
guidelines should apply. I agree with Yuri that there is also (to some
lesser extent, as the editing is not performed by the tool) some
problematic potential in other QA tools like Osmose or "remote batch
fixing" tools like MapRoulette.

The thing with remotely "fixing tags" is that people usually don't know the
situation on the ground and therefore hardly can make an individual
decision for the specific object. The proposed "one-click-solution"
encourages to do quick "fixes" without looking individually, and you even
refuse to notify people that they might be participating in an automated
edit. In examples like the one you gave, even if you look very hard, you
won't see something that confirms the proposed change (you will have to
know the place). I could imagine there are good cases where your tool can
facilitate fixing problems, e.g. with clear typos (highway=residental), but
changing from one tag to a combination of two is not one of them (either we
could make an automated edit, or if it's disputed, we wouldn't do it at
all, rather than sneaking it in via distributed automated editing).

Cheers,
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20171016/1c0fccbc/attachment-0001.html>