Tile cover should always produce tile zooms based on distance to camera
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
_proposed and reported by @astojilj_
Transform#coveringTiles(): this two positions should produce similar tile cover. Now, the maxZoom of tile cover returned is transform.tileZoom.
If mountain peak (attached video) is in center of screen, calculated zoom is 15 and tile cover produces tiles of zoom levels up to 15. If center of screen lays on a point that is in the walley then transform.tileZoom is calculated as 13 and tile cover produces tile set with zoom levels up to 13.
The distance to camera is almost the same. coveringZoomLevel() limits zoom until the tile cover algorithm is run - running it further should make the tiles close to camera in proper zoom level.
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 tracing Transform#coveringTiles() and its coveringZoomLevel() limit. Compare the mountain-peak and valley-centered views described in the issue; done when similar camera distances produce similar tile coverage, with tiles near the camera reaching the appropriate zoom instead of being capped by transform.tileZoom.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100