issues

Table actions

1 row where state = "closed" and user = 5442433 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

state 1

  • closed · 1 ✖

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
320838184 MDU6SXNzdWUzMjA4MzgxODQ= 2108 Avoiding duplicate time coordinates when opening multiple files brey 5442433 closed 0     7 2018-05-07T14:59:54Z 2023-03-12T13:29:40Z 2023-03-12T13:29:40Z NONE      

When opening multiple netCDF files with xr.open_mfdataset(nfiles), if the files have a duplicate time stamp (e.g. when they are a product of a restart and continue process) the final xarray dataset has duplicate time coordinates like,

<xarray.DataArray 'time' (time: 39)> array(['2010-02-01T00:00:00.000000000', '2010-02-01T01:00:00.000000000', '2010-02-01T02:00:00.000000000', '2010-02-01T03:00:00.000000000', '2010-02-01T04:00:00.000000000', '2010-02-01T05:00:00.000000000', '2010-02-01T06:00:00.000000000', '2010-02-01T07:00:00.000000000', '2010-02-01T08:00:00.000000000', '2010-02-01T09:00:00.000000000', '2010-02-01T10:00:00.000000000', '2010-02-01T11:00:00.000000000', '2010-02-01T12:00:00.000000000', '2010-02-01T12:00:00.000000000', '2010-02-01T13:00:00.000000000', '2010-02-01T14:00:00.000000000', '2010-02-01T15:00:00.000000000', '2010-02-01T16:00:00.000000000', '2010-02-01T17:00:00.000000000', '2010-02-01T18:00:00.000000000', '2010-02-01T19:00:00.000000000', '2010-02-01T20:00:00.000000000', '2010-02-01T21:00:00.000000000', '2010-02-01T22:00:00.000000000', '2010-02-01T23:00:00.000000000', '2010-02-02T00:00:00.000000000', '2010-02-02T00:00:00.000000000', '2010-02-02T01:00:00.000000000', '2010-02-02T02:00:00.000000000', '2010-02-02T03:00:00.000000000', '2010-02-02T04:00:00.000000000', '2010-02-02T05:00:00.000000000', '2010-02-02T06:00:00.000000000', '2010-02-02T07:00:00.000000000', '2010-02-02T08:00:00.000000000', '2010-02-02T09:00:00.000000000', '2010-02-02T10:00:00.000000000', '2010-02-02T11:00:00.000000000', '2010-02-02T12:00:00.000000000'], dtype='datetime64[ns]') Coordinates: * time (time) datetime64[ns] 2010-02-01 2010-02-01T01:00:00 ...

Is there a way to avoid this either while reading or afterwards by dropping the non unique time coordinates?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2108/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue

Advanced export

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

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);