I have been considering Bryan's point some more:
The only reason I can see here, and it seems to be the one you are espousing,
is that it's a convenience for someone importing their data - they want the
standard name to be the name they used to use - but why? It's rarely the
case, so why
The CF Specification
(http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/ch04s02.html) states:
'Optionally, the longitude type may be indicated additionally by providing the
standard_name attribute with the value longitude, and/or the axis attribute
with the value X.'
Which suggests that
Dear Mark
I see your point of view, and when we discussed this on the phone it did not
sound like a large issue to me. I agree with you that X/Y and lon/lat are
related ideas in CF. However, it appears there are some concerns.
As you say, as a data-producer, where the vector component is aligned
Hi Mark and all -
I think this is a perfectly reasonable proposal.
Actually, I think the current wording,
x indicates a vector component along the grid x-axis, when this is
not true longitude'
is not intended to prohibit the use of x/y terms in cases when x y are
lon lat, it's there as a
Dear Nan
I can't remember a reason why coordinate variables should not have comment,
institution, source or references atts. Sect 2.6.2 just says variables can
have them, not data variables specifically. I think it's just that we didn't
suppose they'd be needed, but I agree, they are extra info
Dear Jonathan et al.
I appreciate the concerns and I agree that the current situation provides the
information required, however I do not feel comfortable with the way it is
done: I think it is open to ambiguity and I am concerned that there are
multiple standard names for what I consider the
Hi-
I have some climate files that have a rotated-pole projection defined as:
char rotated_pole ;
rotated_pole:grid_mapping_name =
rotated_latitude_longitude ;
rotated_pole:grid_north_pole_latitude = 90.f ;
Hi Don,
this is not a problem in the grid definition, but a problem of the code. This
is not just a problem in your Java code, but also in the Fortran code that is
used in regional climate models (and the output files in the link you provided
are from the Danish regional climate model). It may
On 4/24/2012 4:16 AM, Hedley, Mark wrote:
There are particular issue here with format interoperability and conversion
with respect to phenomenon. In GRIB2, for example, there are codes which
identify vector components:
Wind direction (from which blowing) degree true
Wind speed ms
