Hi John,

Just to say that we've deployed an updated version - there's still a lot to
do, and some queries of course can get the overpass API to time out... but
e.g. here's a sample, looking at hashtag #crows2map (the mapathon
tomorrow), limited to Tanzania:

http://bjohas.de/mmstats/www/mmstats.html?hashtag=crowd2map&from=&to=&user=&bbox=29.3269773,-11.761254,40.6584071,-0.9854812&RedCrossStats=true&queryResults=true&alwaysShowOPdetails=false&showAPIqueries=false&autorun=1

Scroll past the query boxes, to see the output.

In response to your question:

On 9 August 2017 at 22:54, john whelan <jwhelan0...@gmail.com> wrote:

> What is needed is to pick up the coordinates of each tile of each project.
>

Yes - I wished there was an URI like
http://tasks.hotosm.org/project/3296/bbox that gave you the bbox for the
task, and ideally ..../tiles as well.


> Then pickup the mapper's name from the task manager whether or not they
> have completed a tile.
>

That may not be needed, as you can just get the edits in that tile?

Each day scan all the uploads for unusual tags, discard those who weren't
> on the list of HOT mappers, check the coordinates for the project and tile.
>

Our tool does this, but you just have to enter the coordinates manually. I
think the tile may not be needed in the first instance, as it doesn't
really matter, as long as you can find the user? I would do the check per
project, and then message the user. Of course, if you want to give feedback
on the tile, then you need the tile.


> Feed that into a list that a validator could check.  Not easy but
> technically doable.  Ideally sorted by the number of edits the mapper has
> made.
>

If I understand you correctly, then we have this. Our tool outputs links to
OSM for each problematic object. (At the moment only to the OSM site, but
we'll amend this to load them in bulk into JOSM... when we have a moment -
it's easy to do).


> If it picked up suspect tags like living_street in Africa it wouldn't
> break my heart.
>

At the moment, the list of tags that are deemed 'ok' is fixed, but it could
easily be changed.


> Something for the Ottawa summit perhaps?
>

I won't be there, but happy to participate remotely.

Bjoern


>
> On 9 August 2017 at 16:47, Bjoern Hassler <bjohas...@gmail.com> wrote:
>
>> Hi John,
>>
>> We've made a bit of progress regarding mmstats, https://github.com/OS
>> M-Utilities/JOSM-Scripts-HOT/tree/master/www, latest working version
>> deployed here: http://bjohas.de/mmstats/www/mmstats.html
>>
>> We'll make a bit more progress over the next few days, but it does
>> already pick up when mappers are using tags outside a specified set. It's
>> quite simple but would have picked up this issue.
>>
>> It would be great if project owners trialled
>> http://bjohas.de/mmstats/www/mmstats.html on their project hashtag -
>> we'd be quite happy to tailor it (where possible given the currently
>> existing APIs, i.e. red cross / overpass etc).
>>
>> Bjoern
>>
>> On 9 August 2017 at 21:03, john whelan <jwhelan0...@gmail.com> wrote:
>>
>>> Yes I know I'm a bit one tracked sometimes but quite by chance I
>>> stumbled across a HOT mapper who had tagged 264 buildings Yess=Building
>>> in Togo.
>>>
>>> I have corrected these but they were done five months ago.
>>>
>>> In the ideal world we would have enough validators but we don't so could
>>> someone at least scan the mappers mapping on a project and highlight
>>> unusual tags or even no tags?
>>>
>>> If it could be done daily feedback could be given quickly which would
>>> reduce the number of errors and the time spent correcting them.
>>>
>>> It does require some manual validation but it would pick up problems
>>> more quickly.
>>>
>>> Thanks John
>>>
>>> _______________________________________________
>>> HOT mailing list
>>> HOT@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/hot
>>>
>>>
>>
>
_______________________________________________
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot

Reply via email to