pull_requests

Table actions

1 row where user = 5696346

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
298269156 MDExOlB1bGxSZXF1ZXN0Mjk4MjY5MTU2 3136 closed 0 Added suppport for geotiff colormap() colorinterp to be loaded into attrs alando46 5696346 <!-- Feel free to remove check-list items aren't relevant to your change --> This is tangentially related to the [`to_geotiff()` discussion](https://github.com/pydata/xarray/issues/2042). We're using [intake-xarray](https://github.com/intake/intake-xarray) to read a year's worth of Sentinel-2 Scene Classification Layers into a DataArray, doing some processing, and then writing the output to a single band GeoTIFF. When writing the output, we'd like to preserve the colormap of the original underlying data. `xarray-intake` uses `xarray` to read the dataset, so thought it might be useful to add support in `open_rasterio()` to read and load `src.colormap(1)` and `src.colorinterp` into the attributes of the DataArray. My thinking is that if in the future the community ends up wanting to add a `to_geotiff()` method, reading the `src` colormap and colorinterp might be useful. Before adding tests, I thought I'd submit the PR to see what others thought about adding this functionality. If there's support for this, I'm happy to add any needed tests or documentation. - [ ] Tests added - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API 2019-07-17T01:10:45Z 2022-04-07T20:21:59Z 2022-04-07T20:21:58Z   6f0d3978b6e1007a5fe0eeb590b1aeac68f4fded     0 8eb7dd3121aa45914616567c75afa757443c8ad9 7bf9df9d75c40bcbf2dd28c47204529a76561a3f NONE   xarray 13221727 https://github.com/pydata/xarray/pull/3136  

Advanced export

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

CSV options: 

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [auto_merge] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);