<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">have you tried using image/jpeg? <DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR><DIV><DIV>On Jan 23, 2006, at 8:39 PM, Jennifer Zeisloft wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Thank you for responding, Ed. <BR> <BR> Actually, these raster data sets are displayed as part of Chameleon contexts (so there is no mapfile). I added the USGS orthos to a mapfile to see if the result was any different and it wasn't (the mapfile code for this layer is pasted below in any case).<BR> <BR> The application can be found at <A href="http://maps.aqua.wisc.edu/lscmp/viewmaps.phtml">http://maps.aqua.wisc.edu/lscmp/viewmaps.phtml</A>. The example data sets I am referring to can be found in the Wisconsin: Imagery context.<BR> <BR> I have read through the documentation on rasters in MapServer, as well as searched list archives and have not been able to determine how I would go about specifying low or high -color output. So, perhaps this is part of the problem? <BR> <BR> Again, any suggestions are greatly appreciated!! <BR> <BR> Jennifer Zeisloft<BR> <BR> LAYER<BR> NAME DOQ<BR> STATUS ON<BR> CONNECTIONTYPE WMS<BR> TYPE RASTER<BR> CONNECTION "<A href="http://terraservice.net/ogcmap.ashx">http://terraservice.net/ogcmap.ashx</A>"<BR> PROJECTION<BR> "init=epsg:4326"<BR> END # Projection<BR> METADATA<BR> "wms_srs" "EPSG:4326"<BR> "wms_name" "DOQ"<BR> "wms_title" "USGS Digital Ortho-Quadrangles"<BR> "wms_onlineresource" "<A href="http://terraservice.net/ogcmap.ashx">http://terraservice.net/ogcmap.ashx</A>"<BR> "wms_abstract" "NA - test"<BR> "wms_keywordlist" "NA -test"<BR> "wms_server_version" "1.1.1"<BR> "wms_formatlist" "image/png,image/jpeg,image/wbmp"<BR> "wms_format" "image/png"<BR> END # Metadata<BR> END # layer<BR> <BR><BR><DIV><SPAN class="gmail_quote">On 1/23/06, <B class="gmail_sendername">Ed McNierney</B> <<A href="mailto:ed@topozone.com">ed@topozone.com</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2">Jennifer -</FONT></SPAN></DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2"></FONT></SPAN> </DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2">You don't give us much information to go on, other than your dislike of the results!</FONT></SPAN></DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2"></FONT></SPAN> </DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2">If you're consistently seeing poor-quality results, then there may well be something systematic you're doing in your map files or MapServer configuration. I'm assuming you're using MapServer to generate these "horrible-looking" images. If you are, for example, requesting low-color output from high-color images, you're going to see blotchy output. DRGs are low-color images (only 13 unique colors) so they are not as prone to being affected by a low-color output request.</FONT></SPAN></DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2"></FONT></SPAN> </DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2">Could you provide an example of the map file and configuration you're using to retrieve and display these images? There's nothing special about the WMS interface that inherently limits image quality - you can get a perfect reproduction of the source imagery in many cases.</FONT></SPAN></DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2"></FONT></SPAN> </DIV> <DIV align="left" dir="ltr"><SPAN><FONT color="#0000ff" face="Arial" size="2"> - Ed</FONT></SPAN></DIV> <DIV align="left" dir="ltr"><SPAN><FONT size="2"></FONT></SPAN> </DIV> <DIV align="left" dir="ltr"><SPAN><FONT size="2">Ed McNierney<BR>President and Chief Mapmaker<BR>TopoZone.com / Maps a la carte, Inc.<BR>73 Princeton Street, Suite 305<BR>North Chelmsford, MA 01863<BR>Phone: +1 (978) 251-4242<BR>Fax: +1 (978) 251-1396<BR><A href="mailto:ed@topozone.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ed@topozone.com</A></FONT> </SPAN></DIV><BR> <DIV align="left" dir="ltr" lang="en-us"> <HR> <FONT face="Tahoma" size="2"><B>From:</B> UMN MapServer Users List [mailto:<A href="mailto:MAPSERVER-USERS@LISTS.UMN.EDU" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">MAPSERVER-USERS@LISTS.UMN.EDU</A>] <B>On Behalf Of </B>Jennifer Zeisloft<BR><B>Sent:</B> Monday, January 23, 2006 10:00 PM<BR><B>To:</B> <A href="mailto:MAPSERVER-USERS@LISTS.UMN.EDU" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">MAPSERVER-USERS@LISTS.UMN.EDU</A><BR><B>Subject:</B> [UMN_MAPSERVER-USERS] Horrible Looking WMS Raster Imagery<BR></FONT><BR></DIV><DIV><SPAN class="e" id="q_108fa68fbb989116_1"> <DIV></DIV>Greetings All,<BR><BR>We have been noticing that some (but not all) WMS raster images look pretty terrible (extremely low resolution compared to what they should be) when added to our MapServer application. For instance, from TerraServer (<A href="http://terraservice.net/ogcmap.ashx" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://terraservice.net/ogcmap.ashx</A>), USGS Digital Ortho Quads are virtually useless regardless of scale, while USGS DRGs look decent. Daily MODIS imagery from NASA JPL World Map Service (<SPAN><A href="http://wms.jpl.nasa.gov/wms.cgi?" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://wms.jpl.nasa.gov/wms.cgi?</A>) </SPAN>has also typically been a problem. And there are others... <BR><BR>I have recently been playing with GDAL to display our own rasters, but also partially with the hope that it might somehow magically fix this problem (of course it hasn't). <BR><BR>I am wondering whether the display problem is local or if it is on the data custodian's end, and whether this is typically the case. Is there any way to correct it? If it is at the custodial end, what might be done differently to increase the display resolution for WMS clients (so that we don't make the same mistake)?<BR><BR>I really appreciate any hints or ideas you can offer.<BR><BR>Thanks much!<BR><BR>Jennifer Zeisloft<BR>UW Sea Grant<BR> </SPAN></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>