diff --git a/source/arguments.rst b/source/arguments.rst
index 7c9f78583..e46314475 100644
--- a/source/arguments.rst
+++ b/source/arguments.rst
@@ -89,6 +89,9 @@ Options and Flags
 :ref:`gps-accuracy<gps-accuracy>` <positive float>
   Set a value in meters for the GPS Dilution of Precision (DOP) information for all images. If your images are tagged with high precision GPS information (RTK), this value will be automatically set accordingly. You can use this option to manually set it in case the reconstruction fails. Lowering this option can sometimes help control bowling-effects over large areas. Default: ``3``
 
+:ref:`gps-z-offset<gps-z-offset>` <float>
+  Set a GPS offset in meters for the vertical axis (Z) by adding it to the altitude value of the GPS EXIF data. This does not change the value of any GCPs. This can be useful for example when adjusting from ellipsoidal to orthometric height. Default: ``0``
+
 :ref:`help<help>` 
   show this help message and exit
 
@@ -246,7 +249,7 @@ Options and Flags
   Path to the image groups file that controls how images should be split into groups. The file needs to use the following format: image_name group_nameDefault: ``None``
 
 :ref:`split-overlap<split-overlap>` <positive integer>
-  Radius of the overlap between submodels. After grouping images into clusters, images that are closer than this radius to a cluster are added to the cluster. This is done to ensure that neighboring submodels overlap. Default: ``150``
+  Radius of the overlap between submodels in meters. After grouping images into clusters, images that are closer than this radius to a cluster are added to the cluster. This is done to ensure that neighboring submodels overlap. All imagesneed GPS information. Default: ``150``
 
 :ref:`texturing-keep-unseen-faces<texturing-keep-unseen-faces>` 
   Keep faces in the mesh that are not seen in any camera. Default:  ``False``
diff --git a/source/arguments/gps-z-offset.rst b/source/arguments/gps-z-offset.rst
new file mode 100644
index 000000000..6b9873429
--- /dev/null
+++ b/source/arguments/gps-z-offset.rst
@@ -0,0 +1,18 @@
+..
+  AUTO-GENERATED by extract_odm_strings.py! DO NOT EDIT!
+  If you want to add more details to a command, edit a
+  .rst file in arguments_edit/<argument>.rst
+
+.. _gps-z-offset:
+
+gps-z-offset
+````````````
+
+**Options:** *<float>*
+
+Set a GPS offset in meters for the vertical axis (Z) by adding it to the altitude value of the GPS EXIF data. This does not change the value of any GCPs. This can be useful for example when adjusting from ellipsoidal to orthometric height. Default: ``0``
+
+
+
+
+`Learn to edit <https://github.com/opendronemap/docs#how-to-make-your-first-contribution>`_ and help improve `this page <https://github.com/OpenDroneMap/docs/blob/publish/source/arguments_edit/gps-z-offset.rst>`_!
diff --git a/source/arguments/split-overlap.rst b/source/arguments/split-overlap.rst
index 1c5c57491..65961dfa3 100644
--- a/source/arguments/split-overlap.rst
+++ b/source/arguments/split-overlap.rst
@@ -10,7 +10,7 @@ split-overlap
 
 **Options:** *<positive integer>*
 
-Radius of the overlap between submodels in meters. After grouping images into clusters, images that are closer than this radius to a cluster are added to the cluster. This is done to ensure that neighboring submodels overlap.  All images need GPS information. Default: ``150``
+Radius of the overlap between submodels in meters. After grouping images into clusters, images that are closer than this radius to a cluster are added to the cluster. This is done to ensure that neighboring submodels overlap. All imagesneed GPS information. Default: ``150``
 
 
 
diff --git a/source/arguments_edit/gps-z-offset.rst b/source/arguments_edit/gps-z-offset.rst
new file mode 100644
index 000000000..8b1378917
--- /dev/null
+++ b/source/arguments_edit/gps-z-offset.rst
@@ -0,0 +1 @@
+