Merge branch 'main' into rajeeja/vector_calc_curl

Author: erogluorhan

docs/conf.py

@@ -232,7 +232,12 @@ def __getattr__(cls, name):
 ]
 
 # add links to ignore during link checking
-linkcheck_ignore = [r"https://gmao.gsfc.nasa.gov/gmaoftp/*"]
+linkcheck_ignore = [
+    r"https://gmao.gsfc.nasa.gov/gmaoftp/*",
+    r"https://docs.xarray.dev/*",
+    r"https://seatstandards.org/*",
+    # More URLs as needed
+]
 
 
 # custom scripts for making a gallery of examples notebooks

docs/contributing.rst

@@ -608,10 +608,8 @@ As we mentioned a few times throughout this guide, UXarray has a static `documen
 repository's code structure. However, there needs to be some manual additions to the
 proper documentation index file(s) for the automation to work.
 
-The index files ``docs/user_api/index.rst`` and ``docs/internal_api/index.rst`` (paths
-relative from the root directory) are used for UXarray documentation to allow the
-`User API <user_api/index.rst>`_ and `Internal API <internal_api/index.rst>`_,
-respectively, to be automatically generated.
+The index file ``docs/user_api/index.rst`` (path relative from the root directory) is
+used for automatically generating the `User API <api.rst>`_ documentation.
 
 That being said, the code changes, which might be a new function implementation or some
 modifications to existing ones, must be added to the appropriate ``index.rst``
@@ -625,8 +623,8 @@ file so that its documentation page is automatically generated.
     needed. However, it would be a great practice to provide usage examples in the
     same PR, especially for demonstrating the use of complex UXarray functions.
 
-The UXarray documentation houses ``examples/<example-name>.ipynb`` files (paths
-relative from the root directory) to provide `Usage Examples <examples.rst>`_ to be
+The UXarray documentation houses ``docs/examples/<example-name>.ipynb`` files (paths
+relative from the root directory) to provide `Usage Examples <gallery.rst>`_ to be
 automatically generated. If you prefer to provide usage examples for the work you
 have put together, please be sure to put your notebook(s) under this same directory.
 

docs/user-guide/grid-formats.rst

@@ -162,7 +162,7 @@ References
 ----------
 * https://easy.gems.dkrz.de/Processing/healpix/index.html#hierarchical-healpix-output
 * https://healpix.sourceforge.io/
-* https://healpix.jpl.nasa.gov/
+* https://irsa.ipac.caltech.edu/healpix/
 * https://iopscience.iop.org/article/10.1086/427976
 
 Parsed Variables

uxarray/core/dataarray.py

@@ -520,10 +520,10 @@ def zonal_mean(self, lat=(-90, 90, 10), conservative: bool = False, **kwargs):
         ----------
         lat : tuple, float, or array-like, default=(-90, 90, 10)
             Latitude specification:
-            - tuple (start, end, step): For non-conservative, computes means at intervals of `step`.
-              For conservative, creates band edges via np.arange(start, end+step, step).
-            - float: Single latitude for non-conservative averaging
-            - array-like: For non-conservative, latitudes to sample. For conservative, band edges.
+                - tuple (start, end, step): For non-conservative, computes means at intervals of `step`.
+                For conservative, creates band edges via np.arange(start, end+step, step).
+                - float: Single latitude for non-conservative averaging
+                - array-like: For non-conservative, latitudes to sample. For conservative, band edges.
         conservative : bool, default=False
             If True, performs conservative (area-weighted) zonal averaging over latitude bands.
             If False, performs traditional (non-conservative) averaging at latitude lines.