mapbox / mapbox/tilelive-vector
Looking back multiple zooms for fill tile
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
The `fillzoom` capability of tilelive-vector works well for a tileset with one consistent effective maxzoom, where a `fillzoom` tile should exist for all child tiles at higher zooms. However, for a "bumpy maxzoom topography" -- where the effective maxzoom of existing tiles is spatially variable -- the ability to load the highest existing parent zoom tile (within a reasonable threshold) would be useful.
A `lookback`, when specified in the info for a given tileset, would describe the number of zooms that should be looked for, and the highest zoom of these used to overzoom and fill in the missing tile.
For example, when trying to load a z19 tile, where a z17 tile exists, and the `lookback` is 3:
1. Z19 tile attempts to load, but is not found
2. Z18, Z17, Z16 tiles all all attempted to load
3. The highest zoom found is overzoomed
cc @yhahn
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 tilelive-vector's existing fillzoom handling and how the tileset info is read. Use the z19 example to verify that the requested lookback range is attempted and that the highest existing parent tile is used for overzooming and filling; add or update tests for this behavior if the project has coverage there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100