> So, the CF 'topology construct' can only be atttached to a single domain axis 
> of a domain.
That means that UGRID data which maps to a different mesh location is modelled 
as belonging to a separate, independent "domain".
> This seems okay for now, but it means of course that the CF decsription has 
> no concept of the intercoupled nature of the different locations.

> (2) likewise, the CF description has no place for the cross-location 
> connectivities (like face-edge-connectivity)

> So, I'm not sure where any of that might become practically relevant, but I'm 
> still a little worried that they aren't really describing the same ideas with 
> the same range of possibilities.

I"m concerned as well. ONe thing that's become clear to me working with these 
botu unstructured and "staggered" grids in the last few years is that the 
entire "mesh" or whatever we want to call it, is one "thing". That is, you 
cannot treat the collection of nodes, the collection of faces, the collection 
of edges, each as a separate meshes. Sure, data may be associated specifically 
with only one of these, but, for example:

If values on the nodes ar treated as their own thing, you can plot them fine -- 
but if you need to interpolate the values, you need to know how the faces are 
defined.

Values on the edges, similarly, culd be plotted, but and edge is very much an 
interace between two faces -- it does not live on its own at all.

And boundaries are again, very much properties of the faces.

I'm still not clear what a "domain axis" means in the CF data model, but we 
really do need to capture the concept that the mesh is not unrelated pieces, it 
is one thing -- you can't really know what any of the data fully means without 
the full mesh description.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/153*issuecomment-885125597__;Iw!!G2kpM7uM-TzIFchu!ga5Gxvq29rUYNROdSmC8Gq3nbdYm3dyxuCNXBtNWLyjyXsQnfof3_1B0IELF8TO15z7fO1BD8FQ$
 
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].

Reply via email to