Fix 1D quiver when transforming projections

[ocefpaf]

Maybe we should just use np.broadcast_arrays and check if the result is 2D?

Fix #672

[ajdawson]

This PR needs a better description/title. It'd also help if the reference to the issue it fixes is in the description as it would be clickable and generate a reference.

[pelson]

Also, maybe just a test which ensures that the exception doesn't get raised (and the appropriate things are passed to quiver)?

[ocefpaf]

This PR needs a better description/title. It'd also help if the reference to the issue it fixes is in the description as it would be clickable and generate a reference.

Done!

Also, maybe just a test which ensures that the exception doesn't get raised (and the appropriate things are passed to quiver)?

Will do. I just wonder if we should use np.broadcast_arrays to ensure the arrays are in a consistent shape and let both np.broadcast_arrays and matplolib quiver do the raising and testing...

[ocefpaf]

@pelson I am not sure where these test should live so I added a new file. Let me know if I must paste them somewhere else.

PS: I notice that the test test_quiver_transform_xy_2d_uv_1d passes in the non-transform case. Even though the data is OK to be quiver'ed, see here, I do not believe we should cover every corner case and encourage user to pass 2D x, y with 1D u,v. What do you say?

[ocefpaf]

Closed in favor of #677.