tilejson-spec
tilejson-spec copied to clipboard
mapbox
JSON format for describing map tilesets.
* a few minor spelling/typo/grammar changes * use https instead of http as a default
In https://github.com/mapbox/tilejson-spec/blob/master/3.0.0/example/osm.json, it could be interesting to set a date as optional. ## Why this request? Knowing when the vector tiles have been updated. ## Limitations: It will work better...
Currently, all that the specification has to say about the x, y and z URL parameters is > {z}, {x} and {y}, if present, are replaced with the corresponding integers...
I have just been working with some Esri vector tiles, which support a variable zoom depth. That is, tiles are generated to higher zoom levels in areas that contain more...
Landing on the repository one can see all spec versions up to 2.2 There is a branch with a v3 that is not visible unless one knows where to look....
## Motivation I've come across a lot of different tile layer sources over the years which tend to have multiple areas of coverage (multiple bounding boxes). A great example of...
For data-centric layers (e.g. dynamically updated layers containing lots of additional info for features) it will be useful to allow a wildcard definition for the layer fields: ``` "fields": {...
Some renderers (like ours) require to map a geometry type to a layer. Therefore I propose to have an optional field "geometry_type" for the layer definition. The geometry_type should relate...
When more than one tileset is composited, vector_layers get merged into a single list. `source` and `source_name` fields are useful for identifying which vector_layers belong to which member of a...
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...