<br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style><br>
<div class="gmail_quote">2010/3/15 James Perrins <span dir="ltr"><<a href="mailto:james.perrins@gmail.com">james.perrins@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
It seems that mapserver requests too many tiles / images from WMS for<br>
the current screen image required - it then re-samples this resulting<br>
in poor quality being served through mapserver (and often with too<br>
much detail for the size returned meaning its still more broken up on<br>
labels etc)<br>
<br></blockquote><div><br>James,<br><br>MapServer resamples the image according to the desired scale (which is not necessarily the same as the scale of the WMS source). You could somewhat increase the quality of the resampling by specifying a more sophisticated algorithm as a layer processing option, for example:<br>
<br>PROCESSING "RESAMPLE=BILINEAR"<br><br><br>By default a larger image is requersted from the data source which may result in a higher amount of tiles to be downloaded. This effect can be controlled by specifying the oversample ratio, for example:<br>
<br>PROCESSING "OVERSAMPLE_RATIO=1"<br><br><br>Best regards,<br><br>Tamas<br><br></div></div><br>