This repository was archived by the owner on Sep 25, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
This repository was archived by the owner on Sep 25, 2020. It is now read-only.
Reporting false positives #10
Copy link
Copy link
Open
Description
Maproulette has an option to mark something as a false positive. However, there are many reasons something might be a false positive:
- it might be a wrong analysis
- REF data might be wrong
In the first case, do we want to remove it from further analysis? Or just improve our process to make sure it is dropped?
In the second case, we do want it removed, both from our analysis and from the REF data.
I think the only way to do that, is to have a second line of mappers, who look at just the false positives.
So what we need is this:
- query Maproulette to collect all the things marked as false positive. Also copy any available "Comments".
- add these to a list (without destroying what is already on the list)
- Optional: allow mappers to manually add objects to the list, for those that use our mapping layer outside of Maproulette
- allow mappers to visualize the list for further analysis, give access to REF-data managers so they can fix those classified as "RED data error" (see below)
- allow mappers to classify the false positives: REF data error; processing error; resolved and to identify things that need a survey.
- feed the REF data errors to our processing to avoid offering them to mappers again
This would mean, from the regular Maproulette user perspective, every time they answer NO on the flowchart below, they just mark False Positive. We can encourage them to leave a Comment throug the system, so the second line mappers already have an idea what's going on.