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
We've had some similar discussions in the past, how to identify time variables / dimensions / coordinates, following CF conventions, with or without access to udunits, and so on. Annick recently brought this up again (although more aimed at regrid), related discussion on Slack in #ops-development: https://metocean.slack.com/archives/C014SM7A5AN/p1680230791844669 .
The text was updated successfully, but these errors were encountered:
And at the moment, I'm pretty sure we're not requiring that name by convention (CF 1.10 definitely doesn't care: "This convention does not standardize any variable or dimension names.", and we don't mention it in our API conventions 1.1.1 either), so that combo is of course not ideal... :)
We've had some similar discussions in the past, how to identify time variables / dimensions / coordinates, following CF conventions, with or without access to udunits, and so on. Annick recently brought this up again (although more aimed at regrid), related discussion on Slack in #ops-development: https://metocean.slack.com/archives/C014SM7A5AN/p1680230791844669 .
The text was updated successfully, but these errors were encountered: