Consider adding `overzoom` property to document maximum overzoom level

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
json
Domain
documentation

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.

Description

v4

Some tile server implementations support overzooming, 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.

Dominant language
No language data
Stars
297
Forks
51
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/tilejson-spec

All issues in mapbox/tilejson-spec

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.