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

Run file through CF 1.8 compliance checker before release OG1.0 #139

Open
vturpin opened this issue Apr 25, 2023 · 3 comments
Open

Run file through CF 1.8 compliance checker before release OG1.0 #139

vturpin opened this issue Apr 25, 2023 · 3 comments
Labels
1.0 For stuff that must be resolved before we are able to release 1.0

Comments

@vturpin
Copy link
Member

vturpin commented Apr 25, 2023

moderator: @OceanGlidersCommunity/format-maintainers

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Need to run file through CF 1.8 compliance checker produce CDL and file, and update documentation with the trajectory template to be used.

Is this related to a specific platform models
No

Describe the solution you'd like

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@vturpin vturpin added the 1.0 For stuff that must be resolved before we are able to release 1.0 label Apr 25, 2023
@castelao
Copy link
Member

CF-1.8 or CF-1.10? Any reason why not to use CF1.10?

@vturpin
Copy link
Member Author

vturpin commented Feb 12, 2024

This is related to #130 I think and #136 .
Reason I understand so far is the unavailability of CF1.10 compliance checker.

@emmerbodc
Copy link
Collaborator

Ran file sea076_20230906T0852_R.nc through 1.08 version checker.

5 errors

It's not liking the string variables -

Checking variable: TRAJECTORY

ERROR: (2.2): Invalid variable type: <class 'netCDF4._netCDF4.VLType'>: string type (vlen types not supported)
INFO: attribute cf_role is being used in a non-standard way

I think @castelao this is fixed in 1.10?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.0 For stuff that must be resolved before we are able to release 1.0
Projects
None yet
Development

No branches or pull requests

3 participants