home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 195676319

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/790#issuecomment-195676319 https://api.github.com/repos/pydata/xarray/issues/790 195676319 MDEyOklzc3VlQ29tbWVudDE5NTY3NjMxOQ== 2443309 2016-03-12T07:01:12Z 2016-03-12T07:01:12Z MEMBER

Thanks @fmaussion. This was a helpful illustration of how this could be done. The salem GeoTiff and Grid objects include all and more than I was hoping to implement in xarray. However, after a bit more looking into this, I have mixed feelings about whether this would work in xarray. A brief summary of the pros/cons as I see them now.

Pros: - Rasterio supports a wide range of raster formats (e.g. GeoTiff, ArcInfo ASCII Grid, etc.) - Combined with pyproj, coordinate variables can be inferred - Supports windowed reading (and writing), this would fit in well with the chunking approach already taken by xarray. - Supports lazy loading of array values, this would fit in well with the loading policies of the other xarray backends.

Cons: - Would require xarray to adopt conventions for projecting arrays, naming (coordinates, dimensions, arrays), and handling of raster attributes. I can image ways this could be done but it may take us in down a path we don't want to go. - The xarray backends generally return Datasets, however, rasterio returns individual arrays that would better be applied to DataArrays.

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