Skip to content
Brian Case edited this page Apr 3, 2015 · 4 revisions
TileCache is an implementation of a WMS-C (about) compliant server made available under the BSD license by MetaCarta. (Also, TileCacheConfig)

TileCache provides a Python-based WMS-C/TMS server, with pluggable caching mechanisms and rendering backends. In the simplest use case, TileCache requires only write access to a disk, the ability to run Python CGI scripts, and a WMS you want to be cached. With these resources, you can create your own local disk-based cache of any WMS server, and use the result in any WMS-C supporting client, like OpenLayers, or any TMS supporting client, like OpenLayers and worldKit.

This TileCache client supports multiple different rendering backends. Each rendering backend also supports the ability to draw 'metatiles', where a large tile is rendered, and then chopped into smaller tiles using the Python Imaging library.

Layer types
  • MapServer — render a tile using Python mapscript.

  • Mapnik — render a tile using the mapnik Python bindings.

  • Cascading WMS — fetch a tile from a remote WMS service. (Uses urllib to fetch tiles.)

  • ArcXML

  • GDAL

  • Image

In addition, there are several cache backends
  • Disk — Store files on disk. (Files stored in directories like basic/0/000/001/053/000/021/052.png)

  • Memcached — Store data in a memcached instance or cluster. (Requires memcached server running.)

  • AWSS3

  • GoogleDisk

  • MBTiles

  • Redis

  • S3

TileCache supports three tile request mechanisms

The TileCache library can speed up access to your WMS by factors of 10-100, or more. Under mod_python, cached requests can be handled at more than 300 requests per second.

Clone this wiki locally