Sorry I didn't see this before my earlier message, but I think I just
now found the right logfile (threddsServlet.log) with an error message
about the 365-day calendar on my TDS instance. But, if this failure is
due to a problem with that calendar in WMS, how is it that WMS is
working on the NCAR GIS implementation of TDS for that same netCDF
dataset? I thought it was GODIVA that had the calendar issue.
On Wed, Apr 18, 2012 at 10:24 AM, Ben Domenico <address@hidden
I just put that attached file into my demo TDS and I have the same
problem I had with the other climate datasets. The other demo
datasets (including the ones I got from motherlode) work fine with
WMS on my demo server and that tas dataset works fine with the other
services (OPeNDAP, WCS, NCSS) but I can't get at your tas dataset
via the WMS server on my demo system. I get a 500 code "internal
server error" so I must have my WMS configured in some way that
makes it fail for that particular tas dataset.
I'll send this along to the THREDDS support group with your sample
file and my thredds configuration file attached to see if they can
figure out what's wrong. The WMS service seems to work fine on
your TDS server for that sort of dataset.
---------- Forwarded message ----------
To: Ben Domenico <address@hidden
Here is a file I just got with a WCS and I think the following
parameters should work to display it.
On 4/17/2012 12:05 PM, Ben Domenico wrote:
Indeed your WMS works fine. Now I need to figure out why it
work on my demo machine with the netcdf I downloaded from your
The other services work fine for that dataset on my machine and the
other demo datasets work fine with all the services on my demo
It's just WMS for that particular dataset on my server that fails.
On Tue, Apr 17, 2012 at 11:17 AM, Jennifer Boehnert
I wrote up directions on accessing our WMS and WCS. There
links which you can use to see how our WMS is structured.
National Center of Atmospheric Research
PO Box 3000
Boulder, CO, 80307