import pygmt # Load sample earthquake data in a pandas.DataFrame quakes = pygmt.datasets.load_usgs_quakes() # Load the builtin Earth relief grid as an xarray.DataArray. relief = pygmt.datasets.load_earth_relief(resolution="30m") # The Figure object controls all plotting functions fig = pygmt.Figure() # Setup a map with a global region, a Mollweide projection, and automatic ticks fig.basemap(region="g", projection="W200/8i", frame=True) # Plot the Earth relief grid in pseudo-color. fig.grdimage(relief, cmap="geo") # Plot earthquakes as circles. Size maps to magnitude and color to depth. fig.plot(x=quakes.longitude, y=quakes.latitude, sizes=0.01*2**quakes.mag, color=quakes.depth/quakes.depth.max(), cmap="viridis", style="cc") # Show a preview of the image (inline if in a Jupyter notebook). fig.show()
🚨 This package is in the early stages of design and implementation. 🚨
All functions/classes/interfaces are subject to change as we experiment with new design ideas and implement new features. This is NOT a finished product.
PyGMT is a library for processing geospatial and geophysical data and making publication quality maps and figures. It provides a Pythonic interface for the Generic Mapping Tools (GMT), a command-line program widely used in the Earth Sciences.
We rely heavily on new features currently being implemented in GMT. In particular, a new modern execution mode that greatly simplifies figure creation. These features are not available in the 5.4 version of GMT. They will be part of the future 6.0 release of GMT predicted for early 2019.
- Make GMT more accessible to new users.
- Build a Pythonic API for GMT.
- Interface with the GMT C API directly using ctypes (no system calls).
- Support for rich display in the Jupyter notebook.
- Integration with the Scipy stack: numpy.ndarray or pandas.DataFrame for data tables and xarray.DataArray for grids.
- Most discussion happens on Github. Feel free to open an issue or comment on any open issue or pull request.
- We have a chat room on Gitter where you can ask questions and leave comments.
- This project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Code of conduct¶
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Please read our Contributing Guide to see how you can help and give feedback.
Imposter syndrome disclaimer¶
We want your help. No, really.
There may be a little voice inside your head that is telling you that you’re not ready to be an open source contributor; that your skills aren’t nearly good enough to contribute. What could you possibly offer?
We assure you that the little voice in your head is wrong.
Being a contributor doesn’t just mean writing code. Equality important contributions include: writing or proof-reading documentation, suggesting or implementing tests, or even giving feedback about the project (including giving feedback about the contribution process). If you’re coming to the project with fresh eyes, you might see the errors and assumptions that seasoned contributors have glossed over. If you can write any code at all, you can contribute code to open source. We are constantly trying out new skills, making mistakes, and learning from those mistakes. That’s how we all improve and we are happy to help others learn.
This disclaimer was adapted from the MetPy project.