#147: clarification of standard and correction of conformance doc: formula_terms
-----------------------------+------------------------------
  Reporter:  taylor13        |      Owner:  cf-conventions@…
      Type:  defect          |     Status:  new
  Priority:  high            |  Milestone:
 Component:  cf-conventions  |    Version:
Resolution:                  |   Keywords:
-----------------------------+------------------------------

Comment (by davidhassell):

 Hello Karl, Jonathan,

 I'm happy with all the three cases described in CDL in the previous two
 posts being allowed. I'm also fine with Jonathan's proposed text changes,
 and (naturally, as I propsed it!) #140 being accepted.


 There is one further detail - is it allowed for a term variable to have
 bounds but for that variable to ''not'' be listed in the `coordinates`
 attribute of a data variable with uses the formula terms?

 {{{
 dimensions:
     z = 19 ;
     y = 73 ;
     x = 96 ;
     bound = 2 ;
 variables:
     double hybrid_sigma(z) ;
            hybrid_sigma.standard_name =
 "atmosphere_hybrid_sigma_pressure_coordinate" ;
            hybrid_sigma.formula_terms = "a: A b: B ps: PS" ;
            hybrid_sigma.bounds = "hybrid_sigma_bounds" ;
     double A(z) ;                      // HAS bounds
            A.bounds = "A_bounds" ;
     double B(z) ;                      // HAS bounds
            B.bounds = "B_bounds" ;
     double PS(y, x) ;
     double lat(y, x) ;
     double lon(y, x) ;
     double hybrid_sigma_bounds(z, bounds) ;
            hybrid_sigma_bounds.formula_terms = "a: A_bounds b: B_bounds
 ps: PS" ;
     double A_bounds(z, bounds) ;
     double B_bounds(z, bounds) ;
     double air_temperature(z, y, x):
            air_temperature.coordinates = "lat lon" // no A nor B, here
 }}}

 I think that this would be OK, as even though it A is not identified as an
 auxiliary coordinate variable (and so on the face of it the `bounds`
 attribute is non-standardised), its reference from a formula terms means
 that it may be viewed as containing coordinate data (and so its `bounds`
 attribute is, in fact, properly meaningful).

 Thanks,

 David

--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/147#comment:23>
CF Metadata <http://cf-convention.github.io/>
CF Metadata

Reply via email to