Code Sample, a copy-pastable example if possible

python a=xr.DataArray(1.234) '{:1.3f}'.format(a) # throws error '{:1.3f}'.format(a.values) # behaves nicely

Problem description

I think it would be useful for repr(a) to return repr(a.values) when a.ndim==0 and perhaps also when a.size==1. For example, this would make such code work: python a=xr.DataArray(range(4)) ' '.join('{:d}'.format(v) for v in a) while currently one has to write python ' '.join('{:d}'.format(v.values) for v in a) I tried to think whether this will break something else but I couldn't think of anything.

When using Dataset.scatter with hue being a variable of dtype string, the legend turns out to be wrong.

MCVE Code Sample

python import xarray as xr import numpy as np dd = xr.Dataset({'y': (['x'], np.arange(8)), 'label': (['x'], list('AABBCCDD'))}, coords={'x': np.linspace(0,1,8)}) dd.plot.scatter(x='x', y='y', hue='label') Output is (note the legend):

Playing around it seems that it always chooses the first 4 values as the legend labels (note that the order of colors of the points is correct): python import xarray as xr import numpy as np dd = xr.Dataset({'y': (['x'], np.arange(8)), 'label': (['x'], list('ABBACDDC'))}, coords={'x': np.linspace(0,1,8)}) dd.plot.scatter(x='x', y='y', hue='label')

And if there are only 3 labels in total it chooses the first 3: python import xarray as xr import numpy as np dd = xr.Dataset({'y': (['x'], np.arange(6)), 'label': (['x'], list('ABBACC'))}, coords={'x': np.linspace(0,1,6)}) dd.plot.scatter(x='x', y='y', hue='label')

Expected Output

Legend in first two plots should read 'ABCD' and last plot 'ABC'

Versions

Code Sample, a copy-pastable example if possible

Consider the following 4 ways to mask an DataArray:

```python import xarray as xr

ds=xr.Dataset({'a': (['x'], range(10))}, coords={'x': range(10)}) ds['msk']=ds.a>5 msk=ds.a>5

v1=ds.a.where(ds.a>5) v2=ds.a.where(msk) v3=ds.where(ds.msk).a v4=ds.a.where(ds.msk)

', '.join(str(v.name) for v in (v1, v2, v3, v4))#output: 'a, a, a, None'

Problem description

All vs defined above are identical, except that v4 has lost its name in masking. This can cause errors in merging (like just happened to me and was hard and annoying to catch).

Is this behavior intentional? It seems inconsistent to me that ds.a.where(ds.msk) is not equivalent to ds.where(ds.msk).a

Expected Output

I would expect ds.a.where(ds.msk) to return a DataArray with the name a.

Output of xr.show_versions()

I'm trying to build the doc and it fails. I have a fresh miniconda install with a test environment created as instructed in the docs (i.e. conda env create -f ci/requirements-py36.yml followed by conda install -c conda-forge sphinx sphinx_rtd_theme sphinx-gallery numpydoc).

Code Sample, a copy-pastable example if possible

shell make clean make html

Problem description

It generates the following error:

Exception occurred: File "/Users/yohai/miniconda3/envs/test_env/lib/python3.6/site-packages/IPython/sphinxext/ipython_directive.py", line 567, in process_input raise RuntimeError('Non Expected exception in `{}` line {}'.format(filename, lineno)) RuntimeError: Non Expected exception in `/Users/yohai/Dropbox/Coding/xarray/doc/io.rst` line 376 The full traceback has been saved in /var/folders/mj/g9tnmysj6zld_3dg6hm9tkk00000gn/T/sphinx-err-8q55qmxi.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks! make: *** [html] Error 2

The problem seems to be in doc/io.rst. When I delete all lines upto line 367 it builds well The content of the traceback logfile:

Output of xr.show_versions()

The link to the external blogpost about xarray and dask, that was fixed in https://github.com/pydata/xarray/pull/1573, is broken again. Is it available somewhere?

Code Sample, a copy-pastable example if possible

Unnamed arguments that are passed to line plots are directly passed to plot. ```python import xarray as xr import numpy as np

d3 = xr.DataArray(np.random.randn(10, 6, 3), dims=['x', 'y', 'z'], coords=[range(10), range(6), ['foo', 'bar', 'foobar']]) d2 = d3[..., 0].squeeze(drop=True)

This will make triangle markers and dashed lines:

d2.plot.line('^--',x='x') We [recently implemented ](https://github.com/pydata/xarray/pull/2107) faceted line plots:python d3.plot(col='z', hue='x') #should work from commit bc52f8a onwards. ```

However, current implementation does not allow for passing of unnamed arguments: python d3.plot('^--', col='z', hue='x') #gives error d3.plot.line('^--', col='z', hue='x') #gives different error I'd be happy to fix this (it's probably an easy fix, I didn't check) but I'm not sure what the correct user interface should be. Should DataArray.plot with hue as a keyword behave identically to DataArray.plot.line?

When data is more than 2 dimensional, plot() creates a FacetGrid where each facet gets plots two dimensional data. I would find it very useful to have similar functionality for line plots.

Let's define three DataArrays, of 2,3 and 4 dimensions, named d2, d3 and d4.

```python d4=xr.DataArray(np.random.randn(3,4,5,6), dims=['x','y','z','w'], coords=[range(3),range(4),range(5),range(6)]) d3=d4[...,0].drop('w') d2=d3[...,0].drop('z')

d4.plot(row='x', col='y') #creates a 2d facet grid, each facet is a pcolormesh d3.plot(col='x') #creates a 1d facet grid, each facet is a pcolormesh plt.show() ```

It would be very useful to have a similar interface for line plots too. That is, I would expect python d2.plot.line(row='y', x='x') to create a row of panels, each having one line. Similarly, I would expect ```python d3.plot.line(col='y', x='x')

or alternatively

d3.plot.line(col='y', hue='z') to create a row of panels, each having a series of lines, with `hue` corresponding to `z` and so forth. Finally,python d4.plot.line(row='z',col='y', x='x')

or alternatively

d4.plot.line(row='z',col='y', hue='w') `` should create a 2d matrix of panels, each having a series of lines, withhuecorresponding tow`.

This seems to me like a natural generalization of the behaviour of plot(), and I found myself coding manually loops to do that a few times.