Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential Issue -- Computed Standard Names check examines variable(s) examines s_rho #722

Open
daltonkell opened this issue Jan 27, 2020 · 0 comments

Comments

@daltonkell
Copy link
Contributor

In testing this dataset http://tds.eds.ioos.us/thredds/dodsC/ioos/ofs/dbofs/forecast/fields/DBOFS_Forecast_Fields_best.ncd, the Compliance Checker yields a result for the computed_standard_name:

§4.3 Vertical Coordinate
* §4.3.3 The standard_name of `s_rho` must map to the correct computed_standard_name, `{'height_above_mean_sea_level', 'altitude', 'height_above_reference_ellipsoid', 'height_above_geopotential_datum'}`
* §4.3.3 The standard_name of `s_w` must map to the correct computed_standard_name, `{'height_above_mean_sea_level', 'altitude', 'height_above_reference_ellipsoid', 'height_above_geopotential_datum'}`

Both s_rho and s_w are dimensionless vertical coordinates. They each have a formula_terms attribute, and the variables listed there should map to a computed_standard_name, but not s_w or s_rho (see here). As a result, these messages should not appear. @benjwadams could you double check my understanding?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant