Prioritizing problematic edits to flag
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 19
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Came across the following changeset with a 👎 in osmcha.
Notes
- There does not seem to be any geometric modification
- The feature was edited later, modifying
Illarangi SttoIllarangi Street - Shortening
StreetwithStdoes not break the map and it could be a common practice
cc: @anandthakker @geohacker @batpad
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 with the linked OSMCha changeset and the issue notes, then trace how Gabbar prioritizes edits for flagging. Determine how the reported non-geometric Street-to-St edit should be classified and document a concrete completion criterion for prioritization behavior; the payload names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, machine-learning, scikit-learn
- Domain
- data, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100