<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1498044292795_198872">Hi Dan</div><div id="yui_3_16_0_ym19_1_1498044292795_198838"><br></div><div id="yui_3_16_0_ym19_1_1498044292795_198795">I agree with you that we have to be careful to be cordial in the messages we write on notes. Yes, this is not easy for new contributors to respond to the notes, especially if they mainly contribute through smartphones. And contributors should be careful in the messages they add on notes.<br></div><div id="yui_3_16_0_ym19_1_1498044292795_198833"><br></div><div id="yui_3_16_0_ym19_1_1498044292795_198908">But the organizers should assure the interaction with the OSM community and assure we can trace easily these edits for eventual corrections. if the edit comment always contain a hashtag or a word such as nrcs, it should be easy to trace the various edits.<br></div><div id="yui_3_16_0_ym19_1_1498044292795_200987"><br></div><div id="yui_3_16_0_ym19_1_1498044292795_200938">Is Kathmandu Living Labs in the loop? They are quite experienced and could help on this. <br></div><div id="yui_3_16_0_ym19_1_1498044292795_198794"> </div><div class="signature" id="yui_3_16_0_ym19_1_1498044292795_198792"><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;" id="yui_3_16_0_ym19_1_1498044292795_198814"> <br><font id="yui_3_16_0_ym19_1_1498044292795_198813" face="garamond, new york, times, serif">Pierre </font><br></span></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1498044292795_198775"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1498044292795_198725" style="display: block;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1498044292795_198724"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, linéale; font-size: 16px;" id="yui_3_16_0_ym19_1_1498044292795_198723"> <div dir="ltr" id="yui_3_16_0_ym19_1_1498044292795_198753"> <font id="yui_3_16_0_ym19_1_1498044292795_198752" face="Arial" size="2"> <hr id="yui_3_16_0_ym19_1_1498044292795_201029" size="1"> <b><span style="font-weight:bold;">De :</span></b> Dan Joseph <dan.b.joseph@gmail.com><br> <b><span style="font-weight: bold;">À :</span></b> talk@openstreetmap.org <br> <b id="yui_3_16_0_ym19_1_1498044292795_198773"><span style="font-weight: bold;" id="yui_3_16_0_ym19_1_1498044292795_198772">Envoyé le :</span></b> mercredi 21 juin 2017 17h51<br> <b><span style="font-weight: bold;">Objet :</span></b> Re: [OSM-talk] "NRCS basic OSM training" - low quality changesets in Nepal<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1498044292795_198722"><br><div id="yiv6903406190"><div id="yui_3_16_0_ym19_1_1498044292795_198721"><div dir="ltr" id="yui_3_16_0_ym19_1_1498044292795_198720">Hi,<div id="yui_3_16_0_ym19_1_1498044292795_198719">NRCS stands for Nepal Red Cross Society, so the people behind the edits are part of the local community. The mappers would be local volunteers and may not be comfortable responding to changeset comments that are written in English. I would also guess that changeset comments were not part of the training. Errant keys are relatively straight-forward to find and fix in JOSM. If the tag value is legitimate local knowledge then a little bit of cleanup work is worth it. Someone at the Nepal RC who does some GIS work is aware of the data quality issues and working to fix it. Training people who have access to smart-phones and computers and who regularly use map services can be a challenge. Training people who don’t have such access is even more of a challenge. The time before every edit is perfectly in line with the established OSM guidelines is bound to be a bit longer. Changeset comments such as "It's likely we have to fully delete it because it would take days to clean everything up by hand." when talking about local knowledge added by locals seems against the spirit of OSM.</div><div id="yui_3_16_0_ym19_1_1498044292795_198910">All the best,<br clear="none"></div><div id="yui_3_16_0_ym19_1_1498044292795_198954">Dan</div></div><div class="yiv6903406190gmail_extra" id="yui_3_16_0_ym19_1_1498044292795_198914"><br clear="none"><div class="yiv6903406190yqt3695677923" id="yiv6903406190yqtfd69623"><div class="yiv6903406190gmail_quote" id="yui_3_16_0_ym19_1_1498044292795_198913">On Wed, Jun 21, 2017 at 3:21 PM, Jan Michel <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:jan@mueschelsoft.de" target="_blank" href="mailto:jan@mueschelsoft.de">jan@mueschelsoft.de</a>></span> wrote:<br clear="none"><blockquote class="yiv6903406190gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" id="yui_3_16_0_ym19_1_1498044292795_198912">Hi,<br clear="none">
I wrote some changeset comments as well as Michałs. None of the was answered up to now, despite many new edits have been made by the users.<br clear="none">
<br clear="none">
It's not just single mistakes, but they accumulate to a substantial amount of data, here's just a small excerpt of what I found:<br clear="none">
<br clear="none">
Key Occurences<br clear="none">
addr:tole 127<br clear="none">
Addr:city 19<br clear="none">
addr: opening time 28<br clear="none">
addr: place 24<br clear="none">
Addr:place 35<br clear="none">
godawari municipality 34<br clear="none">
<br clear="none">
New keys are "invented" every day. I think something should be done soon as cleaning this up is quite some effort. I wonder if there is somebody from the local community available to help?<br clear="none">
<br clear="none">
Jan<span class="yiv6903406190" id="yui_3_16_0_ym19_1_1498044292795_198927"><br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
On 18.06.2017 23:42, Andrew Hain wrote:<br clear="none">
</span><blockquote class="yiv6903406190gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" id="yui_3_16_0_ym19_1_1498044292795_198930"><span class="yiv6903406190" id="yui_3_16_0_ym19_1_1498044292795_198929">
Have you tried politely making changeset comments asking this?<br clear="none">
<br clear="none">
--<br clear="none">
Andrew<br clear="none"></span>
------------------------------ ------------------------------ ------------<br clear="none">
*From:* Michał Brzozowski <<a rel="nofollow" shape="rect" ymailto="mailto:www.haxor@gmail.com" target="_blank" href="mailto:www.haxor@gmail.com" id="yui_3_16_0_ym19_1_1498044292795_198938">www.haxor@gmail.com</a>><br clear="none">
*Sent:* 18 June 2017 21:32:16<br clear="none">
*To:* <a rel="nofollow" shape="rect" ymailto="mailto:talk@openstreetmap.org" target="_blank" href="mailto:talk@openstreetmap.org" id="yui_3_16_0_ym19_1_1498044292795_199695">talk@openstreetmap.org</a><br clear="none">
*Subject:* [OSM-talk] "NRCS basic OSM training" - low quality changesets in Nepal<span class="yiv6903406190" id="yui_3_16_0_ym19_1_1498044292795_198939"><br clear="none">
There has been a number of users making very low quality edits<br clear="none">
(lowercase names, wrong tags. geometry problems among others) in<br clear="none">
Nepal. They all use this mysterious changeset description: "NRCS basic<br clear="none">
OSM training"<br clear="none">
If this is training, then the instructor clearly has no OSM expertise required.<br clear="none">
The mappers seem to make similar errors: misusing tags in addr:*<br clear="none">
namespace, making up amenity=* tags, starting names from lower case.<br clear="none">
</span></blockquote>
<br clear="none"><div class="yiv6903406190HOEnZb" id="yui_3_16_0_ym19_1_1498044292795_198943"><div class="yiv6903406190h5" id="yui_3_16_0_ym19_1_1498044292795_198942">
<blockquote class="yiv6903406190gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" id="yui_3_16_0_ym19_1_1498044292795_198941">
Can we pin down who trains these mappers and demand them to stop and<br clear="none">
take corrective action?<br clear="none">
<br clear="none">
Michał<br clear="none">
</blockquote>
<br clear="none">
<br clear="none">
______________________________ _________________<br clear="none">
talk mailing list<br clear="none">
<a rel="nofollow" shape="rect" ymailto="mailto:talk@openstreetmap.org" target="_blank" href="mailto:talk@openstreetmap.org" id="yui_3_16_0_ym19_1_1498044292795_199032">talk@openstreetmap.org</a><br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/talk" id="yui_3_16_0_ym19_1_1498044292795_198946">https://lists.openstreetmap.or g/listinfo/talk</a><br clear="none">
</div></div></blockquote></div><br clear="none"></div></div></div></div><div class="yqt3695677923" id="yqtfd41753">_______________________________________________<br clear="none">talk mailing list<br clear="none"><a shape="rect" ymailto="mailto:talk@openstreetmap.org" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br clear="none"><a shape="rect" href="https://lists.openstreetmap.org/listinfo/talk" target="_blank" id="yui_3_16_0_ym19_1_1498044292795_198950">https://lists.openstreetmap.org/listinfo/talk</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>