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/2199#issuecomment-401603966,https://api.github.com/repos/pydata/xarray/issues/2199,401603966,MDEyOklzc3VlQ29tbWVudDQwMTYwMzk2Ng==,1550771,2018-07-01T12:35:56Z,2018-07-01T12:35:56Z,NONE,"Thanks for everyone's feedback, due to trademark concerns we decided to rename both the library and the API to ``.hvplot``. There should be a release and an announcement in the coming week.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327725925
https://github.com/pydata/xarray/issues/2199#issuecomment-394179490,https://api.github.com/repos/pydata/xarray/issues/2199,394179490,MDEyOklzc3VlQ29tbWVudDM5NDE3OTQ5MA==,1550771,2018-06-03T17:56:40Z,2018-06-03T17:56:40Z,NONE,"Thanks again for the feedback, I've decided to go with ``.holoplot`` in the end. I'll work on finishing some of geo related features today and get a 0.1 release and announcement out this week.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327725925
https://github.com/pydata/xarray/issues/2199#issuecomment-393309581,https://api.github.com/repos/pydata/xarray/issues/2199,393309581,MDEyOklzc3VlQ29tbWVudDM5MzMwOTU4MQ==,1550771,2018-05-30T20:34:39Z,2018-05-30T20:37:24Z,NONE,">something like DataArray.hv.plot.contourf() seems too deeply nested.

Actually I suppose that's not what it would be, it could be ``da.hv.plot`` and ``da.hv.contourf`` with ``.plot`` figuring out the ``kind`` for you. I quite like that too.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327725925
https://github.com/pydata/xarray/issues/2199#issuecomment-393300042,https://api.github.com/repos/pydata/xarray/issues/2199,393300042,MDEyOklzc3VlQ29tbWVudDM5MzMwMDA0Mg==,1550771,2018-05-30T20:06:29Z,2018-05-30T20:16:45Z,NONE,">I agree the accessor is the best option for now, but I have no strong opinions about the name of the accessor.

Okay thanks, given xarray's preference for accessor names to match projects I'm now leaning toward ``da.holoplot()``.

>Automatic generation of DynamicMaps. Say I have a DataArray with dimensions ('time', 'lat', 'lon'); I should be able to say da.hv.plot(kdims=['lat', 'lon'] and have time become a dynamic selector.

HoloPlot explicitly does not deal with ``kdims`` and ``vdims`` instead more closely following the API of ``pd.DataFrame.plot`` and ``xr.DataArray``. That said coordinates that are not assigned to the x/y axes will automatically result in a DynamicMap, so this will give you an image plot + a widget to select the time:

```python
da.holoplot(x='lon', y='lat', kind='image')
```

>To go along with the above, lazy loading of dask-backed arrays

That should happen automatically.

>Intelligent faceting which automatically links the facet kdims

You can facet in a number of ways:

```python
da.isel(time=slice(0, 3)).holoplot(x='lon', y='lat', kind='image', by='time')
```

will produce three subplots which are linked on the x- and y-axis, i.e. zooming on one will zoom on all unless you set ``shared_axes=False``. You can also generate a grid with:

```python
da.isel(time=slice(0, 3)).holoplot(x='lon', y='lat', kind='image', row='time', col='some_other_coord')
```

>Plotting not just of DataArrays but Datasets.

This is also already supported, the API here is:

```python
ds.holoplot(x='lon', y='lat', z=['air', 'surface'])
```

Will provide a widget to select between the 'air' and 'surface' data variable.

>Options for projections, coastlines, etc. associated with geoviews

Currently working on that, it's basically just waiting on new HoloViews/GeoViews releases. The API here is as follows:

```python
air_ds.air.holoplot.quadmesh(
    'lon', 'lat', ['air', 'some_other_variable'], crs=ccrs.PlateCarree(), projection=ccrs.Orthographic(-80, 30),
    global_extent=True, width=600, height=500, cmap='viridis'
) * gv.feature.coastline
```

<img width=""1073"" alt=""screen shot 2018-05-30 at 9 03 53 pm"" src=""https://user-images.githubusercontent.com/1550771/40744611-04b83496-644d-11e8-8777-03d449e1d866.png"">
","{""total_count"": 7, ""+1"": 4, ""-1"": 0, ""laugh"": 0, ""hooray"": 3, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327725925
https://github.com/pydata/xarray/issues/2199#issuecomment-393284049,https://api.github.com/repos/pydata/xarray/issues/2199,393284049,MDEyOklzc3VlQ29tbWVudDM5MzI4NDA0OQ==,1550771,2018-05-30T19:16:32Z,2018-05-30T19:16:32Z,NONE,"Thanks for the feedback!  I'll try to drive the pandas conversation along, but since I doubt that will be resolved in the near term so I think until then we should definitely pursue the accessor approach (which is much better than the property monkey patching we're doing now).

Personally I'd prefer ``DataArray.hvplot()`` since I think even the two extra characters make a difference and something like ``DataArray.hv.plot.contourf()`` seems too deeply nested. That said if ""our preference for accessor names to match projects"" is a solidly established convention I'll defer to that and go with ``DataArray.holoplot()``.

@rabernat Since you have used HoloViews with xarray in the past I'd very appreciate your input as well.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,327725925