Slice GeoJSON into vector tiles on the fly in the browser
JavaScript HTML
Latest commit ba4dd53 Dec 23, 2016 @jed jed committed with mourner Describe how to exhaustively pre-generate all tiles (#77)
* Describe how to exhaustively pre-generate all tiles

* clarify that `tileCoords` contains tile coordinates, not tiles

geojson-vt — GeoJSON Vector Tiles

Build Status Coverage Status

A highly efficient JavaScript library for slicing GeoJSON data into vector tiles on the fly, primarily designed to enable rendering and interacting with large geospatial datasets on the browser side (without a server).

Created to power GeoJSON in Mapbox GL JS, but can be useful in other visualization platforms like Leaflet and d3, as well as Node.js server applications.

Resulting tiles conform to the JSON equivalent of the vector tile specification. To make data rendering and interaction fast, the tiles are simplified, retaining the minimum level of detail appropriate for each zoom level (simplifying shapes, filtering out tiny polygons and polylines).

Read more on how the library works on the Mapbox blog.

There's a C++11 port: geojson-vt-cpp


Here's geojson-vt action in Mapbox GL JS, dynamically loading a 100Mb US zip codes GeoJSON with 5.4 million points:

There's a convenient debug page to test out geojson-vt on different data. Just drag any GeoJSON on the page, watching the console.


// build an initial index of tiles
var tileIndex = geojsonvt(geoJSON);

// request a particular tile
var features = tileIndex.getTile(z, x, y).features;

// show an array of tile coordinates created so far
console.log(tileIndex.tileCoords); // [{z: 0, x: 0, y: 0}, ...]


You can fine-tune the results with an options object, although the defaults are sensible and work well for most use cases.

var tileIndex = geojsonvt(data, {
    maxZoom: 14,  // max zoom to preserve detail on
    tolerance: 3, // simplification tolerance (higher means simpler)
    extent: 4096, // tile extent (both width and height)
    buffer: 64,   // tile buffer on each side
    debug: 0      // logging level (0 to disable, 1 or 2)

    indexMaxZoom: 4,        // max zoom in the initial tile index
    indexMaxPoints: 100000, // max number of points per tile in the index
    solidChildren: false    // whether to include solid tile children in the index

By default, tiles at zoom levels above indexMaxZoom are generated on the fly, but you can pre-generate all possible tiles for data by setting indexMaxZoom and maxZoom to the same value, setting indexMaxPoints to 0, and then accessing the resulting tile coordinates from the tileCoords property of tileIndex.

Browser builds

npm install
npm run build-dev # development build, used by the debug page
npm run build-min # minified production build


2.3.0 (Jul 29, 2016)
  • Improved tiling algorithm to avoid redundant clipping when tiles are requested in an empty area.
  • Fixed issues with GeoJSON that only has data above 180 or below -180 longitude.
2.2.0 (Jun 9, 2016)
  • Fixed ring winding order for polygons and multipolygons in accordance with vector tile specification 2.0.
  • Fixed handling of features with null geometry (now ignored instead of throwing an error).
2.1.8 (Nov 9, 2015)
  • Fixed a bug where getTile would initially return null when requesting a child of a solid clipped square tile.
2.1.7 (Oct 16, 2015)
  • Expose transform methods in a separate file (transform.js).
2.1.6 (Sep 22, 2015)
  • Fixed a bug where getTile could generate a lot of unnecessary tiles.
  • Fixed a bug where an empty GeoJSON generated tiles.
2.1.5 (Aug 14, 2015)
  • Added tileCoords property with an array of coordinates of all tiles created so far.
2.1.4 (Aug 14, 2015)
  • Improved getTile to always return null on non-existing or invalid tiles.
2.1.3 (Aug 13, 2015)
  • Added solidChildren option that includes children of solid filled square tiles in the index (off by default).
  • Added back solid tile heuristics (not tiling solid filled square tiles further).
2.1.2 (Aug 13, 2015)
  • Fixed a crazy slowdown (~30x) when generating a huge number of tiles on the first run.
  • Removed clipped solid square heuristics (that actually didn't work since 2.0.0).
2.1.1 (June 18, 2015)
  • Fixed duplicate points in polygons.
2.1.0 (June 15, 2015)
  • Added proper handling for features crossing or near the date line.
2.0.1 (June 9, 2015)
  • 10-20% faster tile indexing.
  • Fixed latitude extremes not being clamped.
2.0.0 (Mar 20, 2015)
  • Breaking: maxZoom renamed to indexMaxZoom, maxPoints to indexMaxPoints, baseZoom to maxZoom.
  • Improved performance of both indexing and on-demand tile requests.
  • Improved memory footprint.
  • Better indexing defaults.
  • Fixed a bug where unnecessary memory was retained in some cases.
1.1.0 (Mar 2, 2015)
  • Add buffer and extent options.
1.0.0 (Dec 8, 2014)
  • Initial release.