PyGMT v0.4.1 released

PyGMT v0.4.1 released

Announcing PyGMT v0.4.1, a patch release with a few new gallery examples!

The PyGMT team is pleased to present version v0.4.1, a quick maintenance release with 4 new gallery examples and a couple of highlights:

  • Change default GitHub branch name from “master” to “main” to increase inclusivity (#1360)
  • Add a “PyGMT Team” page (#1308)

The full list of changes can be found in the changelog. Installation/Upgrade instructions can be found at, or you can try it online first at try-gmt! Special shoutout to @yohaimagen for adding an example for the contour method during the SciPy 2021 sprint! Cheers to @mgrund for adding examples for plotting custom symbols and clipping grid values, and @core-man for adding an example for plotting multiple colormaps. All of these can be found at the PyGMT gallery (click on the image below).

Gallery in PyGMT v0.4.1

Thank you also to new contributors @kadatatlukishore, @sean0921, and @soham4abc for some improvements and quick fixes to our documentation! There is now a team gallery to recognize the people working hard behind the scenes to make PyGMT what it is today - a tool used by geoscientists across the globe! We welcome new contributors to join in and contribute to this amazing open source project :smile:!

PyGMT team gallery

:railway_track: Roadmap to v0.5.0

For the next minor release, here are some things we have planned (many of which we need help with!):

  • :globe_with_meridians: + :snake: Design a fresh new PyGMT logo!
  • Integration with ObsPy :snake: to process seismological data (#967)
  • Add a beginner :beginner: friendly PyGMT tutorial that is a good roadmap for new GMT/PyGMT users (#770)
  • More features/enhancements :sparkles::
    • Allow passing in a list/array of angle/font/justify values to text (#483)
    • Wrap more GMT modules, e.g., xyz2grd (#636), triangulate (#731), nearneighbor (#1379), etc
    • Add Figure.hlines() and Figure.vlines() for plotting horizontal and vertical lines (#670)

:warning: Upcoming deprecations

No one likes software that breaks. To ensure a bug-free product and consistency, these are some of the deprecations coming up for future releases of PyGMT:

  • v0.5.0 - NEP29: drop support for NumPy 1.17 so that NumPy 1.18 or above is required
  • v0.6.0 - Aliases “columns” and “sizes” are replaced by “incols” and “size” respectively (a FutureWarning is raised since PyGMT v0.4.0)
  • v1.0.0 (?) - Short form aliases (e.g. ‘R’) will not work if long form aliases (e.g. ‘region’) are available (a SyntaxWarning is raised since PyGMT v0.4.0, see #1316)

The compatibility matrix will be listed on, so make sure you keep things up to date!

:world_map: Community events

We’re going big on outreach and welcome people to join in on these virtual events:

Feel free to reach out to the PyGMT team during those events, or anytime in between! We have quarterly PyGMT community meetings (see the last one in mid June 2021), and are active on this forum and GitHub too. That’s all for now :smile:

Enjoy :partying_face:

P.S. Feel free to share the word on twitter :bird:, #PyGMT @gmt_dev!