@davidhassell I agree with @marqh. All of this does, in a sense, represent a generalization from the way that CF historically made use of the **`grid_mapping`** attribute and variable. In the past, this information was considered to provide information about how to map from x,y to lat,lon when x and y were 1D and lat and lon were 2D. (The insufficiency of the information provided to actually accomplish this to a high degree of accuracy is a different issue.) In truth you could use the same information to perform the reverse mapping, but we weren't thinking about it that way.
A full and proper representation of any set of coordinate value tuples, regardless of array dimensionality, requires an associated CRS. The expanded **`grid_mapping`** scheme makes this possible. This is why it's important to allow both "true" coordinates and auxiliary coordinates to be specified in the attribute. -- 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-572095602 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].
