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

Unstructured data save should add UGRID to the file conventions #5030

Open
pp-mo opened this issue Oct 20, 2022 · 1 comment
Open

Unstructured data save should add UGRID to the file conventions #5030

pp-mo opened this issue Oct 20, 2022 · 1 comment

Comments

@pp-mo
Copy link
Member

pp-mo commented Oct 20, 2022

Though N.B. I believe there is still some room for doubt about what the exact result should look like.

see Netcdf User Guide Appendix A, under "conventions" :

"""It is possible for a netCDF file to adhere to more than one set of conventions, even when there is no inheritance relationship among the conventions. In this case, the value of the 'Conventions' attribute may be a single text string containing a list of the convention names separated by blank space (recommended) or commas (if a convention name contains blanks). """

So, whether "UGRID 1.0" replaces "CF 1.7", or adds to it, or whatever, not quite sure as yet.
UGRID sample files that I have seen all say just "UGRID 1.0",
( like this example in the UGRID repo )
but that will of course upset the cf-checker, since the 'adoption' relationship between the two is not yet formally agreed(as-of Oct 2022).

@pp-mo
Copy link
Member Author

pp-mo commented Apr 5, 2023

Update
CF refers to netCDF docs @4.9, which does make a statement here
( see "Conventions" in here )

It is possible for a netCDF file to adhere to more than one set of conventions, even when there is no inheritance relationship among the conventions. In this case, the value of the 'Conventions' attribute may be a single text string containing a list of the convention names separated by blank space (recommended) or commas (if a convention name contains blanks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: No status
Development

No branches or pull requests

1 participant