issues: 185441216

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
185441216 MDU6SXNzdWUxODU0NDEyMTY= 1062 Add remaining date units to conventions.py 12307589 closed 0     6 2016-10-26T16:14:44Z 2019-02-24T21:25:39Z 2019-02-24T21:25:39Z CONTRIBUTOR      

Currently _netcdf_to_numpy_timeunit in conventions.py (seemingly) artificially imposes that weeks, months, and years can't be used as time units, despite some of these being CF-compliant (months, years), and datetime64 supporting these units.

Are these possibly disabled because of the way Udunits defines these units?

From CF conventions:

We recommend that the unit year be used with caution. The Udunits package defines a year to be exactly 365.242198781 days (the interval between 2 successive passages of the sun through vernal equinox). It is not a calendar year. Udunits includes the following definitions for years: a common_year is 365 days, a leap_year is 366 days, a Julian_year is 365.25 days, and a Gregorian_year is 365.2425 days.

For similar reasons the unit month, which is defined in udunits.dat to be exactly year/12, should also be used with caution.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1062/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables