THREDDS won't do this. (I don't mess with THREDDS, so I am just
parroting what he said.)
If this is correct, then you might want to consider this point when
deciding which way to represent coordinates.
Grace and peace,
Jim
On Tue, Apr 3, 2012 at 1:02 PM, Upendra Dadi <mailt
Hi Andrew,
Either way it should be okay as far as CF compliance is concerned. But
the dimensions - latitude, longitude and time are not really required. If
it is required to indicate that there is only one station(profile) in the
file, there could be a dimension for number of stations instead, w
Hi All,
I am logging in late into this discussion. I am trying to summarize
where the discussion stands as of now. Please correct me if I am wrong
with these statements:
1) Everybody agrees that CF should allow a way of storing geophysical
variable data even when the geophysical coordinate
This might work here since all the scales used have the same units even
though they are measuring different things. But I think, more
generally, for issues like this, a taxonomy or an ontology on top of
standard names might be more useful.
Upendra
On 12/12/2011 1:35 PM, Jonathan Gregory wro
Hi Jonathan & John,
Thank you for the replies. I understand now. I see that there are
complex semantic issues involved here. But the semantic issues should
not become operational bottlenecks. I work at a data center where I do
come across datasets where ambiguities about what the data repres
e-
From: cf-metadata-boun...@cgd.ucar.edu
[mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Steve Emmerson
Sent: 08 December 2011 23:58
To: Upendra Dadi
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] udunits corresponding to Forel-Ule, milliequivalent
Upendra,
> From the perspecti
t the
values be reported compatibly with others.
I am not knowledgeable enough to know the right answer to your two
questions, but the above may be useful input.
John
On Dec 8, 2011, at 08:35, Upendra Dadi wrote:
Hi All,
The standard name table has an entry called
"sea_water_ph_rep
Hi,
I have some data which has "Forel-Ule" for the units used. Is there
a udunits corresponding to this? Also, what should I be using for
milliequivalent ? Thanks for the help.
Upendra
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http:/
Hi,
I have some data which has "Forel-Ule" for the units used. Is there a
udunits corresponding to this? Also, what should I use for
milliequivalent ? Thanks for the help.
Upendra
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.
Hi All,
The standard name table has an entry called
"sea_water_ph_reported_on_total_scale". I have some data which does not
mention the scale used for the measurement of ph. Should there be an
another entry which does not mention the scale? Most of the standard
names I have seen doesn't men
While the first solution is better in the case when several data variables have
the same status flag, the second solution is better when there are several
data variables each of which have a different status flag but same flag_values
and flag_meanings. Can't we have both the solutions?
Upendra
inversion_checks" ;
Of course, flag_definitions is not a CF attribute and the above solution
wouldn't work with CF based software. Is there a way around within the
ambit of CF other than to repeat the flag definitions?
Upendra
On 11/1/2011 11:38 AM, Jonathan Gregory wrote:
D
Didn't realize that this message is from cf-satellite group. The example
that I gave is for in-situ data. But as can be seen, similar issue
arises for in-situ data as well. CCing this to CF-METADATA group.
Upendra
On 11/1/2011 10:47 AM, Upendra Dadi wrote:
The same issue occurs with
Hi All,
I agree with Eizi, using EPSG code is a good idea. High accuracy
conversion from one datum to another is not always a simple mathematical
transformation. For such transformations, one has to "know" the datum
rather than describe using a small set of parameters. In the US, one
example
Hi All,
I am working with CF standard on discrete sampling geometries. In
all the examples in the CF document, there is no mention of grid_mapping
attribute. As I understand, the information stored within grid_mapping
variable has nothing to do with whether the data is gridded or
non-gridde
Thanks John! calendar grammer could be quite useful when representing
climatology bounds. I find it difficult to use udunits for representing
monthly and seasonal climatology bounds. It would definitely be useful
to have it in CF.
Upendra
On 8/17/2011 7:50 PM, John Caron wrote:
In March I p
Also, isn't ancillary variable more a "metadata variable"? I am not
clear what it means to be a "data variable" to begin with?
Upendra
On 8/16/2011 12:12 PM, Jonathan Gregory wrote:
Dear Upendra
Does the spatio temporal coordinates specified for a variable
apply automatically to all the
Hi Jonathan,
Thanks for you reply. Could you please be more specific on what it
means to be applicable? For example, would ancillary variables
containing standard errors or flag values too come under this category?
These variables wouldn't have much meaning without the original
variable. Tha
Hi All,
Does the spatio temporal coordinates specified for a variable apply
automatically to all the ancillary variables as well or do they need to
be specified explicitly for each ancillary variable? Or is it left to
the software to decide? Is there any recommendation here?
Upendra
__
ll
you much does it?
cheers,
Karl
On 8/11/11 9:33 AM, Steve Hankin wrote:
On 8/11/2011 9:14 AM, Upendra Dadi wrote:
Hi,
I have a related question about "bounds" attribute. I often see
regularly gridded latitude-longitude data which do not have "bounds"
specified wh
-time region that is sampled"? If yes, featureType could possibly
be used to resolve the ambiguity. Just my two cents.
Upendra
On 8/11/2011 12:33 PM, Steve Hankin wrote:
On 8/11/2011 9:14 AM, Upendra Dadi wrote:
Hi,
I have a related question about "bounds" attribute. I
Hi,
I have a related question about "bounds" attribute. I often see
regularly gridded latitude-longitude data which do not have "bounds"
specified when probably they should. But they almost always have
regularly spaced latitude and longitude values which are at the middle
of each cell. CF c
Hi Steve & Nan,
Is this allowed in CF? Isn't ancillary_variable meant to be used for
per value metadata i.e. metadata for each and every value in the
variable it is referring to? If so, shouldn't the ancillary_variable
have the same set of dimensions and in the same order as the variable it
I think this is good summary. More comments below:
On 8/4/2011 5:15 AM, Jon Blower wrote:
Hi Jonathan, all,
There is lots of important metadata which is optional, such as standard names
I think the case of a missing datum is different from the case of a missing
standard name. In order to pl
Hi,
- Original Message -
From: "Bentley, Philip"
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 me
> > it boils down to t
or accuracy, this datum should be specified.
Upendra
On 7/28/2011 11:34 AM, Upendra Dadi wrote:
I have heard this argument before- datum need not be provided for
datasets which are too imprecise. The usual assumption: "Choosing a
wrong datum doesn't change anything. So, lets not spe
I have heard this argument before- datum need not be provided for
datasets which are too imprecise. The usual assumption: "Choosing a
wrong datum doesn't change anything. So, lets not specify datum even
though I have the datum. Lets leave it for the user to choose the datum,
even though I know
Hi Folks,
I am trying to better understand CF model and its relationship with
netCDF-classic data model. Is there even a relationship? If I am
creating a netCDF file using CF conventions, does the file have to be
using classic data model? If I am using netCDF4 with strings and no
other featu
Hi folks,
Can someone please let me know when Discrete Sampling Geometries
(https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions) be
part of CF officially ? Is this chapter going to be added to CF
eventually? Or is this page defunct? I don't see any mention of
CF:featureType in the
Hi,
Does CF allow add_offset for time dimension? How about X and Y dimesions?
Upendra
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Hello,
I have a couple of variables which do not seem to have appropriate
standard names. I want to have standard names for these variables added
in the standard name table. The variables are dissolved oxygen, Apparent
Oxygen Utilization and Oxygen Saturation(
ftp://ftp.nodc.noaa.gov/pub/WOA0
Hello,
This is in regard to the units corresponding to the standard name
sea_water_salinity. We here at NODC use PSS, which is unitless, for
Salinity. PSU is not a good way to represent salinity and shouldn't be
used. The units for sea_water_salinity should be changed to PSS in the
standard n
I agree with Nan. With ACDD it could sometimes be difficult to get feedback on
the issues you have. We have had similar issues as those mentioned by Nan. Some
attributes are ambiguous. Also, I found some minor conflicts with CF
conventions. To give an example, CF requires the grid_mapping attrib
Discovery metadata, as Ken pointed out, allows automated population of
catalogs. The importance of catalogs has not caught on yet. I see data analysis
as consisting of these steps among others:- 1) Search for required data 2)
Download the data 3) Analyze the data.
NetCDF, CF-conventions and THR
Hello,
I am trying to create a CF compliant NetCDF containing climatological
statistics. The data consists of monthly means of a certain parameter
which is calculated from data which starts on 1773-1-13 and ends on
2001-6-29. How do I represent this information using climatology
variable ? The
Hi,
Can anyone in this group please point me to an authoritative website
showing CF conventions for point data, specifically trajectories? I have
been googling for the right web page, but came across couple of
documents which have different attribute names for defining point
features. For exa
ng or semi_major_axis and semi_minor_axis. I
think longitude_of_prime_meridian is in there too. The other
grid_mapping tags are for projected coordinate systems.
-Kyle
On Wed, Mar 3, 2010 at 12:21 PM, Upendra Dadi <mailto:upendra.d...@noaa.gov>> wrote:
Hi,
I am new to CF convention
Hi,
I am new to CF convention. I am looking at how to incorporate
coordinate system information in the netcdf file. Referring to the CF
documentation, I found that there are parameters like grid_mapping_name,
semi_major_axis, longitude_of_prime_meridian, etc to describe the
coordinate system.
38 matches
Mail list logo
