issues
1 row where type = "issue" and user = 33962195 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2132231561 | I_kwDOAMm_X85_F0WJ | 8741 | Add sarxarray into ecosystem list | rogerkuou 33962195 | closed | 0 | 1 | 2024-02-13T12:36:11Z | 2024-02-13T12:59:56Z | 2024-02-13T12:59:56Z | CONTRIBUTOR | What is your issue?I propose to add This is an Xarray extension for handling a specific type of remote sensing data: Synthetic Aperture Radar (SAR) data. A common application of it is ground deformation monitoring. In this application, a stack of SAR images with complex pixel values needs to be processed to retrieve the temporal dynamics. Due to the data volume (1~2TB per data stack), the complex nature of pixels, and the irregular geometry (comparing to optical images), SAR data stacks need some particular care than regular images, such as geoTIFFs. Motivated by this need, we made sarxarray using xr.register_dataarray_accessor as a user-friendly extension to handle SAR data stacks as The following functionalities are implemented:
Sorry I submitted PR #8740 and then realized it would be nicer to open an issue for discussion. Apologies for the confusion! However, since the PR is already opened, I will leave it to be. Thanks very much for your time! |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/8741/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
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]);