[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: [GSN] Updated TIE matrix



Yes, Ethan is right, its a bug in the TDS when the number of vert coords < 3. 
Ill have it fixed in the next release.

Ethan Davis wrote:
Hi Dan, Rudolf,

I'm not sure why there are no coverages for these datasets. I don't think it has to do with the variable metadata (it seems to have everything it might need) and the lat/lon information seems fine. I'm going to guess it is because these variables have a vertical dimension, even though with just one point.

Here's the same dataset on our server via WCS:

http://motherlode.ucar.edu:8080/thredds/wcs/global/testdata/GFS_Global_0p5deg_20060427_0600.grib2?request=GetCapabilities&version=1.0.0&service=WCS


and via OPeNDAP (this is the data description info):

http://motherlode.ucar.edu:8080/thredds/dodsC/model/NCEP/GFS/Global_0p5deg/GFS_Global_0p5deg_20060427_0600.grib2.dds


It looks like only those variables that don't have vertical dimensions are being shown in WCS.


John is out till Wednesday but I'll take a look at the code to double check this (probably not till tomorrow).

Dan, if it makes sense, you might want to try creating one of these without the vertical dimension to see if that works.

Ethan

dan.swank wrote:

Folks,
I have not dealt with this before.
I need some guidance here. Can you please provide an example of what
one of these should look like in order for your application to utilize it?


Ethan:  where would I begin to add this infomation?  in the catalog.xml
or in the NetCDF file metadata?  A Pointer to any docs would also help.

As another note, I've created a global dataset as mentioned in the
telecon this morning @:
http://eclipse.ncdc.noaa.gov:9090/thredds/catalog.html?cmd=subset&catalog=http://eclipse.ncdc.noaa.gov:9090/thredds/gfsmon/catalog.xml&dataset=gfsmon/globaldomain.nc



-Dan


Rudolf Husar wrote the following on 4/27/2006 4:30 PM:


Hi Ethan,
FYI, the WCS getCapbilities doc looks good but it is empty. It has no
coverages listed.
http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS


<http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS>

R


On 4/26/06, *Ethan Davis* <address@hidden
<mailto:address@hidden>> wrote:


    Hi Dan,

    Both the OPeNDAP and WCS URLs are working for me now.

I looked at the OPeNDAP URL
(http://eclipse.ncdc.noaa.gov:9090/thredds/dodsC/gfsmon/largedomain.nc)
in the netCDF-java ToolsUI and could visualize the data just fine.


Don't have a WCS client but tried the WCS URL
(http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS


<http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS>)

    in a browser and got back a valid looking WCS_Capabilities document.

    Ethan





dan.swank wrote:
> Ethan:
>
> I've corrected this.
> OpENDAP now works, WCS gives:
>
> <ServiceExceptionReport version='1.2.0'>
> <ServiceException code='MissingParameterValue'>
> REQUEST parameter missing
> </ServiceException>
> </ServiceExceptionReport>
>
> This is a bit concerning & I'm not sure what to do about it.
> What "Missing parameter Value" is it looking for?
>
> -Dan
>
>
> Ethan Davis wrote the following on 4/26/2006 5:52 PM:
>
>> Hi Dan,
>>
>> Not sure if you got my last email (or if I actually sent it for that
>> matter, oops) ...
>>
>> I'm still having trouble getting largedomain.nc
<http://largedomain.nc> (and smalldomain.nc <http://smalldomain.nc>)
>> through your TDS. Here's what I get from a WCS request:
>>
>>
http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS


<http://eclipse.ncdc.noaa.gov:9090/thredds/wcs/gfsmon/largedomain.nc?REQUEST=GetCapabilities&version=1.0.0&service=WCS>

>>
>>
>> <ServiceExceptionReport version='1.2.0'>
>> <ServiceException code='Invalid Dataset'>
>> /raid/ftp/raid1b/geo-idelargedomain.nc <http://idelargedomain.nc>
(No such file or directory)
>> </ServiceException>
>> </ServiceExceptionReport>
>>
>> And something similar for an OPeNDAP request:
>>
>>
http://eclipse.ncdc.noaa.gov:9090/thredds/dodsC/gfsmon/largedomain.nc.html


>>
>> /raid/ftp/raid1b/geo- idelargedomain.nc
<http://idelargedomain.nc> (No such file or directory)
>>
>> Looks like I steered you wrong in the value of the location
attribute in
>> the datasetScan element. It should end with a slash ("/"). So,
>> "/raid/ftp/raid1b/geo-ide/" instead of
"/raid/ftp/raid1b/geo-ide". Sorry
>> about that, I thought our TDS code would deal with it either way but
>> evidently not.
>>
>> Ethan
>>
>> dan.swank wrote:
>>
>>
>>> Rudolf Husar wrote the following on 4/26/2006 2:33 PM:
>>>
>>>
>>>
>>>> Hi Dan,
>>>>
>>>> OK, moving along nicely, step-by step.
>>>>
>>>> - The average monthly wind data on your server,
largedomain.nc <http://largedomain.nc>
>>>> <http://largedomain.nc> is fine
>>>> - We have now connected the wind vector rendering to your
data,rather
>>>> than to the netCDF file on our server.
>>>> http://webapps.datafed.net/datafed.aspx?dataset_abbr=NCDC_AVG_WIND
>>>>
http://capita.wustl.edu/capita/researchareas/GSN/WMS_DataLayers/NCDC_Wind/NCDC_Wind2.gif


>>>>
>>>>
>>>>
>>> This is great stuff!
>>>
>>>
>>>
>>>> - This is really good news since we are (half way?) to WCS
access to
>>>> the archived model data..
>>>> - There are a few minor issues re full compliance with
netCDF-CF;
>>>> will pass on the list in a bit
>>>>
>>>>
>>> Awaiting these suggestions.
>>>
>>>
>>>
>>>>
>>>> Dan, any chance to run off the same wind aggregation for the
entire
>>>> globe and make another netCDF? For the Beijing demo, they are
looking at
>>>> fine resolution wind data for the wind farm siting demo. The
global wind
>>>> data from the 1 deg NCEP could be used for the 'Prospecting'
part of
>>>> their demo: where in the world are good spots for wind farms. This
>>>> expansion of the domain would also provide a link between the
regional
>>>> China demo and the regional-global orientation of GSN (George,
what do
>>>> you think?)
>>>> Jinsoo, is this correct? Could you use the global wind data for the
>>>> Prospecting part of the demo?
>>>>
>>>>
>>>>
>>> I've attempted to run this with the NCEP-DOE reanalysis 2
(Global ~2°
>>> data for 25 years), but noticed this was on a guassian
grid. You guys
>>> mentioned WCS needs consistant lat/lon grids. So I guess this
option is
>>> out. If so I can fall back on the GFS.
>>>
>>> -Dan
>>>
>>>
>>>
>>>
>>>> Regards, Rudy
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 4/25/06, *dan.swank* <address@hidden
<mailto:address@hidden> <mailto: address@hidden
<mailto:address@hidden>>>
>>>> wrote:
>>>>
>>>> All ,
>>>> Heres the status on our front.
>>>> I've already parsed the original ASCII file I released
yesterday
>>>> into a
>>>> valid NetCDF
>>>> http://nomads.ncdc.noaa.gov/tmp/largedomain.nc
>>>> http://nomads.ncdc.noaa.gov/tmp/smalldomain.nc
>>>> <http://nomads.ncdc.noaa.gov/tmp/smalldomain.nc
<http://nomads.ncdc.noaa.gov/tmp/smalldomain.nc>>
>>>>
>>>> I'm in the process now of getting them on TDS/w WCS service.
>>>> Something
>>>> I'm not experienced with, but doesn't not seem particularly
>>>> difficult.
>>>> Thursday seem slike a realistic deadline to have this, but feel
>>>> free to
>>>> work in parallel just in case.
>>>>
>>>> -Dan
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>


--
Ethan R. Davis Telephone: (303) 497-8155
Software Engineer Fax: (303) 497-8690
UCAR Unidata Program Center E-mail: address@hidden <mailto:address@hidden>
P.O. Box 3000
Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
---------------------------------------------------------------------------







--
Professor of Mechanical Engineering, Director
CAPITA, Washington University
St. Louis, MO 63130
1 Brookings Drive, Box 1124
314 935 6099






NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.