<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Greetings all,</div><div><br></div><div>Once I completed upgrading to mapserver 5.4, I decided I'd give the new AGG renderer a try.</div><div><br></div><div>To date I have been using the GD renderer in 8 bit color mode.</div><div><br></div><div>One problem I had with it the renderer, and my main motivation to use the AGG renderer (apart from what appears to be an overall improvement in appearance) was that any layer containing "ANGLE FOLLOW" within a class label definition caused php/mapscript to crash rendering meta tiles (for ka-map, if that matters). The AGG renderer solved that problem immediately and it works flawlessly in that respect.</div><div><br></div><div>However, as a by-product of changing renderer, the metatiles produced by mapserver differ slightly in colour. Some agree exactly to the RBG colours I am providing, others are rendered with slight variations, and when viewed on the web it becomes fairly obvious where the meta tile borders are.</div><div><br></div><div>I have tried both</div><div><br></div><div><div> OUTPUTFORMAT</div><div> NAME 'AGG_Q'</div><div> DRIVER AGG/PNG</div><div> IMAGEMODE RGB</div><div> FORMATOPTION "QUANTIZE_FORCE=ON"</div><div> FORMATOPTION "QUANTIZE_DITHER=OFF"</div><div> FORMATOPTION "QUANTIZE_COLORS=256"</div><div> END</div><div><br></div><div>and</div><div><br></div><div> OUTPUTFORMAT</div><div> NAME 'AGG'</div><div> DRIVER AGG/PNG</div><div> IMAGEMODE RGB</div><div> END</div><div><br></div><div>but both produce the same results. I have even tried fiddling with the FORMATOPTIONs in the AGG_Q block to no effect.</div><div><br></div><div>I've double-checked the mapscript used to render the tiles to make sure that the correct output format is being selected.</div><div><br></div><div>Is there a known solution to this? How can I force all tiles produced to use the exact same colour settings? I would have thought the quantize option would resove it, although obviously this would have a slight detrimental side-effect for anti-aliasing.</div><div><br></div><div>My map file does include various "ANTIALIAS" options (which the document states are ignored in AGG mode) so I can fall back to GD rendering should I ever get "ANGLE FOLLOW" working again.</div></div><div><br></div><div>Regards,</div><div><br></div><div apple-content-edited="true"> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div apple-content-edited="true"><div><div><div><div><div><div><div><div><div><div><div><div><div><div apple-content-edited="true"><div><div><div><div><div><div><div><div><div><div><div apple-content-edited="true"><div><div><div><div><div><div><div><div>--</div><div>David Nugent (<a href="mailto:davidn@datalinktech.com.au">davidn@datalinktech.com.au</a>)</div><div>Software Engineer</div><div>datalink technologies pty ltd</div><div>Mobile GPS/GPRS business process solutions</div><div><a href="http://www.datalinktech.com.au/">http://www.datalinktech.com.au/</a></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></body></html>