Dear John
As with previous versions, what will go in CF 1.7 is just the list of tickets
which are approved at the arbitrary date we decide to build CF 1.7. We could
decide that this is the list of currently approved tickets today, which we can
write down for reference, and that list would define the contents of the
CF 1.7 document which we have to build.
Yes, we should create the document as soon as we can in the simplest possible
way! As you know, we're trying to work out what that is, given the position we
are currently in with source documents.
Best wishes
Jonathan
----- Forwarded message from John Graybeal <jbgraybeal at mindspring.com> -----
> Date: Sun, 14 Jun 2015 08:22:26 -0700
> From: John Graybeal <jbgraybeal at mindspring.com>
> To: Jonathan Gregory <j.m.gregory at reading.ac.uk>
> CC: CF Metadata List <cf-metadata at cgd.ucar.edu>
> Subject: Re: [CF-metadata] Roms: ocean_s_coordinate_g1 and g2?
> X-Mailer: Apple Mail (2.1878.6)
>
> If we have actually agreed on what CF-1.7 is -- that is, ALL the things that make up CF-1.7 -- then I agree that telling people to put CF-1.7 into the Conventions attribute is Just Fine. But I didn't realize we knew what all the 1.7 things were yet.
>
> Also, if we do know what all the things are that make up CF-1.7, and that's all that's holding up CF-1.7, then the correct thing to do is go old school and just make a plain old CF-1.7 document in the fastest possible way. Don't worry about change markups, don't worry about production, just get it out there. The nice technological approach can then play catch-up, with the advantage of a target document to match.
>
> But I didn't realize CF-1.7 was anywhere close to final form, so putting it in an attribute would be premature if that's true.
>
> John
>
>
> On Jun 12, 2015, at 09:35, Jonathan Gregory <j.m.gregory at reading.ac.uk> wrote:
>
> > Dear Heiko
> >
> > We have to agree a new format for the source of the CF document, because the
> > existing one appears hard to maintain, and that's one reason why CF 1.7 has
> > not been completed. I hope this will be sorted out soon. All agreed tickets
> > will be implemented.
> >
> > In fact, I don't see why we shouldn't decide now on the list of tickets which
> > will be included in CF 1.7 and say that people can put CF-1.7 into the
> > Conventions attribute now, although the document itself does not exist. What
> > do others think?
> >
> > Best wishes
> >
> > Jonathan
> >
> >
> > ----- Forwarded message from Heiko Klein <Heiko.Klein at met.no> -----
> >
> >> Date: Thu, 11 Jun 2015 17:35:15 +0200
> >> From: Heiko Klein <Heiko.Klein at met.no>
> >> To: "cf-metadata at cgd.ucar.edu" <cf-metadata at cgd.ucar.edu>
> >> Subject: Re: [CF-metadata] Roms: ocean_s_coordinate_g1 and g2?
> >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
> >> Thunderbird/31.7.0
> >>
> >> Dear all,
> >>
> >> three years ago, Rich submitted the addition for a new
> >> ocean_s_coordinates_g* to the ticket system:
> >> http://cf-trac.llnl.gov/trac/ticket/93 The ticket was approved by 3
> >> authors and accepted in 2012.
> >>
> >> When will this ticket be available in the CF document? What needs to
> >> be done? (And why does the ticket have 'low' priority?)
> >>
> >> Best regards,
> >>
> >> Heiko
> >>
> >>
> >> On 2012-07-18 07:52, Heiko Klein wrote:
> >>> Rich,
> >>>
> >>> it must have been the netcdf-java package where I have seen these
> >>> standard-names. The description on the netcdf-java pages are outdated,
> >>> still using formula_terms a and b. I just checked the code, and that is
> >>> up to date working with the formula_term -array C(k).
> >>>
> >>> It'll be good to have an official version. Thanks for picking this up
> >>> again.
> >>>
> >>> Heiko
> >>>
> >>>
> >>> On 2012-07-17 17:13, Rich Signell wrote:
> >>>> Heiko,
> >>>>
> >>>> We worked with John Caron several years ago to get these into the CDM
> >>>> in the NetCDF-Java library, so if you have g1 or g2 coordinates they
> >>>> will work with codes that use NetCDF-java (like the Matlab NCTOOLBOX
> >>>> and Unidata's IDV), and I remember we drafted up some documentation
> >>>> to submit to CF, but looks like we dropped the ball. I'll pick it
> >>>> up again.
> >>>>
> >>>> -Rich
> >>>>
> >>>> On Mon, Jul 16, 2012 at 10:24 AM, Heiko Klein <Heiko.Klein at met.no> wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I'm currently working with ROMS ocean model files. The model uses a
> >>>>> generalized ocean_s coordinate as defined by
> >>>>> https://www.myroms.org/wiki/index.php/Vertical_S-coordinate .
> >>>>>
> >>>>> The same page says that their s_coordinate is covered by standard_names
> >>>>> ocean_s_coordinate_g1
> >>>>> ocean_s_coordinate_g2
> >>>>> and I believe I have seen at least the g1 case in a draft of a CF
> >>>>> convention
> >>>>> some month ago. Both cases are also implemented in the netcdf-java
> >>>>> package
> >>>>> with above standard_names:
> >>>>> http://www.unidata.ucar.edu/software/netcdf-java/reference/StandardCoordinateTransforms.html
> >>>>>
> >>>>>
> >>>>> But I cannot find any of those names any longer, neither in CF-1.6
> >>>>> nor in
> >>>>> the standard_names tables.
> >>>>>
> >>>>> Does somebody remember what happened to these vertical coordinates?
> >>>>> According to the ROMS Wiki, the standard_names have been added in March
> >>>>> 2009.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Best regards,
> >>>>>
> >>>>> Heiko
> >>>>> _______________________________________________
> >>>>> CF-metadata mailing list
> >>>>> CF-metadata at cgd.ucar.edu
> >>>>> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >> --
> >> Dr. Heiko Klein Norwegian Meteorological Institute
> >> Tel. + 47 22 96 32 58 P.O. Box 43 Blindern
> >> http://www.met.no 0313 Oslo NORWAY
> >> _______________________________________________
> >> CF-metadata mailing list
> >> CF-metadata at cgd.ucar.edu
> >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
> >
> > ----- End forwarded message -----
> > _______________________________________________
> > CF-metadata mailing list
> > CF-metadata at cgd.ucar.edu
> > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
----- End forwarded message -----
Received on Tue Jun 16 2015 - 05:47:21 BST
