issue_comments: 479822234

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/2865#issuecomment-479822234 https://api.github.com/repos/pydata/xarray/issues/2865 479822234 MDEyOklzc3VlQ29tbWVudDQ3OTgyMjIzNA== 10595679 2019-04-04T09:26:56Z 2019-04-04T09:26:56Z CONTRIBUTOR

@fmaussion done, let's see what CI has to say about my patches ;)

I remember reading a thread somewhere on xarray github repo discussing whether xarray should include the rasterio backend or not.

I understand that bridges between two libraries are always hard to maintain, because you need to know both products (we actually have the same kind of problem with OTB and QGis), but from a user standpoint, they need to exist somewhere. I would probably never have turned to xarray if someone with the required knowledge had not implemented the rasterio backend.

Then of course the user community should take care of maintaining those backends (this is what I am doing right now).

Bridging xarray with rasterio opens xarray to the remote sensing imagery community. And behind rasterio there is gdal, which is an awesome library with so many great capabilities (like this on-the-fly reprojection during reading I mentioned).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   428374352