mapbox / mapbox/mapbox-maps-android
Glitches after changing minZoom of layers dynamically.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 578
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
- Android OS version: Irrelevant
- Devices affected: Irrelevant
- Maps SDK Version: 10.2.0
## Observed behavior and steps to reproduce
For my use-case I have to dynamically change the `minZoom` fields of certain layers.
- I have a layer that has a zoom range from `21.0 - 22.0` initially and the camera currently sits at `10.0` (in the video i used the `water layers` for testing purposes.
- I change the zoom range to `0.0 - 22.0` for that layer. (in the video, press on the button)
- I expect the tiles to load after the change, but what is observed is that the tiles seem to not load at all for certain zoom levels and glitch on various other zoom levels.
https://user-images.githubusercontent.com/21218132/152193659-c045bb16-6058-4894-9e20-cd6079a8ee3d.mp4
## Expected behavior
If a change in `minZoom` of a layer results in that layer now being visible, the layer should be displayed.
## Notes / preliminary analysis
## Additional links and references
[Github sample application](https://github.com/florianPOLARSTEPS/MapboxMinZoom)
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 with the linked GitHub sample application and reproduce the issue using Maps SDK 10.2.0: change a layer's minZoom while the camera is at a lower zoom level. Trace the dynamic layer update and tile visibility behavior across zoom levels. Done means a layer that becomes visible after its minZoom changes loads and displays its tiles without glitches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100