[mapguide-internals] RE: Image size limitation in RenderingService

[Walt Welton-Lair]

The change to RasterAdapter was made 5 years ago.  At the time MapGuide Open Source was under development and only supported a DWF Viewer based client, and the image size limit made sense.  Now that we have image based clients, and also hardware display resolutions have increased over the years, the image size check should probably be changed.

Walt

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Arthur Liu
Sent: Wednesday, September 15, 2010 8:34 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Image size limitation in RenderingService

Hi all,

I met a problem when trying to get a map image with size 2048x2048. The image quality drops significantly compare to 2048x2047.
That happens only in Raster provider and WMS provider,  vector data sources doesn't have this kind of problem.

I found following code in rendering service

RasterAdapter::Stylize()
{
   ...
    while (imgW >= 2048 || imgH >= 2048)
    {
        imgW >>= 1;
        imgH >>= 1;
    }
    ...
}
The map image can be gennerated sucessfully if I comment out the code.

Does there anyone know why there's a limitation of the map image? Is there any solution or workaround to get a large size map image?

Regards,
Arthur
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals