batch fix remaining wiki: links

Dane Springmeyer 2011-12-11 11:15:31 -08:00
parent 2b797d37b6
commit e9d957d089
11 changed files with 17 additions and 17 deletions

@ -45,7 +45,7 @@ _The Mapnik Team_
* LearningMapnik - outline of key topics
* *Troubleshooting Mapnik*
* [wiki:Troubleshooting] - tips for common gochas
* [[Troubleshooting]] - tips for common gochas
* InstallationTroubleshooting - install problems and solutions
* *Mapnik Utilities*
@ -58,8 +58,8 @@ _The Mapnik Team_
* See [MapnikCodeSprint Sprint Schedules]
* *Google Summer of Code*
* 2011: [wiki:GSOC2011]
* 2010: [wiki:GSOC2010]
* 2011: [[GSOC2011]]
* 2010: [[GSOC2010]]
* *Development Ideas and Topics*
* DeveloperTopics is a sandbox for discussing Mapnik development

@ -44,7 +44,7 @@ You may install Proj.4, PostgreSQL/PostGIS, and GDAL if needed.
opts.Add(PathOption('PGSQL_INCLUDES', 'Search path for PostgreSQL include files', '/opt/local/include/postgresql83'))
opts.Add(PathOption('PGSQL_LIBS', 'Search path for PostgreSQL library files', '/opt/local/lib/postgresql83'))
* See [wiki:MacPostGIS_Setup] for setup instructions.
* See [[MacPostGIS_Setup]] for setup instructions.
* *GDAL* binary frameworks - use [kyngchaos.com](http://www.kyngchaos.com/wiki/software:frameworks) or build from source:
$ wget http://download.osgeo.org/gdal/gdal-1.5.0.tar.gz

@ -55,7 +55,7 @@ This is a quick list of things we started work on or achieved during the sprint:
* Improvements to SVG parsing and rendering (artem)
* Fixed feature caching when using multiple styles for faster rendering (woodpeck) (#624)
* Brainstormed and scoped on wiki ideas around [Compositing](/wiki:Ideas/Compositing/) and [Legends](/wiki:Legending/) (gravitystorm, ivansanchez)
* Added Python3 support (haoyu,springmeyer) [wiki:Python3k]
* Added Python3 support (haoyu,springmeyer) [[Python3k]]
* Wrote a render_debug() function to output statistics on rendering times (woodpeck)
* Added the ability to control the timeout of expensive PostGIS queries (jburgess) #632
* Started writing Spreadnik v2 in python (ivansanchez)

@ -129,7 +129,7 @@
### Trac Post-Release
* Update [wiki:MapnikInstallation], [MacInstallation](https://github.com/mapnik/mapnik/wiki/MacInstallation), [LinuxInstallation](https://github.com/mapnik/mapnik/wiki/LinuxInstallation) and [WindowsInstallation](https://github.com/mapnik/mapnik/wiki/WindowsInstallation) links
* Update [[MapnikInstallation]], [MacInstallation](https://github.com/mapnik/mapnik/wiki/MacInstallation), [LinuxInstallation](https://github.com/mapnik/mapnik/wiki/LinuxInstallation) and [WindowsInstallation](https://github.com/mapnik/mapnik/wiki/WindowsInstallation) links
* Create a release page from the relevant section of CHANGELOG like this page [Release0.7.1](https://github.com/mapnik/mapnik/wiki/Release0.7.1)
* Update [MapnikReleases](https://github.com/mapnik/mapnik/wiki/MapnikReleases), a starting page for users to learn about Mapnik development

@ -15,7 +15,7 @@ GettingStarted - 'Hello,world!' using the Python bindings.
## World Population
[wiki:XMLGettingStarted] - Python and XML styling
[[XMLGettingStarted]] - Python and XML styling
[[BR]]
[[Image(population.png)]]

@ -53,7 +53,7 @@ See [OgcServer](https://github.com/mapnik/OGCServer) for more info.
C++ WMS server.
See [wiki:Paleoserver] for more info.
See [[Paleoserver]] for more info.
## Desktop Tools

@ -10,7 +10,7 @@ All current plugins are located in source:trunk/plugins/input/
| **Name**| **Availability**|**Status**|**Build by Default**|**Notes**|
|:-------:|:---------------:|:--------:|:------------------:|:-------:|
| *[postgis](PostGIS)*| 0.2.0| Stable| yes| support for accessing geospatial data through [wiki:PostGIS], the spatial database extension for [PostgreSQL](http://en.wikipedia.org/wiki/PostgreSQL)|
| *[postgis](PostGIS)*| 0.2.0| Stable| yes| support for accessing geospatial data through [[PostGIS]], the spatial database extension for [PostgreSQL](http://en.wikipedia.org/wiki/PostgreSQL)|
| *[raster](Raster)*| 0.2.0| Stable| yes| stripped or tiled raster TIFF image dataset support|
| *[shape](Shape)*| 0.2.0| Stable| yes| vector SHP ([ESRI Shapefile](http://en.wikipedia.org/wiki/Shapefile)) parsing|
| *[gdal](GDAL/)*| 0.5.0| Beta| no| support for [GDAL](http://en.wikipedia.org/wiki/GDAL) datasets|

@ -11,7 +11,7 @@ The RasterSymbolizer is used to render an image from any [GDAL supported format]
* As of Mapnik 0.6.0 the RasterSymbolizer supports transparency and composition modes.
* See the original ticket for details: #259
* See also [wiki:Compositing] for some of the effects.
* See also [[Compositing]] for some of the effects.
* This Symbolizer is often used with DEM (digital elevation model) data containing missing values (for example NASA SRTM DEM data); to achieve nice rendering, the [gdal_fillnodata.py](http://www.gdal.org/gdal_fillnodata.html) tool might be useful.
@ -32,12 +32,12 @@ Processed as described in http://wiki.openstreetmap.org/wiki/Hillshading_using_t
There are two types of raster datasources: *gdal* or *raster*:
* The [wiki:GDAL] plugin is more convenient as it can read the file extents automatically and supports any GDAL-supported type of file
* The [wiki:Raster] driver only works with Tiled or Stripped GeoTIFF files and requires manually setting the file bounds, but can be faster.
* The [[GDAL]] plugin is more convenient as it can read the file extents automatically and supports any GDAL-supported type of file
* The [[Raster]] driver only works with Tiled or Stripped GeoTIFF files and requires manually setting the file bounds, but can be faster.
## XML Layers
See the [wiki:GDAL] plugin and [wiki:Raster] plugin pages for more info
See the [[GDAL]] plugin and [[Raster]] plugin pages for more info
## XML Styles

@ -65,7 +65,7 @@ Apart from the scale, there's also the scale denominator, which plays a further
### Scale denominator
[[Image(scale.png)]][[BR]]
The above image illustrates how scale dependent rendering and resolution interact. Each map has the same extent and proportions. The large map was printed at 1000px by 1000px and the smaller inset at 250px250px, these were both reduced by 50% for display here. What you should notice is that resolution matters for scale. Each of these maps, made with [wiki:Nik2Img], have different levels of detail, because they are at different scales, even though the extents are the same.
The above image illustrates how scale dependent rendering and resolution interact. Each map has the same extent and proportions. The large map was printed at 1000px by 1000px and the smaller inset at 250px250px, these were both reduced by 50% for display here. What you should notice is that resolution matters for scale. Each of these maps, made with [[Nik2Img]], have different levels of detail, because they are at different scales, even though the extents are the same.
What determines the actual scale of the map when printed, is determined by an additional factor which is the number of pixels that make up an inch--Pixels per inch(PPI). Various digital screens have different pixel sizes and therefore PPI differs in ways that software often cannot be aware of. Mapnik calculates it's default at about 90.7 PPI, which originates from an assumed standard pixel size of 0.28 millimeters as defined by the OGC (Open Geospatial Consortium) SLD (Styled Layer Descriptor) [Specification](http://www.opengeospatial.org/standards/sld).

@ -6,7 +6,7 @@
[[TOC]]
This plugin supports reading shapefiles. They can also be read using the [wiki:OGR] Plugin, but the *shape* plugin is better tested and more mature.
This plugin supports reading shapefiles. They can also be read using the [[OGR]] Plugin, but the *shape* plugin is better tested and more mature.
The shapefile plugin will run fastest if you build indexes for your shapefiles using the 'shapeindex' command line tool installed when you build Mapnik.

@ -3,7 +3,7 @@
| *parameter* | *value* | *description* | *unit* | *default* |
----------------|---------|----------------|-------|------------|
| name | - | This is the query field you want to use for the label text, e.g. "street_name" (deprecated in Mapnik2, see section "new syntax" below)| - | - |
|face_name | - | Font name (see [wiki:UsingCustomFonts])| - | - |
|face_name | - | Font name (see [[UsingCustomFonts]])| - | - |
|fontset_name|| FontSet name ||
|size||Font size|||
|text_ratio|| Try to keep a given height to width ratio|||
@ -51,7 +51,7 @@ Some examples of Mapnik's ability to place text along lines:
<TextSymbolizer name="FIELD_NAME" face_name="DejaVu Sans Book" size="10" fill="black" halo_fill= "white" halo_radius="1" placement="line" allow_overlap="false"/>
```
See [wiki:XMLGettingStarted] for more XML example uses of TextSymbolizer.
See [[XMLGettingStarted]] for more XML example uses of TextSymbolizer.
### Python