MerginMaps / MerginMaps/mobile
Slow map rendering when there is a missing layer
Open
Nobody has claimed this yet.
bug
map
performance
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
If a layer is missing (e.g. wrong referenced layer), the app becomes extremely slow. We should just ignore the layer for that session similar to QGIS and not try to render it on every map panning/zooming.
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 reproducing the slowdown with a missing referenced layer, then trace the map-rendering work triggered by panning and zooming. Done means the missing layer is ignored for the session and repeated map interactions no longer attempt to render it.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100