-
Notifications
You must be signed in to change notification settings - Fork 365
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
Request to add transform_first keyword to barbs #2395
Comments
@karlwx I think it would be a little trickier because you need to transform vectors instead of just scalars, but it should in principle be doable. We do have a decorator that you could try playing around with to see whether it would work for your use-case and/or modifying it for the vector transform paths. cartopy/lib/cartopy/mpl/geoaxes.py Line 311 in ea946a1
used in Contour here: cartopy/lib/cartopy/mpl/geoaxes.py Lines 1572 to 1574 in ea946a1
|
Thanks @greglucas. Maybe an easier solution would be to add a keyword argument that would automatically thin the arrays of x, y, and data based on the number of data points within the map extent and the value of |
Possibly, I'm not sure what that would look like though... Would you be able to do that yourself beforehand something like The regridding is located here if you want to dig in and try things out: cartopy/lib/cartopy/vector_transform.py Line 19 in ea946a1
|
Would it be possible to implement something similar to #1291 with barbs? I am experiencing significant slowdowns with the barb transformation with high-resolution data. Appears I'm not the only one: https://stackoverflow.com/questions/71578820/use-transform-first-keyword-in-barbs
Originally posted by @karlwx in #1291 (comment)
The text was updated successfully, but these errors were encountered: