On 8/3/2011 8:19 AM, Jon Blower wrote:
Hi all,
I've been following this thread with great interest. For me it boils down to
this question:
- Is the datum always known by the data provider?
If the answer is yes then I see no reason to omit the datum (and plenty of
reasons to include it).
Hi all,
I am new on this mailing list and I hope my question is not so obvious
My problem is with:
At the adress :
http://cf-pcmdi.llnl.gov/conformance/requirements-and-recommendations/1.5/ I
find
« 2.1 Filename
Requirements:
* Filename must have .nc suffix.
But If I read
Correction to the datum/ellipsoid explanation below.
The NAD83 datum does use the GRS80 ellipsoid. The NAD27 datum uses the Clarke
1866 ellipsoid. Woops!
Dave
On Aug 3, 2011, at 9:07 AM, David Blodgett wrote:
Dear Phil,
I would have thought that if a particular piece of
data analysis is
Bonjour Alain,
Being new to the world of meteorological/oceangraphic data myself
recently, I had the same problem you have when reading the various
conventions available. Based upon discussions about this matter, and how
others are using and interpretating the conventions, I personally have
OK, so this is a use case for an unknown (as opposed to a deliberately
unspecified) datum I guess?
Almost certainly, but by a comparatively small number of individuals within
an organisation I would guess.
All the more reason to encourage people to encode it in NetCDF files! ;-)
Jon
Alain,
Further to my earlier comment, and to address your question regarding
file name suffix, my company makes data available via THREDDS and ERDDAP
neither of which I have found has any problem using files that do not
have a .nc suffix. When editing the metadata for files to be published
via
Glenn
Thanks for your comments. The nc suffix was an example, but I found other cases
in the documentation.
I found a lot of differences between the convention and the list of
requirements and recommendations.
My work is to highlight the differences between a netcdf file (bathymetric
data)
Hi,
- Original Message -
From: Bentley, Philip philip.bent...@metoffice.gov.uk
Date: Wednesday, August 3, 2011 11:17 am
Subject: Re: [CF-metadata] the need to store lat/lon coordinates in a
CF-compliant netCDF file
Hi Jon,
I've been following this thread with great interest. For