@davidhassell that's okay, I'll try to explain things as I see them in
different ways and see if I can help.
Be careful of reused terminology, which doesn't always mean the same thing in
different contexts.
There is no 'mapping' of 2D variables representing coordinate values to one
axis.
I'll try name-spacing, to see if this helps. A cf_axis is not the same concept
as a crs_wkt_axis.
A crs_wkt_axis is a coordinate reference system concept and is all about how
the basis vectors in the CRS are defined and how individual positions are
represented as an ordered tuple of coordinate values.
A cf_axis is a data structure concept which is all about how the data and
locational metadata are laid down as a set of structured arrays with dimension
references.
Given:
* two 2-d auxiliary coordinate variables, each of which span the same two
cf_axes.
Wanted:
* pairs of values (tuples) from each of these auxiliary coordinate variables
* within each pair, the order of values is defined by the crs_wkt_axis order
So, we take the two 2-d variables and for each index location, make a tuple,
ordered by the crs_wkt_axis order
e.g.
CDL
```
foo:grid_mapping = "crs:x y"
x = [[1, 2, 3],
[4, 5, 6]]
y = [[11, 12, 13],
[14, 15, 16]]
```
crs_wkt application ready output
```
coord_tuples = [[(1, 11), (2, 12), (3, 13)],
[(4, 14), (5, 15), (6, 16)]]
```
does this help to demonstrate the different concepts at work here?
mark
--
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/223#issuecomment-571998387
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].
