cleanup old links to trac and svn
parent
0f752142c3
commit
af9ced6f31
25 changed files with 42 additions and 157 deletions
|
@ -78,26 +78,13 @@ Follow instructions from http://osm.fsffrance.org/debian-backports/README to ins
|
|||
postgresql-8.3-postgis postgresql-8.3 \
|
||||
postgresql-server-dev-8.3 postgresql-contrib-8.3 \
|
||||
libsqlite3-dev \
|
||||
subversion build-essential python-nose
|
||||
build-essential python-nose
|
||||
```
|
||||
|
||||
Install Mapnik 0.7.1
|
||||
Mapnik trunk:
|
||||
|
||||
```sh
|
||||
svn co http://svn.mapnik.org/tags/release-0.7.1/ mapnik-0.7.1
|
||||
cd mapnik-0.7.1
|
||||
python scons/scons.py configure INPUT_PLUGINS=all \
|
||||
OPTIMIZATION=3 \
|
||||
SYSTEM_FONTS=/usr/share/fonts/truetype/
|
||||
python scons/scons.py
|
||||
sudo python scons/scons.py install
|
||||
sudo ldconfig
|
||||
```
|
||||
|
||||
or Mapnik trunk:
|
||||
|
||||
```sh
|
||||
svn co http://svn.mapnik.org/trunk mapnik-trunk
|
||||
git clone git://github.com/mapnik/mapnik.git mapnik-trunk
|
||||
cd mapnik-trunk
|
||||
python scons/scons.py configure INPUT_PLUGINS=all \
|
||||
OPTIMIZATION=3 \
|
||||
|
@ -114,7 +101,7 @@ The development libraries have to be present as described above. In the followin
|
|||
DIR_MAPNIK_SRC=/home/$USER/mapnik_svn
|
||||
DIR_MAPNIK_INSTALL=/home/$USER/mapnik_inst
|
||||
|
||||
svn co http://svn.mapnik.org/trunk $DIR_MAPNIK_SVN
|
||||
git clone git://github.com/mapnik/mapnik.git $DIR_MAPNIK_SVN
|
||||
cd $DIR_MAPNIK_SVN
|
||||
|
||||
python scons/scons.py configure INPUT_PLUGINS=all \
|
||||
|
|
|
@ -14,13 +14,13 @@ Currently I have these questions:
|
|||
## Eclipse
|
||||
Here I try to describe my setup. I'm sure there are better ways but this works for me:
|
||||
|
||||
* Checkout the newest trunk version of the repository: `svn checkout http://svn.mapnik.org/trunk mapnik_trunk`
|
||||
* Checkout the latest code: `git clone git://github.com/mapnik/mapnik.git mapnik_trunk`
|
||||
|
||||
This has the advantages that
|
||||
|
||||
* you always have the newest version (`svn update`)
|
||||
* you can quickly add test code and remove it again (`svn revert`)
|
||||
* you can easily create patches (`svn diff`)
|
||||
* you always have the newest version (`git pull`)
|
||||
* you can quickly add test code and remove it again (`svn checkout .`)
|
||||
* you can easily create patches (`git diff`)
|
||||
* Compile it as described in the INSTALL file provided in the root directory of the checkout. I have the following variables in my `config.py`:
|
||||
|
||||
```python
|
||||
|
|
|
@ -45,8 +45,6 @@ Any specific feature request or bug report should be created as a [new ticket](h
|
|||
|
||||
[DeveloperTodo](https://github.com/mapnik/mapnik/wiki/DeveloperTodo)
|
||||
|
||||
[Tickets by owner](https://trac.mapnik.org/report/8) - Your tickets
|
||||
|
||||
|
||||
## Sandbox
|
||||
|
||||
|
|
2
GDAL.md
2
GDAL.md
|
@ -49,8 +49,6 @@ This plugin in Mapnik >= 0.7.0 supports reading overviews created with http://ww
|
|||
lyr.styles.append('Raster Style')
|
||||
```
|
||||
|
||||
See the docstring at: http://svn.mapnik.org/trunk/docs/api_docs/python/mapnik-module.html#Gdal
|
||||
|
||||
## XML
|
||||
|
||||
```xml
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
<!-- Author: ivansanchez -->
|
||||
# Compositing
|
||||
|
||||
[TopOSM](http://wiki.openstreetmap.org/wiki/TopOSM/Details) is pretty inspirational. How about an XML dialect for specifying the composition of multiple Mapnik-rendered layers into a single map. This example is based on [TopOSM's compositing steps](http://wiki.openstreetmap.org/wiki/TopOSM/Details#Combining_images_into_a_final_composite), which also incorporate `gdalwarp`-generated hill shadings. (These could be integrated using a [RasterSymbolizer](http://trac.mapnik.org/wiki/RasterSymbolizer), or a thin wrapper could be generated at runtime.)
|
||||
[TopOSM](http://wiki.openstreetmap.org/wiki/TopOSM/Details) is pretty inspirational. How about an XML dialect for specifying the composition of multiple Mapnik-rendered layers into a single map. This example is based on [TopOSM's compositing steps](http://wiki.openstreetmap.org/wiki/TopOSM/Details#Combining_images_into_a_final_composite), which also incorporate `gdalwarp`-generated hill shadings. (These could be integrated using a [RasterSymbolizer](http://github.com/mapnik/mapnik/wiki/RasterSymbolizer), or a thin wrapper could be generated at runtime.)
|
||||
|
||||
* Note: see also [artem's test images](Compositing) (generated with AGG)
|
||||
* Note: see also the GSOC page on related ideas part [Layer Composites](GSOC2010_Ideas)
|
||||
|
|
|
@ -132,7 +132,7 @@ Then, go recompile (just boost_python) and move the new library into place:
|
|||
unsigned short const* boost::re_detail::re_is_set_member<unsigned short const*, int, boost::icu_regex_traits, unsigned long long>(unsigned short const*, unsigned short const*, boost::re_detail::re_set_long<unsigned long long> const*, boost::re_detail::regex_data<int, boost::icu_regex_traits> const&, bool)in agg_renderer.os
|
||||
```
|
||||
|
||||
* *Solution*: Likely, your boost library was built without regex+icu support. If you have built libboost from source, you can make your system's relevant .so files be recompiled with that support and reinstalled in place in the /lib/ folders. Go to libboost's source folder and run the following command (which you can find on [latest release install details](http://trac.mapnik.org/wiki/Mapnik2#fromlatestrelease|Mapnik2's)):
|
||||
* *Solution*: Likely, your boost library was built without regex+icu support. If you have built libboost from source, you can make your system's relevant .so files be recompiled with that support and reinstalled in place in the /lib/ folders. Go to libboost's source folder and run the following command (which you can find on [latest release install details](http://github.com/mapnik/mapnik/wiki/Mapnik2#fromlatestrelease|Mapnik2's)):
|
||||
|
||||
```sh
|
||||
sudo ./bjam --with-regex toolset=gcc -sHAVE_ICU=1 -sICU_PATH=/usr/local/ -a install
|
||||
|
@ -248,7 +248,7 @@ Note: If the SCons build process simply can't find an include or library and you
|
|||
ImportError: /usr/local/lib/libmapnik.so.0.8: undefined symbol: _ZN5boost11basic_regexIiNS_16icu_regex_traitsEE9do_assignEPKiS4_j
|
||||
```
|
||||
|
||||
* *Solution*: Likely, your boost library was built without regex+icu support. If you have built libboost from source, you can make your system's relevant .so files be recompiled with that support and reinstalled in place in the /lib/ folders. Go to libboost's source folder and run the following command (which you can find on [latest release install details](http://trac.mapnik.org/wiki/Mapnik2#fromlatestrelease|Mapnik2's)):
|
||||
* *Solution*: Likely, your boost library was built without regex+icu support. If you have built libboost from source, you can make your system's relevant .so files be recompiled with that support and reinstalled in place in the /lib/ folders. Go to libboost's source folder and run the following command (which you can find on [latest release install details](http://github.com/mapnik/mapnik/wiki/Mapnik2#fromlatestrelease|Mapnik2's)):
|
||||
|
||||
```sh
|
||||
sudo ./bjam --with-regex toolset=gcc -sHAVE_ICU=1 -sICU_PATH=/usr/local/ -a install
|
||||
|
|
|
@ -1,77 +0,0 @@
|
|||
<!-- Name: MacInstallationPorts -->
|
||||
<!-- Version: 10 -->
|
||||
<!-- Last-Modified: 2009/11/05 11:15:11 -->
|
||||
<!-- Author: springmeyer -->
|
||||
# Installing Mapnik on Mac OS X
|
||||
|
||||
This page describes how to build/install Mapnik from source on Mac OS X >= 10.5, using Macports.
|
||||
|
||||
Unlike the MacInstallation guide, this page assumes you grok [the command-line](http://en.wikipedia.org/wiki/In_the_Beginning...was_the_Command_Line).
|
||||
|
||||
## Dependencies
|
||||
|
||||
* Install [MacPorts](http://www.macports.org/): http://www.macports.org/install.php (requires XCode. Version 1.6 may not set up a .profile, see [ProblemHotlist](https://trac.macports.org/wiki/ProblemHotlist#a4..profilenotsetup) to fix)
|
||||
|
||||
Run
|
||||
|
||||
|
||||
```sh
|
||||
$ sudo port install proj libpng jpeg tiff icu jam
|
||||
$ sudo port install boost +python25 +icu
|
||||
```
|
||||
|
||||
For optional dependencies (such as Cairo or PostGIS), see MacInstallation/Optional (MacInstallation_Optional)
|
||||
|
||||
## Building
|
||||
|
||||
Grab source:
|
||||
|
||||
|
||||
```sh
|
||||
$ git clone https://github.com/mapnik/mapnik.git
|
||||
```
|
||||
|
||||
Patch [SConstruct](http://www.scons.org/doc/1.0.1/HTML/scons-user/x348.html) (get [SConstruct.osx.patch](http://trac.mapnik.org/attachment/wiki/MacInstallationPorts/SConstruct.osx.patch), [download here](http://trac.mapnik.org/raw-attachment/wiki/MacInstallationPorts/SConstruct.osx.patch))
|
||||
|
||||
|
||||
```sh
|
||||
$ patch -p1 < SConstruct.osx.patch
|
||||
```
|
||||
|
||||
Compile/Install
|
||||
|
||||
|
||||
```sh
|
||||
$ cd mapnik
|
||||
$ python scons/scons.py DEBUG=y
|
||||
$ sudo python scons/scons.py install DEBUG=y
|
||||
```
|
||||
|
||||
Add the following line to your ~/.profile
|
||||
|
||||
```sh
|
||||
export PYTHONPATH="/usr/lib/python2.5/site-packages"
|
||||
```
|
||||
|
||||
## Testing
|
||||
|
||||
```sh
|
||||
$ python
|
||||
>>> import mapnik
|
||||
registered datasource : gdal
|
||||
registered datasource : postgis
|
||||
registered datasource : raster
|
||||
registered datasource : shape
|
||||
>>> dir(mapnik) # This gets you a list of symbols
|
||||
['BoostPythonMetaclass', 'Color', 'Coord', 'CreateDatasource', ...]
|
||||
>>> help(mapnik)
|
||||
```
|
||||
|
||||
## References
|
||||
|
||||
* [The Official Mapnik installation guide](http://mapnik.org/documentation/install/)
|
||||
* Conventional MacInstallation guide
|
||||
* http://www.codingadventures.com/2008/04/howto-building-mapnik-on-osx-leopard/
|
||||
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ If you are new to compiling source code, or having trouble getting started on a
|
|||
* Checkout the current repository with subversion:
|
||||
|
||||
```sh
|
||||
svn co http://svn.mapnik.org/trunk/ mapnik
|
||||
git clone git://github.com/mapnik/mapnik.git mapnik
|
||||
```
|
||||
|
||||
* *Recommended*: Proj.4 - [Cartographic Projections Library](http://www.remotesensing.org/proj/)
|
||||
|
@ -124,17 +124,10 @@ If you are new to compiling source code, or having trouble getting started on a
|
|||
1. Download the Mapnik source code from svn
|
||||
|
||||
```sh
|
||||
$ svn co http://svn.mapnik.org/trunk mapnik_svn
|
||||
$ git clone git://github.com/mapnik/mapnik.git mapnik_svn
|
||||
$ cd mapnik_svn
|
||||
```
|
||||
|
||||
or the stable release source code:
|
||||
|
||||
```sh
|
||||
$ wget http://download.berlios.de/mapnik/mapnik-0.7.0.tar.bz2
|
||||
$ tar xvf mapnik-0.7.0.tar.bz2
|
||||
$ cd mapnik-0.7.0/
|
||||
```
|
||||
|
||||
2. Read over the INSTALL instructions for your version
|
||||
|
||||
|
|
|
@ -140,7 +140,7 @@ Grab some dependencies (this is for debian systems)
|
|||
sudo apt-get install libbz2-dev
|
||||
```
|
||||
|
||||
If you are compiling on Mac OS X see: http://trac.mapnik.org/wiki/MacInstallation#Step1:RouteBC
|
||||
If you are compiling on Mac OS X see: http://github.com/mapnik/mapnik/wiki/MacInstallation#Step1:RouteBC
|
||||
|
||||
Otherwise on linux do:
|
||||
|
||||
|
|
|
@ -14,7 +14,6 @@ All properties that previously used underscores, ie '_' now use dashes ('-'). So
|
|||
|
||||
* Mapnik 0.7.2 has compatibility with both syntaxes as of r2579
|
||||
* Mapnik 2.0 moved to only dashes in r2582
|
||||
* Note: branch of trunk tagged before r2582: https://trac.mapnik.org/browser/branches/mapnik2-pre-dashes
|
||||
* properties changed include:
|
||||
|
||||
```python
|
||||
|
|
|
@ -31,7 +31,7 @@ From Steve Chilton's SotM presentation:
|
|||
* iterate alternative label placement
|
||||
* apply point within polygon labels
|
||||
* allow rotation for icons
|
||||
* accept SVG icons (Done? See [Changeset 1793](http://trac.mapnik.org/changeset/1793) )
|
||||
* accept SVG icons (Done)
|
||||
* apply variable widths to canals and rivers
|
||||
* apply vignettes inside polygons
|
||||
* produce spread text labels
|
||||
|
@ -40,11 +40,6 @@ From Steve Chilton's SotM presentation:
|
|||
* more Natural Earth data at low-zooms (May apply more to OSM style than Mapnik-core)
|
||||
* add your advanced cartography requests
|
||||
* as it's already able to replace certain strings in the filename of a Symbolizer, other parameters should be changeable too. Say: I want to define a Template for a Symbolizer in the Stylesheet, but define its parameters (color, width, etc.) from database columns.
|
||||
|
||||
### Bug list
|
||||
List of bugs for squishing or topics to discuss:
|
||||
|
||||
* http://trac.mapnik.org/milestone/MCS1%20Tickets
|
||||
|
||||
### Cascadenik
|
||||
|
||||
|
|
|
@ -39,7 +39,7 @@ This is a quick list of things we started work on or achieved during the sprint:
|
|||
* Forward compatibility of .7.x series a priority (springmeyer)
|
||||
* Lots of work on new prototype for documentation (dodobas) [#288](https://github.com/mapnik/mapnik/issues/288)
|
||||
* Moved Cascadenik to github and refactored lots of code, merging in XML-bad branch (migurski, rcoup, ninow) (http://github.com/mapnik/Cascadenik)
|
||||
* Came up with lots of new ideas and pushed they into tickets against [Sprint Milestone](http://trac.mapnik.org/milestone/MCS1%20Tickets)
|
||||
* Came up with lots of new ideas and pushed they into tickets against [Sprint Milestone](http://http://github.com/mapnik/mapnik/wiki/milestone/MCS1%20Tickets)
|
||||
* Many sprinters installed Mapnik2 - we updated docs with lessons learned (springmeyer)
|
||||
* Extensive review and prioritization of tickets relating to cartographic features (ldp)
|
||||
* Work towards native boost::spirit WKT parser (artem)
|
||||
|
@ -64,8 +64,8 @@ This is a quick list of things we started work on or achieved during the sprint:
|
|||
|
||||
## Trac timeline
|
||||
|
||||
http://trac.mapnik.org/timeline?from=09%2F29%2F10&daysback=10&ticket=on&ticket_details=on&changeset=on&update=Update
|
||||
http://http://github.com/mapnik/mapnik/wiki/timeline?from=09%2F29%2F10&daysback=10&ticket=on&ticket_details=on&changeset=on&update=Update
|
||||
|
||||
## Tickets
|
||||
|
||||
http://trac.mapnik.org/milestone/MCS1%20Tickets
|
||||
http://http://github.com/mapnik/mapnik/wiki/milestone/MCS1%20Tickets
|
|
@ -21,7 +21,7 @@ While Mapnik was the first to use AGG rendering for mapping, the AGG renderer is
|
|||
The [Cairo](http://cairographics.org/) renderer is an auxiliary renderer in Mapnik.
|
||||
|
||||
* Cairo was added in r656 due to its similar reputation for high quality graphics output to various formats
|
||||
* http://trac.mapnik.org/log/trunk/src/cairo_renderer.cpp
|
||||
* http://http://github.com/mapnik/mapnik/wiki/log/trunk/src/cairo_renderer.cpp
|
||||
* Cairo has the '''added advantage''' of supporting both Vector and Raster output.
|
||||
* Mapnik can render to any [surface](http://www.cairographics.org/manual/cairo-surfaces.html) supported by cairo, either directly or by rendering to a cairo [context](http://www.cairographics.org/manual/cairo-context.html).
|
||||
* You can demo the PNG, JPEG, SVG, PDF, and PS formats using the [OSM export tool](http://openstreetmap.org/export/)
|
||||
|
|
|
@ -8,7 +8,7 @@ See also the `grid_renderer` which works better for polygons: https://github.com
|
|||
|
||||
A blog post on the idea is at: http://mapnik.org/news/2010/jul/06/gsoc2010_halfway/.
|
||||
|
||||
Slides from State of the Map Europe 2011 are [available](http://trac.mapnik.org/attachment/wiki/MetaWriter/metawriter-slides-sotmeu.pdf).
|
||||
Slides from State of the Map Europe 2011 are [available](http://http://github.com/mapnik/mapnik/wiki/attachment/wiki/MetaWriter/metawriter-slides-sotmeu.pdf).
|
||||
|
||||
See also Herm's demo, which highlights both visible and invisible features: http://r2d2.stefanm.com/mapnik/demo.html
|
||||
|
||||
|
|
|
@ -33,9 +33,7 @@ If anyone does forge ahead using the old tools available from sun and can compil
|
|||
|
||||
You will need at least:
|
||||
|
||||
* Mapnik trunk (>= r2444) (http://svn.mapnik.org/trunk/)
|
||||
* or
|
||||
* Mapnik 0.7.2 (>= r2444) (http://svn.mapnik.org/branches/0.7.2-dev/)
|
||||
* Mapnik >= 2.x
|
||||
|
||||
For 64 bit builds you need to apply patches from [#675](https://github.com/mapnik/mapnik/issues/675) and [#676](https://github.com/mapnik/mapnik/issues/676)
|
||||
|
||||
|
@ -239,7 +237,7 @@ We just need to patch our ts-specs directory to disable textinfo and bypass this
|
|||
|
||||
```sh
|
||||
cd ts-specs
|
||||
wget http://trac.mapnik.org/raw-attachment/wiki/OpenSolarisInstallation/ts-spec1-compile-gcc44.patch
|
||||
wget http://http://github.com/mapnik/mapnik/wiki/raw-attachment/wiki/OpenSolarisInstallation/ts-spec1-compile-gcc44.patch
|
||||
patch -p0 < ts-spec1-compile-gcc44.patch
|
||||
```
|
||||
|
||||
|
@ -303,7 +301,8 @@ Mapnik 0.7.2:
|
|||
|
||||
```sh
|
||||
cd $SRC
|
||||
svn co http://svn.mapnik.org/branches/0.7.2-dev/ mapnik-0.7.2
|
||||
git clone git://github.com/mapnik/mapnik.git mapnik-0.7.3
|
||||
git checkout v0.7.3
|
||||
cd mapnik-0.7.2
|
||||
export LANG="C"
|
||||
export LC_ALL="C"
|
||||
|
@ -347,7 +346,7 @@ Mapnik2:
|
|||
```sh
|
||||
# mapnik trunk
|
||||
cd $SRC
|
||||
svn co http://svn.mapnik.org/trunk/ mapnik-trunk
|
||||
git clone git://github.com/mapnik/mapnik.git mapnik-trunk
|
||||
cd mapnik-trunk
|
||||
export LANG="C"
|
||||
export LC_ALL="C"
|
||||
|
|
|
@ -13,14 +13,13 @@ To download and build Mapnik, you first need to install quite a bit of dependenc
|
|||
|
||||
sudo zypper install subversion make gcc gcc-c++ libxml2-devel postgresql-devel libgeos-devel libbz2-devel libproj-devel libjpeg-devel libtiff-devel libpng-devel boost-devel python-cairo-devel cairomm-devel libicu-devel libtool
|
||||
|
||||
Use Subversion to fetch the latest stable version of Mapnik. At the time of writing, that was 0.7.0.
|
||||
Use git to fetch the latest version of Mapnik..
|
||||
|
||||
svn export http://svn.mapnik.org/tags/release-0.7.0 mapnik-0.7.0
|
||||
git clone git://github.com/mapnik/mapnik.git
|
||||
|
||||
Build the Mapnik Python module. In the second line, you can omit everything after "scons.py" if you do not want to optimize the build or want to run the build on other machines.
|
||||
|
||||
cd mapnik-0.7.0/
|
||||
cd mapnik/
|
||||
python scons/scons.py CXX="g++ -march=native -O2 -fomit-frame-pointer" configure
|
||||
python scons/scons.py
|
||||
sudo python scons/scons.py install
|
||||
sudo ldconfig
|
||||
sudo python scons/scons.py install
|
|
@ -48,8 +48,8 @@ Still as root:
|
|||
|
||||
```
|
||||
$ cd && mkdir src && cd src
|
||||
$ svn export http://svn.mapnik.org/tags/release-0.7.1 mapnik-0.7.1
|
||||
$ cd mapnik-0.7.1/
|
||||
$ git clone git://github.com/mapnik/mapnik.git
|
||||
$ cd mapnik/
|
||||
$ python scons/scons.py configure
|
||||
$ python scons/scons.py install
|
||||
$ ldconfig
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!-- Name: PolygonSymbolizer -->
|
||||
## Configuration Options for PolygonSymbolizer
|
||||
|
||||
A PolygonSymbolizer is often used to render the area enclosed by a [polygon](http://en.wikipedia.org/wiki/Polygon). For example, the `rundemo.py` and `rundemo.cpp` applications use PolygonSymbolizer objects to "fill-in" [Canadian provinces with different colors and to make bodies of water look blue](http://trac.mapnik.org/attachment/wiki/PolygonSymbolizer/demo256.png?format=raw).
|
||||
A PolygonSymbolizer is often used to render the area enclosed by a [polygon](http://en.wikipedia.org/wiki/Polygon). For example, the `rundemo.py` and `rundemo.cpp` applications use PolygonSymbolizer objects to "fill-in" [Canadian provinces with different colors and to make bodies of water look blue](http://http://github.com/mapnik/mapnik/wiki/attachment/wiki/PolygonSymbolizer/demo256.png?format=raw).
|
||||
|
||||
| *parameter* | *value* | *default* | * description * |
|
||||
-------------|---------|------------|----------------|
|
||||
|
|
|
@ -85,8 +85,6 @@ To style a layer use the [[RasterSymbolizer]]
|
|||
|
||||
## Python
|
||||
|
||||
See the docstring at: http://svn.mapnik.org/trunk/docs/api_docs/python/mapnik-module.html#Raster
|
||||
|
||||
```xml
|
||||
<!-- NOTE: must be in the same SRS as your map-->
|
||||
<Layer name="Raster">
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Mapnik 0.7.2 Release
|
||||
|
||||
- Added forward compatibility for Mapnik 2.0 XML syntax (https://trac.mapnik.org/wiki/Mapnik2/Changes)
|
||||
- Added forward compatibility for Mapnik 2.0 XML syntax (https://http://github.com/mapnik/mapnik/wiki/wiki/Mapnik2/Changes)
|
||||
|
||||
- Build fixes to ensure boost_threads are not used unless THREADING=multi build option is used
|
||||
|
||||
|
|
|
@ -85,6 +85,6 @@ As can be understood from the previous section: even if you project roughly the
|
|||
* [DPI VS PPI](http://www.rideau-info.com/photos/printshop.html)
|
||||
* [Scale and PPI Discussion on Mapnik-Users](https://lists.berlios.de/pipermail/mapnik-users/2008-November/001415.html)
|
||||
* [SLD Implementation Specification](http://portal.opengeospatial.org/files/?artifact_id=1188)
|
||||
* [Mapnik's Scale Denominator Code](http://trac.mapnik.org/browser/trunk/src/scale_denominator.cpp#L37)
|
||||
* [Mapnik's Scale Denominator Code](https://github.com/mapnik/mapnik/blob/master/src/scale_denominator.cpp)
|
||||
* [PCL Scale Denominator Code](http://trac.gispython.org/lab/browser/PCL/trunk/PCL-Core/cartography/context/rendering.py#L112)
|
||||
* [PPI @ Wikipedia](http://en.wikipedia.org/wiki/Pixels_per_inch)
|
|
@ -27,7 +27,6 @@ To check if the raster plugin built and was installed correctly you can do:
|
|||
| encoding | string | Encoding Used | utf-8. ESRI Shapefiles are usually 'latin1' |
|
||||
| file | string | name of shapefile (without extension) | |
|
||||
|
||||
See: http://svn.mapnik.org/trunk/docs/api_docs/python/mapnik-module.html#Shapefile
|
||||
|
||||
# Styling
|
||||
|
||||
|
@ -37,8 +36,6 @@ To style a layer, use any of the Symbolizers like Point, Polygon, or Line, depen
|
|||
|
||||
## Python
|
||||
|
||||
See the docstring at: http://svn.mapnik.org/trunk/docs/api_docs/python/mapnik-module.html#Shapefile
|
||||
|
||||
## C++
|
||||
|
||||
Plugin datasource initialization example code can be found on PluginArchitecture.
|
||||
|
|
|
@ -52,7 +52,7 @@ To get syntax color, see "Syntax highlighting" from http://github.github.com/git
|
|||
|[Filter](http://github.com/mapnik/mapnik/wiki/Filter)|yes|||
|
||||
|[FontSet](http://github.com/mapnik/mapnik/wiki/FontSet)|yes|||
|
||||
|[FreeBSDInstallation](http://github.com/mapnik/mapnik/wiki/FreeBSDInstallation)|yes|||
|
||||
|[GDAL](http://github.com/mapnik/mapnik/wiki/GDAL)|yes (find a place for python api docs e.g http://svn.mapnik.org/trunk/docs/api_docs/python/mapnik-module.html#Gdal not working anymore)|||
|
||||
|[GDAL](http://github.com/mapnik/mapnik/wiki/GDAL)|yes|||
|
||||
|[GEOS](http://github.com/mapnik/mapnik/wiki/GEOS)|yes|||
|
||||
|[GettingStarted](http://github.com/mapnik/mapnik/wiki/GettingStarted)|yes (link to a place for python api docs)|yes (dane)||
|
||||
|[GettingStartedInPython](http://github.com/mapnik/mapnik/wiki/GettingStartedInPython)|yes|yes (dane)||
|
||||
|
@ -70,7 +70,7 @@ To get syntax color, see "Syntax highlighting" from http://github.github.com/git
|
|||
|[Compositing](http://github.com/mapnik/mapnik/wiki/Ideas_Compositing)|yes|||
|
||||
|[Future Features of Mapnik](http://github.com/mapnik/mapnik/wiki/Ideas_FutureMapnik)|yes|||
|
||||
|[Installation Troubleshooting](http://github.com/mapnik/mapnik/wiki/InstallationTroubleshooting)|yes|||
|
||||
|[InstallGuide](http://github.com/mapnik/mapnik/wiki/InstallGuide)|yes? link to the document done but the doc is outdated (trac.mapnik.org links)|||
|
||||
|[InstallGuide](http://github.com/mapnik/mapnik/wiki/InstallGuide)|yes)|||
|
||||
|[How to integrate mapnik with wxPython?](http://github.com/mapnik/mapnik/wiki/IntegrateWithWxPython)|yes|||
|
||||
|[International Text](http://github.com/mapnik/mapnik/wiki/InternationalText)|yes|||
|
||||
|[IntroductionToGIS](http://github.com/mapnik/mapnik/wiki/IntroductionToGIS)|yes|||
|
||||
|
@ -86,7 +86,6 @@ To get syntax color, see "Syntax highlighting" from http://github.github.com/git
|
|||
|[Installing Mapnik on OS X with Homebrew](http://github.com/mapnik/mapnik/wiki/MacInstallation_Homebrew)|yes|||
|
||||
|[Optional Installs](http://github.com/mapnik/mapnik/wiki/MacInstallation_Optional)|yes|||
|
||||
|[Installing Mapnik on OS X from Source](http://github.com/mapnik/mapnik/wiki/MacInstallation_Source)|yes|||
|
||||
|[Installing Mapnik on Mac OS X](http://github.com/mapnik/mapnik/wiki/MacInstallationPorts)|yes (retrieve SConstruct.osx.patch because lost + what do we do with links to doc generated from rst not available e.g https://github.com/mapnik/sphinx-docs )|||
|
||||
|[MacInstallationSource](http://github.com/mapnik/mapnik/wiki/MacInstallationSource)|yes|||
|
||||
|[MacPostGIS_Setup](http://github.com/mapnik/mapnik/wiki/MacPostGIS_Setup)|yes|||
|
||||
|[MacPythonUpgradeIssues](http://github.com/mapnik/mapnik/wiki/MacPythonUpgradeIssues)|yes|||
|
||||
|
@ -112,7 +111,7 @@ To get syntax color, see "Syntax highlighting" from http://github.github.com/git
|
|||
|[Mapnik Renderers](http://github.com/mapnik/mapnik/wiki/MapnikRenderers)|yes|||
|
||||
|[Mapnik Tutorials](http://github.com/mapnik/mapnik/wiki/MapnikTutorials)|yes|||
|
||||
|[MapnikUtilities](http://github.com/mapnik/mapnik/wiki/MapnikUtilities)|yes|||
|
||||
|[MapnikViewer](http://github.com/mapnik/mapnik/wiki/MapnikViewer)|yes (lost ref to http://trac.mapnik.org/raw-attachment/wiki/MapnikViewer/viewer.patch, add the missing file)|||
|
||||
|[MapnikViewer](http://github.com/mapnik/mapnik/wiki/MapnikViewer)|yes |||
|
||||
|[MarkersSymbolizer](http://github.com/mapnik/mapnik/wiki/MarkersSymbolizer)|yes (retrieve offsets_directions.png from http://173.255.217.246:8000/mapnik_trac/raw-attachment/ticket/180/offsets_directions.png )|||
|
||||
|[MaxScaleDenominator](http://github.com/mapnik/mapnik/wiki/MaxScaleDenominator)|yes|||
|
||||
|[MemoryDatasource](http://github.com/mapnik/mapnik/wiki/MemoryDatasource)|yes|||
|
||||
|
|
|
@ -184,7 +184,7 @@ Karmic has Mapnik packages for 0.6.1, so you can either install Mapnik from pack
|
|||
### Then compile and install Mapnik
|
||||
|
||||
```
|
||||
svn co http://svn.mapnik.org/tags/release-0.7.1/ mapnik
|
||||
git clone git://github.com/mapnik/mapnik.git
|
||||
cd mapnik
|
||||
python scons/scons.py configure INPUT_PLUGINS=all OPTIMIZATION=3 SYSTEM_FONTS=/usr/share/fonts/truetype/ttf-dejavu/
|
||||
python scons/scons.py
|
||||
|
@ -251,7 +251,7 @@ This works with the default python-2.6 on jaunty:
|
|||
libsqlite3-dev \
|
||||
subversion build-essential
|
||||
|
||||
svn co http://svn.mapnik.org/tags/release-0.7.0/ mapnik
|
||||
git clone git://github.com/mapnik/mapnik.git
|
||||
cd mapnik
|
||||
python scons/scons.py configure INPUT_PLUGINS=all \
|
||||
OPTIMIZATION=3 \
|
||||
|
|
|
@ -76,7 +76,7 @@ A Style object defines the way objects can be rendered. A Mapnik configuration
|
|||
* *[#Datasource Datasource]*
|
||||
|
||||
## Datasource
|
||||
See also the [0.6.0 Python API docs](http://svn.mapnik.org/tags/release-0.6.0/docs/api_docs/python/mapnik-module.html#Datasource)
|
||||
See also the [Python API docs](http://mapnik.org/docs/v2.1.0/api/python/index.html)
|
||||
|
||||
* Element: *Datasource*
|
||||
* Element type: References the map data source and parameters.
|
||||
|
@ -145,7 +145,7 @@ Also see [[SymbologySupport]] for more info on Symbolizers
|
|||
* Children:
|
||||
* *[#Style Style]*
|
||||
* *[#Layer Layer]*
|
||||
* *FileSource*: See [#574](http://trac.mapnik.org/changeset/574)
|
||||
* *Datasource*: See [#Datasource Datasource] and [#574](http://trac.mapnik.org/changeset/574)
|
||||
* *FileSource*:
|
||||
* *Datasource*: See [#Datasource Datasource]
|
||||
* *FontSet*: Defines a fontset for fallback fonts (if a character isn't found in the first font, proceed through the list until it is found)
|
||||
|
||||
|
|
Loading…
Reference in a new issue