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

Add cf-conventions from technical point of view. #15

Open
paolap opened this issue Oct 18, 2021 · 3 comments
Open

Add cf-conventions from technical point of view. #15

paolap opened this issue Oct 18, 2021 · 3 comments
Assignees

Comments

@paolap
Copy link
Contributor

paolap commented Oct 18, 2021

We should include a page explaining why some attributes are particularly important, listing examples of how they are used by software, and what they can break when absent/wrong

@paolap
Copy link
Contributor Author

paolap commented Oct 20, 2022

This is nearly complete, just need to review maybe add groups??
And possibly implications of multiple time dimensions see #49

@paolap
Copy link
Contributor Author

paolap commented Dec 8, 2022

I'll try to clarify here the dimensions types and implications and then this should be complete

@paolap
Copy link
Contributor Author

paolap commented Jun 16, 2023

Reviewing this and this BigData issue:
ACDguide/BigData#88

which implies we should move the content at the bottom of this file to the Governance book:

https://github.com/ACDguide/BigData/blob/main-backup-221027/BigData/format_metadata.md

I think we could add something as:

CDO expect time to be first dimension
xarray can have issues opening files with:

  • groups
  • several time dimension (see some UM output) what happens is when using open_mfdataset() the variables will be concatenated along more when time axis
  • file with conflicting definition of a dimension and it's associated variable i.e:
    dimensions:
    lat = 129 ;
    lon = 185 ;
    variables:
    float lat(lat, lon) ;
    lat:long_name = "latitude" ;
    lat:units = "degrees_north" ;
    lat:standard_name = "latitude" ;
    float lon(lat, lon) ;
    lon:long_name = "longitude" ;
    lon:units = "degrees_east" ;
    lon:standard_name = "longitude" ;

This is definitely bad practice still there are datasets around doing this

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