home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 302255969

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/1260#issuecomment-302255969 https://api.github.com/repos/pydata/xarray/issues/1260 302255969 MDEyOklzc3VlQ29tbWVudDMwMjI1NTk2OQ== 10050469 2017-05-17T23:07:44Z 2017-05-17T23:10:11Z MEMBER

Folks, I finally managed to find a couple of hours to wrap this up: this is now ready for review.

Everything seems to work the way I'd like it to work, and only one thing is missing: the lazy computation of lons and lats with dask (I don't know how to do this quickly and I have not enough time to spend on this right now, unfortunately). This has been waiting for too long now, so I suggest to merge this when ready and this feature later on.

The solution retained for the API is to add a new open_rasterio top-level function: this makes sense since many keywords of open_dataset aren't relevant for rasterio datasets. It also underlines that rasterio datasets are quit different from xarray's data model.

another example I could add to the soon to come xarray gallery could be:

```python import xarray as xr import matplotlib.pyplot as plt import cartopy.crs as ccrs ds = xr.open_rasterio('RGB.byte.tif', add_latlon=True) ax = plt.subplot(projection=ccrs.PlateCarree()) ds.raster.sel(band=1).plot(ax=ax, x='lon', y='lat', transform=ccrs.PlateCarree()); ax.coastlines('10m'); ````

cc @gidden @jhamman @shoyer

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