[OSM-talk] [OSM-dev] Tool update from HOT: MapCampaigner

[John Whelan]

Do we really need yet another tool to find errors in HOT mapping?

Before the new version of task manager I did a lot of validation in HOT.

One of the problems on the data quality side is new mappers just don't 
completely map a tile and mark it done for validation.  Which means 
finding their new work is not easy.

If you can give feedback to a new mapper ideally within hours but at the 
outside a couple of days it often does correct their mapping behaviour 
in the future.

If its more than a week old you get about a 2% positive reaction.

At a month  they may have already corrected their behaviour or what is 
OpenStreetMap again?

Buildings are a pain to validate.  It takes me three times as long to 
correct a building as it does to map it correctly using the 
building_tool plugin.  I don't validate buildings.

We already have tools to detect overlapping buildings but faced with 500 
or a thousand overlapping buildings that first need to be freshly 
downloaded then dumped in the to do list and inspected to see which is 
the most accurate and some are really bad, Pierre has a tool for 
detecting them by the way, I just don't feel motivated.

The London Mapathons are well organised but many are not.  Essentially 
the problem mappers map once, possible twice.

What they need is simpler tools with less choices or room for error. 
JOSM with the building_tool plugin works well.  I, and others, have used 
it with new mappers and all their work was accurate and correctly labelled.

They don't read the training guides, they just want to map and often the 
people giving the training don't know OpenStreetMap.  The classic is 
"here is a coffee shop so we add shop=coffee."  Well no it was inside a 
building that I know that sells cups of coffee and snacks but not beans 
and it actually should be mapped as amenity=cafe, cuisine=coffee_shop.

What I have been doing of late is downloading chunks of OpenStreetMap 
using geofabrik and looking for problems using JOSM.  Highways that 
cross or don't connect.  Hamlets with the name Hameau, lots of those in 
French speaking Africa. Highways with the name road.  I've added tags to 
a few thousand untagged ways. Connecting highways across a settlement.

It's not prevention but it does improve the overall quality and 
reliability and at the end of the day that is what most end users want.

Cheerio John

Christoph Hormann wrote on 2018-10-01 5:14 AM:
> On Monday 01 October 2018, Nate Smith wrote:
>> Thanks for the comment and questions Frederik. Agreed that quality
>> and quantity isn’t exactly the same. And I hope that the UI in the
>> tool hasn’t communicated that this is just about statistics and
>> quantity - it is more than just a feature counter.
>>
>> We certainly could say it is a richness monitor, but the goal and
>> purpose is more than that. [...]
> Well - we can only evaluate the actual tool and its features, we cannot
> evaluate intentions behind it.
>
> As it is the tool only measures numbers of features and numbers of tags
> (in the form of features missing the tag in question, which is the
> same).  It communicates to the user that these are only things that
> matters:  Adding features and adding tags to those features.
>
> So as Frederik says as it is this is not a quality monitoring tool, this
> is a quantity monitoring tool.
>
> Apart from that you are probably not aware what the term campaign
> communicates in this context.  A campaign in the sense of a political
> or military campaign is an initiative to impose one's views or
> interests on others, swaying people's opinions and influencing their
> behaviour in contrast to engaging in an open argument about the best
> approach and trying to convince people this way.  You should probably
> think carefully if this is what you want to communicate here.
>

-- 
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20181001/ae033c17/attachment.html>