issue_comments

Table actions

4 rows where issue = 251332357 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 3

author_association 2

issue 1

  • open_dataset leading to NetCDF: file not found · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
323464863 https://github.com/pydata/xarray/issues/1510#issuecomment-323464863 https://api.github.com/repos/pydata/xarray/issues/1510 MDEyOklzc3VlQ29tbWVudDMyMzQ2NDg2Mw== kthyng 3487237 2017-08-18T21:27:34Z 2017-08-18T21:27:34Z NONE

Huh! Weird! I had tried accessing a particular value of u with netCDF as a test and it had worked fine and hadn't worried about it after that. I just now tried ocean_time and it works for particular indices (like d['ocean_time'][0]), but as you said doesn't work if I put in d['ocean_time'][:].

Thanks for everyone's help, I'll work on the thredds end of things.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_dataset leading to NetCDF: file not found 251332357
323446484 https://github.com/pydata/xarray/issues/1510#issuecomment-323446484 https://api.github.com/repos/pydata/xarray/issues/1510 MDEyOklzc3VlQ29tbWVudDMyMzQ0NjQ4NA== petacube 30301994 2017-08-18T19:53:56Z 2017-08-18T19:53:56Z NONE

if you pick up variable which does not have ocean_time as dimension panoply plots ok and i would expect dask/xarray will work fine that too.

so maybe you want to explicitly query for variable(s) not connected to ocean_time.

also talk to provider of the dataset and tell them the something wrong with ocean_time dimension.

Stanislav

On Aug 18, 2017, at 3:39 PM, Stanislav Seltser stanislav.seltser@petacube.com wrote:

Kristen, i had opened your threads dataset with panoply and tried to plot variables it opens dataset ok but when it queries it gives me an error about ocean time variable so nothing to do with xarray or dask - its data got corrupted somehow

<PastedGraphic-1.png>

On Aug 18, 2017, at 3:16 PM, Filipe <notifications@github.com notifications@github.com> wrote:

d['ocean_time'][:] 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_dataset leading to NetCDF: file not found 251332357
323443486 https://github.com/pydata/xarray/issues/1510#issuecomment-323443486 https://api.github.com/repos/pydata/xarray/issues/1510 MDEyOklzc3VlQ29tbWVudDMyMzQ0MzQ4Ng== petacube 30301994 2017-08-18T19:39:09Z 2017-08-18T19:39:09Z NONE

Kristen, i had opened your threads dataset with panoply and tried to plot variables it opens dataset ok but when it queries it gives me an error about ocean time variable so nothing to do with xarray or dask - its data got corrupted somehow

On Aug 18, 2017, at 3:16 PM, Filipe notifications@github.com wrote:

d['ocean_time'][:]

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_dataset leading to NetCDF: file not found 251332357
323438668 https://github.com/pydata/xarray/issues/1510#issuecomment-323438668 https://api.github.com/repos/pydata/xarray/issues/1510 MDEyOklzc3VlQ29tbWVudDMyMzQzODY2OA== ocefpaf 950575 2017-08-18T19:16:33Z 2017-08-18T19:19:21Z CONTRIBUTOR

Something is not OK when parsing ocean_time (and some other variables).

If you do d['ocean_time'][:] on your example with netCDF4 you'll get the same error as xarray.

Could it be a bad aggregation on the THREDDS service?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_dataset leading to NetCDF: file not found 251332357

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);