maproulette / maproulette/maproulette-backend
Mappers should be warned about the risks of accepting MAPS.ME edits as fact
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
See http://www.openstreetmap.org/node/4697076691/history and http://www.openstreetmap.org/changeset/52817169 . Here a MAPS.ME-added "embassy" had some extra tags added to it by a well-meaning mapper, but unfortunately "embassy" is one of those tags that MAPS.ME users tend to use for personal markers. In this case basic QA was not done and the embassy was "made to look legitimate" by a Maproulette edit.
A solution here could either be within Maproulette itself (e.g. warning of the dangers of editing in areas with which the mapper is not familiar) or on a challenge by challenge basis, or both.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked OSM node history and changeset to understand the reported MAPS.ME tagging risk. Then determine whether the warning belongs in MapRoulette itself, in challenge configuration, or both; the issue does not name files, tests, or an entry point. Done requires an agreed warning behavior and a defined way to verify it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100