issue_comments: 512353104

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/3131#issuecomment-512353104 https://api.github.com/repos/pydata/xarray/issues/3131 512353104 MDEyOklzc3VlQ29tbWVudDUxMjM1MzEwNA== 35968931 2019-07-17T16:22:26Z 2019-07-17T16:22:26Z MEMBER

Nor am I. I originally thought it should be 'nested' because the concat-in-order behaviour is more similar to the original auto_combine, but I don't know.

It seems to me like it depends on the quality of user's data: if they have high-quality datasets which already have sensible coordinates for each dimension then' by_coords' is best, but if their data is more primitive without coordinates (like mine happens to be) then 'nested' is the most natural default. So do we have a sense of what the largest number of users would find most natural? Or is this not a good way to think about it?

On Wed, 17 Jul 2019, 16:05 Stephan Hoyer, notifications@github.com wrote:

I think "by_coords" is probably the most user friendly default for open_mfdataset? But I'm not entirely sure...

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/3131?email_source=notifications&email_token=AISNPI47L2F45PAJVZX6CHTP74YNFA5CNFSM4IDSQHX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2EQLPA#issuecomment-512296380, or mute the thread https://github.com/notifications/unsubscribe-auth/AISNPI4UBJO5K5NAC65VURTP74YNFANCNFSM4IDSQHXQ . 

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