MerginMaps / MerginMaps/mobile
Position tracking with external GPS
Open
Nobody has claimed this yet.
bug
position tracking
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Problem:
Recording with external GNSS receiver records points on a different place than the crosshair is. With internal GPS the recording works fine.
To reproduce:
- Connect app to an external GNSS receiver
- Start position tracking
- Check where edges are being created
- Stop tracking
- The line has some offset from your actual position.
https://github.com/user-attachments/assets/319db18d-562b-438e-b11a-26f711387022
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
Reproduce the issue with an external GNSS receiver using the five steps in the report, then compare the tracked line with the crosshair and with internal GPS tracking. Trace how the external position is used for edge creation; done means recorded edges align with the actual position and no longer show the reported offset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100