-
Notifications
You must be signed in to change notification settings - Fork 279
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
Common agreement on loading CF non-compliant NetCDF files #5165
Comments
Summary from working group conversations
Note this issue is not intended as a debate, hence why it is not posted as a discussion. The below conversations took place in real time, with a group deliberately sized to aid decision making. Outcome - our ideal implementationWhen loading NetCDF files, Iris will load all CF-compliant elements. A container of non-compliant variables and attributes will be attached to the Encourage users:
Implementation considerations
Working group summary comments
Discussion topicsEncouraging compliance in the community
Files changing from acceptable to unacceptable
Ease of massaging files to be compliant
User experience (UX)
Iris' place in the world
Ease of software development
Preferred approachesDetermined via voting.
|
Iris needs a public statement on how it handles NetCDF files that deviate from the CF conventions. This will serve multiple benefits:
Writing this statement will involve making some difficult decisions. A working group is tackling this now: @tkknight, @bjlittle, @lbdreyer, @pp-mo, @trexfeathers, @stephenworsley, @ESadek-MO, @scottrobinson02, @HGWright
Factors at play
Items affected
(please edit if you know of others)
cell_method
issues #5119Tasks
cell_method
issues #5119The text was updated successfully, but these errors were encountered: