Hello,
In starting to think about:
> (H) Further to the discussion on implications on the CF data model
> (ugrid-conventions/ugrid-conventions/issues/52), the CF data model needs to
> be updated to allow the storage of topological connections between cells
> ("cells" in the CF data model sense). It is not necessary at this stage for
> the connectivity between cell elements (such as the edge of a face) to be a
> part of the CF data model.
For the one case that I thought was not possible in the current CF data model,
i.e. a [1D network
topology](https://urldefense.us/v3/__https://ugrid-conventions.github.io/ugrid-conventions/*1d-network-topology__;Iw!!G2kpM7uM-TzIFchu!gkEbRVWDm8OAd0GAR_p9pl8dtYki7o7-HSGJLjtIHnNlpvKRtYuQk9d3o7xJUf_EfmafcA7vglQ$
),
I now realise the current data model is OK. I was thinking that in this case
the CF domain cells were the nodes, but really a cell is an edge bounded by
two nodes. In this view, the existing CF framework suffices. Remember that the
CF data model is independent of the netCDF encoding, including the UGRID. It
doesn't matter if the CF data model view of the world looks quite different to
that of the UGRID view, as long as it is possible to unambiguously map between
the two.
Thanks,
David
--
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-871255936__;Iw!!G2kpM7uM-TzIFchu!gkEbRVWDm8OAd0GAR_p9pl8dtYki7o7-HSGJLjtIHnNlpvKRtYuQk9d3o7xJUf_EfmafUs7YDn8$
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].
