Updated Mapnik Output Formats (markdown)

ThomasG77 2012-01-07 11:46:07 -08:00
parent 29aec25c24
commit bcce6a1ef7

@ -44,7 +44,7 @@ So to use new format i.e. in python:
or other example in c++: or other example in c++:
save_to_file(vw, "test.png", "png256:t=1:c=128"); save_to_file(vw, "test.png", "png256:t=1:c=128");
For more details see [mapnik-devel email http://lists.berlios.de/pipermail/mapnik-devel/2010-March/001081.html] and ticket #477: http://trac.mapnik.org/ticket/477#comment:10 For more details see [mapnik-devel email](http://lists.berlios.de/pipermail/mapnik-devel/2010-March/001081.html and ticket [#477](https://github.com/mapnik/mapnik/issues/477)
Most render functions like `save_to_string` also take a third argument which must be a `rgba_palette` object. You can create palettes by passing a buffer with RGBA values (4 bytes), a buffer with RGB values (3 bytes) or an Adobe Photoshop .act file (generated by the "Save for Web" dialog") with exactly 772 bytes to the `rgba_palette` constructors. Note that palette objects are mutable and contain a lookup table that cache all values ever retrieved for faster encoding. Most render functions like `save_to_string` also take a third argument which must be a `rgba_palette` object. You can create palettes by passing a buffer with RGBA values (4 bytes), a buffer with RGB values (3 bytes) or an Adobe Photoshop .act file (generated by the "Save for Web" dialog") with exactly 772 bytes to the `rgba_palette` constructors. Note that palette objects are mutable and contain a lookup table that cache all values ever retrieved for faster encoding.