Hi John,
Will do, thanks!
(I have been testing out subsetting via the TDS for the ESG
folks upstairs from me, and I thought they had submitted a
bug report, but it sounds like it hasn't happened yet. I'll write
up what I've got and send it to you off-list.)
Cheers,
--Seth
On Wed, 28 Aug 2013
Hi,
Here at the British Oceanographic Data Centre we use THREDDS to deliver and
subset our numerical model data that we hold in CF netcdf format. I've just
been made aware that during the delivery and subsetting process, THREDDS seems
to be converting the CF files we hold from whatever CF
Hi Sean:
What feature of CF are you using that you need to preserve the version?
John
If you torture data long enough, it will confess.
-- Economist Ronald Coase
On 8/28/2013 3:28 AM, Gaffney, Sean P. wrote:
Hi,
Here at the British Oceanographic Data Centre we use THREDDS to deliver
and
It isn't just about feature presentation, right? On the assumption that the
latest version is always most current (so everyone will use the latest version
if they can), I use the version as a proxy for how
current/up-to-date/sophisticated the data provider is.
It also gives me a clue about
Hi Sean,
Personally, I would regard that as suspect behavior.
I'm of the opinion that it's best practice for a data service to
affect the data it operates on in very targeted and transparent
way, and that it should pass everything else through untouched.
If it doesn't do that, it's harder to
Hi John and all:
For sure its a good idea to preserve the CF Conventions attribute if it
exists. I will add that to our issue tracker.
Remember that THREDDS is a general purpose subsetter, not specific to
CF. So we deal with lots of source datasets (eg GRIB) that arent CF. The
point is that
Hi Seth:
On 8/28/2013 12:59 PM, Seth McGinnis wrote:
Hi Sean,
Personally, I would regard that as suspect behavior.
I'm of the opinion that it's best practice for a data service to
affect the data it operates on in very targeted and transparent
way, and that it should pass everything else
