Version 4.4.1 dependency and/or linux platform dependency?

[Brian Davis]

Frank,

Thanks for your reply.
Yes, you understood my problem correctly.
Now, I am trying to understand your response .....
I AM making wms requests, and if I understand your comments correctly,
I have to "pre-adjust my bounding box to match the aspect ratio
of the image size" .... not sure what this means ......

To avoid this, do I add an entry to my map file like:
CONFIG MS_NONSQUARE NO
or
CONFIG MS_NONSQUARE FALSE
?
Or, do I really have to resize the browser display area each
time I select a new area of new x/y shape?

The original image dimensions, on which I am zooming on, are
10020 x 5010.

In my map file, I have an entry for
SIZE 500 250
and corresponding width and height specifications in my url call to mapserv.

I added the
CONFIG MS_NONSQUARE NO
entry to the map file, with no effect.
I usually assume it is always my fault, so I am not ready to blame
mapserver yet.  Any hints you can provide would be greatly appreciated.

Maybe I can tar up my entire web site, send it to you, go on vacation,
have you fix everything while I'm gone, then take credit for it when
I get back?????!!!!!! :)


Brian.




On Thu, 21 Apr 2005 10:06:51 -0400, Frank Warmerdam <fwarmerdam at GMAIL.COM>
wrote:

>On 4/21/05, Brian Davis <bdavis at usgs.gov> wrote:
>> When I zoom in to a map, the four corner points of my rubber-band box
>> are the new corners for the data displayed in my 400x200 browser space.
>> So, if I define an area that is 2:1 in x size to y size, I zoom in
>> as expected.  But when defining space that is not this 2:1 rectangular
>> ratio, the data gets stretched/contracted/distorted to fit that space,
>> because the corners of my new definition become the drawn corners,
>> instead of extra data in either the x or y direction being used to
>> fill the the remaining area.
>
>Brian,
>
>As I understand it, the problem you are seeing is that MapServer
>used to expand the region you requested as needed in order to
>ensure square pixels, and now does not resulting in distorted
>results, is that right?
>
>Indeed, for MapServer 4.4 there was "nonsquare" support
>added to MapServer.  In WMS mode this is on by default,
>in order to comply with the specification.  In non-WMS mode
>it is supposed to be off by default (giving you the traditional
>aspect preserving behavior) unless you add the following
>line to your .map file:
>
>  CONFIG MS_NONSQUARE YES
>
>Is your client requesting data via WMS?  If so, then you
>will pretty much have to pre-adjust your bounding box to
>match the aspect ratio of the image size.  If you are getting
>this behavior in traditional MapServer cgi mode and haven't
>defined MS_NONSQUARE then we should look into what is
>going on.
>
>Best regards,
>--
>---------------------------------------+-----------------------------------
---
>I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
>light and sound - activate the windows | http://pobox.com/~warmerdam
>and watch the world go round - Rush    | Geospatial Programmer for Rent