Comments (4)
On second thoughts, I realise that since it's not clear what to do, it would make sense to discuss it first in our new forum. Therefore I've opened a discussion of this question. Please comment there, rather than here.
from cf-conventions.
In the discussion, @davidhassell, @martinjuckes and I have agreed that this is a defect. I am therefore changing the label of this issue from enhancement
to defect
.
I propose the changes described below to remedy the defect. Note also that I am proposing to update the text to replace "dimensionless" with "parametric (usually dimensionless)". That reflects the revision we made quite a long time ago in Section 4.3.3.
In Section 1.4, replace this text
To achieve the goal of being able to spatially locate all data values, this convention includes the definitions of common dimensionless vertical coordinates in Appendix D, Parametric Vertical Coordinates. These definitions provide a mapping between the dimensionless coordinate values and dimensional values that can be uniquely located with respect to a point on the earthโs surface. The definitions are associated with a coordinate variable via the
standard_name
andformula_terms
attributes. For backwards compatibility with COARDS use of these attributes is not required, but is strongly recommended.
with
In particular a model may output data on the parametric (usually dimensionless) vertical coordinate used in its mathematical formulation. To achieve the goal of being able to spatially locate all data values, this convention provides a mapping, via the
standard_name
andformula_terms
attributes of a parametric vertical coordinate variable, between its values and dimensional vertical coordinate values that can be uniquely located with respect to a point on the earth's surface (Section 4.3.3, Parametric Vertical Coordinate; Appendix D, Parametric Vertical Coordinates).
This removes the "recommendation" which causes the confusion. That recommendation is not necessary here, because it's included in Section 1.5 on "Relationship to the COARDS Conventions". The relevant sentence currently reads
But we recommend that the
standard_name
andformula_terms
attributes be used to identify the appropriate definition of the dimensionless vertical coordinate (see Section 4.3.2, "Dimensionless Vertical Coordinate").
which should be updated to read
But we recommend that the
standard_name
andformula_terms
attributes be used to identify the appropriate definition of the dimensionless vertical coordinate (see Section 4.3.3, "Parametric Vertical Coordinate").
In the preamble to Section 4, replace this text:
We extend COARDS by providing explicit definitions of dimensionless vertical coordinates. The definitions are associated with a coordinate variable via the
standard_name
andformula_terms
attributes. For backwards compatibility with COARDS use of these attributes is not required, but is strongly recommended.
with
As an extension to COARDS, we strongly recommend that a parametric (usually dimensionless) vertical coordinate variable should be associated via
standard_name
andformula_terms
attributes with its explicit definition, which provides a mapping between its values and dimensional vertical coordinate values that can be uniquely located with respect to a point on the earth's surface.
Here, I have retained the recommendation, but it's rephrased to make clear that it refers to the use of the convention for parametric vertical coordinates, rather than to the standard_name
attribute specifically.
I have prepared pull request 520 to implement the above. In the PR, I have also corrected a couple of minor punctuation faults in Sect 1.
Since this is a defect issue, the change will be accepted in the absence of any objection in three weeks, on 20th May.
from cf-conventions.
Thanks, @JonathanGregory. PR #520 looks fine to me (I've made one minor suggestion)
from cf-conventions.
Thanks, @davidhassell; I've committed your change to the PR.
from cf-conventions.
Related Issues (20)
- Add a missing author to the list HOT 1
- Fix affiliation for Dave Allured HOT 2
- Problems in the github document build process HOT 7
- Simple correction to Example 6.1.2 HOT 5
- corrections to `units_metadata` text HOT 2
- Formatting of local links in text; Lists of Figures, Tables and Examples HOT 1
- Clarification of the use of `long_name`, `standard_name`, `cf_role` and non-standard attributes HOT 4
- Persistent removal of trailing whitespace for clean `diff`s HOT 13
- Incorporating the CFA convention for aggregated datasets into CF HOT 4
- In exceptional cases allow a standard name to be aliased into two alternatives HOT 6
- Appendix B: New element in XML file header to record the "first published date" HOT 5
- Include DOI and License information in the conventions document HOT 20
- Update the XML format specification in Appendix B to provide a robust link to the XML schema file HOT 7
- Embed images into HTML document HOT 6
- Add link status checks to PR test actions
- Boundary variables for auxiliary coordinates of more than two dimensions
- Support localization of natural language attributes and variables HOT 5
- Use of "most rapidly varying" HOT 9
- Composite/array values in string valued global attributes HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cf-conventions.