You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To get the region of the a PyGMT Figure, fig.region can be used. In case a figure contains different plots with different regions, fig.region always provides the region related to the first plot. This affects the hlines and vlines methods. By default, a line is plotted extending over the complete plotting region. This leads to unexpected / wrong lines for the second and following plots, as the region values related to the first plot are used. A workaround is to explicitly specify the limits.
I can confirm the bug. Figure.region calls the Session.extract_region method, which wraps the GMT_Extract_Region API function.
The GMT_Extract_Region API function opens the "hidden" PS file and reads the information from lines with the PROJ tag, so it can only find the first "region".
Description of the problem
To get the
region
of the a PyGMT Figure,fig.region
can be used. In case a figure contains different plots with different regions,fig.region
always provides theregion
related to the first plot. This affects thehlines
andvlines
methods. By default, a line is plotted extending over the complete plotting region. This leads to unexpected / wrong lines for the second and following plots, as the region values related to the first plot are used. A workaround is to explicitly specify the limits.Minimal Complete Verifiable Example
Full error message
System information
The text was updated successfully, but these errors were encountered: