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
Is your feature request related to a problem? Please describe.
The time variable is called time for most netcdf datasets around. Since the update to the "new CDS", the data retrieved from CDS instead has a time variable called valid_time. This is inconvenient in our processes, so we rename it. I understand it is only a minor edit we have to do, but I was wondering if it could be considered to rename it back to time anyway.
Describe the solution you'd like
Rename the time variable to time instead of valid_time
Describe alternatives you've considered
Our current workaround, renaming the variable ourselves.
Additional context
No response
Organisation
Deltares
The text was updated successfully, but these errors were encountered:
Yes, this is one of the things that broke my workflow as well, and it is quite inconvenient to do this kind of compat breaking changes in the upstream. It's an unfortunate and hard to justify change.
Is your feature request related to a problem? Please describe.
The time variable is called
time
for most netcdf datasets around. Since the update to the "new CDS", the data retrieved from CDS instead has a time variable calledvalid_time
. This is inconvenient in our processes, so we rename it. I understand it is only a minor edit we have to do, but I was wondering if it could be considered to rename it back totime
anyway.Describe the solution you'd like
Rename the time variable to
time
instead ofvalid_time
Describe alternatives you've considered
Our current workaround, renaming the variable ourselves.
Additional context
No response
Organisation
Deltares
The text was updated successfully, but these errors were encountered: