Hi all,
This is kind of a dual post since I left something on GitHub ... is issue tracking getting watched? Is it a good place for discussion?
In practice, Mesh2 is just a regular ol' 2D mesh unless you search
for the Mesh2_layers to find out it is more than that. There is a
temptation for both 2D and 3D data holders to reference Mesh2D as their
"mesh". There is some economy to re-use of the 2D mesh, and it helps to
avoid inconsistency, but the same mesh can't be used for two different data structures with different dims. It also belies the over-simplicity of the
earlier discussion of whether there should be a prescribed variable
order because now there is more than one mesh and how do you order those? My apologies if I've missed something. This seems like a common use case.
Also, in ours and many other vertical coordinate systems (Z, SZ hybrid) the number of layers will vary in shallow and deep fluids. The vertical dimension is going to be a maximum number of layers, similar to what CF would call an incomplete multidimensional array representation (http://cfconventions.org/Data/cf-conventions/cf-conventions-1.6/build/cf-conventions.html#idp6424656)
Is there a place in the UGRID standard to flag the first in-domain layer in the water column for each node or volume? This to me is distinct from being physically wet/dry at the moment, and at least in our model it is a permanent choice.
Thanks for any guidance you can give,
Eli
This is kind of a dual post since I left something on GitHub ... is issue tracking getting watched? Is it a good place for discussion?
--
You received this message because you are subscribed to the Google Groups "UGRID Interoperability" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ugrid-interoperab...@googlegroups.com.
To post to this group, send email to ugrid-inter...@googlegroups.com.
Visit this group at http://groups.google.com/group/ugrid-interoperability.
For more options, visit https://groups.google.com/d/optout.