cf-convention / cf-convention.github.io Goto Github PK

At the top of the standard names table (version 27, html edition):

http://cfconventions.org/Data/cf-standard-names/27/build/cf-standard-name-table.html

there is a link to the 'Guidelines for Construction of CF Standard Names', which sounds like a useful document.

Unfortunately the link:
http://cf-pcmdi.llnl.gov/documents/cf-standard-names/guidelines
points to the old site, and is currently unavailable.

The file is available in github, it is just that the link is broken.

https://github.com/cf-convention/cf-convention.github.io/blob/master/Data/cf-standard-names/docs/guidelines.html

Thanks.

I seem to remember a glossary document on the old site - would explain concisely things like "ancillary variables". I found it very useful. Does this still exist, and can it be added?

On the CF Metadata Documents page http://cfconventions.org/documents.html, the XML files older than version 26 (?) are broken links.

The area-type-table published at http://cfconventions.org/Data/cf-standard-names/docs/area-type-table.html is out of date.

There is a cf-metadata organization on github: https://github.com/cf-metadata, with one repository in it called cf-conventions. The repository appears unmaintained (last update rhattersley March 10).

(Because this is the only repository that pluralizes convention in the name, it is more visible than the actual cf-convention repository for searches for 'cf conventions'.)

Can this repository be deleted, or else made fully active and up to date for its desired purpose?

There is a document "Guidelines for construction of CF standard names" which can be found here:
http://helene.llnl.gov/cf/documents/cf-standard-names/guidelines

This document needs to be migrated to the new site, if it isn't there already. Perhaps under the cf-documents folder, linked to from the site's front page quick links (because this is a common task for new users).

Where can I see changes in the standard name table?

I would expect that the xml file is being revision controlled somewhere in github, with releases corresponding to the version number.

On this page:

https://github.com/cf-convention/repository-cf/tree/master/cf-standard-names/trunk

I see only an old 1.0 xml (this is sort of a template, right?)

While on this page:

https://github.com/cf-convention/cf-convention.github.io/tree/master/Data/cf-standard-names

I see folders that contain the different versions of XML within them, like:

https://github.com/cf-convention/cf-convention.github.io/tree/master/Data/cf-standard-names/27/src

