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 Dec 13, 2021. It is now read-only.
Hesitant to raise this issue because it felt above my head to diagnose, but here is a synopsis of deeper issue of an original question raised here on stackoverflow.
Original question was how to convert dates of a netcdf file, read into R using ncdf4::nc_open() that had units of "minutes since 1850-01-16T14:06:00"
Through exploring answers to the question we noticed that we could answer the original question of how to convert the dates, but the outputs never aligned with the expected results, which we knew from opening the same file in {xarray} and panoply. With the ultimate solution resulting in multiplying the time dimension by sixty before converting to datetime (which is counterintuitive to the netcdf units) and then correcting the alignment of the day.
I guess the larger question is whether anyone else has encountered this mismatch of time/attributes across packages.
Happy to provide more context if there is an avenue to diagnosing the issue. Also understand if this is an edge case where the juice is not worth the squeeze. Appreciate the work you do.
The text was updated successfully, but these errors were encountered:
Not sure if this helps anything but it seems to be linked to the date structure, which is handled by cftimes by xarray. If this is something you are already aware of I can close the issue.
Hi this is just an old copy of ncdf4, where I was experimenting with windows support - to get fixes into the package you need to contact the author directly.
fwiw on SO I think the answer needs to not assume local time, but there's no information about whether a time zone is in use, the question doesn't include the full header output but it really needs that at least
Hesitant to raise this issue because it felt above my head to diagnose, but here is a synopsis of deeper issue of an original question raised here on stackoverflow.
Original question was how to convert dates of a netcdf file, read into R using ncdf4::nc_open() that had units of "minutes since 1850-01-16T14:06:00"
Through exploring answers to the question we noticed that we could answer the original question of how to convert the dates, but the outputs never aligned with the expected results, which we knew from opening the same file in {xarray} and panoply. With the ultimate solution resulting in multiplying the time dimension by sixty before converting to datetime (which is counterintuitive to the netcdf units) and then correcting the alignment of the day.
I guess the larger question is whether anyone else has encountered this mismatch of time/attributes across packages.
Happy to provide more context if there is an avenue to diagnosing the issue. Also understand if this is an edge case where the juice is not worth the squeeze. Appreciate the work you do.
The text was updated successfully, but these errors were encountered: