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`
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:
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:
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
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