sij/mapnik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Clone of mapnik from Github, for future local revisions
9169 commits 112 branches 95 tags 181 MiB
C++ 94.8%
Python 3.2%
CMake 1.2%
Shell 0.5%
CSS 0.1%
Find a file
artemp 38da080f82 make concrete image_data type names more expressive and explicit about color channels/depth: 
image_data_32 -> image_data_rgba8
image_data_8  -> image_data_gray8
image_data_16 -> image_data_gray16
image_data_float32  -> image_data_gray32f

NOTE: currently image_data_gray16::pixel_type = std::int16_t (signed 16 bit int) to match GDAL
should we support unsigned types?
2014-12-04 11:02:42 +01:00
benchmark make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
bindings/python make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
demo make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
deps gdal : experimenting with fetching gray scale single band as image_data_float32 2014-12-02 15:56:40 +01:00
docs add mention of always using std:: for cmath 2014-11-12 09:57:52 -08:00
fonts upgrade bundled unifont to 7.0.05 and dejavu to 2.34 2014-10-20 22:17:27 -07:00
include make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
plugins/input make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
scons upgrade scons to 2.3.4 2014-10-20 22:18:07 -07:00
src make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
tests make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
utils make concrete image_data type names more expressive and explicit about color channels/depth: 2014-12-04 11:02:42 +01:00
.gitignore no need to ingore obsolete files [skip ci] 2014-10-23 00:43:23 -07:00
.travis.yml travis: test PLUGIN_LINKING=static 2014-11-11 15:27:29 -08:00
AUTHORS.md add to authors 2014-10-23 00:04:52 -07:00
CHANGELOG.md Add to changelog 2014-10-23 01:36:39 -07:00
configure Allow user to specify a python executable.¬ 2014-09-03 15:56:58 -07:00
COPYING + update FSF address 2013-03-22 08:32:08 +00:00
INSTALL.md improve register_datasources + drop filesystem v2 support since v3 is default in boost >= 1.46 2014-10-13 17:43:14 -07:00
localize.sh put mapnik-config on PATH [skip ci] 2014-10-23 00:06:40 -07:00
Makefile silence boost warnings 2014-10-21 16:37:27 -07:00
README.md simplify readme 2014-10-17 17:32:44 -07:00
run_tests Allow user to specify a python executable.¬ 2014-09-03 15:56:58 -07:00
SConstruct get mapnik version in a less brittle way 2014-10-23 01:02:14 -07:00

README.md 

    _/      _/                                _/  _/
   _/_/  _/_/    _/_/_/  _/_/_/    _/_/_/        _/  _/
  _/  _/  _/  _/    _/  _/    _/  _/    _/  _/  _/_/
 _/      _/  _/    _/  _/    _/  _/    _/  _/  _/  _/
_/      _/    _/_/_/  _/_/_/    _/    _/  _/  _/    _/
                     _/
                    _/

Build Status

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.

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.

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.