maproulette / maproulette/maproulette-frontend
Improve feature parity with classic osm and embedded Rapid editor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 11
Description
What would you like to see?
When loading area-based tasks with the classic osm editor, the area of interest is clearly conveyed and apparent. When switching to the embedded Rapid editor, the area of interest is ambiguous almost no certainty about the area being conveyed.
Why is this useful?
Either editor that the user selects should convey the same knowledge and functionality
Additional context
Sharing to prompt further discussion around the idea and to share inroads on a prototype as it evolves.
Comparison
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 comparing how area-based tasks convey the area of interest in the classic OSM editor and the embedded Rapid editor, using the linked comparison image and any prototype context in the issue. Done means either editor clearly conveys the same area-related knowledge and functionality when users switch between them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100