In a current project, we have a similiar use case as @hrajagers : our projected x/y coordinates depend on two dimensions. Our wind `x_wind` and `y_wind` blows along the coordinate axes (the 1d-ones).
``` int i(i) ; ... int j(j) ; ... double x(j, i) ; x:standard_name = "projection_x_coordinate" ; ... double y(j, i) ; y:standard_name = "projected_y_coordinate" ; ... double lon(j, i) ; lon:standard_name = "longitude" ; ... double lat(j, i) ; lat:standard_name = "latitude" ; ... float x_wind(j, iv) ; x_wind:standard_name = "x_wind" ; ... float y_wind(jv, i) ; y_wind:standard_name = "y_wind" ; ... ``` I added the `i(i)` and `j(j)` variables so that the user will (hopefully) wonder if the x-wind is orientated along the axis with `...:standard_name = 'projected_x_coordinate'` or along the 1d coordinate axis. Maybe, we should also rename our variable `x` and `y`. New standard names like `wind_along_dimension_one`, `wind_along_dimension_two`, `sea_water_velocity_along_dimension_one`, ... would be the most simple solution for clearly indicating the situation described in item (1) of the initial post of Bert. Similarly, one could add standard names like `wind_along_coordinate_variable_one`, ... to indicate that the wind is oriented as described in item (2) of the initial post of Bert. In addition, one needed to specify the `coordinates` attribute properly and provide the coordinate axis in _correct_ order (which is not necessary up till now). -- 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-609892771 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].
