home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 379823407

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/issues/2042#issuecomment-379823407 https://api.github.com/repos/pydata/xarray/issues/2042 379823407 MDEyOklzc3VlQ29tbWVudDM3OTgyMzQwNw== 601025 2018-04-09T17:04:40Z 2018-04-09T17:04:40Z NONE

On Apr 9 2018 12:49 AM, Fabien Maussion wrote:

I do not care about the to_rasterio but I do care about a ''to_tiff''

Yes sorry, I meant to_tiff

ah... got it.

If xarray has no way to output tiffs then I cannot use xarray.

I'm not saying it shouldn't exist, I'm just asking whether it should be in the xarray codebase or elsewhere.

fair enough. I just need them to play well enough together that I can read, process, and write a chunk/window at a time (whether that is with a simple xr.compute() or something else).

If you'd like to parse new attributes when opening the geotiff file this could be added easily. PRs are welcome!

what is a PR? Did you mean functionality request?

I'm still not clear where dask.array, xarray, rasterio, and pangeo begin and end. I think I have posted an issue about extending the metatdata/tags some place, but I am sure it is not as clear as it should be, and for the life of me I am not sure where I posted that.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  312203596
Powered by Datasette · Queries took 3.61ms · About: xarray-datasette