sij/mapnik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated API changes between v2.0 and v2.1 (markdown)

springmeyer 2012-08-22 18:46:36 -07:00
parent 2492313a69
commit 2ae18177d5
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
API-changes-between-v2.0-and-v2.1.md

@ -15,7 +15,7 @@
* default `marker-placement` is now `point` instead of `line` - meaning if you want your symbols (like arrows) to be oriented along lines you now need to specify `placement=line`, whereas previously this was the default. This changes reflects the goal of making the MarkersSymbolizer default behavior more reasonable for any geometry type, including points, lines, and polygons and to make it consistent with the `TextSymbolizer` and `ShieldSymbolizer` which also default to `point` placement. * default `marker-placement` is now `point` instead of `line` - meaning if you want your symbols (like arrows) to be oriented along lines you now need to specify `placement=line`, whereas previously this was the default. This changes reflects the goal of making the MarkersSymbolizer default behavior more reasonable for any geometry type, including points, lines, and polygons and to make it consistent with the `TextSymbolizer` and `ShieldSymbolizer` which also default to `point` placement.
* `width` and `height` are now optional expressions rather than raw floats and their values represent diameter in pixels not radii. If not set they will be `None`, but the default ellipse has a `radius` of `10` meaning that if you set `width="20"` and `height="20"` then there will be no change in the rendering size of the ellipse. The arrow default dimensions can be maintained with `width="27" height="12"`. Altering width or height will build a new `ellipse` svg marker internally by default if no custom file type is provided. For non-ellipse types setting `width` and `height` will proportionally scale the marker, but ideally you should use `transform="scale(x,y)" instead. * `width` and `height` are now optional expressions rather than raw floats and their values represent diameter in pixels not radii. If not set they will be `None`, but the default ellipse has a `radius` of `10` meaning that if you set `width="20"` and `height="20"` then there will be no change in the rendering size of the ellipse. The arrow default dimensions can be maintained with `width="27" height="12"`. Altering width or height will build a new `ellipse` svg marker internally by default if no custom file type is provided. For non-ellipse types setting `width` and `height` will proportionally scale the marker, but ideally you should use `transform="scale(x,y)" instead.
* A new `fill-opacity` setting is available and now `opacity` reverse to a new overall opacity that will be multiplied against the `fill-opacity` or `stroke-opacity` - this is to match how svg behaves. * A new `fill-opacity` setting is available and now `opacity` reverse to a new overall opacity that will be multiplied against the `fill-opacity` or `stroke-opacity` - this is to match how svg behaves.
* In Python a mapnik.Feature now expects a mapnik.Context() as a first argument and a feature id as the second argument, which stores all attribute names (previously mapnik.Feature only needed a single argument of the feature id and redundantly stored feature attribute names per feature). * In Python a mapnik.Feature now expects a mapnik.Context() as a first argument and a feature id as the second argument, which stores all attribute names (previously mapnik.Feature only needed a single argument of the feature id and redundantly stored feature attribute names per feature) [#834](https://github.com/mapnik/mapnik/issues/834).
## Added ## Added
* `MarkersSymbolizer` * `MarkersSymbolizer`