[MapRoulette] Request for comments: Liking and Flagging challenges

SomeoneElse · 2022-12-15T18:32:21.060Z

Thanks - good to know that that API format https://maproulette.org/api/v2/project/47143/challenges works.

mvexel · 2022-12-15T18:55:28.628Z

Yea, most everything in MapRoulette can be read-accessed with the API. It’s just building UX around it that’s sometimes hard & more time consuming.

SomeoneElse · 2022-12-15T20:01:12.739Z

Actually one more question - is there an RSS feed of “new challenges”?

Had it been immediately visible when it was added, a challenge whose entire description was “Replace diplomatic=high_commission with diplomatic=embassy + embassy=high_commission” (an obvious mechanical edit) could have been nipped in the bud.

mvexel · 2022-12-15T22:21:59.420Z

SomeoneElse:

Actually one more question - is there an RSS feed of “new challenges”?

Not currently. Interesting idea though.

mvexel · 2022-12-16T16:26:34.582Z

Ticket for RSS feed opened, RSS feed for newly created discoverable challenges · Issue #1904 · maproulette/maproulette3 · GitHub Not currently scoped however.

mvexel · 2023-01-22T21:35:42.330Z

An update, it is now possible to Flag (or “report”, still not sure what the best term is) challenges. A short blog post by the devs who implemented this is here.

SomeoneElse · 2023-04-13T13:24:59.924Z

mvexel:

The log-in requirement to see the Challenge browse page is a bug that we’re working on.

That seems to have been closed without a fix actually happening?

What I wrote a few months ago still largely seems to be true - the UI is still very limited. There are the API links above of course, which should allow people to download the revevant data before analysing it manually. The bug that was open for this seems to have been closed without the issue being fixed though, or maybe it;s just not live yet?

SomeoneElse · 2023-04-13T13:39:39.038Z

mvexel:

Yea, most everything in MapRoulette can be read-accessed with the API. It’s just building UX around it that’s sometimes hard & more time consuming.

Is there any documentation of what APIs there are?

hfs · 2023-04-13T15:46:21.763Z

The API documentation can be found here:

https://maproulette.org/docs/

SomeoneElse · 2023-04-13T16:50:19.742Z

If that is what passes for documentation these days then I am William Shakespeare

PierZen · 2023-04-14T01:43:06.607Z

What seems to be missing is the hiearchy of metadata. For people not familiar, could you briefly describe the Challenges, the projects, how they are related. Is there an instruction to list all challenges, all projects, plus geolocation and a brief description of these ?

hfs · 2023-04-14T12:23:43.227Z

All the conceptual stuff is explained in the end user documentation? Documentation | MapRoulette Docs. In my opinion it makes sense to use MapRoulette first before trying to access the API? There you will quickly discover the hierarchy of projects › challenges › tasks.

SomeoneElse · 2023-04-14T13:05:02.271Z

hfs:

In my opinion it makes sense to use MapRoulette first before trying to access the API?

I’m using the API because it was suggested by the Maproulette author above. What I’d like to be able to do is to download a list of “challenges” that form part of a “project”, and then download a list of changesets that have been performed as a result of each challenge. I can get changeset data and metadata from the OSM API; but I don’t see a documented way of getting a list of changesets (without going through the code, of course).

For context, I’m a member of the Data Working Group, and we occasionally get reports of problematic challenges**. The Maproulette UI’s openness to outsiders is somewhat limited (see above in this thread), but the API appears that it might be an easier way to get at that data.

** we have 4 tickets open at the moment, of varying ages.

ivanbranco · 2023-04-14T13:10:24.794Z

Is this feature handled by someone? No generated issue has been closed yet since February 3 (the three closed ones are tests).

hfs · 2023-04-14T15:43:48.562Z

SomeoneElse:

[…], and then download a list of changesets that have been performed as a result of each challenge

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?

PierZen · 2023-04-14T22:27:17.766Z

hfs:

All the conceptual stuff is explained in the end user documentation? Documentation | MapRoulette Docs.

Thanks for the documentation.

hfs:

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.

A maproulette hashtag is not sufficient. I prefer solution like for the HOT Tasking manager where the host key is added to the tags with information about the project + map/validate info (HOT Tasking Manager). MapRoulette and OSM could be better integrated providing details with the host key (example: https://maproulette.org/api/v2/challenge/77/nextTask/53906) . This would let the comment key for the osm contributor.

SomeoneElse · 2023-04-15T01:40:07.529Z

hfs:

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

That’s a shame. Up til now I’ve been looking for changesets with a changeset comment that matches the suggested comment in maproulette. An example changeset is here, but that seem unrelated to the maproulette description, even though the comment mathes - presumably because “#fix-osmcha-detection #maproulette” matches lots of chllenges.

Mateusz_Konieczny · 2023-04-15T07:52:18.713Z

SomeoneElse:

Up til now I’ve been looking for changesets with a changeset comment that matches the suggested comment in maproulette.

note that it works only when person creating MR thing decided to fill default changeset comment and people editing based on MR instructions have not deleted/replaced it

Mateusz_Konieczny · 2023-04-15T07:53:11.164Z

mvexel:

Flagging is a way to signal that you think the challenge is confusing / causing bad edits in OSM.

What is happening once challenge is flagged and report issue is created at github?

As far as I can see at Issues · maproulette/challenge-reports · GitHub reporting has no effect whatsoever.

mvexel · 2023-04-24T17:03:50.797Z

At this moment it’s self-governing. The challenge maintainer gets an email with the github link to engage with the person who added the flag. From there on it’s a public discussion between the author and the flagger. If that does not work out there’s the Maproulette team (basically, me) and the DWG to mediate, but capacity of both is limited.

If people want to step up and help out with building a process and volunteer as “moderators” that would be great.