You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.
CF recommends that the units of latitude and longitude are set to degrees_north or degrees_east. One reasoning they give is that "Udunits package does not recognize the directionality implied by the "north" part of the unit specification".
I therefore suggest that, if the user selects south or west, rosetta switches the sign of the data and produce output netcdf file with north/east values, as recommended.
The text was updated successfully, but these errors were encountered:
Also just noticed that in the variable specifications, degree_north is used and in platform specification, degrees_north. Both are recognized and accepted by udunits, but wouldn't it be an idea to stay consistent? :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CF recommends that the units of latitude and longitude are set to degrees_north or degrees_east. One reasoning they give is that "Udunits package does not recognize the directionality implied by the "north" part of the unit specification".
http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#latitude-coordinate
I therefore suggest that, if the user selects south or west, rosetta switches the sign of the data and produce output netcdf file with north/east values, as recommended.
The text was updated successfully, but these errors were encountered: