-
-
Notifications
You must be signed in to change notification settings - Fork 281
Redefine Mapper Level Milestones #3713
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Another option discussed in the Activation Working Group was to leave intermediate at 250 and increase advanced to 750. This would have less disturbance on existing mappers (i.e. no one would 'return' to beginner). |
Hi all, the Quality Control Working Group would like to prioritize this one |
Hi all. Linking to a research paper looking at The Role of Volunteer Experience on Performance on Online Volunteering Platforms and specifically HOTOSM Tasking Manager. It might be of interest and relevance specifically to redefining the mapper level milestones. |
Currently Mapper Levels are defined as:
When vetting mappers requesting to become part of a validation team, we often find mappers with 500+ changesets that have mapped <1000 buildings and few of any other features. Obviously not what any experienced mapper would call "advanced". Therefore, I suggest we redefine these levels, if we cannot move towards a more sophisticated equation like X buildings, Y roads and Z 'other ways and POIs' then we should simply increase these numbers. I suggest doubling them to 500 and 1000 changeset milestones.
Moving towards the more sophisticated method of determining experience I think we could look towards the work done for the badges on the Missing Maps User Profiles http://www.missingmaps.org/users/#/ that has many different 'experience' types including things like participating in mapathons as a way to earn 'credit'/badges. Maybe we would need to simplify this to get us back to a 'beginner, intermediate, advanced' levels but as mentioned in #2907 - the current method is probably not good enough for our needs going forward.
The text was updated successfully, but these errors were encountered: