[WMS] Problems with terraservice DOQ layer

[dmorissette]

Subject:         [mapserver-users] WMS layer is blank
   Date:         Mon, 18 Nov 2002 14:51:32 -0800
   From:         Dylan Keon <keon@nacse.org>
     To:         mapserver-users@lists.gis.umn.edu

Hi listers,

I'm trying to display a WMS layer (Terraserver DOQ) in a simple 
interface.  I've tried everything I can think of to get it to display, 
but just get a blank image.  The extent and epsg codes are correct.  The 
other layer in the mapfile (a shapefile) appears, but not the WMS layer.

I compiled MapServer with --enable-debug...the WMS request URL printed 
to the server log is good.  I can copy that URL to a browser and the 
correct DOQ image appears.  The mapfile is below.  Thanks for any help.

Dylan


################### mapfile ######################
NAME "wms_test"
SIZE 600 400
STATUS ON
EXTENT 371000 5250000 492000 5353000 #minx miny maxx maxy
UNITS METERS
SHAPEPATH "/tmp/gis"
IMAGETYPE PNG

PROJECTION
   "init=epsg:26910" #NAD83 UTM zone 10N
END

WEB
   IMAGEPATH "/www/temp/"
   IMAGEURL "/temp/"
END

LAYER
   NAME ONP_boundary
   TYPE POLYGON
   STATUS DEFAULT
   DATA onp_bnd
   TRANSPARENCY 50
   CLASS
     NAME "ONP boundary"
     OUTLINECOLOR 0 0 0
     COLOR 243 248 245
   END
END

LAYER
   NAME ortho
   METADATA
     "wms_title" "USGS Digital Ortho-Quadrangles"
     "wms_srs"   "EPSG:26910"
   END
   STATUS DEFAULT
   TYPE RASTER
   MINSCALE 1000
   MAXSCALE 200000
   CONNECTIONTYPE WMS
   CONNECTION 
"http://terraservice.net/ogcmap.ashx?
VERSION=1.1.1&SERVICE=wms&LAYERS=DOQ&FORMAT=png&styles="
   PROJECTION
     "init=epsg:26910" #NAD83 UTM zone 10N
   END
END

END
#########################################

[dmorissette]

Unfortunately it's not the first time we have problems with the terraservice 
WMS.  I thought we had resolved all previous issues so this is a new problem.  I 
did some quick tests and after editing the mapfile a little to work on my system 
(and disable minscale/maxscale) I do indeed get a blank map with MapServer 3.6.  

However MapServer 3.7 with the latest fixes from bug 214 does display 
something... well, just the USGS logo since at the scale at which I'm working 
(default extents in the mapfile) even the map that's downloaded is empty except 
for the logo.


Could we get a set of extents at which we should see some data with this WMS 
layer?

[fwarmerdam]

Daniel, 

I found the returned file was an RGB JPEG file, and the built-in jpeg
support will fall over on that.  I didn't see any such error reported, but
I am not sure that errors are always getting propagated out properly.

So, I would encourage you to check if it is going through drawJPEG or drawGDAL.

[dmorissette]

Dylan Keon wrote:
> 
> I successfully compiled the latest 3.7 CVS version (thanks Frank,
> Assefa, and Daniel), and can report that this version is able to display
> WMS layers retrieved from terraservice.
> 
> However, now I seem to be running into the 24-bit vs 8-bit problem (I
> think).  The DOQ image retrieved directly into the browser looks great,
> but the image retrieved and rendered by MapServer looks pretty bad.
> Please have a look at http://www.nacse.org/~keon/temp/wms to see what I
> mean.  Ignoring the issues about 24-bit file size vs. 8-bit, etc. for
> the moment, any suggestions on how to get the good-looking image in my
> interface? :-)  I'm using gd 1.8.4, would switching to 2.0.7 help?
> 

[dmorissette]

I looked at your test page and it looks like the problem is a color resampling 
issue and upgrading to GD 2.x should help.  Frank may be able to comment more on 
what is happening exactly.

BTW for the record, I copied here the terraservice URL from your test page with 
valid extents to test this:
http://terraservice.net/ogcmap.ashx?
VERSION=1.1.1&SERVICE=wms&LAYERS=DOQ&FORMAT=png&styles=&REQUEST=GetMap&WIDTH=480
&HEIGHT=320&SRS=EPSG:26910&BBOX=475896.477051,5303707.861328,478310.148926,53053
17.236328&EXCEPTIONS=application/vnd.ogc.se_inimage

[fwarmerdam]

Daniel, 

Is this still considered outstanding?  Do you need feedback from Dylan?

[keon@…]

Upgrading to 3.7 fixed the problem I was having.  If I can provide any other
feedback, let me know.  Otherwise, I don't see any reason to keep this bug open.

[dmorissette]

Marking as fixed since Dylan confirmed that things work fine in 3.7 with GD 2.