Merge branch 'main' into refactor/data_kind

Author: seisman

.github/workflows/ci_docs.yml

@@ -113,7 +113,7 @@ jobs:
             sphinx-autodoc-typehints
             sphinx-copybutton
             sphinx-design
-            sphinx-gallery<0.17.0
+            sphinx-gallery
             sphinx_rtd_theme
 
       # Download cached remote files (artifacts) from GitHub

ci/requirements/docs.yml

@@ -28,5 +28,5 @@ dependencies:
     - sphinx-autodoc-typehints
     - sphinx-copybutton
     - sphinx-design
-    - sphinx-gallery<0.17.0
+    - sphinx-gallery
     - sphinx_rtd_theme

doc/techref/index.md

@@ -8,5 +8,6 @@ visit the {gmt-docs}`GMT Technical Reference <reference.html>`.
 ```{toctree}
 :maxdepth: 1
 
+projections.rst
 encodings.md
 ```

examples/projections/table/README.txt renamed to doc/techref/projections.rst

@@ -1,5 +1,5 @@
-Projection Table
-----------------
+GMT Map Projections
+-------------------
 
 The table below shows the projection codes for the 31 GMT projections:
 

environment.yml

@@ -40,7 +40,7 @@ dependencies:
     - sphinx-autodoc-typehints
     - sphinx-copybutton
     - sphinx-design
-    - sphinx-gallery<0.17.0
+    - sphinx-gallery
     - sphinx_rtd_theme
     # Dev dependencies (type hints)
     - mypy

examples/projections/README.txt

@@ -1,10 +1,11 @@
 Projections
 ===========
 
-PyGMT supports many map projections. Use the ``projection`` parameter to specify which
-one you want to use in all plotting methods. The projection is specified by a one-letter
-code along with (sometimes optional) reference longitude and latitude and the
-width of the map (for example, **A**\ *lon0/lat0*\ [*/horizon*\ ]\ */width*). The map
-height is determined based on the region and projection.
+PyGMT supports many map projections; see :doc:`/techref/projections` for an overview.
+Use the ``projection`` parameter to specify which one you want to use in all plotting
+methods. The projection is specified by a one-letter code along with (sometimes optional)
+reference longitude and latitude and the width of the map (for example,
+**A**\ *lon0/lat0*\ [*/horizon*\ ]\ */width*). The map height is determined based on the
+region and projection.
 
 These are all the available projections:

pygmt/datasets/tile_map.py

@@ -122,7 +122,7 @@ def load_tile_map(
       * band         (band) uint8 ... 1 2 3
       * y            (y) float64 ... -7.081e-10 -7.858e+04 ... -1.996e+07 -2.004e+07
       * x            (x) float64 ... -2.004e+07 -1.996e+07 ... 1.996e+07 2.004e+07
-        spatial_ref  int64 ... 0
+        spatial_ref  int... 0
     >>> # CRS is set only if rioxarray is available
     >>> if hasattr(raster, "rio"):
     ...     raster.rio.crs

pygmt/src/text.py

@@ -63,7 +63,7 @@ def text_(  # noqa: PLR0912
     The text strings passed via the ``text`` parameter can contain ASCII characters and
     non-ASCII characters defined in the Adobe ISOLatin1+, Adobe Symbol, Adobe
     ZapfDingbats and ISO-8859-x (x can be 1-11, 13-16) encodings. Refer to
-    :doc:`techref/encodings` for the full list of supported non-ASCII characters.
+    :doc:`/techref/encodings` for the full list of supported non-ASCII characters.
 
     Full option list at :gmt-docs:`text.html`.