[CF-metadata] Using a standard_name more than once in a file
Hello Evan,
Opinion on this is divided - some communities have decided to regard the Standard Name as mandatory. The CF Conventions state that the Standard Name may be omitted providing that the Long Name is supplied. In my view (automated data aggregation) in your case I would use the Long Name to describe each navigation stream and the Standard Names to label the primary navigation stream.
Cheers, Roy.
________________________________________
From: Manning, Evan M (398B) [Evan.M.Manning at jpl.nasa.gov]
Sent: 30 March 2015 00:33
To: cf-metadata at cgd.ucar.edu
Subject: [CF-metadata] Using a standard_name more than once in a file
I'm defining a data set, and I have a question about reusing standard_names in a file.
For example this a swath, so there a lat/lon/time for each observed spot. There is also a subsatellite lat/lon and mid-scan time. And in some cases I have separate lat/lon by MW band.
So, does every lat get standard_name set to latitude, or just the primary one?
On the one hand, I can see that users of each field could benefit from having
the standard_name set so that users of that field know what it is. But on the
other hand, if a user or program wants to come in and see what is "the" latitude,
maybe things work better if the standard_name latitude is only used once?
(Latitude is a key geolocation parameter. Does the answer to the above question
change if we're talking about something less foundational, like land_area_fraction
or sensor_view_angle?)
On a related topic, I see that adding standard_names platform_latitude, etc.
has been discussed but the discussion seems to be stalled. What are the prospects?
Thanks!
-- Evan
This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
Received on Mon Mar 30 2015 - 00:51:26 BST
This archive was generated by hypermail 2.3.0
: Tue Sep 13 2022 - 23:02:42 BST