Glancing at my local copy of the cf-checker code, I believe it is
case-sensitive, yes.
As it ought to be: the spec lists valid values for axis as capital letters and
uses the markup that indicates an exact term.
--Seth
On Fri, 23 Jul 2010 12:55:04 -0600
John Caron wrote:
>the units appear
the units appear ok. is the CF checker case sensitive on the "t" ?
On 7/23/2010 12:27 PM, Karl Taylor wrote:
Stephane,
axis="T" is correct. I'm guessing, the units on your time coordinate
aren't recognized by udunits.
Karl
On 7/23/10 11:02 AM, Stephane Poirier wrote:
Hi All,
I am trying t
Stephane,
axis="T" is correct. I'm guessing, the units on your time coordinate
aren't recognized by udunits.
Karl
On 7/23/10 11:02 AM, Stephane Poirier wrote:
Hi All,
I am trying to have our netCDF files comply to CF-1.0 convention.
CF-Convention compliance checker for NetCDF format
(http:
Hi All,
I am trying to have our netCDF files comply to CF-1.0 convention.
CF-Convention compliance checker for NetCDF format
(http://titania.badc.rl.ac.uk/cgi-bin/cf-checker.pl) returns the following
error when checking my netCDF file's "time" variable: ERROR (4): axis attribute
inconsistent w
Cristina,
My understanding of the conventions is that your standard names would become:
CHL: "mass_concentration_of_chlorophyll_in_sea_water"
CHL_error: "mass_concentration_of_chlorophyll_in_sea_water standard_error"
CHL_count: "mass_concentration_of_chlorophyll_in_sea_water
number_of_observation
Dear Jonathan, and all,
I need to creat a netcdf with 3 variable.
CHL: chloropyll(nx,ny)
CHL_error: the standard deviation (nx,ny)
Chl_count: aNumer of Observation (nx,ny)
Following the section 3.4 of the CF standard, I undestood that
- for standard deviation variable I must set its stand
