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/814#issuecomment-355011878,https://api.github.com/repos/pydata/xarray/issues/814,355011878,MDEyOklzc3VlQ29tbWVudDM1NTAxMTg3OA==,10050469,2018-01-03T13:30:25Z,2018-01-03T13:30:25Z,MEMBER,Indeed. Thanks to all people involved!,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-354980754,https://api.github.com/repos/pydata/xarray/issues/814,354980754,MDEyOklzc3VlQ29tbWVudDM1NDk4MDc1NA==,810663,2018-01-03T10:33:21Z,2018-01-03T10:33:21Z,NONE,Closed by #1750?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-348357025,https://api.github.com/repos/pydata/xarray/issues/814,348357025,MDEyOklzc3VlQ29tbWVudDM0ODM1NzAyNQ==,1217238,2017-11-30T23:41:55Z,2017-11-30T23:41:55Z,MEMBER,"I think either way works. Probably easiest to fork this branch and then
merge in the latest from master.
On Thu, Nov 30, 2017 at 3:38 PM Neil Parley
wrote:
> I think also I could make you a contributor or transfer the branch to
> someone. So that might be an option too.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
>
> .
>
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-348225565,https://api.github.com/repos/pydata/xarray/issues/814,348225565,MDEyOklzc3VlQ29tbWVudDM0ODIyNTU2NQ==,6215361,2017-11-30T15:38:57Z,2017-11-30T15:38:57Z,NONE,I think also I could make you a contributor or transfer the branch to someone. So that might be an option too.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-348221278,https://api.github.com/repos/pydata/xarray/issues/814,348221278,MDEyOklzc3VlQ29tbWVudDM0ODIyMTI3OA==,3169620,2017-11-30T15:25:44Z,2017-11-30T15:25:44Z,CONTRIBUTOR,"I'm happy to pick this up - I'm not sure how best to pick up someone else's pull request though. Am I best off forking nparley:master then resubmitting, or creating a new one and merging in the changes from nparley:master?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-309810114,https://api.github.com/repos/pydata/xarray/issues/814,309810114,MDEyOklzc3VlQ29tbWVudDMwOTgxMDExNA==,1217238,2017-06-20T16:14:36Z,2017-06-20T16:14:36Z,MEMBER,"No worries! The great thing about GitHub is that it's pretty easy for
someone else to pick up your work :)
On Tue, Jun 20, 2017 at 12:25 AM, Neil Parley
wrote:
> Sorry guys I don't have time to do anything on this (or any open source
> stuff) at the moment.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
>
> .
>
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-309667894,https://api.github.com/repos/pydata/xarray/issues/814,309667894,MDEyOklzc3VlQ29tbWVudDMwOTY2Nzg5NA==,6215361,2017-06-20T07:25:11Z,2017-06-20T07:25:11Z,NONE,Sorry guys I don't have time to do anything on this (or any open source stuff) at the moment. ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-309485895,https://api.github.com/repos/pydata/xarray/issues/814,309485895,MDEyOklzc3VlQ29tbWVudDMwOTQ4NTg5NQ==,1217238,2017-06-19T16:02:00Z,2017-06-19T16:02:00Z,MEMBER,"Yes, we would still love to get this in, though it might need a few other
changes to work now. Could you open a new PR with the tests added back in?
(Assuming Neil is not interested in picking this back up)
On Mon, Jun 19, 2017 at 8:58 AM, DWesl wrote:
> If you're still looking for the old tests, it looks like they disappeared
> in the last merge commit, f48de5
>
> .
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or mute
> the thread
>
> .
>
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-309484883,https://api.github.com/repos/pydata/xarray/issues/814,309484883,MDEyOklzc3VlQ29tbWVudDMwOTQ4NDg4Mw==,22566757,2017-06-19T15:58:27Z,2017-06-19T15:58:27Z,CONTRIBUTOR,"If you're still looking for the old tests, it looks like they disappeared in the last merge commit, [f48de5](https://github.com/pydata/xarray/pull/814/commits/f48de5a3ea916b80a7bfc070c3c1c3549e931189#diff-48ab4ba033ad06981f566a2e2f561f5aL1819).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-262383397,https://api.github.com/repos/pydata/xarray/issues/814,262383397,MDEyOklzc3VlQ29tbWVudDI2MjM4MzM5Nw==,6215361,2016-11-22T22:21:15Z,2016-11-22T22:21:15Z,NONE,"This did used to have some tests, but they seem to have got lost somewhere along the way. I'll add the old tests back in, which would be a start.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-262372139,https://api.github.com/repos/pydata/xarray/issues/814,262372139,MDEyOklzc3VlQ29tbWVudDI2MjM3MjEzOQ==,1217238,2016-11-22T21:32:57Z,2016-11-22T21:32:57Z,MEMBER,"> This is looking pretty comprehensive to me. Could maybe do with a couple of tests perhaps, but otherwise :+1: .
Indeed, merging this is really just blocked on tests right now. We need at least *something* so we can verify that this basically works.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-262359050,https://api.github.com/repos/pydata/xarray/issues/814,262359050,MDEyOklzc3VlQ29tbWVudDI2MjM1OTA1MA==,810663,2016-11-22T20:39:23Z,2016-11-22T20:39:23Z,NONE,"This is looking pretty comprehensive to me. Could maybe do with a couple of tests perhaps, but otherwise 👍 .","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-238586208,https://api.github.com/repos/pydata/xarray/issues/814,238586208,MDEyOklzc3VlQ29tbWVudDIzODU4NjIwOA==,6215361,2016-08-09T15:15:53Z,2016-08-09T15:15:53Z,NONE,"This adds the extra code that @pelson suggested but it would be nice to create a little unit test with a mixed Dimension and Auxiliary coordinates. Is there an easy way to create a simple cube in Iris that could test this?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-228703831,https://api.github.com/repos/pydata/xarray/issues/814,228703831,MDEyOklzc3VlQ29tbWVudDIyODcwMzgzMQ==,810663,2016-06-27T10:00:54Z,2016-06-27T10:00:54Z,NONE,"> @pelson @rhattersley any tips on handling the edge cases of cubes with some, but not all missing dim_coords?
I might consider something like (untested):
```
for dim in xrange(cube.ndim):
try:
dim_coord = cube.coord(dim_coords=True, dimensions=(dim,))
except iris.exceptions.CoordinateNotFoundError:
index_coord = range(cube.shape[dim])
```
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-228608416,https://api.github.com/repos/pydata/xarray/issues/814,228608416,MDEyOklzc3VlQ29tbWVudDIyODYwODQxNg==,1217238,2016-06-26T16:04:11Z,2016-06-26T16:04:11Z,MEMBER,"No worries, no rush here from my end :).
On Sun, Jun 26, 2016 at 1:35 PM Neil Parley notifications@github.com
wrote:
> @shoyer https://github.com/shoyer I have not forgotten about this PR, I
> just been working a lot on a pandas PR updating the ci and it's been taking
> up a lot of my spare time.
>
> —
> You are receiving this because you were mentioned.
>
> Reply to this email directly, view it on GitHub
> https://github.com/pydata/xarray/pull/814#issuecomment-228596914, or mute
> the thread
> https://github.com/notifications/unsubscribe/ABKS1tPi3K7IyPa2MwwQWDfnrwMemmetks5qPmQJgaJpZM4H9jGH
> .
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-228596914,https://api.github.com/repos/pydata/xarray/issues/814,228596914,MDEyOklzc3VlQ29tbWVudDIyODU5NjkxNA==,6215361,2016-06-26T11:35:36Z,2016-06-26T11:35:36Z,NONE,"@shoyer I have not forgotten about this PR, I just been working a lot on a pandas PR updating the ci and it's been taking up a lot of my spare time.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-228414378,https://api.github.com/repos/pydata/xarray/issues/814,228414378,MDEyOklzc3VlQ29tbWVudDIyODQxNDM3OA==,1217238,2016-06-24T17:51:42Z,2016-06-24T17:51:42Z,MEMBER,"@pelson @rhattersley any tips on handling the edge cases of cubes with some, but not all missing dim_coords?
@nparley I would hate for this to get lost. I'm OK merging this before it covers every edge case -- let's just document the limitations and leave that for later cleanup.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-221758131,https://api.github.com/repos/pydata/xarray/issues/814,221758131,MDEyOklzc3VlQ29tbWVudDIyMTc1ODEzMQ==,1217238,2016-05-26T01:58:38Z,2016-05-26T01:58:38Z,MEMBER,"OK, I was not paying attention here with #860 -- I assumed that the build problem was with the build including Iris, but it was actually the other build that started spontaneously failing.
I'm afraid I already merged that PR, so could you please try rebasing again? Sorry for the hassle! On the plus side, I think using conda-forge will ultimately work better than using all the separate channels.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-221629657,https://api.github.com/repos/pydata/xarray/issues/814,221629657,MDEyOklzc3VlQ29tbWVudDIyMTYyOTY1Nw==,1217238,2016-05-25T16:24:14Z,2016-05-25T16:24:14Z,MEMBER,"@nparley Let's see if https://github.com/pydata/xarray/pull/860 works. I think that will probably solve the CI issue (at least on Travis-CI).
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-221624107,https://api.github.com/repos/pydata/xarray/issues/814,221624107,MDEyOklzc3VlQ29tbWVudDIyMTYyNDEwNw==,6215361,2016-05-25T16:04:45Z,2016-05-25T16:04:45Z,NONE,"I have merged upstream and it seems to be failing but I don't think it's related to this PR, as a clean clone of master branch is also failing https://travis-ci.org/nparley/xarray/jobs/132872124
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-219908364,https://api.github.com/repos/pydata/xarray/issues/814,219908364,MDEyOklzc3VlQ29tbWVudDIxOTkwODM2NA==,1217238,2016-05-18T02:23:45Z,2016-05-18T02:23:45Z,MEMBER,"@rhattersley I think this function is cleaner without the `cf_var_name` argument, so I would probably remove it. That said, I usually try to avoid issuing warnings _at all_.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-218735368,https://api.github.com/repos/pydata/xarray/issues/814,218735368,MDEyOklzc3VlQ29tbWVudDIxODczNTM2OA==,917914,2016-05-12T11:53:54Z,2016-05-12T11:53:59Z,NONE,"There's been a question over whether `parse_cell_methods` should really have the `cf_var_name` argument. It's only used if it raises a warning, and even then it's only used to help make the message more user friendly. In itself that doesn't seem like a big deal, but it did make me wonder if you'd rather if it didn't raise the warning _at all_?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-218525434,https://api.github.com/repos/pydata/xarray/issues/814,218525434,MDEyOklzc3VlQ29tbWVudDIxODUyNTQzNA==,1217238,2016-05-11T17:09:39Z,2016-05-11T17:09:39Z,MEMBER,"@jhamman and I have a few minor suggestions, but otherwise this looks good!
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-218357035,https://api.github.com/repos/pydata/xarray/issues/814,218357035,MDEyOklzc3VlQ29tbWVudDIxODM1NzAzNQ==,2443309,2016-05-11T04:10:40Z,2016-05-11T04:10:40Z,MEMBER,"This PR needs ""what's new"" and ""api"" entries in the docs.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-218094052,https://api.github.com/repos/pydata/xarray/issues/814,218094052,MDEyOklzc3VlQ29tbWVudDIxODA5NDA1Mg==,6215361,2016-05-10T08:39:59Z,2016-05-10T08:39:59Z,NONE,"@shoyer @pelson @rhattersley Is there anything you think could be added to this PR or is this ok for now?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-212415277,https://api.github.com/repos/pydata/xarray/issues/814,212415277,MDEyOklzc3VlQ29tbWVudDIxMjQxNTI3Nw==,6215361,2016-04-20T13:05:07Z,2016-04-20T13:05:07Z,NONE,"OK this update uses `iris.fileformats._pyke_rules.compiled_krb.fc_rules_cf_fc` as @pelson mentioned in the comment above. I also added a cell method to the test
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-207460668,https://api.github.com/repos/pydata/xarray/issues/814,207460668,MDEyOklzc3VlQ29tbWVudDIwNzQ2MDY2OA==,6215361,2016-04-08T14:47:08Z,2016-04-08T14:47:08Z,NONE,"OK the latest commit tries to do the cell methods:
``` python
>>> print(cube)
sea_water_potential_temperature / (degC) (-- : 148; -- : 180)
Auxiliary coordinates:
latitude x x
longitude x x
Scalar coordinates:
depth: 4.99994 m, bound=(0.0, 10.0) m
time: 1-01-01 12:00:00
Attributes:
Conventions: CF-1.5
Cell methods:
mean: time_counter
>>> print(xarray.DataArray.from_iris(cube))
array([[ nan, nan, nan, ..., nan, nan, nan],
[ nan, nan, nan, ..., nan, nan, nan],
[ nan, nan, nan, ..., nan, nan, nan],
...,
[ nan, nan, nan, ..., nan, nan, nan],
[ nan, nan, nan, ..., nan, nan, nan],
[ nan, nan, nan, ..., nan, nan, nan]], dtype=float32)
Coordinates:
deptht float64 5.0
time_counter object 1-01-01 12:00:00
nav_lat (dim0, dim1) float32 -78.1906 -78.1906 -78.1906 -78.1906 ...
nav_lon (dim0, dim1) float32 80.0 82.0 83.9999 85.9999 87.9999 ...
* dim0 (dim0) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 ...
* dim1 (dim1) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 ...
Attributes:
units: degC
long_name: Temperature
standard_name: sea_water_potential_temperature
cell_methods: time_counter: mean
Conventions: CF-1.5
>>> print(xarray.DataArray.from_iris(cube).to_iris())
sea_water_potential_temperature / (degC) (dim0: 148; dim1: 180)
Dimension coordinates:
dim0 x -
dim1 - x
Auxiliary coordinates:
latitude x x
longitude x x
Scalar coordinates:
depth: 4.99993801117 m
time: 1-01-01 12:00:00
Attributes:
Conventions: CF-1.5
Cell methods:
mean: time_counter
```
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205368702,https://api.github.com/repos/pydata/xarray/issues/814,205368702,MDEyOklzc3VlQ29tbWVudDIwNTM2ODcwMg==,1217238,2016-04-04T16:04:26Z,2016-04-04T16:04:26Z,MEMBER,"One other thing that I noticed from the latest example -- it would be nice to covert cell methods from Cubes into string attributes on DataArrays.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205368137,https://api.github.com/repos/pydata/xarray/issues/814,205368137,MDEyOklzc3VlQ29tbWVudDIwNTM2ODEzNw==,1217238,2016-04-04T16:02:38Z,2016-04-04T16:02:38Z,MEMBER,"> Is there any way to know for sure whether a coordinate has been automatically created? Or is the name the only clue?
I'm afraid the name is the only clue. My inclination would be not to do anything special here to ""un-name"" default coordinates, assuming Iris has a straightforward way to get rid of them. Dimensions like `dim0` come up quickly in demo code but rarely in practice -- it's mostly a signal to the user that the should pick a meaningful name.
> If this is the way to do things then does this comment need deleting?
Yes, that comment is out of date. I'm currently refactoring that code though, so let me take care care of it.
There's a separate argument about whether or not xarray should automatically convert cubes when passed into the `xarray.DataArray` constructor. We do this for pandas objects, but not any other labelled array types, currently.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205292756,https://api.github.com/repos/pydata/xarray/issues/814,205292756,MDEyOklzc3VlQ29tbWVudDIwNTI5Mjc1Ng==,6215361,2016-04-04T13:16:45Z,2016-04-04T13:16:45Z,NONE,"The comment was just to mention that I had based my code on the code from cdms2 from #236 as suggested by @shoyer. I guess this comment would not be needed in the final merge.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205286718,https://api.github.com/repos/pydata/xarray/issues/814,205286718,MDEyOklzc3VlQ29tbWVudDIwNTI4NjcxOA==,917914,2016-04-04T13:00:04Z,2016-04-04T13:00:04Z,NONE,"> Uses the same template as the cdms2 conversion.
If this is the way to do things then does [this comment](https://github.com/pydata/xarray/blob/2ee2c653946cc12e80e640144835044f08cae8fc/xarray/core/variable.py#L36) need deleting?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205261854,https://api.github.com/repos/pydata/xarray/issues/814,205261854,MDEyOklzc3VlQ29tbWVudDIwNTI2MTg1NA==,917914,2016-04-04T11:49:23Z,2016-04-04T11:49:23Z,NONE,"> What do people think about keeping or dropping the automatic dimension coordinates that xarray creates?
Is there any way to know for sure whether a coordinate has been automatically created? Or is the name the only clue?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-205207053,https://api.github.com/repos/pydata/xarray/issues/814,205207053,MDEyOklzc3VlQ29tbWVudDIwNTIwNzA1Mw==,6215361,2016-04-04T09:17:20Z,2016-04-04T09:17:20Z,NONE,"Latest commit fixes bug if the Iris cube does not have any dimension coordinates. What do people think about keeping or dropping the automatic dimension coordinates that xarray creates? And if dropping should be done should all coordinates named `dim{x}` be dropped? Or are we happy with just leaving them there?
For example at the moment:
``` python
>>> print(cube)
sea_water_potential_temperature / (degC) (-- : 148; -- : 180)
Auxiliary coordinates:
latitude x x
longitude x x
Scalar coordinates:
depth: 4.99994 m, bound=(0.0, 10.0) m
time: 1-01-01 12:00:00
Attributes:
Conventions: CF-1.5
Cell methods:
mean: time_counter
>>> print(xarray.DataArray.from_iris(cube).to_iris())
sea_water_potential_temperature / (degC) (dim0: 148; dim1: 180)
Dimension coordinates:
dim0 x -
dim1 - x
Auxiliary coordinates:
latitude x x
longitude x x
Scalar coordinates:
depth: 4.99993801117 m
time: 1-01-01 12:00:00
Attributes:
Conventions: CF-1.5
```
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204950134,https://api.github.com/repos/pydata/xarray/issues/814,204950134,MDEyOklzc3VlQ29tbWVudDIwNDk1MDEzNA==,6215361,2016-04-03T11:53:25Z,2016-04-03T11:53:25Z,NONE,"Ok, bounds can just be something to add to the converter if / when it's supported.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204802488,https://api.github.com/repos/pydata/xarray/issues/814,204802488,MDEyOklzc3VlQ29tbWVudDIwNDgwMjQ4OA==,1217238,2016-04-02T20:41:21Z,2016-04-02T20:41:21Z,MEMBER,"There's no good solution for representing bounds in xarray -- we can put these as coordinates on Dataset objects, but they aren't supported on DataArray objects. I had some plans to add an `IntervalIndex` type to pandas (https://github.com/pydata/pandas/pull/8707) which would let us support bounds, but honestly I'm not sure if/when I'll finish that.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204765160,https://api.github.com/repos/pydata/xarray/issues/814,204765160,MDEyOklzc3VlQ29tbWVudDIwNDc2NTE2MA==,6215361,2016-04-02T17:48:01Z,2016-04-02T17:48:01Z,NONE,"There is a problem when it comes to bounds. Xarray adds the bounds as another DataArray to the DataSet, i.e.:
```
Data variables:
votemper (dim0, dim1) float64 nan nan nan nan nan nan nan nan nan ...
deptht_bnds (bnds) float64 0.0 10.0
```
I can get the name of this variable from the Coord attribute in the DataArray for another variable, i.e. `ds['votemper'].coords['deptht'].bounds` but can't get the bound array from the DataArray? is that correct?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204692732,https://api.github.com/repos/pydata/xarray/issues/814,204692732,MDEyOklzc3VlQ29tbWVudDIwNDY5MjczMg==,810663,2016-04-02T10:40:59Z,2016-04-02T10:40:59Z,NONE,"Thanks for pinging @shoyer. I'll also ping @rhattersley, and one of us will take a good look in the next few days. :+1:
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204617927,https://api.github.com/repos/pydata/xarray/issues/814,204617927,MDEyOklzc3VlQ29tbWVudDIwNDYxNzkyNw==,1217238,2016-04-02T00:37:47Z,2016-04-02T00:38:31Z,MEMBER,"This is awesome!
Let's try to add some documentation -- at least a mention in What's New.
CC @pelson
","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204340656,https://api.github.com/repos/pydata/xarray/issues/814,204340656,MDEyOklzc3VlQ29tbWVudDIwNDM0MDY1Ng==,6215361,2016-04-01T10:21:23Z,2016-04-01T10:21:23Z,NONE,"`docker pull nparley/xarray_test` is a python 2.7 environment with Iris etc. which mirrors the travis `CONDA_ENV=py27-cdat+iris+pynio`.
It doesn't do everything, but it's a good first go. Here is an example:
``` python
>>> import xarray
>>> import iris
>>> nc_file = 'E1_north_america.nc'
>>> cube = iris.load_cube(nc_file)
>>> darray = xarray.open_dataset(nc_file)['air_temperature']
>>> print(darray)
[435120 values with dtype=float32]
Coordinates:
* time (time) datetime64[ns] 1860-06-01 1861-06-01 ...
* latitude (latitude) float32 15.0 16.25 17.5 18.75 20.0 ...
* longitude (longitude) float32 225.0 226.875 228.75 ...
forecast_period (time) timedelta64[ns] 449 days 18:00:00 ...
forecast_reference_time datetime64[ns] 1859-09-01T06:00:00
height float64 1.5
Attributes:
standard_name: air_temperature
units: K
Model scenario: E1
ukmo__um_stash_source: m01s03i236
source: Data from Met Office Unified Model 6.05
cell_methods: time: mean (interval: 6 hour)
>>> print(xarray.DataArray.from_iris(cube))
[435120 values with dtype=float32]
Coordinates:
* time (time) datetime64[ns] 1860-06-01 1861-06-01 ...
* latitude (latitude) float32 15.0 16.25 17.5 18.75 20.0 ...
* longitude (longitude) float32 225.0 226.875 228.75 ...
forecast_reference_time datetime64[ns] 1859-09-01T06:00:00
height float64 1.5
forecast_period (time) timedelta64[ns] 449 days 18:00:00 ...
Attributes:
Model scenario: E1
STASH: m01s03i236
Conventions: CF-1.5
source: Data from Met Office Unified Model 6.05
standard_name: air_temperature
units: K
>>> print(cube)
air_temperature / (K) (time: 240; latitude: 37; longitude: 49)
Dimension coordinates:
time x - -
latitude - x -
longitude - - x
Auxiliary coordinates:
forecast_period x - -
Scalar coordinates:
forecast_reference_time: 1859-09-01 06:00:00
height: 1.5 m
Attributes:
Conventions: CF-1.5
Model scenario: E1
STASH: m01s03i236
source: Data from Met Office Unified Model 6.05
Cell methods:
mean: time (6 hour
>>> print(darray.to_iris())
air_temperature / (K) (time: 240; latitude: 37; longitude: 49)
Dimension coordinates:
time x - -
latitude - x -
longitude - - x
Auxiliary coordinates:
forecast_period x - -
Scalar coordinates:
forecast_reference_time: 1859-09-01 06:00:00
height: 1.5 m
Attributes:
Model scenario: E1
source: Data from Met Office Unified Model 6.05
ukmo__um_stash_source: m01s03i236
```
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657
https://github.com/pydata/xarray/pull/814#issuecomment-204337823,https://api.github.com/repos/pydata/xarray/issues/814,204337823,MDEyOklzc3VlQ29tbWVudDIwNDMzNzgyMw==,6215361,2016-04-01T10:09:31Z,2016-04-01T10:09:31Z,NONE,"Reference https://github.com/pydata/xarray/issues/621 and https://github.com/pydata/xarray/issues/37. Uses template from https://github.com/pydata/xarray/pull/236.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,145140657