20

MapRoulette and OSM are not integrated at this point. A user looks at a task in MapRoulette and locks it. They do the OSM edit normally in an editor and upload the changeset. OSM and the changeset don’t “know” anything about MapRoulette. There’s a suggested changeset comment, but users are of course free to change it – most don’t. And then you go back to MapRoulette to mark the task as completed. You could also submit several changesets for one task. Or none at all if you fixed the task already yesterday.

So there’s no direct way to find the changesets that came out of a challenge.

In the past what I’ve done is to get the contributors to a challenge and the days they were active. Then fetch all changesets of these users on the days they were active. And finally filter the changeset comments for the hashtags or URL MapRoulette proposes to put in the comment.

It’s a bit cumbersome to work with two disconnected APIs, but for me it worked well enough.

Here I created some contributor stats for a finished challenge, and evaluated the changesets this way: Ungemappte Wohngebiete in Deutschland anhand Zensus - #256 by hfs

Here’s the code I used to fetch the status of all tasks of all challenges in a project, using the Python MapRoulette Client library: landuse_without_buildings/13_challenge_status.py at master · hfs/landuse_without_buildings · GitHub

And here’s the code to correlate that with changesets of the contributors: landuse_without_buildings/14_mapper_stats.ipynb at master · hfs/landuse_without_buildings · GitHub

Maybe that helps?

2 Likes