issue_comments: 130868683

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/523#issuecomment-130868683 https://api.github.com/repos/pydata/xarray/issues/523 130868683 MDEyOklzc3VlQ29tbWVudDEzMDg2ODY4Mw== 950575 2015-08-13T22:38:57Z 2015-08-13T22:38:57Z CONTRIBUTOR

@ocefpaf To be clear, by "strongly prefer to get this fix upstream" I mostly meant that I am reluctant to include this in xray.

Great. We don't need another interpretation of the CF-standards out there!

See the WOA13 dataset above as an example of the problems this brings. The data has no calendar and use units months since. CF discourage the use of months for obvious reasons and no calendar translates to:

gregorian or standard Mixed Gregorian/Julian calendar as defined by Udunits.

Which one! Year zero is invalid in one and (kind of) accepted in the other!!

Long story short: the dataset is valid CF but it is unclear how to interpret the dates. No one cares because people using that dataset know that t16 means Autumn (Oh no wait!! I am in the South Hemisphere, so that means Spring :stuck_out_tongue_winking_eye:)

PS: Note that there is a none calendar too in the CF conventions that is more adequate for datasets like that.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   99847237