I found WCS GetCapabilities and DescribeCoverage requests were working
but GetCoverage was returning a 404 error with blank message because the
default wcs cachepath in my threddsconfig was not a valid path. Remming
out the default path eg. '/data/tmp/thredds/wcsCache/' or setting a
valid path fixed it.
[mailto:thredds-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Roy Mendelssohn
Sent: Friday, 19 October 2007 2:46 AM
To: John Caron
Subject: Re: [thredds] THREDDS & WCS
I am having problems with WCS as we are testing 3.16.19. We made the
changes in the thredds config file, so the service is running, and I
get a return on the getcapabilities request, but it doesn't contain
the coverage itself and therefore all other requests break down. Has
the info that needs to be in the catalog.xml changed. It would seem
so if I compare:
It is unclear on the last page which that info is required.
On Oct 8, 2007, at 4:48 PM, John Caron wrote:
> My apologies, this was poorly documented.
> WCS is turned off by default for security reasons, and must be
> turned on in the threddsConfig.xml file:
> <scour>15 min</scour>
> <maxAge>30 min</maxAge>
> This page has been updated now:
> which references:
> Rochelle.O'Hagan@xxxxxxxx wrote:
>> Hi John,
>> I had set up the catalog differently. I have now changed it to
>> what you
>> advised, but still get the "The requested resource () is not
>> I can get coverages back from motherlode.ucar.edu, but not from the
>> server I set up for testing. Is this likely to be something wrong
>> my setup of the server? Does the WCS part of the THREDDS server
>> the netCDF subset service, OpenDAP server or nj22? I notice that the
>> <nj22Config> element is commented out in the threddsConfig.xml file.
>> Thanks for your help,
>> Rochelle O'Hagan
>> -----Original Message-----
>> From: John Caron [mailto:caron@xxxxxxxxxxxxxxxx]
>> Sent: Wednesday, 3 October 2007 2:52 AM
>> To: O'Hagan, Rochelle (CLW, Black Mountain)
>> Cc: thredds@xxxxxxxxxxxxxxxx
>> Subject: Re: [thredds] THREDDS & WCS
>> Hi Rochelle:
>> Rochelle.O'Hagan@xxxxxxxx wrote:
>>> Hi All,
>>> I'm just starting to use THREDDS (v3.16) and am having problems
>>> the WCS functionality. I can make GetCapabilities & DescribeCoverage
>>> requests successfully, but can't get GetCoverage to work at all.
>>> I've tried with the example data (testData & wcsExample) and with a
>>> catalog I've set up myself, but always get back a message "The
>>> resource () is not available."
>>> I'm new to all this sort of thing, so is there something I'm
>>> The GetCoverage request is below:
>> where did you get that URL?
>> im guessing it should be:
>> http://localhost:8080/thredds/wcs/galeon/testdata/ocean.nc? etc
> thredds mailing list
> For list information or to unsubscribe, visit: http://
"The contents of this message do not reflect any position of the U.S.
Government or NOAA."
Supervisory Operations Research Analyst
Environmental Research Division
Southwest Fisheries Science Center
1352 Lighthouse Avenue
Pacific Grove, CA 93950-2097
e-mail: Roy.Mendelssohn@xxxxxxxx (Note new e-mail address)
"Old age and treachery will overcome youth and skill."
thredds mailing list
For list information or to unsubscribe, visit: