issue_comments: 437988119

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/issues/1982#issuecomment-437988119 https://api.github.com/repos/pydata/xarray/issues/1982 437988119 MDEyOklzc3VlQ29tbWVudDQzNzk4ODExOQ== 110313 2018-11-12T18:45:21Z 2018-11-12T18:45:21Z NONE

How about searching in the parent group until the root group is reached? As far as I can see it, this cannot cause any conflict. It would be really awesome to have this functionality. I really like to idea of nicely organizing NetCDF files while still having the full functionality of xarray at hand.

On 12 Nov 2018, at 18:55, Stephan Hoyer notifications@github.com wrote:

When reading a sub group from a netCDF file with dimensions defined in the root group, the dimensions are not read from the root group. This contradicts the netCDF documentation, which states that dimensions are scoped such that they can be seen by all sub groups.

To be clear, xarray does properly read "dimensions" in parent groups. (This is actually ensured by libraries like netCDF4-Python.)

What xarray doesn't do is read "coordinates" from parent groups. As far as I can tell, this isn't part of either the netCDF4 data model or CF conventions. This might be a usability improvement but the right way to do isn't dictated by the specs.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/1982#issuecomment-437972944, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGu6bZgyAIR4mLV-kuxGg4uF9r6T41Pks5uubYUgaJpZM4SmZFw. 

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