good point - The auxiliary coordinate variable station_name in these
examples is missing a standard_name; and indeed station_description
or station_name would fit the bill. I'd be happy with either or
both.
For that matter, if one of the stations in the examples had a WMO
ID, then it would also need a variable wmo_platform_id (btw, that's
a name change from the text's station_wmo_id)
The example variable station_info also has no standard_name, but the
example variable station_elevation already has one.
- Jeff
On 8/25/11 8:47 AM, Renata McCoy wrote:
There is also a 'station_name' as recommended
attribute in a discrete geometries section, see
and even more info on the station (like station_info anf
station_elevation) in the Example H.3. Timeseries of station
data
Greetings,
Renata
------------------------------------------------------------
Renata McCoy
PCMDI/ LLNL, (925) 424-5237, [email protected]
------------------------------------------------------------
On Aug 25, 2011, at 5:50 AM, Jonathan Gregory wrote:
Dear Jeff
I think this one is fine
- wmo_platform_id : variable of
integer type, containing the WMO
identifier of an observing station
or other platform
For this one
- station_description : variable
of character type containing a
description of a time series
station
I now wonder what we mean by "description". What is
probably expected is a
geographical location of some sort, isn't it. Could we
call it station_name?
Like long_name and standard_name, it could still be
several words.
Best wishes
Jonathan
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
|
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
