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-07-30 18:35:28 -07:00
parent 0e71717cfc
commit 45369418a8
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -10,9 +10,12 @@
* `MarkersSymbolizer` * `MarkersSymbolizer`
* `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 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 scale the marker, but ideally you should use `transform="scale(x,y)" instead.
* `opacity` setting now affects (overrides) the opacity of any fill and stroke - use `fill-opacity` and `stroke-opacity` to set each of these opacities individually. This change ensures Mapnik's marker properties and svg rendering matches the svg as close as possible.
## Added ## Added
* `MarkersSymbolizer`
* `fill-opacity` is new.
* `opacity` value now works to set the alpha of bitmap images.
* `Expression` - you can now use the built in keyword of `[mapnik::geometry_type]` to filter features by geometry type either by name or integer key. The mapping is `0:no geometry`, `1:point`, '2:linestring`, `3:polygon`, and `4:collection`. A collection indicates that the `Feature` has more than one geometry of different types. So a `Feature` with three linestrings will be reported as `linestring` but a `Feature` with a point and a linestring will be reported as a `collection`. - for more details see [#546](https://github.com/mapnik/mapnik/issues/546) * `Expression` - you can now use the built in keyword of `[mapnik::geometry_type]` to filter features by geometry type either by name or integer key. The mapping is `0:no geometry`, `1:point`, '2:linestring`, `3:polygon`, and `4:collection`. A collection indicates that the `Feature` has more than one geometry of different types. So a `Feature` with three linestrings will be reported as `linestring` but a `Feature` with a point and a linestring will be reported as a `collection`. - for more details see [#546](https://github.com/mapnik/mapnik/issues/546)
* To All symbolizers (in most cases) * To All symbolizers (in most cases)
* `comp-op` - All symbolizers now support compositing in the AGG and Cairo renderers * `comp-op` - All symbolizers now support compositing in the AGG and Cairo renderers