Re: [thredds] 4.2 WMS troubles

• To: thredds@xxxxxxxxxxxxxxxx
• Subject: Re: [thredds] 4.2 WMS troubles
• From: Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
• Date: Tue, 23 Nov 2010 16:44:16 -0700

Hi Mike, Phil,

On 11/23/2010 2:10 PM, Mike Grogan wrote:
> John and All,
> 
> We are seeing some WMS issues moving from 4.1 to 4.2.  Specifically:
> 
> 1.  A black image (no data I assume) is being returned for the entire
> spatial domain of our datasets.

I'm guessing this has to do with the change in the way the WMS code
determines the default color scale range. Basically, the default range
for all data is -50,50 though that can be configured [1] and there are
extensions to the standard that allow specifying a range in a request
[2]. (There was a good discussion about the reasons for this change on
this email list back in Sept [3].)

[1]
http://www.resc.reading.ac.uk/trac/myocean-tools/wiki/WmsDetailedConfiguration

[2] http://www.resc.rdg.ac.uk/trac/ncWMS/wiki/WmsExtensions (see the
COLORSCALERANGE parameter)

[3]
http://www.unidata.ucar.edu/mailing_lists/archives/thredds/2010/thread.html#00293

> 2.  There are way significantly fewer available projections in
> GetCapabilities for 4.2 versus 4.1  (as in 6 versus several hundred in 4.1)

Yes. In 4.1, the list basically included all the CRS available from the
geotoolkit package. It felt like a bit of overkill. The list has been
trimmed down and we are looking at making it configurable.

> 3.  GetLegendGraphic requests yield HTTP 500 errors - Internal Server Error

Can you look in your threddsServlog.log files and see if you are getting
any error message?

Hope that helps,

Ethan

> 4.  Interestingly, GetFeatureInfo requests seem to work fine ...
> returning data for a particular point properly.
> 
> Any thoughts on where we might have gone wrong?
> 
> - Mike Grogan and Phil Cogbill
> 

• Follow-Ups:
  • Re: [thredds] 4.2 WMS troubles
    • From: Mike Grogan

• References:
  • [thredds] 4.2 WMS troubles
    • From: Mike Grogan