Dear Randy Thanks for reminding us of the ticket. I'm sorry, I had forgotten we had in the end concluded it, thanks to you. The next version of CF is being worked on, in which this change will be included.
Best wishes Jonathan ----- Forwarded message from Randy Horne <[email protected] Date: Tue, 5 May 2015 14:40:45 -0400 From: Randy Horne <[email protected]> To: Jonathan Gregory <[email protected]> CC: [email protected] Subject: Re: [CF-metadata] Usage of status flag as a standard name modifier X-Mailer: Apple Mail (2.2098) Dear All: Please refer to trac item #74 (Allow sharing of ancillary variables among multiple data variables). This enhancement support handling data variables that do not have standard names. here are the final posts in this trac item ???. ++++ Dear All: This post defines "strawman" redlines to the CF standard to reflect this enhancement in the CF standard. (1) In paragraph 3.5 Flags ... Change example 3.3 to be: byte current_speed_qc(time, depth, lat, lon) ; current_speed_qc:long_name = "Current Speed Quality" ; current_speed_qc:standard_name = "status_flag" ; current_speed_qc:_FillValue = -128b ; current_speed_qc:valid_range = 0b, 2b ; current_speed_qc:flag_values = 0b, 1b, 2b ; current_speed_qc:flag_meanings = "quality_good sensor_nonfunctional outside_valid_range" ; The only change made to this example is the removal of the "sea_water_speed" from the flag variable's standard_name. Immediately after the example, add the following sentence: "Note that the data variable containing current speed has an ancillary_variables attribute with a value containing current_speed_qc." (2) In Appendix C. Standard Name Modifiers ... Add the following statement after the existing description for the number_of_observations modifier. "The use of this modifier is deprecated and the standard_name number_of_observations is preferred to describe this type of metadata variable." Add the following statement after the existing description for the status_flag modifier. "The use of this modifier is deprecated and the standard_name status_flag is preferred to describe this type of metadata variable." (3) Note that a post requesting standard_names status_flag and number_of_observations are posted to the CF metadata message board. very respectfully, randy comment:53Changed 19 months ago by jonathan Dear Randy Thanks. I think that is fine and I support this change being made. We should also add to Sect 3.3 of the conformance document: Recommendations: ??? Use of the standard_name modifiers status_flag and number_of_observations is deprecated, and the corresponding standard_names are recommended instead. Cheers Jonathan comment:54Changed 19 months ago by rhorne@??? Dear CF committee: Three weeks has gone by without any additional comments on this enhancement. Do you support this enhancement ? very respectfully, randy comment:55Changed 19 months ago by biard I'm good with it. (Not that it mattersmuch! :-)) I think the final solution sidesteps the thorny issues of data relationships that this ticket raised. It's also a good way to address the particular issues. comment:56Changed 19 months ago by jonathan Dear all Assuming that Nan supports this proposal as it was most recently summarised ???in comment 52, then this ticket has sufficient support to be accepted according to the rules. Jeff, please could you include it in the new CF version you are currently compiling. Randy should be added to the list of additional authors of the CF standard in the new version. Thank you, Randy. Jonathan comment:57Changed 19 months ago by ngalbraith I support this update - thanks, all. +++++ very respectfully, randy > On May 5, 2015, at 12:54 PM, Jonathan Gregory <[email protected]> > wrote: > > Dear Ajay > > We have discussed this before, I seem to recall, without reaching a conclusion > about it. Yes, with the existing convention you can't use a modifier without > a standard name. Is it possible you could devise and propose standard names > for your data? > > Cheers > > Jonathan > > ----- Forwarded message from Ajay Krishnan - NOAA Affiliate > <[email protected]> ----- > >> Date: Wed, 29 Apr 2015 14:44:07 -0400 >> From: Ajay Krishnan - NOAA Affiliate <[email protected]> >> To: "[email protected]" <[email protected]> >> Subject: [CF-metadata] Usage of status flag as a standard name modifier >> >> Dear CF community, >> >> What is the best way to represent status flag for variables that do not >> have a standard name? >> I presume that the standard name modifier cannot be used in this case. >> >> Can long names be used in such cases? >> >> Thanks, >> Ajay > >> _______________________________________________ >> CF-metadata mailing list >> [email protected] >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > > ----- End forwarded message ----- > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata ____________________________________ Randy C. Horne ([email protected]) Principal Engineer, Excalibur Laboratories Inc. voice & fax: (321) 952.5100 url: http://www.excaliburlabs.com ----- End forwarded message ----- _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
