Hello, I have been looking at the Finite Element based CF proposal for Unstructured Grid data model (https://publicwiki.deltares.nl/display/NETCDF/Finite+Element+based+CF+proposal+for+Unstructured+Grid+data+model) which was written up some time ago by Bert. This proposes an encoding for the information required for a consistent spatial interpretation of the values.
Given that UGRID is going to be incorporated into CF _[1]_, I was looking at this with to see if backward incompatible changes could occur if this new proposal (or something like it) become part of UGRID at a later date. _[1] it seems like this will indeed happen, once the management side is sorted out ..._ My conclusion from a quick read of Bert's document was that adding the "Function Space" capability, would not impact on files encoded using UGRID 1.0 - which would be good. However, the proposal does suggest renaming certain special attributes (e.g. `face_node_connectivity` becomes `element_vertex_connectivity`). This could be bad for CF backwards compatibility, but, I presume, is easily avoided with a little thought at this stage. Does all this sound like a a reasonable assessment? Thanks, David -- 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/issues/153#issuecomment-572043075 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
