Consider adding `overzoom` property to document maximum overzoom level
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Some tile server implementations support [_overzooming_](https://www.mapbox.com/help/define-overzoom/), where tiles are generated and served at zoom levels beyond a tileset's zoom extent using the lowest available zoom level as the source of truth for overzoomed tiles.
Mapbox's tile server includes an overzoom max of 30 for all vector tilesets, which means tiles can be requested from any tileset from the `minzoom` to zoom 30, regardless of the `maxzoom`. Requesting tiles beyond z30 from Mapbox results in a 422 error.
If `overzoom` were a property on tileJSON, clients would know when to stop requesting tiles without hitting an error or relying on a separate source of truth.
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 TileJSON specification and the existing maxzoom property described in the issue. Determine how an overzoom maximum should be defined so clients know when to stop requesting tiles; the work is done when the specification clearly documents that property and its limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100