issue_comments: 346028156

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/1704#issuecomment-346028156 https://api.github.com/repos/pydata/xarray/issues/1704 346028156 MDEyOklzc3VlQ29tbWVudDM0NjAyODE1Ng== 14314623 2017-11-21T13:35:38Z 2017-11-21T13:35:38Z CONTRIBUTOR

Yes that would be phenomenal. It would be absolutely sufficient for this to be an optional step that needs to be activated with e.g. xr.open_mfdataset(filelist, full_check=True). In my particular use case I encountered very long load times, and it would be great if in any such problematic cases there would be an easy way to activate a suite of verbose checks to quickly identify problems. For normal use these could be largely deactivated to achieve a fast and streamlined readin?

Sent from my iPhone

On Nov 21, 2017, at 12:17 AM, Joe Hamman notifications@github.com wrote:

@jbusecke -

... would it be possible to implement a check for such errors that displays a warning?

In your case, what would that have looked like? Many users have actually requested that xarray provide a more streamlined reader function that does less checking. Perhaps it would have been useful for you to have xarray raise an error when it encountered files that weren't consistent (either in the variable, dimensions, or coordinates)?

— 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
}
   272415954