Hi Davie :
Yes, Rich is correct, and Im surprised that 3.17 worked..
Send me some sample files if you havent got this solved.
Richard Signell wrote:
Roy & Dave,
I'm sure that John Caron will comment ono what changed, but doesn't
stuff in time aggregations need to understand time? So one way to
fix it would be to add:
<dimension name="ocean_time" orgName="time"/>
to your aggregation to rename your dimension "time" => "ocean_time".
So for example your aggregation would look like:
<aggregation dimName="ocean_time" type="joinExisting">
<dimension name="ocean_time" orgName="time"/>
<scan
location="/home/om/dods-data/thredds/roms/eac/102/avg/"
suffix=".nc" />
</aggregation>
-Rich
On Fri, Oct 16, 2009 at 10:47 AM, Roy Mendelssohn
<Roy.Mendelssohn@xxxxxxxx> wrote:
Thought this might be a better place to field this question.
-Roy
Begin forwarded message:
From: Davie Robertson <rjdave@xxxxxxxxx>
Date: October 16, 2009 6:25:26 AM PDT
To: IOOS Model Data Interoperability Working Group
<ioos_model_data_interop@xxxxxxxxxxxxxxxx>
Subject: working aggregation breaks with upgrade to TDS 4.X
Reply-To: ioos_model_data_interop@xxxxxxxxxxxxxxxx
Hi all,
I want to upgrade my TDS to 4.1 so I can serve compressed netcdf 4
files. I have tested it and it works great! However the upgrade to 4.1
breaks a couple of my aggregated datasets. The problem occurs when my
aggregating variable and it's dimension have different names. For
example my working dataset uses ocean_time(ocean_time) but the broken
ones use ocean_time(time). 3.17 works fine for either case but 4.1
(and probably 4.0) crap out with:
Error {
code = 500;
message = "AggregationExisting: no coordinate variable for agg
dimension=time";
};
The relevant section of my catalog is:
<dataset name="Averages"
ID="eac_301_averages"
urlPath="roms/eac/301/avg" >
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/
ncml-2.2">
<aggregation dimName="ocean_time" type="joinExisting">
<scan
location="/home/om/dods-data/thredds/roms/eac/301/avg/"
suffix=".nc" />
</aggregation>
</netcdf>
</dataset>
Any ideas? The earlier runs with ocean_time(ocean_time) are fine on
4.1 and 3.17.
Thanks,
David Robertson
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"IOOS Model Data Interoperability Working Group" group.
To post to this group, send email to
ioos_model_data_interop@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
ioos_model_data_interop+unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/ioos_model_data_interop?hl=en
-~----------~----~----~----~------~----~------~--~---
**********************
"The contents of this message do not reflect any position of the U.S.
Government or NOAA."
**********************
Roy Mendelssohn
Supervisory Operations Research Analyst
NOAA/NMFS
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)
voice: (831)-648-9029
fax: (831)-648-8440
www: http://www.pfeg.noaa.gov/
"Old age and treachery will overcome youth and skill."
"From those who have been given much, much will be expected"
_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
