<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Aug 1, 2021, 08:12 by dfjkman@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Hi Shawn,<br></div><div><br></div><div>One of the problems is the number of projects on the go at any one time,<br></div><div>Africa has more HOT projects on the go than the rest of the world put<br></div><div>together, many of them overlap and many of them die a natural death without<br></div><div>ever being validated leaving a great deal of mess behind. Many of the HOT<br></div><div>mappers are new to OSM and the same few validators tend to be spread over<br></div><div>many projects and even they may not know what they are looking at in the<br></div><div>satellite imagery, I suspect they also get overwhelmed with the amount of<br></div><div>corrections they have to make.<br></div></blockquote><div dir="auto">Note that it is responsibility of HOT to avoid this.<br></div><div dir="auto"><br></div><div dir="auto">In this case they should more effort into recruiting people who can cleanup<br></div><div dir="auto">invalid data (either experienced mappers already or willing to stay for longer)<br></div><div dir="auto">over recruiting even more inexperienced mappers.<br></div><div dir="auto"><br></div><div dir="auto">Even if raw statistics like count of mapped buildings looks worse when<br></div><div dir="auto">doing mapping properly.<br></div><div dir="auto"><br></div><div dir="auto">If HOT validators are overloaded it is a sign of HOT mismanaging situation.<br></div><div dir="auto">It is not responsibility of mapper community to cleanup such mapping,<br></div><div dir="auto">it is responsibility of HOT.<br></div><div dir="auto"><br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"> The real problem comes where you have a particular mapper who is<br></div><div>unwilling to take the advice given and continues to make the same errors<br></div><div>over and over.<br></div></blockquote><div dir="auto">In such case their edits should be reverted.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Then you get projects that come through and make changes to major road<br></div><div>classifications, remove roads that do not appear in imagery but have been<br></div><div>mapped by a local mapper and change classifications. After you make<br></div><div>corrections the whole thing kicks off again with the next project that comes<br></div><div>through with a new hashtag. Sort of like a 'Mad Max' movie. As a local<br></div><div>mapper you either run around trying to fix the errors or slink off to some<br></div><div>far flung corner and map in peace.<br></div></blockquote><div dir="auto">There is a big danger that some well meaning and well funded projects such<br></div><div dir="auto">as HOT-directed remote mapping will destroy any potential local communities :(<br></div> </body>
</html>