(BTW, Shouldn't all these folders be turned into a single folder with tagged releases? Perhaps this should be a separate issue -- not sure)

Link to Udunits documentation on the CF Standard Name Table page is broken in all versions. It should be pointing to here (so that it will not break again when the Udunits version changes):
https://www.unidata.ucar.edu/software/udunits/#documentation

or here for the current version:
https://www.unidata.ucar.edu/software/udunits/udunits-current/doc/udunits/udunits2.html

If someone wants to contribute to CF our web pages direct them to the mail list and the trac site, but not the github project site. The website needs revision so people will know how to engage.

At the very least, a quick link should be included on http://cfconventions.org and a short explanation of how one contributes, including a link to the github CF project should appear on http://cfconventions.org/discussion.html . Also, need links to
https://github.com/cf-convention/cf-conventions/blob/master/CONTRIBUTING.md
and possibly
http://cfconventions.org/rules.html

The page http://cfconventions.org/standard-names-26.html is a bit messy (under chrome browser). The description and name columns get mixed up starting from atmosphere_mass_content_of_inorganic_chlorine.
I wanted to update the page but I could not find the standard-names-26.xml file. Can you add this file.

The functionality discussed in this issue has been implemented by @bzah in this pull request in response to this later similar issue.

It would be useful (for me, anyway) to be able to search units on the CF standard name HTML pages. This can help narrow down the list if you're searching for a standard name to match an existing parameter in a data set (although you might have to try a few convertible units).

I would make a pull request on cf-standard-name-table.xsl but I can't find a master version, just copies that stop appearing in the cf-standard-names folders after version 22. Am I missing it?

missing files,

please cherry pick out of history

Data/cf-conventions/cf-conventions-1.0/xsl/template/titlepage.xsl
Data/cf-conventions/cf-conventions-1.1/xsl/template/titlepage.xsl
Data/cf-conventions/cf-conventions-1.2/xsl/template/titlepage.xsl
Data/cf-conventions/cf-conventions-1.3/xsl/template/titlepage.xsl
Data/cf-conventions/cf-conventions-1.7/docbooksrc/.svn/tmp/tempfile.tmp
Data/cf-conventions/cf-conventions-1.7/xsl/template/.svn/all-wcprops
Data/cf-conventions/cf-conventions-1.7/xsl/template/.svn/entries
Data/cf-conventions/cf-conventions-1.7/xsl/template/.svn/format
Data/cf-conventions/cf-conventions-1.7/xsl/template/.svn/text-base/titlepage.xsl.svn-base
Data/cf-conventions/cf-conventions-1.7/xsl/template/titlepage.xsl
Data/docbook-xsl-1.73.2/params/.svn/text-base/template.xml.svn-base
Data/docbook-xsl-1.73.2/params/template.xml
Data/docbook-xsl-1.73.2/roundtrip/.svn/prop-base/template.dot.svn-base
Data/docbook-xsl-1.73.2/roundtrip/.svn/text-base/template-pages.xml.svn-base
Data/docbook-xsl-1.73.2/roundtrip/.svn/text-base/template.dot.svn-base
Data/docbook-xsl-1.73.2/roundtrip/.svn/text-base/template.xml.svn-base
Data/docbook-xsl-1.73.2/roundtrip/template-pages.xml
Data/docbook-xsl-1.73.2/roundtrip/template.dot
Data/docbook-xsl-1.73.2/roundtrip/template.xml
Data/docbook-xsl-1.73.2/template/.svn/all-wcprops
Data/docbook-xsl-1.73.2/template/.svn/entries
Data/docbook-xsl-1.73.2/template/.svn/text-base/titlepage.xml.svn-base
Data/docbook-xsl-1.73.2/template/.svn/text-base/titlepage.xsl.svn-base
Data/docbook-xsl-1.73.2/template/titlepage.xml
Data/docbook-xsl-1.73.2/template/titlepage.xsl

The functionality discussed in this issue has been implemented by @bzah in this pull request.

When I go to the CF Standard Name Table page and search the standard name used for psl in the CMIP6 Data Request (DR 01.00.22), air_pressure_at_sea_level, I get Found 0 standard names matching query: air_pressure_at_sea_level, which led me to believe that there was an error in the name, or that I should not use underline characters in the names, when searching

Now, if I look for air_pressure_at_mean_sea_level, I get psl, Found 1 standard names matching query: air_pressure_at_mean_sea_level and also the following information

air_pressure_at_mean_sea_level
alias: air_pressure_at_sea_level

I could be useful if the search could search both the main/canonical (or whatever you call these) names and the aliases

I don't know if this one is also for @mattben , or for somebody else working on the Search

The Ontology Registry and Repository (ORR) at https://mmisw.org has been maintaining an RDF version of the CF standard name vocabulary. Although the involved conversion and registration process is performed automatically, it still needs to be triggered manually, once we learn that a new CF version has been released. This entry is to get some input about how we could proceed to automate this as well.

One initial idea is simply to put together a cronjob that checks for any new version. In contrast to the individual <version-number> directories, I notice there is a current directory as well, which seems like an appropriate place to directly check for the last version number, that is, by looking into https://github.com/cf-convention/cf-convention.github.io/blob/master/Data/cf-standard-names/current/src/cf-standard-name-table.xml.

One other possible mechanism it that we could provide an ORR-based URL that CF could enable in this repository as a "webhook" to be triggered whenever there's a new version released.

Worth noting, we also keep a NVS-ORR mapping ontology relating the ORR and the NVS RDF versions of CF. This mapping is also generated as part of our automated process. So, a relevant question (if appropriate here) is about how long does it usually take for the NVS version to be updated upon a new version of CF.

Any comments/suggestions would be greatly appreciated.

Moving to github should help the community contribute and be able to
fix problem with the CF documents. But I'm a little confused about
what to do if we see a problem at http://cf-convention.github.io/ and
we want to submit a pull request to change them.

At the CF github organization (https://github.com/cf-convention) I see
three repositories:

1. cf-convention.github.io
   which controls the github pages showing up at
   http://cf-convention.github.io/
2. cf-documents
   which contains HTML and PDF versions of the documents
3. repository-cf
   a git svn clone of the old PCMI SVN repository

So if we see a problem with pages on http://cf-convention.github.io/,
which repo are we supposed to send a pull request to?

There are several defectively defined links on http://cfconventions.org/wkt-proj-4.html .

I will create a pull request in a few minutes to solve it.

In #87 I have made a modification to the governance page to create a link to the existing constitution from the white paper, which I converted to adoc. When this is merged, I will propose some small changes from the CF governance panel.

When I follow the links from the Latest CF Conventions Documents page to the html versions of the CF convention (I have not checked the pdf version)

• Most Recent Release (v1.7) Single HTML brings me to a page that has the expected Version 1.7 in the header (after the list of contributors), and the footer says Last updated 2017-08-01
• but Current Working Draft (v1.8) Single HTML brings me to a page that has also Version 1.7 in the header, when you would expect 1.8 or 1.8 draft . The footer of the draft correctly shows a different date, Last updated 2017-08-15

Several suggestions for the 'latest' page:

• Fix typos ('lastest', 'Convetions')
• Include the latest version of standard names table, in similar form
• Consider including other latest specification docs: areas table, any other similar tables
• With these changes made, make this a high-visibility link on the home page. It's the thing most people want.

When I hover over take a look at the Discussion page on the home page, the displayed link is http://cf-convention.github.io/discussion.html when it should probably rather be http://cfconventions.org/discussion.html

Going to cf-convention.github.io redirects to cfconventions.org, which is down.

The page about governance on the live website http://cfconventions.org/governance.html isn't correctly formatted at the top. It looks right when viewed at https://github.com/cf-convention/cf-convention.github.io/blob/master/governance.md. Is there something wrong with formatting?

Jonathan

Pages like http://cfconventions.org/discussion.html are suddenly no longer viewing correctly. See enclosed screenshot. (Happened shortly after change to eliminate Working Groups from header, which was visibly correct for a brief period.)

Not sure if this is something I could have done on my end (i.e., a local problem), but I don't think so.

Is this document available anymore? There is a page for it but no links: http://cfconventions.org/requirements-and-recommendations.html

This page https://github.com/cf-convention/cf-convention.github.io/wiki needs updating, now that the merging is largely over.

I will be trying to do everything it says shortly, so that will be a test. :-)

Things that are obviously wrong include:

• all the actual cf docs and standard names live in the cf-documents repo -- there is no repo by that name, though there is a directory under Data
• most people can't push to this repo, so a brief description for them should say "if you don't have push permissions, fork the repo and make your changes to your copy, then do a pull request"
• The logic behind the three repos section is outdated
• Pros, Cons, Possible Solutions sections are outdated (can be deleted?)

The CF Conventions site should have a clear contact point or mechanism on each page. Whether this is the CF mail list, or (I think better) a specific support email, having the info linked from each page will help people contact CF with issues.

I wasn't sure if it was intentional, but a significant number of documents from the old site haven't made it to the new site (that I can tell). Below are the links from old location to the new location I think they should go.

here I'm following the principle that we shouldn't lose anything from the old site, but maybe decisions have been made to let some things go. If so we can document those decisions in a page on the new site.

The link to the COARDS Convention from the cfconventions.org home page is broken ... it should be https://ferret.pmel.noaa.gov/noaa_coop/coop_cdf_profile.html (the domain name has changed).

Don't know if this is something for @mattben or @japamment, but I have followed a latest link found on Google, and landed on: http://cfconventions.org/latest.html

This links to v27 of Standard Names Table, when the actual latest version is v50. I have not checked if the other links on the latest page were better

As you can see below, I was looking for something pretty straightforward!

Requirements and Recommendation links at http://cfconventions.org/requirements-and-recommendations.html for versions 1.5 and older do not exist.

I have noticed, via an exception raised in a script I have wrote that parses the standard name tables across all versions including for the last modified dates, that there is a redundant colon in the last_modified date stamp for version 23 of the standard name table. For quick inspection, as copied from the head of the relevant XML source file:

<?xml version="1.0"?>
<standard_name_table xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="cf-standard-name-table-1.1.xsd">
   <version_number>23</version_number>
   <last_modified>2013-03-23:T12:30:00Z</last_modified>

Though this is an old version, ideally the misplaced colon could be removed for a correction, as the datetime as-is breaks ISO 8601 compliance & anyone who might want to parse the full dataset such as myself will have to add in lines to manually remove the colon before e.g. converting datetimes to other datetime formats such as Python datetime.datetime object.

Documents page (http://cfconventions.org/documents.html) should include the areas table, and any other known tables.

The two new dimensionless vertical coordinates for ocean models from Trac Ticket 93 have been approved for inclusion in CF-1.7, but do not yet appear in the draft document. The appendix-d.xml docbook and the docbook info/changes docbook need to be modified.

Hi There! Is this the source for the globe logo being used on the GitHub Pages CF site?
https://commons.wikimedia.org/wiki/File:Simple_Globe.svg

If so, would you consider declaring the logo attribution and license so that the CF site's usage is more compliant with the author's license?

If not, is there some other license or attribution for the logo that needs to be declared?

When looking at the content of .md pages in https://github.com/cf-convention/cf-convention.github.io, most links don't work (though they work fine on the actual site). This is perhaps unavoidable, but it makes it hard to maintain the site and check for broken links while editing the pages.

So this task is to see whether there is a way to manage the links so that they are internally consistent in the repository, as well as in the web site itself. (Maybe involving localizing them?)

This task is meant for John G, as a training exercise. But feel free to add comments/suggestions/wisdom.

From Bob Simons on CF Metadata List:

On the http://cfconventions.org/ web site, the link to "CF Conventions Document" points to http://cfconventions.org/latest.html which just leads to an HTTP 404 error.

Reference #13 for history...

As there are currently no Working Groups, suggest removing this from the header navigation. It is easy to add it back if we ever have one, but meantime it just wastes people's time.

If I click the CF Standard Name Table link at
http://cfconventions.org/
I get this empty page:

In the answer to question My variable depends on the type of surface. How can I specify the surface type? there is a link to the Area Type Table. The link is broken. It directs to

• http://cfconventions.org/Data/cf-standard-names/docs/area-type-table.html

but should direct to

• http://cfconventions.org/Data/area-type-table/current/build/area-type-table.html

The black CF MetaData header is styled in such a way that it obscures the actual content of the page. This is worked around in most of the pages by leaving several blanks lines at the top of the page.

But when you are linking to content within a page (anchored content), the browser puts the anchor at the top of the page, which is behind the top border. Users will be confused because they won't see the section title that they just tried to jump to.

To make the anchor links work as expected throughout the pages, it will be necessary to fix the styling on the header.

There are a few links in-line in the 3rd bullet of the governance page (https://github.com/cf-convention/cf-convention.github.io/blob/master/governance.md) that aren't hooked up.

Under H.1 Point Data Example there is a non-ASCII character used for the quotation on this line:

          time:standard_name = “time”;

If you attempt to create netCDF files from the examples listed that contain these examples, the program will crash with a SEGFAULT.

[1]    16207 segmentation fault  ncgen -o point.nc point.cdl

If you're like me and try to find out what is wrong by debugging it, you'll wind up in a lot of pain and suffering staring at:

Program received signal SIGSEGV, Segmentation fault.
0x000000010000e865 in processsemantics ()
(gdb) bt
#0  0x000000010000e865 in processsemantics ()
#1  0x0000000100004313 in main ()
(gdb) q

I finally determined that the cause was a non-ASCII character being used in the CDL.

Could you please find it in your hearts to replace all non-ASCII quotation marks with ASCII quotation marks in the CDL examples?

The DIscussion page (http://cfconventions.org/discussion.html) is good, a few suggestions about its links and their content:

• the About the Trac Site page is good, but includes a lot of information about the email lists, and then says in the last section "Don't send email to the email lists", which really only applies for trac issues. Instead:
  • Mention the Discussion Lists first on the Discussion page, since that is the first thing most people are exposed to
  • Under References on the Discussion page, a page About the Discussion Lists should be first; move Discussion Lists content (from the About the Trac Site link) into that page and reference it from the Trac site
  • The last paragraph in About the Trac Site should say "For Trac issues, don't send email direct..."
• Perhaps organize the links so that the About link comes before the site link(s), and all the LIsts links come before all the Trac links
• Indicate with each link whether it is external to the site (it is disconcerting to try to get more information about something, but be sent directly to the external site instead). This should be a small indication, not sure yet the best way to do it in the Google web sites.

The directory for cf-conventions under the Data directory in the repo (https://github.com/cf-convention/cf-convention.github.io/tree/master/Data/cf-convetions) has a type in the directory name (missing the first 'n' of conventions). This error propagates to the links on the main web site.

It will be likely be a pain to fix this, but it will be a bigger pain to maintain it this way over the years, as people continually link to the existing (bad) name, and try to link to the correctly spelled name that doesn't work.

I believe there is a clean way to make this change in git, so the only things that have to change after that are the internal links, of which there aren't too many.

1. Do we stay with jekyll?
2. Do we stay with two repos cf-documents and cf-convention.github.io`
3. How do we display all the pages nicly?
4. is the xml file good enough and we can scratch the html / pdf version
5. can we write a parse that will convert the xml in to a html and pdf file to automagically keep all three version (pdf, html, xml) in cynic?

On the index page a link directs to the NetCDF library page at Unidata. The provided URLs (http://www.unidata.ucar.edu/packages/netcdf/index.html) has changed to https://www.unidata.ucar.edu/software/netcdf/index.html (packages replaced by software).

Two links to the UDUnits API Documentation are given in the FAQ. They do not work anymore because one part of the URL changed. It should not be http://www.unidata.ucar.edu/software/udunits/udunits-2.2.16/doc/udunits/udunits2lib.html but https://www.unidata.ucar.edu/software/udunits/udunits-current/doc/udunits/udunits2lib.html .

The CF data model will guide the development of CF by providing a framework for ensuring that proposed changes fit into CF in a logical way, rather than just a pragmatic one.

To ensure this occurs, some additional rules for conventions changes have been drafted in Pull Request #72

In brief, a proposed change should be assessed for data model compatibility. If it is not compatible, and the proposal cannot be acceptably modified so that it is, then the data model will be changed to accommodate the change. The proposer is not required to have detailed data model knowledge - the new rules state that "The assessment will be carried out by a member of the conventions committee or another suitably qualified person. If no-one volunteers, the chairman of the committee will ask someone to do it".

See cf-convention/cf-conventions#159 for more details.

I had to do some digging in order to find I could report CF web related problems this repository...

There is no obvious Contact link or page on the http://cfconventions.org/ web site, so maybe you could add a link to the issue pages https://github.com/cf-convention/cf-convention.github.io/issues from the CF Discussion page

I have just realized that there is no way to cite or even acknowledge the CF conventions. Or if there is, it is not easy to find it on the CF site.

Should there be some zenodo stuff that can be cited (don't really know how this works), until the time there is a GMD (or other) paper about the CF conventions

And it would be useful to have a standard acknowledgment sentence that people can copy/paste, even if they usually forget about that...

I'm working on an update to guidelines for data providers in the OceanSITES project. We refer to the CF convention many times in the document, and sometimes to specific chapters. It would be great if these links could point directly to the most recent version of the document.

There's a handy page at http://cfconventions.org/latest.html, but I can't seem to get to the latest conventions document in html via a direct link, as far as I can tell. Since I want people to actually read the CF doc, I really want to limit the clicks they need to go through. And, I don't want to risk sending people to old versions of the document.

At the moment I'm trying to link to the latest on discrete sampling geometries, cf-conventions.html#discrete-sampling-geometries, which is now in /Data/cf-conventions/cf-conventions-1.7.

Is there actually a URL that will point directly to the most recent conventions document, in html?