-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time variables with "nanoseconds" units fail to load #192
Comments
Can you open an issue for the nanoseconds support at JuliaGeo/CFTime.jl ? I will handle it there . Maybe this part is already resolved:
Yes, this one should be easy to address. In fact, I just committed this in Can you confirm that it also work for you (with the master version of CFTime)?
If you can share an example file, that would also be useful. (A file with random data still reproducing the issue is also fine). |
Thanks for the fix.
Ok, will do that.
Yes, it works now with floats and missing values.
I think the issue was just handling the missing values in the input, but I can provide an example file if you still need it. |
Thanks a lot! In fact, as the missing value issue is solved, I have everything to reproduce the issue with the time units (so no need to upload an example). |
Hi,
Apologies if this is the wrong place to address this. I want to combine files that were split into yearly chunks back to one big one. A task that is easy to do in python with
xarray
usingmfdataset
orconcat
, but in julia I am failing miserably, or I am missing something obvious. Any pointers would be highly appreciated.It looks like
NCDatasets
(or whatever) stumbles upon time variables with units "nanoseconds since ..."Accessing the "time" variable now raises a warning, as discussed in #173
However according to the comment #181 (comment), "nanoseconds" should be a valid unit.
Manually converting with "seconds" works fine:
However, the same trick fails with a different file where
time
is float and contains missing values, but that may be a different issue:Environment
The text was updated successfully, but these errors were encountered: