There's a lot of code common between symbolizers which do things like layout, setup, etc... So it seems sensible to extract the common operations & loops into a single place which is independent of the actual renderer. I've started doing this with C++11 lambdas, although that might not be the best implementation long term. Should be easy enough to change, though. |
||
---|---|---|
benchmark | ||
bin | ||
bindings/python | ||
boost | ||
demo | ||
deps | ||
docs | ||
fonts | ||
include | ||
plugins/input | ||
scons | ||
src | ||
tests | ||
utils | ||
workspace | ||
.gitignore | ||
.travis.yml | ||
AUTHORS.md | ||
CHANGELOG.md | ||
configure | ||
COPYING | ||
INSTALL.md | ||
localize.sh | ||
Makefile | ||
README.md | ||
run_tests | ||
SConstruct |
_/ _/ _/ _/
_/_/ _/_/ _/_/_/ _/_/_/ _/_/_/ _/ _/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/ _/
_/
_/
What is Mapnik?
Mapnik is an open source toolkit for developing mapping applications. At the core is a C++ shared library providing algorithms and patterns for spatial data access and visualization. High-level bindings for JavaScript, Python, and Ruby facilitate rapid application development in a variety of environments.
Overview
Mapnik is basically a collection of geographic objects like maps, layers, datasources, features, and geometries. The library doesn't rely on any OS specific "windowing systems" and it can be deployed to any server environment. It is intended to play fair in a multi-threaded environment and is aimed primarily, but not exclusively, at web-based development.
For further information see http://mapnik.org and also our wiki documentation here on GitHub.
Installation
See INSTALL.md for installation instructions and the Install page on the wiki for guides.
License
Mapnik software is free and is released under the LGPL (GNU Lesser General Public License). Please see COPYING for more information.