palette_force and quantize_force are mutually exclusive, in the sense that only one of them is applied (depending on which comes first in the mapserver code) * quantize_force is more flexible as it doesn't need to create a palette beforehand, but different colors can be seen from one map to another depending on the extent * palette_force produces more consistent results colorwise but a palette file has to be created beforehand. I'd recommend creating a palette with exactly 256 colors in it if you're looking for rendering speed, or with just the exact colors of your features if you're looking for rendering quality.
regards, thomas On Jan 8, 2008 6:54 PM, rich.fromm <[EMAIL PROTECTED]> wrote: > Flavio Hendry wrote: > > > > AGG has to be 24bit. > > > > I'm pretty sure that's not true. I'm using something like the following: > > IMAGETYPE AGG_Q > OUTPUTFORMAT > NAME 'AGG_Q' > DRIVER AGG/PNG > IMAGEMODE RGB > FORMATOPTION "PALETTE_FORCE=TRUE" > # for why this is needed at all: > # http://trac.osgeo.org/mapserver/ticket/2096 > # this must be an absolute path (should be able to be relative to > the map file for mapserver 5.2) > # http://trac.osgeo.org/mapserver/ticket/2115 > FORMATOPTION "PALETTE=/absolute/path/to/colors.palette" > FORMATOPTION "QUANTIZE_FORCE=ON" > FORMATOPTION "QUANTIZE_DITHER=OFF" > FORMATOPTION "QUANTIZE_COLORS=256" > END > > which gives me (this is the result of running `file output.png`): > > PNG image data, 640 x 480, 8-bit colormap, non-interlaced > > - Rich > > -- > View this message in context: > http://www.nabble.com/Polygon-style-with-outline-width-tp13586055p14694909.html > Sent from the Mapserver - User mailing list archive at Nabble.com. >
