MerginMaps / MerginMaps/mobile
Optionally require minimum accuracy to capture points from GPS
Open
Nobody has claimed this yet.
enhancement
GPS
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Sometimes it would be useful to force users to get accuracy of X meters if they want to capture a point from GPS, not allowing them to capture point if the accuracy is worse than that.
Questions:
- would that be per-project configuration (set by admin) or would that be left to users to set it up in settings?
- would be users allowed to move the crosshair manually?
- how about editing of existing geometries?
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
The issue names no files, tests, or entry points, so first trace the GPS point-capture flow in the mobile app. Clarify whether the accuracy threshold is project- or user-configured and how manual crosshair movement and editing existing geometries should behave; done means these decisions are implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100