A stylish alternative for caching your map tiles.
rburhum Merge pull request #349 from kevinzg/master
Fix MVT related issues
Latest commit 1ecbb8f Nov 8, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
TileStache Fix empty pbf tile response Nov 7, 2018
Vagrant Fix a GDAL issue in the Vagrant provisioning script - Fixes #212 May 6, 2015
examples Deleted unused config file Sep 8, 2016
man Merge pull request #267 from sebastic/manpages Oct 27, 2016
scripts Add Python 2 print line, and mark scripts executable. Mar 30, 2017
tests Merge branch 'master' into py3hotfix Oct 12, 2017
www Added more collaborators to home page Apr 21, 2013
.gitignore Adding egg-info to ignored directories Oct 27, 2016
.travis.yml Prepared to release from master branch Jun 13, 2018
API.html Reversed boolean flag related to empty fields Jul 16, 2015
CHANGELOG Bumped version to 1.51.13 Sep 24, 2018
LICENSE Committed to BSD license Nov 15, 2010
MANIFEST.in Bumped to 1.50.1: fixed missing ttf file Jan 30, 2015
Makefile Removed PyPI setup from Makefile Jun 13, 2018
README.md "mapbox_vector_tile" missing as a dependency Nov 20, 2017
Vagrantfile Vagrant box URL was 404. Replace with working box. Nov 2, 2015
docker-compose.yml upgrading mapbox-vector-tile and fixing tests Sep 19, 2017
requirements.txt upgrading mapbox-vector-tile to fix build on python 3 Sep 19, 2017
runtests.sh add script to run nose tests Feb 5, 2013
setup.py Allow Werkzeug versions other than 0.11.13 Sep 24, 2018
tilestache.cfg Added sample OSM palette to illustrate 8-bit PNGs Jul 15, 2011
tilestache.cgi Introduced a full set of path possibilities to Disk cache configuration Apr 24, 2010



a stylish alternative for caching your map tiles

Build Status

TileStache is a Python-based server application that can serve up map tiles based on rendered geographic data. You might be familiar with TileCache, the venerable open source WMS server from MetaCarta. TileStache is similar, but we hope simpler and better-suited to the needs of designers and cartographers.


import TileStache
import ModestMaps

config = {
  "cache": {"name": "Test"},
  "layers": {
    "example": {
        "provider": {"name": "mapnik", "mapfile": "examples/style.xml"},
        "projection": "spherical mercator"

# like http://tile.openstreetmap.org/1/0/0.png
coord = ModestMaps.Core.Coordinate(0, 0, 1)
config = TileStache.Config.buildConfiguration(config)
type, bytes = TileStache.getTile(config.layers['example'], coord, 'png')

open('tile.png', 'w').write(bytes)




Install the pure python modules with pip:

sudo pip install -U pillow modestmaps simplejson werkzeug uuid mapbox-vector-tile

Install pip (http://www.pip-installer.org/) like:

curl -O -L https://bootstrap.pypa.io/get-pip.py
sudo python get-pip.py

Install Mapnik via instructions at:



TileStache can be run from the download directory as is. For example the scripts:

tilestache-render.py tilestache-seed.py tilestache-server.py

Can all be run locally like:


To install globally do:

python setup.py install
  • Note: you may need to prefix that command with 'sudo' to have permissions to fully install TileStache.


To make sure TileStache is working start the development server:


Then open a modern web browser and you should be able to preview tiles at:


This is a previewer that uses ModestMaps and OpenStreetMap tiles from http://tile.osm.org as defined in the default config file 'tilestache.cfg'


The next step is to learn how build custom layers and serve them.

See the docs for details.


Rendering providers:

  • Mapnik
  • Proxy
  • Vector
  • Templated URLs

Caching backends:

  • Local disk
  • Test
  • Memcache
  • S3

Design Goals

The design of TileStache focuses on approachability at the expense of cleverness or completeness. Our hope is to make it easy for anyone to design a new map of their city, publish a fresh view of their world, or even build the next 8-Bit NYC (http://8bitnyc.com).

  • Small

The core of TileStache is intended to have a small code footprint. It should be quick and easy to to understand what the library is doing and why, based on common entry points like included CGI scripts. Where possible, dynamic programming "magic" is to be avoided, in favor of basic, procedural and copiously-documented Python.

  • Pluggable

We want to accept plug-ins and extensions from outside TileStache, and offer TileStache itself as an extension for other systems. It must be possible to write and use additional caches or renderers without having to modify the core package itself, extend classes from inside the package, or navigate chains of class dependencies. Duck typing and stable interfaces win.

  • Sensible Defaults

The default action of a configured TileStache instance should permit the most common form of interaction: a worldwide, spherical-mercator upper-left oriented tile layout compatible with those used by OpenStreetMap, Google, Bing Maps, Yahoo! and others. It should be possible to make TileStache do whatever is necessary to support any external system, but we eschew complex, impenetrable standards in favor of pragmatic, fast utility with basic web clients.


BSD, see LICENSE file.