-
Notifications
You must be signed in to change notification settings - Fork 220
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
Add a gallery example for Figure.legend with StringIO input #3444
Comments
The Should such a gallery example also explain the (main) GMT legend codes (see https://docs.generic-mapping-tools.org/6.5/legend.html#legend-codes)? I feel, for the mentioned GMT example, some addional comments are needed, as understanding a GMT legend specification file requires some knowledge of the GMT syntax (: . |
perhaps we should have a tutorial for legend rather than a gallery example. |
Hm, should such a tutorial focus on creating a legend manually (including the main GMT legend codes) or covering both auto-legends (including the main modifiers that can be appended to the |
We should not explain too many details about the legend codes in either a gallery example or a tutorial. These details should be written in the API documentation of
I think we have both a tutorial and multiple gallery examples. The tutorial should include topics like:
The gallery example should show what |
We already use the auto-legend feature in some tutorials/gallery examples, but we don't have an example for how to manually specify the legend specification. This gallery example (https://www.pygmt.org/dev/gallery/embellishments/legend.html) provides a link to the GMT official documentation and mentions that
Figure.legend
can accept a legend specification file without details.After #3438 is merged, it would be possible to store the legend specification in a StringIO object, so an example would be good.
I think we can add the GMT official example at https://docs.generic-mapping-tools.org/6.5/legend.html#examples as a PyGMT gallery example, similar to the test in #3438.
The text was updated successfully, but these errors were encountered: