issues

Table actions

2 rows where user = 12813228 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 2

state 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
1138440632 PR_kwDOAMm_X84y2G8- 6276 Allow to parse more backend kwargs to pydap backend jgliss 12813228 closed 0     5 2022-02-15T09:50:41Z 2022-02-17T12:51:50Z 2022-02-17T12:51:50Z CONTRIBUTOR   0 pydata/xarray/pulls/6276
  • [x] Closes #6274
  • [x] Tests added
  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [x] New functions/methods are listed in api.rst
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6276/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1137148310 I_kwDOAMm_X85Dx4GW 6274 Enable to parse more backend_kwargs when opening via PydapDataStore (e.g. output_grid) jgliss 12813228 closed 0     2 2022-02-14T11:15:15Z 2022-02-17T12:51:49Z 2022-02-17T12:51:49Z CONTRIBUTOR      

Is your feature request related to a problem?

I am planning to use xarray to access netcdf data from a thredds server. For my particular application, I need to be able to set pydap client option output_grid=False, to avoid some issues that I have experienced with a particular dataset on the server I am downloading from.

I use xarray.open_dataset to access the data via pydap backend, which currently only allows to specify "session" as a keyword in backend_kwargs.

https://github.com/pydata/xarray/blob/8c5c230881d616af32c5a42cca261eb11fce3916/xarray/backends/pydap_.py#L89

It would be helpful to be able to provide additional backend_kwargs accepted by the pydap client (such as output_grid).

https://github.com/pydap/pydap/blob/dbe9b8d15831f21c28b97ed5661b2708faec45f2/src/pydap/client.py#L58

Describe the solution you'd like

It could be perhaps as simple as extending the signature of PydapDataStore.open from:

```python @classmethod def open(cls, url, session=None):

ds = pydap.client.open_url(url, session=session)
return cls(ds)

```

to, e.g.:

```python @classmethod def open(cls, url, **kwargs):

ds = pydap.client.open_url(url, **kwargs)
return cls(ds)

```

Describe alternatives you've considered

No response

Additional context

No response

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6274/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]);