Re: [CF-metadata] Web reference to a standard name?
Thanks all, Interesting to see the new MMI ontology work. I take from this discussion then that there is not currently a CF 'blessed' method to reference a term? E.g. for air_temperature I can choose from any of these: http://mmisw.org/ont/cf/parameter/air_temperature http://vocab.ndg.nerc.ac.uk/term/P071/16/CFSN0023 http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.html#air_temperature plus: http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.xml Cheers, Dom On 14/12/10 08:18, Lowry, Roy K. wrote: Dear All, Working to find a way of harmonising the two sources of web-served Standard Names is on by ‘To-Do’ list for next year (part of an issue list fed into the NETMAR project by John G.) Cheers, Roy. *From:* cf-metadata-boun...@cgd.ucar.edu [mailto:cf-metadata-boun...@cgd.ucar.edu] *On Behalf Of *John Graybeal *Sent:* 13 December 2010 22:28 *To:* Benno Blumenthal *Cc:* cf-metadata@cgd.ucar.edu *Subject:* Re: [CF-metadata] Web reference to a standard name? A minor clarification as to how MMI is doing things: Benno, all, On Dec 13, 2010, at 07:25, Benno Blumenthal wrote: We have tried to get standard URIs for CF concepts, but the effort bogged down. As for standard names, MMI established a set of URIs at http://marinemetadata.org/cf but has not been keeping up to date. Thanks for the mention. This is our older URL, sorry; we are now maintaining CF standard names in our ontology repository, using resolvable URLs. [1] There was a period when MMI was not keeping up to date with CF changes, but in the recent past we have been continuously updating the SKOS ontology for the parameter names at the site Carlos mentioned [1] (We will forward the misleading /cf URL above, or fix it to make clear in some other way the current status; thanks for calling that out.) As with Roy's handling, we provide URLs both for the current version at the reference URL, and for individual releases of the vocabulary. John [1] http://mmisw.org/ont/cf/parameter I have written a XSL transform at http://iridl.ldeo.columbia.edu/ontologies/xslt/.cfsn2rdf.xsl that can be applied to http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.xml to generate an up-to-date version, e.g. xsltproc http://iridl.ldeo.columbia.edu/ontologies/xslt/.cfsn2rdf.xsl http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/16/cf-standard-name-table.xml On the other hand, Roy has created opaque URIs for standard names at http://vocab.ndg.nerc.ac.uk/list/P07/9 contains all the Standard Names that have ever been published, including names that have been aliased http://vocab.ndg.nerc.ac.uk/list/P071/9 contains the Standard Names that are currently valid (i.e. those that have not been deprecated through aliasing) http://vocab.ndg.nerc.ac.uk/list/P072/9 contains the Standard Names that have been deprecated through aliasing The mapping between deprecates and their replacement aliases my be obtained through the following API call http://vocab.ndg.nerc.ac.uk/axis2/services/vocab/getMap?subjectList=http://vocab.ndg.nerc.ac.uk/list/P072/current&predicate=255&objectList=http://vocab.ndg.nerc.ac.uk/list/P071/current&inference=false <http://vocab.ndg.nerc.ac.uk/axis2/services/vocab/getMap?subjectList=http://vocab.ndg.nerc.ac.uk/list/P072/current&predicate=255&objectList=http://vocab.ndg.nerc.ac.uk/list/P071/current&inference=false> he changes them with each version, so it is both more definitive and harder to use. It is also pure SKOS, so one needs to add structure to actually connect it with a CF-described dataset. I plan to write out a map between the two, so that I can use his relationships between CF standard_names, but I do not have it yet. Additional information and ontologies describing the CF structure both as attributes and conceptually are available at http://iridl.ldeo.columbia.edu/ontologies/, including the connections between the standard_name ontologies and the CF structure. Benno On Mon, Dec 13, 2010 at 9:22 AM, Dominic Lowe mailto:dominic.l...@stfc.ac.uk>> wrote: > Hello all, > > What's the current CF recommended scheme for referencing a standard name on > the web? (either by URL or URN). > > I know about the vocab server and the xml/html online versions and could > choose to use URLs to point to items in any of these but is there a > definitive pattern that should be used? (or at least a best practice that > should be encouraged?). > > Much appreciated, > > Dominic > -- > Scanned by iCritical. > ___ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu <mailto:CF-metadata@cgd.ucar.edu> > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > -- Dr. M
[CF-metadata] Web reference to a standard name?
Hello all, What's the current CF recommended scheme for referencing a standard name on the web? (either by URL or URN). I know about the vocab server and the xml/html online versions and could choose to use URLs to point to items in any of these but is there a definitive pattern that should be used? (or at least a best practice that should be encouraged?). Much appreciated, Dominic -- Scanned by iCritical. ___ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Re: [CF-metadata] Some questions about 360-day calendars
Hi Jon 4) Finally on practical note: I seem to remember that someone has implemented the 360-day calendar using the Java library joda-time? Is this code available for re-use? I don't know about joda-time, but there is a python implementation in the CDMS cdtime module: http://esg.llnl.gov/cdat/cdms_html/cdms-3.htm Cheers, Dom Thanks in advance, Jon -- ___ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Re: [CF-metadata] example 7.8
All, This particular example has confused me in the past but for a different reason. It seems to me like the time values are not the best choice to represent the climatological time intervals. i.e. instead of: > time="1960-4-16", "1960-7-16", "1960-10-16", "1961-1-16" ; > climatology_bounds="1960-3-1", "1990-6-1", >"1960-6-1", "1990-9-1", >"1960-9-1", "1990-12-1", >"1960-12-1", "1991-3-1" ; I think it would be better to have the time values as the midpoint of the bounds. i.e. time="1975-4-16", "1975-7-16", "1975-10-16", "1976-1-16" ; climatology_bounds="1960-3-1", "1990-6-1", "1960-6-1", "1990-9-1", "1960-9-1", "1990-12-1", "1960-12-1", "1991-3-1" ; This corresponds better with the recomendation given in section 7.4 which states: "The time coordinates should be values that are representative of the climatological time intervals, such that an application which does not recognise climatological time will nonetheless be able to make a reasonable interpretation. " And also corresponds with the example in section 7.7 which is as follows: time="1965-1-15", "1975-1-15", "1985-1-15" ; climatology_bounds="1961-1-1", "1970-2-1", "1971-1-1", "1980-2-1", "1981-1-1", "1990-2-1" ; Regards, Dominic Lowe On Friday 03 July 2009 09:24:54 Heinke Hoeck wrote: > Dear all, > > I need help for 'Example 7.8. Climatological seasons'. > This should be: > 'average seasonal-minimum temperature for the four standard > climatological seasons MAM JJA SON DJF'. > > dimensions: > time=4; > nv=2; > variables: > float temperature(time,lat,lon); > temperature:long_name="surface air temperature"; > temperature:cell_methods="time: minimum within years time: mean over > years"; > temperature:units="K"; > double time(time); > time:climatology="climatology_bounds"; > time:units="days since 1960-1-1"; > double climatology_bounds(time,nv); > data: // time coordinates translated to date/time format > time="1960-4-16", "1960-7-16", "1960-10-16", "1961-1-16" ; > climatology_bounds="1960-3-1", "1990-6-1", > "1960-6-1", "1990-9-1", > "1960-9-1", "1990-12-1", > "1960-12-1", "1991-3-1" ; > > Where is the information that the intervals are 3 months (seasons)? > In the climatology_bounds the intervals are 30 years and 3 months. > In the cell_methods no interval information is given. > > Best wishes > Heinke > ___ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata ___ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Re: [CF-metadata] Climatological months time units attributes
Hi Christian, Section 7.7 here might help: http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.3/cf-conventions.html#climatological-statistics Regards Dominic On Tuesday 15 July 2008 10:55:18 Christian Pagé wrote: > Hello everyone, > > I want to create a CF-compliant NetCDF file, but I have some problems to > understand correctly the CF convention related to climatological time axis. > What I want to do is just create a NetCDF file having 12 records, one for > each month of the year, containing a mean or an anomaly of temperature over > a particular period. Thus, it is not bound to any particular year, and > using the month time udunits has lead into trouble because it is the mean > tropical month. I would be grateful to see some examples or some links that > would point to some more information on how to define proper attributes for > a CF-compliant NetCDF file. > > Best regards, > > Christian ___ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
