New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1D quiver in non-PlateCarree projections #672
Milestone
Comments
ocefpaf
added a commit
to ocefpaf/cartopy
that referenced
this issue
Sep 14, 2015
BTW: This bug was found by a student @rafacsantana during our Python course here. Hopefully the students will be sending PRs of their own soon 😉 |
👍 - let's fix it. |
Ping @scmc72 / @Jozhogg if you're interested. |
Taking a look now 👍 |
@Jozhogg take a look at: |
My bad. I sent this after a long day and forgot to cross-reference issue/PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using quiver with 1D arrays of
x
,y
,u
,v
works just fine withccrs.PlateCarree()
, but raises aValueError
with any other projection:Using
np.atleast_2d
fixes this, and the quiver docs do say:Plot a 2-D field of arrows
.However, I wonder if the
atleast2d
should be inside Cartopy, or if the 1D case should raise an error in PlateCarree too.(See http://nbviewer.ipython.org/gist/ocefpaf/b2f79fe0f96fa1776b97 for a SSCCE.)
The text was updated successfully, but these errors were encountered: