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
Justification codes like BL and TR are commonly used in GMT and PyGMT. Currently, we have explanations like:
The justification is a two-character code that is a combination of a horizontal (L\ (eft), C\ (enter), or R\ (ight)) and a vertical (T\ (op), M\ (iddle), or B\ (ottom)) code.
Instead of repeatedly explaining justification codes in different plotting methods, I feel it makes more sense to have a separate page explaining justification codes then we can link to this page when necessary.
Looking at the divio documentation system, I feel it should belong to "Reference" documentation, rather than "Tutorials". Currently, we have an "API Reference" page (https://www.pygmt.org/dev/api/index.html), but apparently "justification" is not an API thing. Maybe we need another section like "Technical Reference" or something else?
The text was updated successfully, but these errors were encountered:
How PyGMT parameters converts to GMT command line options [very technical but maybe useful to some new maintainers and even users]
Explanation of some common options/parameters.
How the "current" CPT works.
...
seisman
changed the title
Add explainations for justification codes
Add a new documentation group for "technical explanations" or "showcases"
Dec 19, 2023
Justification codes like
BL
andTR
are commonly used in GMT and PyGMT. Currently, we have explanations like:Instead of repeatedly explaining justification codes in different plotting methods, I feel it makes more sense to have a separate page explaining justification codes then we can link to this page when necessary.
Looking at the divio documentation system, I feel it should belong to "Reference" documentation, rather than "Tutorials". Currently, we have an "API Reference" page (https://www.pygmt.org/dev/api/index.html), but apparently "justification" is not an API thing. Maybe we need another section like "Technical Reference" or something else?
The text was updated successfully, but these errors were encountered: