osmandapp / osmandapp/OsmAnd-iOS
Persist OSM edits on the user’s device
Open
Nobody has claimed this yet.
osmedit
- Dominant language
- Objective-C++
- Stars
- 351
- Forks
- 119
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 87
Description
When a user is editing the map the changes he makes should be persisted even after the changes are sent to OSM servers.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the iOS map-editing flow and its OSM upload handling, then determine where device persistence belongs. Done means edits remain available on the user's device after they are sent to OSM servers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, objective-c
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100