issue_comments

Table actions

3 rows where issue = 467735754 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Landsat Surface Reflectance bands have tricky metadata 'band' attribute · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
511135221 https://github.com/pydata/xarray/issues/3108#issuecomment-511135221 https://api.github.com/repos/pydata/xarray/issues/3108 MDEyOklzc3VlQ29tbWVudDUxMTEzNTIyMQ== rbavery 22258697 2019-07-13T16:27:06Z 2019-07-13T16:27:06Z NONE

Sounds good, I'll look into contributing a Landsat reader to Satpy, that's a better home for it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Landsat Surface Reflectance bands have tricky metadata 'band' attribute 467735754
511133975 https://github.com/pydata/xarray/issues/3108#issuecomment-511133975 https://api.github.com/repos/pydata/xarray/issues/3108 MDEyOklzc3VlQ29tbWVudDUxMTEzMzk3NQ== rabernat 1197350 2019-07-13T16:11:17Z 2019-07-13T16:11:17Z MEMBER

Suggested workaround would be to write a preprocessor function to fix the bad coordinate before concatenating bands.

I'm working on this at the scipy sprint, writing a new Landsat SR specific file opener and contacting the data provider to let them know that the metadata's band attribute should reflect the band number

Are you aware of satyp? https://satpy.readthedocs.io/en/latest/ It sounds like what you are doing is within the scope of that project. (They use xarray under the hood.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Landsat Surface Reflectance bands have tricky metadata 'band' attribute 467735754
511133886 https://github.com/pydata/xarray/issues/3108#issuecomment-511133886 https://api.github.com/repos/pydata/xarray/issues/3108 MDEyOklzc3VlQ29tbWVudDUxMTEzMzg4Ng== rabernat 1197350 2019-07-13T16:10:07Z 2019-07-13T16:10:07Z MEMBER

Hi @rbavery -- I am inclined to consider this a problem with your data, not a problem with xarray.

However, it would be nice to have some tutorial examples of how to deal with such situations. That is what I'm working on in #1391. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Landsat Surface Reflectance bands have tricky metadata 'band' attribute 467735754

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]);