Hi Christy,
That's right, 5.6.4 shouldn't require any modifications for users, it's only a
bug fix release. Would you be able to provide a small test case (data+mapfile)
?
Alan
On July 13, 2010 09:46:24 am Christy Nieman wrote:
> Hi,
>
> I've just compiled mapserver 5.6.4 in an FGS enviromnme
On 7/13/2010 8:46 AM, Christy Nieman wrote:
Hi,
I've just compiled mapserver 5.6.4 in an FGS enviromnment, and when I
rendered a map I noticed that it was taking a very long time. Once the
image was displayed, it seemed that the largest scale class for each
layer had been used for a rather small
Checked the mapserver binaries - both have AGG (and since both using the
same mapfile, both have the same output format specified). Will work on
getting a sample mapfile that demonstrates this.
On 07/13/2010 10:05 AM, Andy Colson wrote:
On 7/13/2010 8:46 AM, Christy Nieman wrote:
Hi,
I've j
On 07/13/2010 09:46 AM, Christy Nieman wrote:
I've just compiled mapserver 5.6.4 in an FGS enviromnment, and when I
rendered a map I noticed that it was taking a very long time. Once the
image was displayed, it seemed that the largest scale class for each
layer had been used for a rather small sc
Christy Nieman wrote:
> Attached is a sample.
>
> With mapserver 5.6.3's shp2img, in the mapfile as provided, I get a thin
> lines and small labels on them. With 5.6.4's shp2img I get thicker
> lines with larger labels. If you uncomment the MAXSCALEDENOM in the
> smallest scale class, in 5.6.3 y
I tested (and reported back to the ticket), that it looks good now.
On 07/13/2010 11:47 AM, Daniel Morissette wrote:
Christy Nieman wrote:
Attached is a sample.
With mapserver 5.6.3's shp2img, in the mapfile as provided, I get a thin
lines and small labels on them. With 5.6.4's shp2img I
