Re: [CF-metadata] [cf-convention/cf-conventions] Reference UGRID conventions in CF (#153)

2020-10-19 Thread JonathanGregory
Dear @davidhassell Thanks for this summary. I agree with **(A)**, **(B)** and **(E)** as given. Re **(C)**, I would suggest that only the UGRID attributes which can appear on data variables should be added to CF Appendix A. If I have read the document correctly, these are `mesh`, `location`

Re: [CF-metadata] [cf-convention/cf-conventions] Reference UGRID conventions in CF (#153)

2020-10-19 Thread Ryan Abernathey
Thanks to everyone who is working through this important issues. I strongly support incorporating SGRID into this same framework. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [CF-metadata] [cf-convention/cf-conventions] State the principles for design of the CF conventions (#273)

2020-10-19 Thread David Hassell
Three weeks have elapsed with no further comment, so the changes have been merged and this issue is closed. Thanks again, David -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [CF-metadata] [cf-convention/cf-conventions] Issue 273, principles for design (#303)

2020-10-19 Thread David Hassell
Merged #303 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/pull/303#event-3894123874 This list forwards relevant notifications from Github. It is distinct from

Re: [CF-metadata] [cf-convention/cf-conventions] Reference UGRID conventions in CF (#153)

2020-10-19 Thread David Hassell
A note on the CF data model: I think that UGRID need not affect the CF data model at this time. This is because CF does not currently formalise connections between data variables, on the same or different domains. A mesh topology variable collates multiple domains (one for faces, one for