{"action":"created","issue":{"url":"https://api.github.com/repos/pydata/xarray/issues/869","repository_url":"https://api.github.com/repos/pydata/xarray","labels_url":"https://api.github.com/repos/pydata/xarray/issues/869/labels{/name}","comments_url":"https://api.github.com/repos/pydata/xarray/issues/869/comments","events_url":"https://api.github.com/repos/pydata/xarray/issues/869/events","html_url":"https://github.com/pydata/xarray/issues/869","id":158518147,"number":869,"title":"open netCDF gives 'time' dim with 1969 change in timezone","user":{"login":"brews","id":2049051,"avatar_url":"https://avatars.githubusercontent.com/u/2049051?v=3","gravatar_id":"","url":"https://api.github.com/users/brews","html_url":"https://github.com/brews","followers_url":"https://api.github.com/users/brews/followers","following_url":"https://api.github.com/users/brews/following{/other_user}","gists_url":"https://api.github.com/users/brews/gists{/gist_id}","starred_url":"https://api.github.com/users/brews/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brews/subscriptions","organizations_url":"https://api.github.com/users/brews/orgs","repos_url":"https://api.github.com/users/brews/repos","events_url":"https://api.github.com/users/brews/events{/privacy}","received_events_url":"https://api.github.com/users/brews/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-04T18:46:38Z","updated_at":"2016-06-04T19:47:39Z","closed_at":"2016-06-04T19:47:39Z","body":"I'm on xarray version 0.7.2\r\nnetCDF4-python version 1.2.2\r\nPython version via Conda: 3.5.1 |Continuum Analytics, Inc.| (default, Dec  7 2015, 11:16:01)  [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)]\r\n\r\nThe `time` dim on Datasets read in from netCDF files seems to change timezones in 1969. This is especially a pain for annual data because the bug causes annual indexes to shift by one year. I've seen this problem in reanalysis for NCEP/NCAR, Twentieth Century Reanalysis, and some reconstructed SST fields.\r\n\r\nFor example, if a read in a netCDF file. Take NCEP/NCAR Reanalysis 1 monthly mean geopotential height as an example (ftp://ftp.cdc.noaa.gov/Datasets/ncep.reanalysis.derived/pressure/hgt.mon.mean.nc ; a 278 MB file).\r\n\r\n```python\r\nimport xarray as xr\r\n\r\nds = xr.open_dataset('~/Downloads/hgt.mon.mean.nc')\r\nprint(ds.time)\r\n```\r\n\r\nThe interesting part of this printed time dim is always around 1969:\r\n\r\n       ...\r\n       '1969-09-01T00:00:00.000000000Z', '1969-10-01T00:00:00.000000000Z',\r\n       '1969-11-01T00:00:00.000000000Z', '1969-12-01T00:00:00.000000000Z',\r\n       '1969-12-31T17:00:00.000000000-0700',\r\n       '1970-01-31T17:00:00.000000000-0700',\r\n       '1970-02-28T17:00:00.000000000-0700',\r\n        ...\r\n\r\nYou can see we go from `Z` to`-0700`. It also gives me an extra measure for Dec 1969 :-\\\r\n\r\nI don't think this is a hidden calendar or datetime-like feature that I'm unaware of...? Seems like a bug with you guys or upstream.\r\n\r\nThanks for your help!\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/pydata/xarray/issues/comments/223774592","html_url":"https://github.com/pydata/xarray/issues/869#issuecomment-223774592","issue_url":"https://api.github.com/repos/pydata/xarray/issues/869","id":223774592,"user":{"login":"brews","id":2049051,"avatar_url":"https://avatars.githubusercontent.com/u/2049051?v=3","gravatar_id":"","url":"https://api.github.com/users/brews","html_url":"https://github.com/brews","followers_url":"https://api.github.com/users/brews/followers","following_url":"https://api.github.com/users/brews/following{/other_user}","gists_url":"https://api.github.com/users/brews/gists{/gist_id}","starred_url":"https://api.github.com/users/brews/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brews/subscriptions","organizations_url":"https://api.github.com/users/brews/orgs","repos_url":"https://api.github.com/users/brews/repos","events_url":"https://api.github.com/users/brews/events{/privacy}","received_events_url":"https://api.github.com/users/brews/received_events","type":"User","site_admin":false},"created_at":"2016-06-04T19:47:39Z","updated_at":"2016-06-04T19:47:39Z","body":"@fmaussion Yes this solves the problem! Closed.\r\n\r\nNow the problem is that my Basemap and Cartopy 0.14 in conda currently depend on numpy 1.10*. This puts me in Dependency Hell.\r\n\r\nDoes anyone happen to have a channel for these (or at least Cartopy 0.14) that will work with numpy 1.11*?"}}
{"actor":{"display_login":"brews"}}