Skip to content

Mapnik API for rendering spatial data => vector tiles and rendering vector tiles => image tiles

License

Notifications You must be signed in to change notification settings

flippmoke/mapnik-vector-tile

 
 

Repository files navigation

mapnik-vector-tile

A high performance library for working with vector tiles from the team at MapBox.

Provides C++ headers that support rendering geodata into vector tiles and rendering vector tiles into images.

Many efforts at vector tiles use GeoJSON or other text based formats that are easy to parse in the browser.

This approach is different: tiles are encoded as protobuf messages and storage is tightly designed around the Mapnik rendering engine. In this case Mapnik is the client rather than the browser. This provides a geodata format that is a drop-in replacement for datasources like postgis and shapefiles without compromising on speed and can be styled using existing design tools like TileMill.

Implementation details

Vector tiles in this code represent a direct serialization of Mapnik layers optimized for space efficient storage and fast deserialization directly back into Mapnik objects. For those familiar with the Mapnik API vector tiles here can be considered a named array of mapnik::featureset_ptr whose geometries have been pre-tiled.

A vector tile can consist of one or more ordered layers identified by name and containing one or more features.

Features contain attributes and geometries: either point, linestring, or polygon. Features expect single geometries so multipolygons or multilinestrings are represented as multiple features, each storing a single geometry part.

Geometries are stored as an x,y,command stream (where command is a rendering command like move_to or line_to). Geometries are clipped, reprojected into the map srs, converted to screen coordinates, and delta and zigzag encoded.

Feature attributes are encoded as key:value pairs which are dictionary encoded at the layer level for compact storage of any repeated keys or values. Values use variant type encoding supporting both unicode strings, boolean values, and various integer and floating point types.

Vector tiles are serialized as protobuf messages which are then zlib compressed.

The assumed projection is Spherical Mercator (epsg:3857).

Requires

  • Mapnik v2.2.0: libmapnik and mapnik-config
  • Protobuf: libprotobuf and protoc

Ubuntu Dependencies Installation

apt-get install libprotobuf7 libprotobuf-dev protobuf-compiler
apt-add-repository ppa:mapnik/v2.2.0
apt-get update && apt-get install libmapnik libmapnik-dev

OS X Dependencies Installation

brew install protobuf
brew install mapnik

Building

Just type:

make

This builds the protobuf C++ wrappers: vector_tile.pb.cc and vector_tile.pb.h

Then include vector_tile.pb.cc in your code. The rest is header only.

Tests

Run the C++ tests like:

make test

Examples

C++

See examples in examples/c++

Python

These require the protobuf python bindings and the rtree library which can be installed like:

sudo apt-get install libspatialindex-dev
pip install protobuf rtree

To build and test the python example code do:

make python && make python-test

Run the example code:

python examples/python/hello-world.py

Authors

See also

About

Mapnik API for rendering spatial data => vector tiles and rendering vector tiles => image tiles

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C++ 94.2%
  • Python 5.3%
  • Shell 0.5%