Skip to content
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

[ENH]: quiverkey accepts transform argument directly instead of coordinates #28263

Open
ZhaJiMan opened this issue May 20, 2024 · 0 comments
Open

Comments

@ZhaJiMan
Copy link

Problem

quiverkey now uses the coordinates argument to set its transform instead of using transform argument like other artists. And it only supports four coordinates: axes, figure, data and inches. When I pass transform=cbar.ax.transAxes to make the quiverky above a color bar, it will fail due to the coordinates argument (actually its _set_transform method under the hood). Another example is that when using Cartopy, I want to pass transform=ccrs.PlateCarree() to use longitude and latitude as X and Y.

I hope quiverkey to accept transform directly, which is consistent with other artists, and make the coordiantes more flexible.

Proposed solution

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant