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

CF compliance work #7

Open
wants to merge 18 commits into
base: master
Choose a base branch
from
Open

CF compliance work #7

wants to merge 18 commits into from

Conversation

leifdenby
Copy link
Collaborator

@leifdenby leifdenby changed the title Cf compliance refactor CF compliance work May 19, 2018
@leifdenby
Copy link
Collaborator Author

@sjboeing I've been thinking about this work and I would like to get it into our fork. I was thinking that I could make the functionality opt-in rather than default. That way it wouldn't change default behaviour, but if someone asks for units, longname attributes etc they could enable this.

Specifically when enabled it would require that for all scalar fields it is defined: 1) what grid the variable exists on (staggered or non-staggered in each dimension), 2) what the units of the field are and 3) what the "longname" of the field is (and optionally the "standard_name" can be provided too.

Thoughts?

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

Successfully merging this pull request may close these issues.

1 participant