<div dir="ltr">Mikel et al,<div><br></div><div>I agree that we need to change the way we do mapathons, the credibility of HOT and OSM is at risk.</div><div><span style="text-size-adjust: auto;">I have observed some characteristics about the OSM mapping through HOT tasks being done by mapathons, primarily ones done by corporate sponsors.</span><div style="text-size-adjust: auto;">It appears that often these efforts are not well led, or at least not led by individuals that have a good level of OSM experience and skills. The results are that very common mistakes and errors are created.</div><div style="text-size-adjust: auto;">1) The instructions are not followed, nor even apparently read.</div><div style="text-size-adjust: auto;">2) Individuals assume that a tile must be completely mapped and will add features that are not called for in the instructions such as landuse or highways.</div><div style="text-size-adjust: auto;">3) The tagging of features is not done based on OSM guidance, for example a path in Tanzania is often tagged as "motorway", "primary", "secondary" or other type of highway.</div><div style="text-size-adjust: auto;">4) Additional tags are added without local knowledge such as railroads, traffic cameras, and businesses that are not apparent from imagery.</div><div style="text-size-adjust: auto;">5) Using iD with the default image (Bing) without changing the background image leads people to mark a tile as "bad imagery" when the Digital Globe or Esri imagery in that location is fine.<br></div><div style="text-size-adjust: auto;">6) Sometimes mappers will assume that OSM is a game like Sim City or Minecraft and create their own imaginary features</div><div style="text-size-adjust: auto;">7) One characteristic of many of these mappers is an apparent hurried to try to finish a tile. The buildings are over-generalized by either combining buildings, creating polygons much larger than the actual building, often the shapes are very crude and are not carefully formed with right angles, many buildings are skipped or overlooked, many are overlapping with other buildings or roads, and in many cases create self-intersecting polygons</div><div style="text-size-adjust: auto;">8) Once a mapper starts with these bad habits the habits are picked up by others working at the same time which expands the problems</div><div style="text-size-adjust: auto;">9) It appears that after a small number of edit sessions the mappers from these efforts do not continue with other HOT tasks, and presumably go a way thinking they have done their feel-good-humanitarian-service.</div><div style="text-size-adjust: auto;"><br></div><div style="text-size-adjust: auto;">The net result of these mapathons is that rather than contributing to the completion of mapping in an area, there is actually more work required to clean up the messes than there would have been to properly trace the features from scratch.</div><div style="text-size-adjust: auto;">I do not believe this is a validation issue, but is an issue with leadership. The individual organizing the event for the corporation or group may have little or no OSM experience, and have been giving the task of setting up the mapathon and do not have the skills or expertise to help newbie mappers. I also have seen people that claim to have OSM experience or skills often are very inexperienced and have very slight exposure, There is a lot to learn about OSM, and we do ourselves a disservice by saying that it's easy and anyone can do it. We should be happy to teach people, but I don't believe any of us doesn't have more to learn.</div><div style="text-size-adjust: auto;">I have led several corporate mapathons in person and remotely, they are hard work. The same can be said for tertiary school effort.</div><div style="text-size-adjust: auto;"><br></div><div style="text-size-adjust: auto;">Perhaps HOT should establish a test or a vetting process for potential mapathon leaders?</div><div style="text-size-adjust: auto;"><br>Emmor</div><br class="gmail-Apple-interchange-newline"></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 2:06 PM Mikel Maron <<a href="mailto:mikel.maron@gmail.com">mikel.maron@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
Important to note the guidelines are suggestions not enforced requirements of the OSMF. More on that in the blog post <br><a href="https://blog.openstreetmap.org/2019/02/09/organised-editing-guidelines/" target="_blank">https://blog.openstreetmap.org/2019/02/09/organised-editing-guidelines/</a> <div><br></div><div>My opinion is master list of mapathons is a very good idea. I don’t think the wiki is best system suited to be the place for that primary list. Another tool could mirror to the wiki for archiving purposes.</div><div><br></div><div>I agree with Pierre. Data quality needs to become a primary focus of these and other mapping activities asap. Otherwise it’s not valuable experience for those present or everyone else working with OSM data. I think that will take more than trend, but a substantial direct investment by HOT, Missing Maps and others in systematically operationalizing data quality improvements across through training, monitoring, etc.<br><div id="gmail-m_-2969640424364709222temp-enhancr-placeholder" class="gmail-m_-2969640424364709222enhancr-placeholder-medium"></div><br>Mikel<br><p class="gmail-m_-2969640424364709222yahoo-quoted-begin" style="font-size:15px;color:rgb(113,95,250);padding-top:15px;margin-top:0px">On Wednesday, March 27, 2019, 11:22 AM, Pierre Béland via HOT <<a href="mailto:hot@openstreetmap.org" target="_blank">hot@openstreetmap.org</a>> wrote:</p><blockquote class="gmail-m_-2969640424364709222iosymail"><div id="gmail-m_-2969640424364709222yiv7986055758"><div><div class="gmail-m_-2969640424364709222yiv7986055758ydpa1ea26c9yahoo-style-wrap" style="font-family:verdana,helvetica,sans-serif;font-size:13px"><div><div>Shoud I insist, we also need a new trend where such projects take responsability to produce quality data. Badly, too often, this is not what we observe. For the Ebola response in North Kivu, the coordinators, we had to restart the mapping of Butembo in december since the data produced by newbies was so imprecise, so incomplete.</div><div><br clear="none"></div><div>Adequate training material and mapathon procedures need to be developped for Live data monitoring, interaction with newbies, and correct immediately quality problems. <br clear="none"></div><div class="gmail-m_-2969640424364709222yiv7986055758ydpa1ea26c9signature"><span style="font-style:italic;color:rgb(0,0,191);font-weight:bold"> <br clear="none">Pierre <br clear="none"></span></div></div>
<div><br clear="none"></div><div><br clear="none"></div>
</div><div class="gmail-m_-2969640424364709222yiv7986055758ydp805062a5yahoo_quoted" id="gmail-m_-2969640424364709222yiv7986055758ydp805062a5yahoo_quoted_3745708970">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div class="gmail-m_-2969640424364709222yiv7986055758yqt9981346311" id="gmail-m_-2969640424364709222yiv7986055758yqtfd98368"><div>
Le mercredi 27 mars 2019 10 h 40 min 07 s HAE, Rory McCann <<a href="mailto:rory@technomancy.org" target="_blank">rory@technomancy.org</a>> a écrit :
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div dir="ltr">The OSM community & Foundation has recently adopted the Organised<br clear="none">Editing Guidelines, to guide events like this. The community wants to<br clear="none">help you make this a successful mapathon.<br clear="none"><br clear="none">In emails like this, and in accordance with the OEG, you should link to<br clear="none">the wiki page(s) describing your mapathon.<br clear="none"><br clear="none"><a rel="nofollow" shape="rect" href="https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines" target="_blank">https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines</a><br clear="none"><br clear="none"><a rel="nofollow" shape="rect" href="https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities" target="_blank">https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities</a><br clear="none"><br clear="none"><br clear="none"></div></div>
</div></div><div class="gmail-m_-2969640424364709222yiv7986055758yqt9981346311" id="gmail-m_-2969640424364709222yiv7986055758yqtfd14852">
</div></div></div></div><div class="gmail-m_-2969640424364709222yqt9981346311" id="gmail-m_-2969640424364709222yqtfd62043">_______________________________________________<br clear="none">HOT mailing list<br clear="none"><a shape="rect" href="mailto:HOT@openstreetmap.org" target="_blank">HOT@openstreetmap.org</a><br clear="none"><a shape="rect" href="https://lists.openstreetmap.org/listinfo/hot" target="_blank">https://lists.openstreetmap.org/listinfo/hot</a><br clear="none"></div><blockquote></blockquote></blockquote></div>
</div>_______________________________________________<br>
HOT mailing list<br>
<a href="mailto:HOT@openstreetmap.org" target="_blank">HOT@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/hot" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/hot</a><br>
</blockquote></div>