The Geotiffs have displayed correctly in a number of programs and
they appear to be correct. We may be the first testing this on
aggregated datasets. I was using curl and constrained http's to try
and download files, and I also was having problems with the netcdf,
but I can never be too sure because I am not that certain of the
syntax.
Can the IDL WCS add-on produce the http request it is sending to the
server, and capture any errors? I want to get a look at them to see
what might be happening. Also, I will be seeing John (Caron) at
Livermore, and if I have more information I might be able to sit down
with him and try to figure out where the problem is if it persists
(i.e. in our setup or in the TDS). Either way, we are pretty close.
Also we have IDL, what does one need to do to get the add-on?
-Roy
At 8:57 PM -0600 6/12/06, Ben Domenico wrote:
Hi Roy,
With the RSI IDL wcs add on, I've tried 4 of your "aggregated"
datasets and all of them returned a geoTIFF without an error
message. A couple returned geoTIFFfloat, but a couple others time
out. I am unable to access any of the coverages in netCDF form via
IDL WCS client. All such attempts return an error message of one
sort or another. I haven't done this very systematically yet, so I
haven't kept track of the error messages, etc.
Are any of these more "important" than others or easier to visualize
and interpret? I have no way to evaluate whether the coverages that
do come across make any sense. A handful of "use cases" and
expected displays would help in the checkout process.
As to where to publish your WCS server, I need to give that a bit
more thought. I was attempting to shift from the GALEON wiki which
worked pretty well last year to the GALEON OGCnetwork this year.
But I'm not sure the OGCnetwork approach works well for community
contributions.
<http://www.ogcnetwork.net/galeon>http://www.ogcnetwork.net/galeon
Maybe some of the others have suggestions for how to use the
OGCnetwork in this fashion.
-- Ben
