[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[python #ACE-827366]: Improve speed of contourf plots

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [python #ACE-827366]: Improve speed of contourf plots
  • Date: Tue, 28 Sep 2021 16:53:01 -0600
Hello! We appreciate you reaching out.

This feature was officially added in Cartopy 0.20.0, released on September 17! 
It was *not* included in the previously released version 0.19.0.post1. If you 
update to 0.20.0, this can be accessed with the `transform_first` boolean 
kwarg; if you specify `True`, it will use the "fast" contour pipeline described 
in that PR. The documentation for this is available here:

  
https://scitools.org.uk/cartopy/docs/latest/reference/generated/cartopy.mpl.geoaxes.GeoAxes.html#cartopy.mpl.geoaxes.GeoAxes.contour

and the `contourf` documentation just below that. An example contrasting the 
behavior with this enabled and disabled was also added:

  
https://scitools.org.uk/cartopy/docs/latest/gallery/scalar_data/contour_transforms.html

I hope this helps! Don't hesitate to follow up and let me know if not.


All the best,

Drew


> I had installed the specialized version of Conda from github as described 
> below, order to access the 'fast' method of contour filling.
> 
> Do we happen to know if that feature is available in the newest version of 
> Cartopy (0.19.0.post1)?  I would like to update away from 0.18, but don't 
> want to lose access to the 'fast' plotting option in that customized release.
> 
> If it does exist, do we happen to know what the kwarg will be to 'turn it 
> on'?  I was following issue #1690 where a few names were suggested, but I 
> can't find a conclusion as to what the final naming convention is.
> 
> I know its an abstract question, but I appreciate any help you can provide?
> 


Ticket Details
===================
Ticket ID: ACE-827366
Department: Support Python
Priority: Low
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.