Re: [OSM-talk] [MapRoulette] MapRoulette find your challenge? Your opinions please.

2017-07-21 Thread tuxayo
n't influence it too much. But not too big so use data from last month if possible. To have fresh data and not stale because of a contributor having skipped too much and not enough other contributors. One month is also kind of arbitrary. Cheers, -- tuxayo [1] http://blog.improve-osm

Re: [OSM-talk] Follow up on last summer discussion about the Automated Edits Code of Conduct and the DWG

2017-05-04 Thread Victor Grousset/tuxayo
shades. Indeed, this shows that Armchair Mapping is orthogonal to the 3 above categories. > An example with net benefit for OSM is MapRoulette. Therefore I would > suggest to ask Martijn first for his best practices and then start to > make rules on that. Ask about what exactly? About how to avoid the issues with armchair mapping? Cheers, -- Victor Grousset/tuxayo ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Follow up on last summer discussion about the Automated Edits Code of Conduct and the DWG

2017-04-20 Thread Victor Grousset/tuxayo
, think about it and write this. Feel free to comment here or in the discussion section :) Cheers, -- Victor Grousset/tuxayo ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Is there a uMap like app where one would use addresses instead of placing points manually?

2016-08-06 Thread tuxayo
Hi, Or maybe one can do this in uMap and I haven't found it? The need is to share locations on a map (that's why I though of uMap[1]) using their addresses. [1] https://wiki.openstreetmap.org/wiki/UMap Cheers, -- tuxayo ___ talk mailing

Re: [OSM-talk] Automated edits code of conduct

2016-07-20 Thread tuxayo
ated dupe node merge spent many hours > preparing it, but they still fucked it up, and the damage is still there 6 > years later. > > http://www.openstreetmap.org/node/357366507 Damn, nice catch! At least now there is a note so hopefully it wont stay forgotten for man

Re: [OSM-talk] Automated edits code of conduct

2016-07-18 Thread tuxayo
On 18/07/2016 15:57, Martin Koppenhoefer wrote: >> Il giorno 18 lug 2016, alle ore 00:01, tuxayo ha scritto: >> >> If the edit was discussed and approved, then if after the fact, damage >> that was considered acceptable is discovered. Or damage that doesn't >>

Re: [OSM-talk] Automated edits code of conduct

2016-07-17 Thread tuxayo
On 14/07/2016 11:14, Éric Gillet wrote: > tuxayo: >> A fourth approach to fix that would be to have a first automated edit >> changeset and then a manual fix changeset for the other errors. >> A variant would be to reverse the order: fix the other errors first w

Re: [OSM-talk] Automated edits code of conduct

2016-07-13 Thread tuxayo
r: fix the other errors first when inspecting the selected/searched objects to be automatically edited. And then doing the automated edit. Cheers, -- tuxayo ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Automated edits code of conduct

2016-07-12 Thread tuxayo
actually a great idea! Even something as simple as a message when first using the search and replace would be efficient. *Who have the time to open a ticket?* https://josm.openstreetmap.de/newticket Are there any other common places where first time mass edits could be performed without passing by th

Re: [OSM-talk] Automated edits code of conduct

2016-07-11 Thread tuxayo
of an mapper/software error, the > error may be applied to less content than a large edit. > But contributors can put a lot more focus and time in the "automated" > edit than on each one-by-one manual updates, so I don't think the net > gai

Re: [OSM-talk] Automated edits code of conduct

2016-07-10 Thread tuxayo
feel free to correct me. And sorry for posting this before the end of our discussion but this debate is very close to what I was planning to post here when we would have finished. -- tuxayo ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk