MerginMaps / MerginMaps/mobile
Enhance digitizing and identification speed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
- [x] #3578
- [ ] Understand why is it computational-heavy in the first place
---
**Outdated:**
slow recording mode ➝ change SnapUtils to not do transformation after each map change
.. we might rename them to CrosshairUtils while doing that
slow identification ➝ simplify geometries with more than x vertices [Done ✅]
slow performance while tracking ➝ figure out why
slow Highlight.qml ➝ rewrite to cpp(? - we might do this later)
https://github.com/MerginMaps/input/issues/833
---
Author of the original task:
Tomas Mizera
Original tags:
migrate to github
Original task URL: https://app.clickup.com/t/861n417r8
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 by reviewing the remaining computational-heavy checklist and the digitizing, identification, and tracking paths referenced in the issue. Inspect SnapUtils and the possible CrosshairUtils rename, then consider the Highlight.qml performance note. Done means identifying the main bottleneck and documenting or implementing a focused speed improvement, with validation for the affected workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100