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

Prototype metadata cube saving #414

Closed
gavinevans opened this issue Jan 26, 2018 · 1 comment
Closed

Prototype metadata cube saving #414

gavinevans opened this issue Jan 26, 2018 · 1 comment
Assignees

Comments

@gavinevans
Copy link
Contributor

gavinevans commented Jan 26, 2018

As an IMPROVER developer, I want to be able to insert attributes that provide a link to a metadata description of the IMPROVER project specific metadata so that collaborators and users of the resulting files will be able to understand the meaning of the metadata.

Related issues: #412, #393

The existing load wrapper can be used in the prototype.

Following the example in metarelate/statistical-process#7 (comment), where a separate metadata cube is specified prior to saving all other cubes to a netCDF file. This metadata cube acts as a container for the references to the metadata registry.

Note that when loaded in using Iris v1.13.0, the metadata cube will not appear as a separate cube, but rather the attributes will appear as attributes on all the other cubes in the file, see metarelate/statistical-process#7 (comment) for an example. This behaviour should be checked and Mark Hedley consulted to check whether this behaviour will be retained with different versions of Iris, so this behaviour should be tested with Iris v1.13.0 and possibly more experimental Iris versions.

Acceptance criteria:

  • Create this in a branch and agree with the team that this approach is sensible.
  • Modify the load wrapper, so that only the data cube is loaded, rather than the metadata container.
  • Re-create acceptance results related to the "form of difference" attribute to prototype how this would work.
  • Do not recreate every single known good output acceptance test. This will be captured in a follow-on issue, if appropriate.
  • Talk through results with Mark Hedley.
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

3 participants