TileJSON 📄

TileJSON Tileset Metadata (3.0.0)

Open Beta
.json · application/json

TileJSON is a compact open JSON specification from Mapbox describing a tileset: where to fetch tiles (a URL template), within what geographic bounds they exist, the minimum and maximum zoom, attribution, and layer descriptions. It is not the tiles themselves but a machine-readable manifest wrapper that MapLibre, Mapbox GL JS and OpenLayers recognize automatically, configuring bounds, zoom and attribution on their own. On osm2cdr.ru the export generates a single 3.0.0 JSON file for the chosen area: bounds come from the bbox, center is computed automatically, and vector_layers lists the layer names. The tile URL template is configurable via a parameter.

Eksporter TileJSON nå ✨ Åpen beta — gratis, ingen begrensninger

Hovedfunksjoner

Compliance with the TileJSON 3.0.0 specification
bounds, center, minzoom/maxzoom, attribution and scheme=xyz fields
A vector_layers section with the layer names of the exported area
Configurable tile URL template ({z}/{x}/{y})
Lightweight format with no external dependencies — standard library only

Om TileJSON-formatet

TileJSON is a small JSON file that answers the client's questions: where to take tiles from, within which bounds they exist, at which zooms and whom to credit in the attribution. The specification was invented by Mapbox and is now a de facto standard: MapLibre, Mapbox GL JS and OpenLayers understand such a manifest out of the box.

The point is the separation: tiles sit in storage and are cached for a long time, while the lightweight manifest is served separately and updated when the bounds or the zooms change. One link to the JSON is enough for the client — it will set the bounds, the center, the zoom range and the attribution itself.

The export returns a single file of version 3.0.0: the bounds are taken from the selected area, the center is computed from them, the layer names are listed, the addressing scheme is xyz, and the tile URL template is set by a parameter. The tiles themselves are not inside — they are exported separately as MVT, PMTiles or raster XYZ tiles.

Hvilket program åpner TileJSON-filer

Følgende programmer og applikasjoner kan åpne, redigere og arbeide med TileJSON Tileset Metadata (3.0.0) (.json)-filer eksportert fra OSM2CDR:

💻MapLibre GL JS 💻Mapbox GL JS 💻OpenLayers 💻TileServer GL 💻Martin

Format specifications

Hvem bruker TileJSON-kart

🏗
Wiring a published tileset into MapLibre/Mapbox with a single url line
A published tile set is connected to a map with a single link, without setting bounds and zooms by hand.
💻
Describing a PMTiles or MVT set hosted on S3 / R2 / GitHub Pages
A ready description for a set posted on S3, R2 or GitHub Pages — the address of the manifest is all the client needs.
📊
Machine-readable metadata for geo-catalogs and style validation tools
Machine-readable metadata for geocatalogs and for checking styles with developer tools.
🎨
Separating style from tileset metadata for convenient CDN caching
Separating style from metadata: the tiles are cached by a CDN for a long time while the lightweight manifest is updated on its own.

Slik eksporterer du TileJSON

1
Velg område
Tegn et rektangel eller polygon på det interaktive kartet på osm2cdr.ru
2
Velg TileJSON
Velg TileJSON Tileset Metadata (3.0.0) fra listen over 127 tilgjengelige eksportformater
3
Eksporter
Klikk Eksporter og motta .json-filen din på 1–5 minutter
4
Last ned
Last ned den ferdige TileJSON-filen og åpne den i MapLibre GL JS

Slik åpner du filen etter eksporten

Populære kart i TileJSON

Free

Få karteksporter i TileJSON Tileset Metadata (3.0.0)

Last ned profesjonelle TileJSON-kart fra OpenStreetMap. Umiddelbar generering, uansett område.

Gratis / eksport
Eksporter TileJSON nå →

Ofte stilte spørsmål

Does this format contain the tiles themselves?
Can I set my own tile address?
Which engines understand TileJSON?
What should I put into the tile address before publishing?
Is CORS required?
Can raster tiles be described by this format too?

Relaterte formater

Ofte eksportert sammen