> Thank you all for digging into this topic! If you all agree that the > `sea_water_x_velocity` is the velocity component in the direction indicated > by the `axis = X` attribute, and if that attribute can be used on an > auxiliary coordinate variable (typically 2D for a curvilinear structured mesh > or 1D for an unstructured mesh) then that is more or less in line with what > we were hoping for. In that case, I would appreciate some guidance on -- as > @JimBiardCics suggested -- how to best propose to change the language as it > links to both the CF conventions document (related to the axis attribute on > auxiliary coordinate variables) and the standard names table.
Some Ocean Models use a NEMO tripolar model grid in the horizontal plane. This is not a projection. The is represented in netCDF with 2 2D auxiliary coordinates, providing a WGS84 latitude longitude coordinate value pair at each grid point. The axis attribute is used to indicate the `x` and `y` and to enable quantities which are solved on grid axes to be represented. This is deemed reasonable for this data, even though the `x` and `y` directions vary with respect to the coordinate reference system across locations in the horizontal grid. So, I think that the methodology described here is sound and has precedent. -- 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/252#issuecomment-610335413 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].
