Because of the aggregation and because we have the data defined in
4-dimensions and because our vertical is defined at .0 rather than at
0, not all clients might work. I just sort of clutzed my way through
by trial and error to the following URL:
http://oceanwatch.pfeg.noaa.gov:8081/thredds/wcs/satellite/AG/ssta/14day?request=GetCoverage&version=1.0.0&service=WCS&format=NetCDF3&coverage=AGssta&Vertical=.0&time06-01-09T23:59:59Z&bbox=230,20,240,40
Below is the total output (including ncdump -h on the output) - I
don't know if all the files work, but this one sure does and shows
the information it took to get the file given the Coverage
description. It takes me forever to get these correct as I don't
know what I am doing, but if anyone else is wiling to test also I
sure would appreciate it.
-Roy
[homework:~/desktop] rmendels% curl -o test.nc
'http://oceanwatch.pfeg.noaa.gov:8081/thredds/wcs/satellite/AG/ssta/14day?request=GetCoverage&version=1.0.0&service=WCS&format=NetCDF3&coverage=AGssta&Vertical=.0&time06-01-09T23:59:59Z&bbox=230,20,240,40'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 84008 100 84008 0 0 61800 0 0:00:01 0:00:01 --:--:-- 152k
[homework:~/desktop] rmendels% ncdump -h test.nc
netcdf test {
dimensions:
time = 1 ;
altitude = 1 ;
lat = 201 ;
lon = 101 ;
variables:
float AGssta(time, altitude, lat, lon) ;
AGssta:long_name = "SST 11 km" ;
AGssta:standard_name = "sea_surface_temperature" ;
AGssta:units = "degree_C" ;
AGssta:_FillValue = -1.e+32f ;
AGssta:missing_value = -1.e+32f ;
AGssta:numberOfObservations = 2322138 ;
AGssta:actual_range = -1.9f, 33.8f ;
AGssta:coordsys = "geographic" ;
AGssta:fraction_digits = 1 ;
double time(time) ;
time:long_name = "End Time" ;
time:standard_name = "time" ;
time:units = "seconds since 1970-01-01T00:00:00Z" ;
time:actual_range = 1150070399., 1150070399. ;
time:_CoordinateAxisType = "Time" ;
float altitude(altitude) ;
altitude:long_name = "Altitude" ;
altitude:standard_name = "altitude" ;
altitude:units = "m" ;
altitude:actual_range = 0.f, 0.f ;
altitude:_CoordinateAxisType = "Height" ;
float lat(lat) ;
lat:long_name = "Latitude" ;
lat:standard_name = "latitude" ;
lat:units = "degrees_north" ;
lat:point_spacing = "even" ;
lat:actual_range = -75.f, 75.f ;
lat:coordsys = "geographic" ;
lat:fraction_digits = 1 ;
lat:_CoordinateAxisType = "Lat" ;
float lon(lon) ;
lon:long_name = "Longitude" ;
lon:standard_name = "longitude" ;
lon:units = "degrees_east" ;
lon:point_spacing = "even" ;
lon:actual_range = 0.f, 360.f ;
lon:coordsys = "geographic" ;
lon:fraction_digits = 1 ;
lon:_CoordinateAxisType = "Lon" ;
// global attributes:
:History = "GeoGrid extracted from dataset null" ;
:Convention = "_Coordinates" ;
}
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
