: Basques, Bob (CI-StPaul)
<bob.basq...@ci.stpaul.mn.us<mailto:bob.basq...@ci.stpaul.mn.us>>
Cc: mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
Subject: Re: [mapserver-users] Understanding extents and resolutions
Bob,
I am not sure I am understanding your re
: Thursday, October 01, 2015 1:37 PM
To: Lime, Steve D (MNIT)
Cc: Zach Chehayeb; mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] Understanding extents and resolutions
All,
Yeah, I just figured it out for myself too. My tests were against a WMS call
to MapServer vs a MapServer direct
Hello All,
Can anyone explain or point me in the right direction on how mapserver logic
works when a requested map extent cannot be produced at the requested
resolution with square pixels?
I am using mapserver in an application that requests mapserver to produce
various map extents at various
s, Bob (CI-StPaul) [mailto:bob.basq...@ci.stpaul.mn.us]
Sent: Thursday, October 01, 2015 12:29 PM
To: Zach Chehayeb
Cc: mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] Understanding extents and resolutions
Zach,
If I’m understanding your question correctly, MapServer will always gi
Zach,
If I’m understanding your question correctly, MapServer will always give you
your requested coordinate space inside of the requested image size, by
buffering the image results along the axis that is larger than the coordinate
window needs to draw completely. In other words, MapServer
ct: Re: [mapserver-users] Understanding extents and resolutions
Bob,
I am not sure I am understanding your response correctly. Are you suggesting
that it is the coordinate window ratio that determines whether mapserver locks
on the east/west or north/south bounds? If so, this doesn’t align w
:29 PM
> To: Zach Chehayeb
> Cc: mapserver-users@lists.osgeo.org
> Subject: Re: [mapserver-users] Understanding extents and resolutions
>
> Zach,
>
> If I’m understanding your question correctly, MapServer will always give you
> your requested coordinate space inside of the r
