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

Optimal metadata for a daytime maximum #12

Open
gavinevans opened this issue Feb 7, 2018 · 0 comments
Open

Optimal metadata for a daytime maximum #12

gavinevans opened this issue Feb 7, 2018 · 0 comments

Comments

@gavinevans
Copy link

As a developers, we need to have a clear way of recording that the contents of a file is a "daytime maximum", so that this can be differentiated from other files.

For calculating a daytime maximum screen temperature, it is necessary to take files over a period e.g. 09Z to 21Z and calculate the maximum. Currently the only knowledge that a daytime maximum has been calculated is within the filename, for example:

temperature_at_screen_level_daytime_max / (K) (time: 1; percentile: 1; index: 121)
     Dimension coordinates:
          time                                     x              -         -
          percentile                               -              x         -
          index                                    -              -         x
     Auxiliary coordinates:
          forecast_period                          x              -         -
          altitude                                 -              -         x
          latitude                                 -              -         x
          longitude                                -              -         x
     Scalar coordinates:
          forecast_reference_time: 2017-10-13 04:00:00
          height: 1.5 m
     Cell methods:
          weighted_mean: model

The fact that a maximum has been calculated is typically recorded in the cell method. However, it is not clear how to specify the time period over which the maximum has been calculated.

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