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

Extend axis identifiers to include probabilistic dimensions #8

Open
fionaRust opened this issue Oct 24, 2017 · 5 comments
Open

Extend axis identifiers to include probabilistic dimensions #8

fionaRust opened this issue Oct 24, 2017 · 5 comments

Comments

@fionaRust
Copy link

As developers we want to be able to use a short hand way of accessing the probabilistic dimensions on a cube without searching for a coordinate name.

Within Iris we can access spatial and time dimension using axis="T" or axis="X" etc. We would like to do the same for ensemble, percentiles and probabilities.

Note this may not be the best place for this ticket

@bayliffe
Copy link

See CF proposals for an E axis identifier to denote an ensemble/realization axis. It is in this vein that we think additional identifiers would be extremely useful for denoting types of probabilistic data.

@bayliffe
Copy link

As an alternative we could decide to use the 'var_name' to store the barest description of the data being stored, thus eliminating the need to pass the more complicated 'name' element. In this situation the 'percentiles_over_realizations' coordinate would have 'var_name' of just 'percentiles', functioning as an easy identifier of the different probabilistic data axes.

@marqh
Copy link
Member

marqh commented Oct 25, 2017

See CF proposals for an E axis identifier to denote an ensemble/realization axis. It is in this vein that we think additional identifiers would be extremely useful for denoting types of probabilistic data.

there was a varied discussion about adding new axis labels within CF but it did not reach a positive conclusion, there were concerns about expanding this capability beyond X, Y, Z or T.

I think that axis label metadata will struggle to live up to your requirements

@marqh
Copy link
Member

marqh commented Oct 25, 2017

I think that the use of controlled var_name within software is a common pattern and can be made to be robust through good design.

I think that this could provide a useful pattern for you, without being overly constraining.

@bayliffe
Copy link

bayliffe commented May 2, 2019

@marqh we are closing our local copy of this ticket as we are unlikely to return to this issue any time soon. I do not have permission to close tickets in this repository, so please close it when possible. Thanks.

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