AGG support

[Vincent Schut]

sorry if this appears twice, but resending because I did not see my 
message appear in my mailbox in more than half an hour after sending...

Hi all,

Always eager to try new stuff, I decided to try the agg rendering. Not
surprisingly (no offense :-)) I get a serviceException from my mapserver
WMS service:

<?xml version='1.0' encoding="ISO-8859-1" standalone="no" ?>
<!DOCTYPE ServiceExceptionReport SYSTEM
"http://schemas.opengis.net/wms/1.1.1/exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1">
<ServiceException code="InvalidFormat">
msWMSGetLegendGraphic(): Image handling error. Unsupported output format
(image/png).
</ServiceException>
</ServiceExceptionReport>

This is of course using a WMS request that does work when I replace the
agg outputformat with my original GD one.
I have defined the outputformat in my map file as follows (the commented
lines are the original GD png outputformat which works, so you can
compare it with the AGG one):

#     OUTPUTFORMAT
#         NAME png_rgba
#         DRIVER "GD/PNG"
#         MIMETYPE "image/png"
#         IMAGEMODE rgba
#         TRANSPARENT on
#         EXTENSION "png"
#         #FORMATOPTION interlace=on
#     END #outputformat

    OUTPUTFORMAT
        NAME    png_rgba
        DRIVER    "AGG/PNG"
        IMAGEMODE    RGBA
        TRANSPARENT on
        EXTENSION "png"
        MIMETYPE "image/png"
    END

As I said, I am using mapserver cgi as WMS.

Any clues how to get the new outputformat recognized by mapserver WMS?

Vincent.

John Novak wrote:
> Tom,
>
> Please do provide input on your experiences with the new AGG code,
>
> Best,
>
> John Novak
>
> On 3/9/07, *Steve Lime* < Steve.Lime at dnr.state.mn.us 
> <mailto:Steve.Lime at dnr.state.mn.us>> wrote:
>
>     Use at your own peril, but you can certainly play with it. John
>     Novak has done the bulk of the work to date
>     with new input coming from Assefa. It looks promising so many
>     thanks for the excellent work to date.
>
>     I don't believe there are extensions to the Windows Makefile but I
>     did commit configure support for *nix
>     yesterday. Works fine on my SuSE box. Just do a --with-agg=path to
>     agg when running configure and
>     it should work. You need agg version 2.4 at this point. Agg
>     doesn't have install scripts so I just left it
>     where I built it ( e.g. /usr/local/src/agg-2.4). Configure will
>     look for that type of setup or in the system libs.
>
>     To use simply plop a OUTPUTFORMAT in your mapfile like so:
>
>     OUTPUTFORMAT
>         NAME                myAggRgb
>         DRIVER      AGG/PNG
>         IMAGEMODE   RGB
>       END
>
>     RGB and RGBA are supported.
>
>     The AGG driver uses GD as the buffer manager, so basically AGG
>     renders to a GD image so we can use GD
>     file writing and any of the other GD writing code. That allows us
>     to concentrate on pieces of the rendering
>     while still creating complete images. At the moment I believe
>     polygons and lines are rendered using AGG
>     while markers and text fallback on their GD counterparts.
>
>     Steve
>
>
>     >>> On 3/9/2007 at 1:36 PM, in message
>     <2576812186CDD411BF1500508B6DCE9511B30C88 at ecnwri1.ontario.int.ec.gc.ca
>     <mailto:2576812186CDD411BF1500508B6DCE9511B30C88 at ecnwri1.ontario.int.ec.gc.ca>>,
>     "Kralidis,Tom [Burlington]" < Tom.Kralidis at EC.GC.CA
>     <mailto:Tom.Kralidis at EC.GC.CA>> wrote:
>     > Just noticed mapagg.cpp in CVS HEAD.
>     >
>     > Is / can this be tried out?  Any build details?
>     >
>     > ..Tom
>
>
>
>
> -- 
> John Novak
> Novacell Technologies and the Old Topo Depot
> http://www.novacell.com
> 877-old-topos