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
I keep getting these warnings when reading grib wind data files from NOAA. Logs says it's coming from gribberish, but is it actually coming from xarray?
Not a life ending problem, but it is flooding my logs to the point where they become unreadable. Using newest version of xarray/gribberish, but was same before. Can't really convert to "nanosecond precision" since files are from NOAA.
.venv/lib/python3.13/site-packages/gribberish/gribberish_backend.py:50: UserWarning: Converting non-nanosecond precision datetime values to nanosecond precision. This behavior can eventually be relaxed in xarray, as it is an artifact from pandas which is now beginning to support non-nanosecond precision values. This warning is caused by passing non-nanosecond np.datetime64 or np.timedelta64 values to the DataArray or Variable constructor; it can be silenced by converting the values to nanosecond precision ahead of time.
[[package]]
name = "gribberish"
version = "0.21.2"
[[package]]
name = "xarray"
version = "2025.1.1"
The text was updated successfully, but these errors were encountered:
Hi Matthew,
I keep getting these warnings when reading grib wind data files from NOAA. Logs says it's coming from gribberish, but is it actually coming from xarray?
Not a life ending problem, but it is flooding my logs to the point where they become unreadable. Using newest version of xarray/gribberish, but was same before. Can't really convert to "nanosecond precision" since files are from NOAA.
.venv/lib/python3.13/site-packages/gribberish/gribberish_backend.py:50: UserWarning: Converting non-nanosecond precision datetime values to nanosecond precision. This behavior can eventually be relaxed in xarray, as it is an artifact from pandas which is now beginning to support non-nanosecond precision values. This warning is caused by passing non-nanosecond np.datetime64 or np.timedelta64 values to the DataArray or Variable constructor; it can be silenced by converting the values to nanosecond precision ahead of time.
The text was updated successfully, but these errors were encountered: