issue_comments: 410068839
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/2288#issuecomment-410068839 | https://api.github.com/repos/pydata/xarray/issues/2288 | 410068839 | MDEyOklzc3VlQ29tbWVudDQxMDA2ODgzOQ== | 1828519 | 2018-08-02T21:09:38Z | 2018-08-02T21:09:38Z | CONTRIBUTOR | For the user base I think if we can cover as many groups as possible that would be best. I know there are plenty of people who need to describe CRS information in their data, but don't use geotiffs and therefore don't really need rasterio/gdal. The group I immediately thought of was the metpy group which is why I talked to @dopplershift in the first place. The immediate need for this group (based on his scipy talk) will be people reading NetCDF files and putting the data on a cartopy plot. I think @dopplershift and I agreed that when it comes problems building/distributing software dealing with this type of data the cause is almost always gdal/libgdal. I'm in favor of making it optional if possible. For the I just did a search for "geoxarray" on github and @wy2136's repositories came up where they are importing a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
341331807 |