MerginMaps / MerginMaps/mobile
Streaming mode: inconsistent initial point recording between time and distance threshold
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
**Description**
When streaming mode is started with a time threshold set, two initial points are recorded immediately at the beginning, ignoring the configured time interval. When a distance threshold is used instead, no initial point is recorded at all until the threshold condition is first met.
**Environment**
[x] PROD
**Application (+ app version, build, operating system)**
- Android app: 2026.2.0 (Pixel 9, Android 16)
- iOS app: 2026.2.0 (iOS 26.0)
**Steps to reproduce**
1. Open a project with a line or polygon layer (e.g. tc04_recording)
2. Go to Settings → Streaming and set a **time threshold** (e.g. 20 seconds)
3. Start recording a line/polygon feature and enter streaming mode (hold GPS button)
4. Observe the number of points recorded immediately at the start before the first interval elapses
5. Repeat steps 2–4 using a **distance threshold** instead of time threshold
**Actual results**
- Time threshold: two points are recorded immediately at start, before the first time interval elapses
- Distance threshold: no initial point is recorded when streaming starts; recording only begins once the distance condition is first met
**Expected results**
- Time threshold: one initial point should be recorded when streaming starts, then subsequent points at each time interval
- Distance threshold: one initial point should be recorded when streaming starts, then subsequent points each time the distance condition is met
- Behaviour should be consistent between both threshold types
**Screenshots or logs**
https://github.com/user-attachments/assets/4dffd556-35d8-4370-b0bc-ea06525f9376
*Conclusion*
*Created by Claude and supervised by a human test analyst.*
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
No source file, test, or entry point is named. Start by locating the streaming-mode recording logic for time and distance thresholds, then compare how the first point is handled in each path. Done means one point is recorded at startup for both modes, with later points following the configured threshold behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100