Update documentation

2025-07-07 18:01:32 +00:00 · 2025-07-07 18:01:32 +00:00 · 12423c2f2a
commit 12423c2f2a
--- a/_images/Background_animation.webp
+++ b/_images/Background_animation.webp
--- a/_images/EDL_animation.webp
+++ b/_images/EDL_animation.webp
--- a/_images/FOV_animation.webp
+++ b/_images/FOV_animation.webp
--- a/_images/UR_3D.webp
+++ b/_images/UR_3D.webp
--- a/_images/abs_accuracy.webp
+++ b/_images/abs_accuracy.webp
--- a/_images/align_pc.webp
+++ b/_images/align_pc.webp
--- a/_images/bioskeys.webp
+++ b/_images/bioskeys.webp
--- a/_images/camera_animation.webp
+++ b/_images/camera_animation.webp
--- a/_images/cameras.webp
+++ b/_images/cameras.webp
--- a/_images/clipping.webp
+++ b/_images/clipping.webp
--- a/_images/clipping_animation.webp
+++ b/_images/clipping_animation.webp
--- a/_images/clusterodm.webp
+++ b/_images/clusterodm.webp
--- a/_images/congratulations.webp
+++ b/_images/congratulations.webp
--- a/_images/digitalsurfacemodel.webp
+++ b/_images/digitalsurfacemodel.webp
--- a/_images/dockeradvanced.webp
+++ b/_images/dockeradvanced.webp
--- a/_images/dockericon.webp
+++ b/_images/dockericon.webp
--- a/_images/dockersettings.webp
+++ b/_images/dockersettings.webp
--- a/_images/flightplanning.webp
+++ b/_images/flightplanning.webp
--- a/_images/forward_facing.webp
+++ b/_images/forward_facing.webp
--- a/_images/gitgui.webp
+++ b/_images/gitgui.webp
--- a/_images/gitguisuccess.webp
+++ b/_images/gitguisuccess.webp
--- a/_images/height_animation.webp
+++ b/_images/height_animation.webp
--- a/_images/height_profile.webp
+++ b/_images/height_profile.webp
--- a/_images/installpython3.webp
+++ b/_images/installpython3.webp
--- a/_images/lawnmower_pattern.webp
+++ b/_images/lawnmower_pattern.webp
--- a/_images/macwhale.webp
+++ b/_images/macwhale.webp
--- a/_images/measurement.webp
+++ b/_images/measurement.webp
--- a/_images/measurement1.webp
+++ b/_images/measurement1.webp
--- a/_images/measurement2.webp
+++ b/_images/measurement2.webp
--- a/_images/measurement3.webp
+++ b/_images/measurement3.webp
--- a/_images/measurement4.webp
+++ b/_images/measurement4.webp
--- a/_images/measurement7.webp
+++ b/_images/measurement7.webp
--- a/_images/msimbasi_bowling.webp
+++ b/_images/msimbasi_bowling.webp
--- a/_images/navigation.webp
+++ b/_images/navigation.webp
--- a/_images/orthophoto.webp
+++ b/_images/orthophoto.webp
--- a/_images/pencil.webp
+++ b/_images/pencil.webp
--- a/_images/pointcloud.webp
+++ b/_images/pointcloud.webp
--- a/_images/pointcloud_elevation.webp
+++ b/_images/pointcloud_elevation.webp
--- a/_images/rel_accuracy.webp
+++ b/_images/rel_accuracy.webp
--- a/_images/rotation.webp
+++ b/_images/rotation.webp
--- a/_images/seedling.webp
+++ b/_images/seedling.webp
--- a/_images/smrf.webp
+++ b/_images/smrf.webp
--- a/_images/stockpile.webp
+++ b/_images/stockpile.webp
--- a/_images/texturedmodel.webp
+++ b/_images/texturedmodel.webp
--- a/_images/thermal.webp
+++ b/_images/thermal.webp
--- a/_images/vimdiff_ceres_change.webp
+++ b/_images/vimdiff_ceres_change.webp
--- a/_images/virtualboxsettings.webp
+++ b/_images/virtualboxsettings.webp
--- a/_images/virtualizationcheck.webp
+++ b/_images/virtualizationcheck.webp
--- a/_images/webodmdashboard.webp
+++ b/_images/webodmdashboard.webp
--- a/_images/webodmsuccess.webp
+++ b/_images/webodmsuccess.webp
--- a/_sources/arguments/align.rst.txt
+++ b/_sources/arguments/align.rst.txt
@ -15,7 +15,7 @@ Path to a GeoTIFF DEM or a LAS/LAZ point cloud that the reconstruction outputs s

 See `Multi-temporal datasets for further usage information. <../../map-accuracy/#improving-relative-accuracy>`_

-.. figure:: ../images/align_pc.gif
+.. figure:: ../images/align_pc.webp
   :alt: Animated gif comparing two separately processed, but aligned digital surface models.
   :align: center

--- a/_sources/arguments/auto-boundary.rst.txt
+++ b/_sources/arguments/auto-boundary.rst.txt
@ -57,14 +57,14 @@ Example Images

 True: ``--auto-boundary``
 ^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140864618-2a0c95f2-669e-45dc-b5c5-df82a555e4e5.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140864618-2a0c95f2-669e-45dc-b5c5-df82a555e4e5.webp
  :alt: WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree.

  The WebODM 3D View shows the full extent of the reconstruction, bounded by the ``--auto-boundary`` option.

 False: ``null``
 ^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140864753-db3695c5-3ba2-48fb-a644-3e591913de72.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140864753-db3695c5-3ba2-48fb-a644-3e591913de72.webp
  :alt: WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree.

  The WebODM 3D View shows the full extent of the recosntruction. Compared to the ``--auto-boundary`` reconstruction above, one can see that the full reconstruction area is much larger (and therefore more visually sparse).
--- a/_sources/arguments/boundary.rst.txt
+++ b/_sources/arguments/boundary.rst.txt
@ -62,28 +62,28 @@ GeoJSON.io

 New GeoJSON
 """"""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102197-b44fea3b-01df-4f2f-9cde-f1c94ba2e8d3.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102197-b44fea3b-01df-4f2f-9cde-f1c94ba2e8d3.webp
  :alt: GeoJSON.io interface with empty GeoJSON map and text.

  After opening the above link to GeoJSON.io, one should pan and zoom the map preview to find their area of interest.

 Creating A Polygon
 """""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102194-7992ddf8-81ce-4ee9-bb81-b5d93cb05e25.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102194-7992ddf8-81ce-4ee9-bb81-b5d93cb05e25.webp
  :alt: Choosing the "Draw Polygon" menu option in the Map View.

  Selecting the "Draw Polygon" menu option will allow you to place vertices for your polygon by left-clicking on the map.

 Placing Vertices
 """""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102186-38a4107f-4c93-46f9-b423-3ce40fddff4b.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102186-38a4107f-4c93-46f9-b423-3ce40fddff4b.webp
  :alt: Placing vertices in the Map View to create the boundary GeoJSON.
  
  Choose the appropriate locations of the boundary of your polygon by left-clicking on the map to place a vertex. You can place as many vertices as you require.

 Completing A Polygon
 """""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102193-4e619f4e-e95d-4c3d-8f89-29a38015bce0.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102193-4e619f4e-e95d-4c3d-8f89-29a38015bce0.webp
  :alt: Completed polygon in the Map View and GeoJSON text view.

  To close the polygon, you left-click on your first vertex. You will be able to close your polygon once you have placed at least three vertices on the map.
@ -91,7 +91,7 @@ Completing A Polygon

 Saving A Polygon
 """""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102199-a5d37bbf-d057-46d8-8baf-91817c7e2f30.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102199-a5d37bbf-d057-46d8-8baf-91817c7e2f30.webp
  :alt: Saving the polygon using the Save menu and choosing GeoJSON.

  Select "Save" and then "GeoJSON" to save the completed GeoJSON boundary to disk. Your browser will prompt or otherwise alert you that the file is ready to download. Alternatively, you can copy and paste the text-only representation of the GeoJSON boundary from the right panel with the "JSON" header.
@ -138,21 +138,21 @@ Saving A Polygon

 Downloading A Polygon
 """"""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145103954-17ba7c31-fda6-4883-b7a6-3f0bacc266dd.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145103954-17ba7c31-fda6-4883-b7a6-3f0bacc266dd.webp
  :alt: Browser Download/Save file prompt for the generated GeoJSON file.

  Once the GeoJSON file has been chosen for saving, the browser will prompt you to save it to disk. Choose an appropriate location where you can access it at a later time to load into WebODM.

 Setting Boundary [GeoJSON] In Task Options
 """""""""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102200-02bd1c97-e0e8-4932-a77d-91562823b46e.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102200-02bd1c97-e0e8-4932-a77d-91562823b46e.webp
  :alt: Task Options preview showing Boundary field and "Load" icon.
  
  When you are editing the Task Options for your Task, you can choose to load the Boundary [GeoJSON] created above by clicking the "Load" icon. Alternatively, you can paste the textual representation of the boundary into the Boundary [GeoJSON] text box.
  
 Boundary [GeoJSON] Loaded In Task Options
 """"""""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145102196-8f87e4ac-197f-4ce0-ac6f-082772921ea0.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145102196-8f87e4ac-197f-4ce0-ac6f-082772921ea0.webp
  :alt: Task Options preview showing loaded Boundary with GeoJSON text.
  
  Once the Boundary [GeoJSON] has been loaded from disk or pasted from the system clipboard, you can confirm its presence by seeing the text in the text box. You can now save the Task Options to enable the Boundary [GeoJSON] for the processing Task.
@ -164,28 +164,28 @@ QGIS
 
 Creating A New Temporary Scratch Layer
 """""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109912-9176cd94-1140-43ac-a371-96de2b874ec3.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109912-9176cd94-1140-43ac-a371-96de2b874ec3.webp
  :alt: Choosing the "Create A Temporary Scratch Layer" tool to make an empty layer to create our Boundary [GeoJSON] within.
  
  You will first need a layer to create your Boundary [GeoJSON] within, so creating a New Temporary Scratch layer is a way to do this without needing to setup a file on disk first.
  
 New Temporary Scratch Layer Geometry Type
 """"""""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109915-ddbfed43-da5e-466b-a4b6-d6ff3b96a555.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109915-ddbfed43-da5e-466b-a4b6-d6ff3b96a555.webp
  :alt: Setting "Polygon" as the Geometry Type for the Temporary Scratch Layer.
  
  There are numerous choices of geometry types that can be represented by a given layer. OpenDroneMap is designed to work with Single Polygon, so you will choose Polygon from the Geometry Type menu.
  
 New Temporary Scratch Layer Settings
 """""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109917-58b6c147-bdae-45be-839d-5d56b1a22fe8.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109917-58b6c147-bdae-45be-839d-5d56b1a22fe8.webp
  :alt: Leaving the remaining settings in their Default state.
  
  Similar to Geometry Types, there are a large number of settings and options you can adjust for a Temporary Scratch Layer. You should leave these at their pictured defaults for usage with OpenDroneMap.

 Adding an Orthophoto Background
 """"""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109918-df591ce8-3df4-485d-a775-81813b7e61ef.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109918-df591ce8-3df4-485d-a775-81813b7e61ef.webp
  :alt: Browsing to a generated Orthophoto from WebODM that covers the Area Of Interest (AOI).
  
  If you have run the task already without a Boundary [GeoJSON], you can load the generated Orthophoto from OpenDroneMap into QGIS to use as your basemap for creating your Boundary [GeoJSON]. This should ensure that your boundary polygon exactly matches the data in your Task, as different basemaps can have errors of 1-10m or more. 
@ -193,35 +193,35 @@ Adding an Orthophoto Background
  
 Adding A Polyon Feature
 """"""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109907-b61afb3c-fdd2-4eef-872a-91f2ea97d887.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109907-b61afb3c-fdd2-4eef-872a-91f2ea97d887.webp
  :alt: Selecting the "Add A Polygon Feature" tool to begin creating a boundary polygon.
  
  After selecting the "Add A Polygon Feature" tool, you can begin placing vertices on the map to create your boundary. To finish your polygon, you will right-click on the canvas. Similar to GeoJSON.io, a finished polygon will have a darker outline and a darker fill to indicate that it is "solid".
  
 Toggle Editing Off
 """""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109924-42480f63-2cfa-427c-8414-f45d39f796f7.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109924-42480f63-2cfa-427c-8414-f45d39f796f7.webp
  :alt: Clicking the "Toggle Editing" tool will prompt you to save your changes to the Temporary Scratch Layer.
  
  Once you are finished with your boundary polygon, you can click the "Toggle Editing" tool to accept your changes and write them out to the Temporary Scratch Layer and make the layer valid for saving/exporting to disk.
  
 Save Changes To Temporary Scratch Layer
 """"""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109921-73ab273a-7180-40ea-ba3d-75ecb65c97f5.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109921-73ab273a-7180-40ea-ba3d-75ecb65c97f5.webp
  :alt: QGIS Dialog asking you to Save your changes to the Temporary Scratch Layer.
  
  Clicking Save on this dialog will write the changes to the Temporary Scratch Layer and enable export/save functionality.
  
 Export Temporary Scratch Layer Features
 """"""""""""""""""""""""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109911-45d7dae3-49ce-40fb-8df0-85a164763810.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109911-45d7dae3-49ce-40fb-8df0-85a164763810.webp
  :alt: A right-click on the Temporary Scratch Layer in the Layers panel will expose the Export menu item, with the Save Features As sub-menu item.
  
  Right-click on the Temporary Scratch Layer in the Layers panel to bring up the Export menu and the Save Features As sub-menu item, selecting Save Features As. This will prompt you to choose the export format, location and file name, and settings for your layer.
  
 Save Vector Layer As
 """""""""""""""""""""
-.. figure:: https://user-images.githubusercontent.com/19295950/145109923-b55dfc1a-5c31-4382-8b1f-3bc6322b0f33.png
+.. figure:: https://user-images.githubusercontent.com/19295950/145109923-b55dfc1a-5c31-4382-8b1f-3bc6322b0f33.webp
  :alt: The "Save Vector Layer As" dialog showing Format as GeoJSON, an example of a valid File Name and path, CRS of EPSG:4326 and other default options. 
  
  This dialog will require you to choose GeoJSON as the format, a valid filename and path for the GeoJSON to be written out to disk with, and a valid CRS. The safest CRS choice with GeoJSON is EPSG:4326, so choose that if it is not chosen by default. All other options should be left as default and do not apply for OpenDroneMap usage.
@ -231,35 +231,35 @@ Example Images

 True: ``--boundary [GeoJSON]`` - Point Cloud
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140858936-10fda65f-c278-46ae-95bd-7af8f8369554.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140858936-10fda65f-c278-46ae-95bd-7af8f8369554.webp
  :alt: WebODM displaying the "clipped" reconstruction of the Brighton Beach dataset Point Cloud.

  The WebODM 3D View shows the modified extent of the reconstruction Point Cloud, bounded by the GeoJSON proivded to the ``--boundary`` option.

 True: ``--boundary [GeoJSON]`` - Orthophoto
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140859033-c6cab4f0-74b3-4266-b5ec-4a90da931340.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140859033-c6cab4f0-74b3-4266-b5ec-4a90da931340.webp
  :alt: WebODM displaying the "clipped" reconstruction of the Brighton Beach dataset Orthophoto.

  The WebODM 3D View shows the modified extent of the reconstruction Orthophoto, bounded by the GeoJSON proivded to the ``--boundary`` option.

 True: ``--boundary [GeoJSON]`` - Digital Elevation Model
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140859073-28db5174-9a40-42d8-86d6-f345d9dad5a8.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140859073-28db5174-9a40-42d8-86d6-f345d9dad5a8.webp
  :alt: WebODM displaying the "clipped" reconstruction of the Brighton Beach dataset Digital Elevation Model.

  The WebODM 3D View shows the modified extent of the reconstruction Digital Elevation Model, bounded by the GeoJSON proivded to the ``--boundary`` option.

 True: ``--boundary [GeoJSON]`` - 3D Model/Textured Mesh
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140859125-4854e651-9eff-430d-956c-16f4d9a52dfd.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140859125-4854e651-9eff-430d-956c-16f4d9a52dfd.webp
  :alt: WebODM displaying the "clipped" reconstruction of the Brighton Beach dataset 3D Model/Textured Mesh.

  The WebODM 3D View shows the modified extent of the reconstruction 3D Model/Textured Mesh, bounded by the GeoJSON proivded to the ``--boundary`` option.

 False: ``null``
 ^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/140858712-9bfd8c56-a52a-480e-b68d-d5a97bc516fd.png
+.. figure:: https://user-images.githubusercontent.com/19295950/140858712-9bfd8c56-a52a-480e-b68d-d5a97bc516fd.webp
  :alt: WebODM displaying the full reconstruction of the Brighton Beach dataset Point Cloud.

  The WebODM 3D View shows the full extent of the recosntruction. Compared to the ``--boundary`` reconstruction above, one can see that the full reconstruction area is much larger and includes many features outside of the Area Of Interest used to generate the GeoJSON.
--- a/_sources/arguments/build-overviews.rst.txt
+++ b/_sources/arguments/build-overviews.rst.txt
@ -60,14 +60,14 @@ Example Images

 True: ``--build-overviews``
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127073339-6b2a0a4f-6ede-4dc1-8da4-5bc9646de304.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127073339-6b2a0a4f-6ede-4dc1-8da4-5bc9646de304.webp
  :alt: QGIS displaying the generated Overviews

  The Layer Properties panel demonstrates that this OpenDroneMap-generated GeoTIFF has internal Overviews.

 False: ``null``
 ^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127074349-a3f84c4c-d05c-4bf1-bd7c-790781ad0fe3.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127074349-a3f84c4c-d05c-4bf1-bd7c-790781ad0fe3.webp
  :alt: QGIS displaying the file is lacking Overviews

  The Layer Properties panel demonstrates that this OpenDroneMap-generated GeoTIFF lacks internal Overviews.
--- a/_sources/arguments/camera-lens.rst.txt
+++ b/_sources/arguments/camera-lens.rst.txt
@ -56,21 +56,21 @@ The following examples are all data taken with a standard Rectilinear Lens. Manu

 ``auto`` : Rectilinear Data
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127077336-ae79a958-a953-4376-86fd-430d0e5457f2.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127077336-ae79a958-a953-4376-86fd-430d0e5457f2.webp
  :alt: Rectilinear data rendered by ``auto`` Camera Lens Model

  This Point Cloud shows a proper reconstruction via the ``auto`` (``brown``) Camera Lens Model, which is appropriate for this sensor.

 ``brown`` : Rectilinear Data
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127077753-580a174e-7572-4315-8801-224ce097d9fc.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127077753-580a174e-7572-4315-8801-224ce097d9fc.webp
  :alt: Rectilinear data rendered by ``brown`` Camera Lens Model

  As in the prior example, this Point Cloud is reconstructed via the ``brown`` Camera Lens Model.

 ``fisheye`` : Rectilinear Data
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127077826-53d459fe-5e4e-4b10-8e70-fbddf775c4f7.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127077826-53d459fe-5e4e-4b10-8e70-fbddf775c4f7.webp
  :alt: Rectilinear data rendered by ``fisheye`` Camera Lens Model

  In this Point Cloud reconstruction, severe bowling and other artifacts have been introduced via the use of the wrong Camera Lens Model.
@ -78,7 +78,7 @@ The following examples are all data taken with a standard Rectilinear Lens. Manu
 ``perspective`` : Rectilinear Data
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-.. figure:: https://user-images.githubusercontent.com/19295950/127077485-699f9e61-72a6-45f2-990f-f5748b6ee99f.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127077485-699f9e61-72a6-45f2-990f-f5748b6ee99f.webp
  :alt: Rectilinear data rendered by ``perspective`` Camera Lens Model

  This Point Cloud rendered well, very similar to the ``auto`` and ``brown`` examples. One may see artifacts in the ``perspective`` Camera Lens Model in very large collections, or over very flat/homogenus terrain (agricultural fields). In such cases, forcing ``brown`` may help.
@ -86,7 +86,7 @@ The following examples are all data taken with a standard Rectilinear Lens. Manu
 ``spherical`` : Rectilinear Data
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-.. figure:: https://user-images.githubusercontent.com/19295950/127078960-27e35cbb-a378-4d0d-92e2-42dbfd1edd7c.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127078960-27e35cbb-a378-4d0d-92e2-42dbfd1edd7c.webp
  :alt: Rectilinear data rendered by ``spherical`` Camera Lens Model

  This Point Cloud failed to reconstruct properly due to the manual selection of the ``fisheye`` Camera Lens Model. Similar failures to reconstruct can often indicate the wrong manual selection, or in edge cases, wrong ``auto`` selection of the Camera Lens Model, and you are advised to try another Model that is more appropriate.
--- a/_sources/arguments/cog.rst.txt
+++ b/_sources/arguments/cog.rst.txt
@ -55,34 +55,34 @@ Example Images

 True: ``--cog``
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127079824-c85fa5a9-842a-4f28-a380-b6404aac7ef2.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127079824-c85fa5a9-842a-4f28-a380-b6404aac7ef2.webp
  :alt: GDAL Info showing LAYOUT=COG

  The Raster Information tool in QGIS can print information from gdalinfo which can be used to confirm the conformance of a GeoTIFF to the COG spec.

-.. figure:: https://user-images.githubusercontent.com/19295950/138731905-d10483bd-b91b-4f63-bfb4-89c0f50bf74b.png
+.. figure:: https://user-images.githubusercontent.com/19295950/138731905-d10483bd-b91b-4f63-bfb4-89c0f50bf74b.webp
  :alt: QGIS Layer Properties showing Internal Overviews

  The Layer Properties panel can show that there are in fact internal overviews. Keep in mind that not every GeoTIFF has internal overviews, but every COG must.

-.. figure:: https://user-images.githubusercontent.com/19295950/138733095-fb5f07ef-fbb0-48f4-8401-25cbf5294b9d.png
+.. figure:: https://user-images.githubusercontent.com/19295950/138733095-fb5f07ef-fbb0-48f4-8401-25cbf5294b9d.webp
  :alt: QGIS Layer Properties showing an on-disk file size of 8.78 MB

  Note that the on-disk file size is 8.78 MB for the COG due to the presence of internal overviews when compared to the 6.30 MB of the non-COG GeoTIFF below.

 False: ``null``
 ^^^^^^^^^^^^^^^
-.. figure:: https://user-images.githubusercontent.com/19295950/127080115-7e09ba30-140f-402d-b00a-8bb0c7bc72ff.png
+.. figure:: https://user-images.githubusercontent.com/19295950/127080115-7e09ba30-140f-402d-b00a-8bb0c7bc72ff.webp
  :alt: GDAL Info not showing LAYOUT=COG

  The Raster Information tool in QGIS does not show LAYOUT=COG, which indicates that this GeoTIFF does not meet the COG spec.

-.. figure:: https://user-images.githubusercontent.com/19295950/138732051-d227c98d-10a5-46de-ac99-8c5ffb0a12b2.png
+.. figure:: https://user-images.githubusercontent.com/19295950/138732051-d227c98d-10a5-46de-ac99-8c5ffb0a12b2.webp
  :alt: QGIS Layer Properties not showing Internal Overviews

  The Layer Properties panel shows that the GeoTIFF lacks all levels of Internal Pyramids.

-.. figure:: https://user-images.githubusercontent.com/19295950/138733132-a9c4f8b4-673a-426b-a665-bde5e89e4de3.png
+.. figure:: https://user-images.githubusercontent.com/19295950/138733132-a9c4f8b4-673a-426b-a665-bde5e89e4de3.webp
  :alt: QGIS Layer Properties showing an on-disk file size of 6.30 MB

  Note that the on-disk file size is 6.30 MB for the COG due to the lack of internal overviews when compared to the 8.78 MB of the COG GeoTIFF above.
--- a/_sources/index.rst.txt
+++ b/_sources/index.rst.txt
@ -30,7 +30,7 @@ The documentation is available in several languages. Some translations are incom
 |
 |

-.. figure:: images/seedling.png
+.. figure:: images/seedling.webp
    :alt: image of seedling
    :align: right
    :height: 70
@ -41,7 +41,7 @@ The documentation is available in several languages. Some translations are incom
    installation


-.. figure:: images/pencil.png
+.. figure:: images/pencil.webp
    :alt: image of pencil
    :align: right
    :height: 60
--- a/_sources/installation.rst.txt
+++ b/_sources/installation.rst.txt
@ -62,7 +62,7 @@ Step 1. Check Virtualization Support

 Docker requires a feature from your CPU called virtualization, which allows it to run virtual machines (VMs). Make sure you have it enabled! Sometimes this is disabled. To check, on Windows 8 or higher you can open the **Task Manager** (press CTRL+SHIFT+ESC) and switch to the **Performance** tab.

-.. figure:: images/virtualizationcheck.png
+.. figure:: images/virtualizationcheck.webp
   :alt: Image of checking virtualization in Windows 8 or higher
   :align: center

@ -73,7 +73,7 @@ www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead.

 If virtualization is disabled, you’ll need to enable it. The procedure unfortunately is a bit different for each computer model, so the best way to do this is to look up on a search engine “how to enable vtx for <type your computer model here>”. Often times it’s a matter of restarting the computer, immediately pressing F2 or F12 during startup, navigating the boot menu and changing the settings to enable virtualization (often called “VT-X”).

-.. figure:: images/bioskeys.png
+.. figure:: images/bioskeys.webp
   :alt: Table of different bios keys
   :align: center

@ -89,7 +89,7 @@ First, you’ll need to install:

 For Python 3, make sure you check **Add Python 3.x to PATH** during the installation.

-.. figure:: images/installpython3.png
+.. figure:: images/installpython3.webp
   :alt: Screenshot of Python3 installation process
   :align: center

@ -119,7 +119,7 @@ If you installed Docker Toolbox (see below if you installed Docker for Windows i
 3. Right click the **default** VM and press **Settings...**
 4. Move the **Base Memory** slider from the **System** panel and allocate 60-70% of all available memory, optionally adding 50% of the available processors from the **Processor** tab also

-.. figure:: images/virtualboxsettings.png
+.. figure:: images/virtualboxsettings.webp
   :alt: Screenshot of VirtualBox Settings
   :align: center

@ -134,13 +134,13 @@ If you installed Docker for Windows instead:
 3. From the panel, click **Advanced** and use the sliders to allocate 60-70% of available memory and use half of all available CPUs.
 4. Press **Apply**.

-.. figure:: images/dockericon.png
+.. figure:: images/dockericon.webp
   :alt: Screenshot of Docker Icon
   :align: center

 *Step 1 Docker icon*

-.. figure:: images/dockersettings.png
+.. figure:: images/dockersettings.webp
   :alt: Screenshot of Docker Settings
   :align: center

@ -156,7 +156,7 @@ Open the **Git Gui** program that comes installed with Git. From there:
 * In **Target Directory** click browse and navigate to a folder of your choosing (create one if necessary)
 * Press **Clone**

-.. figure:: images/gitgui.png
+.. figure:: images/gitgui.webp
   :alt: Screenshot of Git Gui
   :align: center

@ -164,7 +164,7 @@ Open the **Git Gui** program that comes installed with Git. From there:

 If the download succeeded, you should now see this window:

-.. figure:: images/gitguisuccess.png
+.. figure:: images/gitguisuccess.webp
   :alt: Screenshot of Git Gui after successful download
   :align: center

@ -183,7 +183,7 @@ From Git Gui, go to the **Repository** menu, then click **Git Bash**. From the c
 	
 Several components will download to your machine at this point, including WebODM, NodeODM and ODM. After the download you should be greeted by the following screen:

-.. figure:: images/webodmsuccess.png
+.. figure:: images/webodmsuccess.webp
   :alt: Screenshot of after successfully downloading WebODM
   :align: center

@ -238,7 +238,7 @@ There are only two programs to install:

 After installing docker you should find an icon that looks like a whale in the task bar.

-.. figure:: images/macwhale.png
+.. figure:: images/macwhale.webp
   :alt: Screenshot of Docker whale
   :align: center

@ -280,7 +280,7 @@ Docker on macOS works by running a VM in the background (think of it as a “com
 3. Adjust the CPUs slider to use half of all available CPUs and the memory to use 60-70% of all available memory
 4. Press **Apply & Restart**

-.. figure:: images/dockeradvanced.png
+.. figure:: images/dockeradvanced.webp
   :alt: Screenshot of Docker advanced settings
   :align: center

@ -435,7 +435,7 @@ Hello, WebODM!

 After running ./webodm.sh start and opening WebODM in the browser, you will be greeted with a welcome message and will be asked to create the first user. Take some time to familiarize yourself with the web interface and explore its various menus.

-.. figure:: images/webodmdashboard.png
+.. figure:: images/webodmdashboard.webp
   :alt: Screenshot of WebODM Dashboard
   :align: center

@ -445,7 +445,7 @@ Notice that under the **Processing Nodes** menu there’s a "node-odm-1" node al

 If you’ve made it this far, congratulations! Now it’s time to start processing some data.

-.. figure:: images/congratulations.png
+.. figure:: images/congratulations.webp
   :alt: Image of celebratory dance
   :align: center

--- a/_sources/large.rst.txt
+++ b/_sources/large.rst.txt
@ -36,7 +36,7 @@ Distributed Split-Merge

 ODM can also automatically distribute the processing of each submodel to multiple machines via `NodeODM <https://github.com/OpenDroneMap/NodeODM>`_ nodes, orchestrated via `ClusterODM <https://github.com/OpenDroneMap/ClusterODM>`_.

-.. figure:: images/clusterodm.png
+.. figure:: images/clusterodm.webp
   :alt: image of lens distortion effect on bowling of data
   :align: center

--- a/_sources/map-accuracy.rst.txt
+++ b/_sources/map-accuracy.rst.txt
@ -15,7 +15,7 @@ Local or relative accuracy can be defined as the degree to which de distances be

 Relative accuracy is independent of the location of the map in the world, so a map can have a high relative accuracy (in size and shape) but its position in the world can be shifted (Figure 1). 

-.. figure:: images/rel_accuracy.png
+.. figure:: images/rel_accuracy.webp
   :alt: Model showing high relative accuracy
   :align: center
   
@ -27,7 +27,7 @@ Relative accuracy is independent of the location of the map in the world, so a m

 Absolute accuracy is the accuracy of the reconstruction in relation to its true position on the planet (Pix4D 2019). Figure 2 shows a relative and absolute accurate model, as the points are correctly placed according to its real world position. 

-.. figure:: images/abs_accuracy.png
+.. figure:: images/abs_accuracy.webp
   :alt: Model showing high absolute accuracy
   :align: center

@ -263,7 +263,7 @@ When previously mapped sites need revisited, OpenDroneMap can align multiple ver

 **Output example for aligned datasets:**

-.. figure:: images/align_pc.gif
+.. figure:: images/align_pc.webp
   :alt: Animated gif comparing two separately processed, but aligned digital surface models.
   :align: center

@ -350,7 +350,7 @@ At the end of the script you obtain a directory by epoch (at the same level as t
   ├── 1_after/
   └── time-sift-block/

-.. |image1| image:: https://forge.inrae.fr/Denis.Feurer/timesift-odm-data-example/-/raw/main/Example.png?ref_type=heads
+.. |image1| image:: https://forge.inrae.fr/Denis.Feurer/timesift-odm-data-example/-/raw/main/Example.webp?ref_type=heads


 -----------------------
--- a/_sources/multispectral.rst.txt
+++ b/_sources/multispectral.rst.txt
@ -63,7 +63,7 @@ Thermal Support

 ODM has support for radiometric calibration of thermal data, which is able to generate temperature orthophotos from long-wave infrared (LWIR) cameras. LWIR images can be processed alone or as part of a multispectral dataset.

-.. figure:: images/thermal.jpeg
+.. figure:: images/thermal.webp
   :alt: Screen shot of thermal imagery as displayed in WebODM
   :align: center

--- a/_sources/outputs.rst.txt
+++ b/_sources/outputs.rst.txt
@ -8,7 +8,7 @@ Point Cloud

 ``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The georeferenced point cloud in different file formats

-.. figure:: images/pointcloud.png
+.. figure:: images/pointcloud.webp
   :alt: image of OpenDroneMap derived point cloud
   :align: center
   
@ -23,7 +23,7 @@ Point Cloud

 You can access the point cloud and textured meshes using MeshLab. Open MeshLab, and choose ``File:Import Mesh`` and choose your textured mesh from a location similar to the following: ``odm_texturing\odm_textured_model.obj``

-.. figure:: images/UR_3D.gif
+.. figure:: images/UR_3D.webp
   :alt: image of OpenDroneMap derived textured mesh
   :align: center
   
@ -36,7 +36,7 @@ Orthophoto

 ``odm_orthophoto/odm_orthphoto.original.tif`` -- The orthophoto in its original un-cropped state.

-.. figure:: images/orthophoto.png
+.. figure:: images/orthophoto.webp
   :alt: image of OpenDroneMap orthophoto
   :align: center

@ -52,7 +52,7 @@ Data will be stored in:
 * ``odm_dem/dtm.tif``
 * ``odm_dem/dsm.tif``

-.. figure:: images/digitalsurfacemodel.png
+.. figure:: images/digitalsurfacemodel.webp
   :alt: image of OpenDroneMap derived digital surface model
   :align: center
   
@ -102,7 +102,7 @@ List of all outputs
    │   ├── odm_georeferencing_log.txt      # Georeferencing log
    │   └── odm_georeferencing_utm_log.txt  # Log for the extract_utm portion
    ├── odm_orthophoto/
-    │   ├── odm_orthophoto.png              # Orthophoto image (no coordinates)
+    │   ├── odm_orthophoto.webp              # Orthophoto image (no coordinates)
    │   ├── odm_orthophoto.tif              # Orthophoto GeoTiff
    │   ├── odm_orthophoto_log.txt          # Log file
    │   └── gdal_translate_log.txt          # Log for georeferencing the png file
--- a/_sources/tutorials.rst.txt
+++ b/_sources/tutorials.rst.txt
@ -10,7 +10,7 @@ Below you will find instructions for some common use cases.
 Creating High Quality Orthophotos
 *********************************

-.. figure:: images/orthophoto.png
+.. figure:: images/orthophoto.webp
   :alt: image of OpenDroneMap orthophoto
   :align: center

@ -26,7 +26,7 @@ Creating Digital Elevation Models

 By default ODM does not create digital elevation models (DEMs). To create a digital terrain model, make sure to pass the ``--dtm`` flag. To create a digital surface model, be sure to pass the ``--dsm`` flag.

-.. figure:: images/digitalsurfacemodel.png
+.. figure:: images/digitalsurfacemodel.webp
   :alt: image of OpenDroneMap derived digital surface model
   :align: center

@ -43,7 +43,7 @@ Overall the ``--smrf-threshold`` option has the biggest impact on results.

 SMRF is good at avoiding Type I errors (small number of ground points mistakenly classified as non-ground) but only "acceptable" at avoiding Type II errors (large number non-ground points mistakenly classified as ground). This needs to be taken in consideration when generating DTMs that are meant to be used visually, since objects mistaken for ground look like artifacts in the final DTM.

-.. figure:: images/smrf.png
+.. figure:: images/smrf.webp
   :alt: image of lens distortion effect on bowling of data
   :align: center

@ -68,7 +68,7 @@ You can also click in the camera icon to display single images in a frame on the

 Within the image frame there are links to download the image and the GeoJSON camera file.

-.. figure:: images/cameras.png
+.. figure:: images/cameras.webp
   :alt: Camera locations
   :align: center

@ -77,7 +77,7 @@ Textured model

 Activate this function to show load the textured model. Depending on the file size and connection speed, it may take several seconds to load.

-.. figure:: images/texturedmodel.png
+.. figure:: images/texturedmodel.webp
   :alt: Textured model
   :align: center

@ -99,7 +99,7 @@ Field of view

 In order to control model elements to be included within the scene the field of view can be adjusted. Default value is set to 60 degrees.

-.. figure:: images/FOV_animation.gif
+.. figure:: images/FOV_animation.webp
   :alt: Field of view adjustment
   :align: center

@ -113,7 +113,7 @@ Eye Dome-lighting group objects, shade their outlines and enhances depth percept

 By default, Eye Dome-Lighting is enabled on Potree 3D viewer, but it can be disabled by clicking on the enable option.

-.. figure:: images/EDL_animation.gif
+.. figure:: images/EDL_animation.webp
   :alt: Eye dome lighting adjustment
   :align: center

@ -123,7 +123,7 @@ Background

 Potree 3D viewer background can be modified. Available options are **Skybox** / **Gradient** / **Black** / **White** / **None**

-.. figure:: images/Background_animation.gif
+.. figure:: images/Background_animation.webp
   :alt: Background selection
   :align: center

@ -149,7 +149,7 @@ It also has controls for showing or hiding the resulting measurement labels.

 Measurements are performed by left clicking on the desired points and for some tools right clicking is needed in order to terminate the process.

-.. figure:: images/measurement.png
+.. figure:: images/measurement.webp
   :alt: Tools - Measurement tools
   :align: center

@ -177,7 +177,7 @@ This tool measures the height or vertical distance between two points.
 To start a measurement, click on the height icon and then click on the desired two points. The process will be automatically ended.
 Further information can also be obtained from selecting this element under the scene section.

-.. figure:: images/height_animation.gif
+.. figure:: images/height_animation.webp
   :alt: Height measurement
   :align: center

@ -217,7 +217,7 @@ This tool creates a height profile formed by a line on the model.
 To start a measurement, click on the Height profile icon and then form a line on the model by clicking on the desired points (two or more). Right click to finish measurement.
 Further information and options, such as "Show 2d Profile", can also been obtained from selecting this element under the scene section.

-.. figure:: images/height_profile.png
+.. figure:: images/height_profile.webp
   :alt: Height profile
   :align: center

@ -237,7 +237,7 @@ Clipping
 ---------


-.. figure:: images/clipping.png
+.. figure:: images/clipping.webp
   :alt: Tools - Clipping tools
   :align: center

@ -248,14 +248,14 @@ Highlight is set by default as the clipping method. If display only the points c

 To remove the clipping volume or polygons click on the "Remove all measurements" icon.

-.. figure:: images/clipping_animation.gif
+.. figure:: images/clipping_animation.webp
   :alt: Tools - Clipping
   :align: center

 Navigation
 -----------

-.. figure:: images/navigation.png
+.. figure:: images/navigation.webp
   :alt: Tools - Navigation controls
   :align: center

@ -299,7 +299,7 @@ The camera animation button creates a camera animation path. Position of the cam

 To create an animation, adjust the points for the camera locations and camera direction, then select the camera element under the Scene section to create more point, change animation speed or play the animation.

-.. figure:: images/camera_animation.gif
+.. figure:: images/camera_animation.webp
   :alt: Tools - Navigation controls
   :align: center

@ -315,7 +315,7 @@ Each element under these groups can be selected to get further information or to

 For instance, point clouds properties can be modified to show elevation and also the color ramp cam be customized.

-.. figure:: images/pointcloud_elevation.png
+.. figure:: images/pointcloud_elevation.webp
   :alt: Tools - Navigation controls
   :align: center

@ -339,7 +339,7 @@ Most stockpile measurement jobs does not require a crosshatch pattern or angled

 In most of the cases a lawn mower flight pattern is capable of producing highly accurate stockpile models.

-.. figure:: images/lawnmower_pattern.png
+.. figure:: images/lawnmower_pattern.webp
   :alt: a simple lawnmower flight pattern can produce accurate results
   :align: center

@ -382,7 +382,7 @@ Measuring

 As almost 50% of the material will be found in the first 20% of the stockpile height, special care should be taken in adequately defining the base plane.

-.. figure:: images/stockpile.png
+.. figure:: images/stockpile.webp
   :alt: almost 50% of the material will be found in the first 20% of the stockpile height
   :align: center

@ -390,31 +390,31 @@ In WebODM Dashboard, clic on "view map" to start a 2D view of your project.

 Once in the 2D map view, clic on the "Measure volume, area and length" button.

-.. figure:: images/measurement1.png
+.. figure:: images/measurement1.webp
   :alt: clic on the "Measure volume, area and length" button
   :align: center

 then clic on "Create a new measurement"

-.. figure:: images/measurement2.png
+.. figure:: images/measurement2.webp
   :alt: clic on "Create a new measurement"
   :align: center

 Start placing the points to define the stockpile base plane

-.. figure:: images/measurement3.png
+.. figure:: images/measurement3.webp
   :alt: Define the stockpile base plane
   :align: center

 Clic on "Finish measurement" to finish the process.

-.. figure:: images/measurement4.png
+.. figure:: images/measurement4.webp
   :alt: Clic on "Finish measurement" to finish the process
   :align: center

 Dialog box will show the  message "Computing ..." for a few seconds, and after the computing is finished the volume measurement value will be displayed.

-.. figure:: images/measurement7.png
+.. figure:: images/measurement7.webp
   :alt: Clic on "Finish measurement" to finish the process
   :align: center

@ -790,7 +790,7 @@ Calibrating the Camera

 Camera calibration is a special challenge with commodity cameras. Temperature changes, vibrations, focus, and other factors can affect the derived parameters with substantial effects on resulting data. Automatic or self calibration is possible and desirable with drone flights, but depending on the flight pattern, automatic calibration may not remove all distortion from the resulting products. James and Robson (2014) in their paper `Mitigating systematic error in topographic models derived from UAV and ground‐based image networks <https://onlinelibrary.wiley.com/doi/full/10.1002/esp.3609>`_ address how to minimize the distortion from self-calibration.

-.. figure:: images/msimbasi_bowling.png
+.. figure:: images/msimbasi_bowling.webp
   :alt: image of lens distortion effect on bowling of data
   :align: center

@ -798,7 +798,7 @@ Camera calibration is a special challenge with commodity cameras. Temperature ch

 To mitigate this effect, there are a few options but the simplest are as follows: fly two patterns separated by 20°, and rather than having a nadir (straight down pointing) camera, use one that tilts forward by 5°.

-.. figure:: images/flightplanning.gif
+.. figure:: images/flightplanning.webp
  :alt: animation showing optimum
  :align: center
  :height: 480
@ -811,13 +811,13 @@ Alternatively, the following experimental method can be applied: fly with much l
 * Crossgrid overlap percentages can be lower than parallel flights. To get good 3D results, you will require 68% overlap and sidelap for an equivalent 83% overlap and sidelap.
 * To get good 2D and 2.5D (digital elevation model) results, you will require 42% overlap and sidelap for an equivalent 70% overlap and sidelap.

-.. figure:: images/rotation.gif
+.. figure:: images/rotation.webp
  :alt: animation showing experimental optimum
  :align: center

 Vertically separated flight lines also improve accuracy, but less so than a camera that is forward facing by 5°.

-.. figure:: images/forward_facing.png
+.. figure:: images/forward_facing.webp
   :alt: figure showing effect of vertically separated flight lines and forward facing cameras on improving self calibration
   :align: center

@ -831,16 +831,16 @@ Starting from ODM ``2.0`` people can supply image masks to inform the software t

 To add a mask, simply create a new black and white image of the same dimension as the target image you want to mask (you can use a program such as GIMP to do this). Color in black the areas to exclude from the reconstruction. 

-.. figure:: https://user-images.githubusercontent.com/1951843/93247037-ade87a00-f75b-11ea-8b42-25bc1d89279d.png
+.. figure:: https://user-images.githubusercontent.com/1951843/93247037-ade87a00-f75b-11ea-8b42-25bc1d89279d.webp
   :alt: Target image
   :align: center

-.. figure:: https://user-images.githubusercontent.com/1951843/93247007-a2954e80-f75b-11ea-87b3-4f04bd1737b9.png
+.. figure:: https://user-images.githubusercontent.com/1951843/93247007-a2954e80-f75b-11ea-87b3-4f04bd1737b9.webp
   :alt: Image mask
   :align: center


-.. figure:: https://user-images.githubusercontent.com/1951843/93246970-8f827e80-f75b-11ea-8179-5a8fdd9f5193.png
+.. figure:: https://user-images.githubusercontent.com/1951843/93246970-8f827e80-f75b-11ea-8179-5a8fdd9f5193.webp
   :alt: 3D result (building is masked)
   :align: center

@ -986,7 +986,7 @@ After finish hosting ClusterODM on the head node and finish wiring it to the Nod

 Replace user and hostname with your appropriate username and the hpc address. Basically, this command will tunnel the port of the hpc to your local port. After this, open a browser in your local machine and connect to `http://localhost:10000`. Port 10000 is where ClusterODM's administrative web interface is hosted at. This is what it looks like:

-.. figure:: https://user-images.githubusercontent.com/70782465/214938402-707bee90-ea17-4573-82f8-74096d9caf03.png
+.. figure:: https://user-images.githubusercontent.com/70782465/214938402-707bee90-ea17-4573-82f8-74096d9caf03.webp
   :alt: Screenshot of ClusterODM's administrative web interface
   :align: center

@ -1001,7 +1001,7 @@ ssh -L localhost:3000:localhost:3000 user@hostname

 Port 3000 is ClusterODM's proxy. This is the place we assign tasks to ClusterODM. Once again, connect to `http://localhost:3000` with your browser after tunneling. Here, you can Assign Tasks and observe the tasks' processes.

-.. figure:: https://user-images.githubusercontent.com/70782465/214938234-113f99dc-f69e-4e78-a782-deaf94e986b0.png
+.. figure:: https://user-images.githubusercontent.com/70782465/214938234-113f99dc-f69e-4e78-a782-deaf94e986b0.webp
   :alt: Screenshot of ClusterODM's jobs interface
   :align: center

@ -1044,7 +1044,7 @@ Modify code

 For our test today, we will attempt to upgrade Ceres Solver to version 2.2.0. Most external libraries like Ceres can be found in the Superbuild directory. In this case we edit SuperBuild/cmake/External-Ceres.cmake, and set it to use version 2.2.0

-.. figure:: images/vimdiff_ceres_change.png
+.. figure:: images/vimdiff_ceres_change.webp

 Now that we've made that small, but substantive change, we need to rebuild Ceres on the docker image for testing.

--- a/arguments/align/index.html
+++ b/arguments/align/index.html
@ -458,7 +458,7 @@
 <p>Path to a GeoTIFF DEM or a LAS/LAZ point cloud that the reconstruction outputs should be automatically aligned to. Experimental. Default: <code class="docutils literal notranslate"><span class="pre">None</span></code></p>
 <p>See <a class="reference external" href="../../map-accuracy/#improving-relative-accuracy">Multi-temporal datasets for further usage information.</a></p>
 <figure class="align-center">
-<img alt="Animated gif comparing two separately processed, but aligned digital surface models." src="../../_images/align_pc.gif" />
+<img alt="Animated gif comparing two separately processed, but aligned digital surface models." src="../../_images/align_pc.webp" />
 </figure>
 <p>Animated gif comparing two separately processed, but aligned digital surface models.</p>
 <p><a class="reference external" href="https://github.com/opendronemap/docs#how-to-make-your-first-contribution">Learn to edit</a> and help improve <a class="reference external" href="https://github.com/OpenDroneMap/docs/blob/publish/source/arguments_edit/align.rst">this page</a>!</p>
--- a/arguments/auto-boundary/index.html
+++ b/arguments/auto-boundary/index.html
@ -516,7 +516,7 @@
 <section id="true-auto-boundary">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--auto-boundary</span></code><a class="headerlink" href="#true-auto-boundary" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id2">
-<img alt="WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree." src="https://user-images.githubusercontent.com/19295950/140864618-2a0c95f2-669e-45dc-b5c5-df82a555e4e5.png" />
+<img alt="WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree." src="https://user-images.githubusercontent.com/19295950/140864618-2a0c95f2-669e-45dc-b5c5-df82a555e4e5.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the full extent of the reconstruction, bounded by the <code class="docutils literal notranslate"><span class="pre">--auto-boundary</span></code> option.</span><a class="headerlink" href="#id2" title="Link to this image"></a></p>
 </figcaption>
@ -525,7 +525,7 @@
 <section id="false-null">
 <h3>False: <code class="docutils literal notranslate"><span class="pre">null</span></code><a class="headerlink" href="#false-null" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id3">
-<img alt="WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree." src="https://user-images.githubusercontent.com/19295950/140864753-db3695c5-3ba2-48fb-a644-3e591913de72.png" />
+<img alt="WebODM displaying the reconstruction extent of a terrestrial orbit survey of a Northern Catalpa tree." src="https://user-images.githubusercontent.com/19295950/140864753-db3695c5-3ba2-48fb-a644-3e591913de72.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the full extent of the recosntruction. Compared to the <code class="docutils literal notranslate"><span class="pre">--auto-boundary</span></code> reconstruction above, one can see that the full reconstruction area is much larger (and therefore more visually sparse).</span><a class="headerlink" href="#id3" title="Link to this image"></a></p>
 </figcaption>
--- a/arguments/boundary/index.html
+++ b/arguments/boundary/index.html
@ -523,7 +523,7 @@
 <section id="new-geojson">
 <h4>New GeoJSON<a class="headerlink" href="#new-geojson" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id2">
-<img alt="GeoJSON.io interface with empty GeoJSON map and text." src="https://user-images.githubusercontent.com/19295950/145102197-b44fea3b-01df-4f2f-9cde-f1c94ba2e8d3.png" />
+<img alt="GeoJSON.io interface with empty GeoJSON map and text." src="https://user-images.githubusercontent.com/19295950/145102197-b44fea3b-01df-4f2f-9cde-f1c94ba2e8d3.webp" />
 <figcaption>
 <p><span class="caption-text">After opening the above link to GeoJSON.io, one should pan and zoom the map preview to find their area of interest.</span><a class="headerlink" href="#id2" title="Link to this image"></a></p>
 </figcaption>
@ -532,7 +532,7 @@
 <section id="creating-a-polygon">
 <h4>Creating A Polygon<a class="headerlink" href="#creating-a-polygon" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id3">
-<img alt="Choosing the &quot;Draw Polygon&quot; menu option in the Map View." src="https://user-images.githubusercontent.com/19295950/145102194-7992ddf8-81ce-4ee9-bb81-b5d93cb05e25.png" />
+<img alt="Choosing the &quot;Draw Polygon&quot; menu option in the Map View." src="https://user-images.githubusercontent.com/19295950/145102194-7992ddf8-81ce-4ee9-bb81-b5d93cb05e25.webp" />
 <figcaption>
 <p><span class="caption-text">Selecting the “Draw Polygon” menu option will allow you to place vertices for your polygon by left-clicking on the map.</span><a class="headerlink" href="#id3" title="Link to this image"></a></p>
 </figcaption>
@ -541,7 +541,7 @@
 <section id="placing-vertices">
 <h4>Placing Vertices<a class="headerlink" href="#placing-vertices" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id4">
-<img alt="Placing vertices in the Map View to create the boundary GeoJSON." src="https://user-images.githubusercontent.com/19295950/145102186-38a4107f-4c93-46f9-b423-3ce40fddff4b.png" />
+<img alt="Placing vertices in the Map View to create the boundary GeoJSON." src="https://user-images.githubusercontent.com/19295950/145102186-38a4107f-4c93-46f9-b423-3ce40fddff4b.webp" />
 <figcaption>
 <p><span class="caption-text">Choose the appropriate locations of the boundary of your polygon by left-clicking on the map to place a vertex. You can place as many vertices as you require.</span><a class="headerlink" href="#id4" title="Link to this image"></a></p>
 </figcaption>
@ -550,7 +550,7 @@
 <section id="completing-a-polygon">
 <h4>Completing A Polygon<a class="headerlink" href="#completing-a-polygon" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id5">
-<img alt="Completed polygon in the Map View and GeoJSON text view." src="https://user-images.githubusercontent.com/19295950/145102193-4e619f4e-e95d-4c3d-8f89-29a38015bce0.png" />
+<img alt="Completed polygon in the Map View and GeoJSON text view." src="https://user-images.githubusercontent.com/19295950/145102193-4e619f4e-e95d-4c3d-8f89-29a38015bce0.webp" />
 <figcaption>
 <p><span class="caption-text">To close the polygon, you left-click on your first vertex. You will be able to close your polygon once you have placed at least three vertices on the map.
 A completed polygon will have a different representation than one that is in-progress. It will have a darker border and a fill, implying that it is now a “solid” polygon. If your polygon looks like this, you are ready to save it.</span><a class="headerlink" href="#id5" title="Link to this image"></a></p>
@ -560,7 +560,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="saving-a-polygon">
 <h4>Saving A Polygon<a class="headerlink" href="#saving-a-polygon" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id6">
-<img alt="Saving the polygon using the Save menu and choosing GeoJSON." src="https://user-images.githubusercontent.com/19295950/145102199-a5d37bbf-d057-46d8-8baf-91817c7e2f30.png" />
+<img alt="Saving the polygon using the Save menu and choosing GeoJSON." src="https://user-images.githubusercontent.com/19295950/145102199-a5d37bbf-d057-46d8-8baf-91817c7e2f30.webp" />
 <figcaption>
 <p><span class="caption-text">Select “Save” and then “GeoJSON” to save the completed GeoJSON boundary to disk. Your browser will prompt or otherwise alert you that the file is ready to download. Alternatively, you can copy and paste the text-only representation of the GeoJSON boundary from the right panel with the “JSON” header.</span><a class="headerlink" href="#id6" title="Link to this image"></a></p>
 <div class="legend">
@ -610,7 +610,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="downloading-a-polygon">
 <h4>Downloading A Polygon<a class="headerlink" href="#downloading-a-polygon" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id7">
-<img alt="Browser Download/Save file prompt for the generated GeoJSON file." src="https://user-images.githubusercontent.com/19295950/145103954-17ba7c31-fda6-4883-b7a6-3f0bacc266dd.png" />
+<img alt="Browser Download/Save file prompt for the generated GeoJSON file." src="https://user-images.githubusercontent.com/19295950/145103954-17ba7c31-fda6-4883-b7a6-3f0bacc266dd.webp" />
 <figcaption>
 <p><span class="caption-text">Once the GeoJSON file has been chosen for saving, the browser will prompt you to save it to disk. Choose an appropriate location where you can access it at a later time to load into WebODM.</span><a class="headerlink" href="#id7" title="Link to this image"></a></p>
 </figcaption>
@ -619,7 +619,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="setting-boundary-geojson-in-task-options">
 <h4>Setting Boundary [GeoJSON] In Task Options<a class="headerlink" href="#setting-boundary-geojson-in-task-options" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id8">
-<img alt="Task Options preview showing Boundary field and &quot;Load&quot; icon." src="https://user-images.githubusercontent.com/19295950/145102200-02bd1c97-e0e8-4932-a77d-91562823b46e.png" />
+<img alt="Task Options preview showing Boundary field and &quot;Load&quot; icon." src="https://user-images.githubusercontent.com/19295950/145102200-02bd1c97-e0e8-4932-a77d-91562823b46e.webp" />
 <figcaption>
 <p><span class="caption-text">When you are editing the Task Options for your Task, you can choose to load the Boundary [GeoJSON] created above by clicking the “Load” icon. Alternatively, you can paste the textual representation of the boundary into the Boundary [GeoJSON] text box.</span><a class="headerlink" href="#id8" title="Link to this image"></a></p>
 </figcaption>
@ -628,7 +628,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="boundary-geojson-loaded-in-task-options">
 <h4>Boundary [GeoJSON] Loaded In Task Options<a class="headerlink" href="#boundary-geojson-loaded-in-task-options" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id9">
-<img alt="Task Options preview showing loaded Boundary with GeoJSON text." src="https://user-images.githubusercontent.com/19295950/145102196-8f87e4ac-197f-4ce0-ac6f-082772921ea0.png" />
+<img alt="Task Options preview showing loaded Boundary with GeoJSON text." src="https://user-images.githubusercontent.com/19295950/145102196-8f87e4ac-197f-4ce0-ac6f-082772921ea0.webp" />
 <figcaption>
 <p><span class="caption-text">Once the Boundary [GeoJSON] has been loaded from disk or pasted from the system clipboard, you can confirm its presence by seeing the text in the text box. You can now save the Task Options to enable the Boundary [GeoJSON] for the processing Task.</span><a class="headerlink" href="#id9" title="Link to this image"></a></p>
 </figcaption>
@ -644,7 +644,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="creating-a-new-temporary-scratch-layer">
 <h4>Creating A New Temporary Scratch Layer<a class="headerlink" href="#creating-a-new-temporary-scratch-layer" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id10">
-<img alt="Choosing the &quot;Create A Temporary Scratch Layer&quot; tool to make an empty layer to create our Boundary [GeoJSON] within." src="https://user-images.githubusercontent.com/19295950/145109912-9176cd94-1140-43ac-a371-96de2b874ec3.png" />
+<img alt="Choosing the &quot;Create A Temporary Scratch Layer&quot; tool to make an empty layer to create our Boundary [GeoJSON] within." src="https://user-images.githubusercontent.com/19295950/145109912-9176cd94-1140-43ac-a371-96de2b874ec3.webp" />
 <figcaption>
 <p><span class="caption-text">You will first need a layer to create your Boundary [GeoJSON] within, so creating a New Temporary Scratch layer is a way to do this without needing to setup a file on disk first.</span><a class="headerlink" href="#id10" title="Link to this image"></a></p>
 </figcaption>
@ -653,7 +653,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="new-temporary-scratch-layer-geometry-type">
 <h4>New Temporary Scratch Layer Geometry Type<a class="headerlink" href="#new-temporary-scratch-layer-geometry-type" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id11">
-<img alt="Setting &quot;Polygon&quot; as the Geometry Type for the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109915-ddbfed43-da5e-466b-a4b6-d6ff3b96a555.png" />
+<img alt="Setting &quot;Polygon&quot; as the Geometry Type for the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109915-ddbfed43-da5e-466b-a4b6-d6ff3b96a555.webp" />
 <figcaption>
 <p><span class="caption-text">There are numerous choices of geometry types that can be represented by a given layer. OpenDroneMap is designed to work with Single Polygon, so you will choose Polygon from the Geometry Type menu.</span><a class="headerlink" href="#id11" title="Link to this image"></a></p>
 </figcaption>
@ -662,7 +662,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="new-temporary-scratch-layer-settings">
 <h4>New Temporary Scratch Layer Settings<a class="headerlink" href="#new-temporary-scratch-layer-settings" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id12">
-<img alt="Leaving the remaining settings in their Default state." src="https://user-images.githubusercontent.com/19295950/145109917-58b6c147-bdae-45be-839d-5d56b1a22fe8.png" />
+<img alt="Leaving the remaining settings in their Default state." src="https://user-images.githubusercontent.com/19295950/145109917-58b6c147-bdae-45be-839d-5d56b1a22fe8.webp" />
 <figcaption>
 <p><span class="caption-text">Similar to Geometry Types, there are a large number of settings and options you can adjust for a Temporary Scratch Layer. You should leave these at their pictured defaults for usage with OpenDroneMap.</span><a class="headerlink" href="#id12" title="Link to this image"></a></p>
 </figcaption>
@ -671,7 +671,7 @@ A completed polygon will have a different representation than one that is in-pro
 <section id="adding-an-orthophoto-background">
 <h4>Adding an Orthophoto Background<a class="headerlink" href="#adding-an-orthophoto-background" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id13">
-<img alt="Browsing to a generated Orthophoto from WebODM that covers the Area Of Interest (AOI)." src="https://user-images.githubusercontent.com/19295950/145109918-df591ce8-3df4-485d-a775-81813b7e61ef.png" />
+<img alt="Browsing to a generated Orthophoto from WebODM that covers the Area Of Interest (AOI)." src="https://user-images.githubusercontent.com/19295950/145109918-df591ce8-3df4-485d-a775-81813b7e61ef.webp" />
 <figcaption>
 <p><span class="caption-text">If you have run the task already without a Boundary [GeoJSON], you can load the generated Orthophoto from OpenDroneMap into QGIS to use as your basemap for creating your Boundary [GeoJSON]. This should ensure that your boundary polygon exactly matches the data in your Task, as different basemaps can have errors of 1-10m or more.
 If have not generated an Orthophoto for your Area Of Interest (AOI), you can use one of the various methods within QGIS to add a basemap. Just be mindful of possible differences in location, angle, skew, scale, and other registration changes that can occur between your data and a basemap provider’s data.</span><a class="headerlink" href="#id13" title="Link to this image"></a></p>
@ -681,7 +681,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="adding-a-polyon-feature">
 <h4>Adding A Polyon Feature<a class="headerlink" href="#adding-a-polyon-feature" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id14">
-<img alt="Selecting the &quot;Add A Polygon Feature&quot; tool to begin creating a boundary polygon." src="https://user-images.githubusercontent.com/19295950/145109907-b61afb3c-fdd2-4eef-872a-91f2ea97d887.png" />
+<img alt="Selecting the &quot;Add A Polygon Feature&quot; tool to begin creating a boundary polygon." src="https://user-images.githubusercontent.com/19295950/145109907-b61afb3c-fdd2-4eef-872a-91f2ea97d887.webp" />
 <figcaption>
 <p><span class="caption-text">After selecting the “Add A Polygon Feature” tool, you can begin placing vertices on the map to create your boundary. To finish your polygon, you will right-click on the canvas. Similar to GeoJSON.io, a finished polygon will have a darker outline and a darker fill to indicate that it is “solid”.</span><a class="headerlink" href="#id14" title="Link to this image"></a></p>
 </figcaption>
@ -690,7 +690,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="toggle-editing-off">
 <h4>Toggle Editing Off<a class="headerlink" href="#toggle-editing-off" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id15">
-<img alt="Clicking the &quot;Toggle Editing&quot; tool will prompt you to save your changes to the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109924-42480f63-2cfa-427c-8414-f45d39f796f7.png" />
+<img alt="Clicking the &quot;Toggle Editing&quot; tool will prompt you to save your changes to the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109924-42480f63-2cfa-427c-8414-f45d39f796f7.webp" />
 <figcaption>
 <p><span class="caption-text">Once you are finished with your boundary polygon, you can click the “Toggle Editing” tool to accept your changes and write them out to the Temporary Scratch Layer and make the layer valid for saving/exporting to disk.</span><a class="headerlink" href="#id15" title="Link to this image"></a></p>
 </figcaption>
@ -699,7 +699,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="save-changes-to-temporary-scratch-layer">
 <h4>Save Changes To Temporary Scratch Layer<a class="headerlink" href="#save-changes-to-temporary-scratch-layer" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id16">
-<img alt="QGIS Dialog asking you to Save your changes to the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109921-73ab273a-7180-40ea-ba3d-75ecb65c97f5.png" />
+<img alt="QGIS Dialog asking you to Save your changes to the Temporary Scratch Layer." src="https://user-images.githubusercontent.com/19295950/145109921-73ab273a-7180-40ea-ba3d-75ecb65c97f5.webp" />
 <figcaption>
 <p><span class="caption-text">Clicking Save on this dialog will write the changes to the Temporary Scratch Layer and enable export/save functionality.</span><a class="headerlink" href="#id16" title="Link to this image"></a></p>
 </figcaption>
@ -708,7 +708,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="export-temporary-scratch-layer-features">
 <h4>Export Temporary Scratch Layer Features<a class="headerlink" href="#export-temporary-scratch-layer-features" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id17">
-<img alt="A right-click on the Temporary Scratch Layer in the Layers panel will expose the Export menu item, with the Save Features As sub-menu item." src="https://user-images.githubusercontent.com/19295950/145109911-45d7dae3-49ce-40fb-8df0-85a164763810.png" />
+<img alt="A right-click on the Temporary Scratch Layer in the Layers panel will expose the Export menu item, with the Save Features As sub-menu item." src="https://user-images.githubusercontent.com/19295950/145109911-45d7dae3-49ce-40fb-8df0-85a164763810.webp" />
 <figcaption>
 <p><span class="caption-text">Right-click on the Temporary Scratch Layer in the Layers panel to bring up the Export menu and the Save Features As sub-menu item, selecting Save Features As. This will prompt you to choose the export format, location and file name, and settings for your layer.</span><a class="headerlink" href="#id17" title="Link to this image"></a></p>
 </figcaption>
@ -717,7 +717,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="save-vector-layer-as">
 <h4>Save Vector Layer As<a class="headerlink" href="#save-vector-layer-as" title="Link to this heading"></a></h4>
 <figure class="align-default" id="id18">
-<img alt="The &quot;Save Vector Layer As&quot; dialog showing Format as GeoJSON, an example of a valid File Name and path, CRS of EPSG:4326 and other default options." src="https://user-images.githubusercontent.com/19295950/145109923-b55dfc1a-5c31-4382-8b1f-3bc6322b0f33.png" />
+<img alt="The &quot;Save Vector Layer As&quot; dialog showing Format as GeoJSON, an example of a valid File Name and path, CRS of EPSG:4326 and other default options." src="https://user-images.githubusercontent.com/19295950/145109923-b55dfc1a-5c31-4382-8b1f-3bc6322b0f33.webp" />
 <figcaption>
 <p><span class="caption-text">This dialog will require you to choose GeoJSON as the format, a valid filename and path for the GeoJSON to be written out to disk with, and a valid CRS. The safest CRS choice with GeoJSON is EPSG:4326, so choose that if it is not chosen by default. All other options should be left as default and do not apply for OpenDroneMap usage.</span><a class="headerlink" href="#id18" title="Link to this image"></a></p>
 </figcaption>
@ -730,7 +730,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="true-boundary-geojson-point-cloud">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--boundary</span> <span class="pre">[GeoJSON]</span></code> - Point Cloud<a class="headerlink" href="#true-boundary-geojson-point-cloud" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id19">
-<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Point Cloud." src="https://user-images.githubusercontent.com/19295950/140858936-10fda65f-c278-46ae-95bd-7af8f8369554.png" />
+<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Point Cloud." src="https://user-images.githubusercontent.com/19295950/140858936-10fda65f-c278-46ae-95bd-7af8f8369554.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the modified extent of the reconstruction Point Cloud, bounded by the GeoJSON proivded to the <code class="docutils literal notranslate"><span class="pre">--boundary</span></code> option.</span><a class="headerlink" href="#id19" title="Link to this image"></a></p>
 </figcaption>
@ -739,7 +739,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="true-boundary-geojson-orthophoto">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--boundary</span> <span class="pre">[GeoJSON]</span></code> - Orthophoto<a class="headerlink" href="#true-boundary-geojson-orthophoto" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id20">
-<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Orthophoto." src="https://user-images.githubusercontent.com/19295950/140859033-c6cab4f0-74b3-4266-b5ec-4a90da931340.png" />
+<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Orthophoto." src="https://user-images.githubusercontent.com/19295950/140859033-c6cab4f0-74b3-4266-b5ec-4a90da931340.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the modified extent of the reconstruction Orthophoto, bounded by the GeoJSON proivded to the <code class="docutils literal notranslate"><span class="pre">--boundary</span></code> option.</span><a class="headerlink" href="#id20" title="Link to this image"></a></p>
 </figcaption>
@ -748,7 +748,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="true-boundary-geojson-digital-elevation-model">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--boundary</span> <span class="pre">[GeoJSON]</span></code> - Digital Elevation Model<a class="headerlink" href="#true-boundary-geojson-digital-elevation-model" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id21">
-<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Digital Elevation Model." src="https://user-images.githubusercontent.com/19295950/140859073-28db5174-9a40-42d8-86d6-f345d9dad5a8.png" />
+<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset Digital Elevation Model." src="https://user-images.githubusercontent.com/19295950/140859073-28db5174-9a40-42d8-86d6-f345d9dad5a8.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the modified extent of the reconstruction Digital Elevation Model, bounded by the GeoJSON proivded to the <code class="docutils literal notranslate"><span class="pre">--boundary</span></code> option.</span><a class="headerlink" href="#id21" title="Link to this image"></a></p>
 </figcaption>
@ -757,7 +757,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="true-boundary-geojson-3d-model-textured-mesh">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--boundary</span> <span class="pre">[GeoJSON]</span></code> - 3D Model/Textured Mesh<a class="headerlink" href="#true-boundary-geojson-3d-model-textured-mesh" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id22">
-<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset 3D Model/Textured Mesh." src="https://user-images.githubusercontent.com/19295950/140859125-4854e651-9eff-430d-956c-16f4d9a52dfd.png" />
+<img alt="WebODM displaying the &quot;clipped&quot; reconstruction of the Brighton Beach dataset 3D Model/Textured Mesh." src="https://user-images.githubusercontent.com/19295950/140859125-4854e651-9eff-430d-956c-16f4d9a52dfd.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the modified extent of the reconstruction 3D Model/Textured Mesh, bounded by the GeoJSON proivded to the <code class="docutils literal notranslate"><span class="pre">--boundary</span></code> option.</span><a class="headerlink" href="#id22" title="Link to this image"></a></p>
 </figcaption>
@ -766,7 +766,7 @@ If have not generated an Orthophoto for your Area Of Interest (AOI), you can use
 <section id="false-null">
 <h3>False: <code class="docutils literal notranslate"><span class="pre">null</span></code><a class="headerlink" href="#false-null" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id23">
-<img alt="WebODM displaying the full reconstruction of the Brighton Beach dataset Point Cloud." src="https://user-images.githubusercontent.com/19295950/140858712-9bfd8c56-a52a-480e-b68d-d5a97bc516fd.png" />
+<img alt="WebODM displaying the full reconstruction of the Brighton Beach dataset Point Cloud." src="https://user-images.githubusercontent.com/19295950/140858712-9bfd8c56-a52a-480e-b68d-d5a97bc516fd.webp" />
 <figcaption>
 <p><span class="caption-text">The WebODM 3D View shows the full extent of the recosntruction. Compared to the <code class="docutils literal notranslate"><span class="pre">--boundary</span></code> reconstruction above, one can see that the full reconstruction area is much larger and includes many features outside of the Area Of Interest used to generate the GeoJSON.</span><a class="headerlink" href="#id23" title="Link to this image"></a></p>
 </figcaption>
--- a/arguments/build-overviews/index.html
+++ b/arguments/build-overviews/index.html
@ -522,7 +522,7 @@
 <section id="true-build-overviews">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--build-overviews</span></code><a class="headerlink" href="#true-build-overviews" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id2">
-<img alt="QGIS displaying the generated Overviews" src="https://user-images.githubusercontent.com/19295950/127073339-6b2a0a4f-6ede-4dc1-8da4-5bc9646de304.png" />
+<img alt="QGIS displaying the generated Overviews" src="https://user-images.githubusercontent.com/19295950/127073339-6b2a0a4f-6ede-4dc1-8da4-5bc9646de304.webp" />
 <figcaption>
 <p><span class="caption-text">The Layer Properties panel demonstrates that this OpenDroneMap-generated GeoTIFF has internal Overviews.</span><a class="headerlink" href="#id2" title="Link to this image"></a></p>
 </figcaption>
@ -531,7 +531,7 @@
 <section id="false-null">
 <h3>False: <code class="docutils literal notranslate"><span class="pre">null</span></code><a class="headerlink" href="#false-null" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id3">
-<img alt="QGIS displaying the file is lacking Overviews" src="https://user-images.githubusercontent.com/19295950/127074349-a3f84c4c-d05c-4bf1-bd7c-790781ad0fe3.png" />
+<img alt="QGIS displaying the file is lacking Overviews" src="https://user-images.githubusercontent.com/19295950/127074349-a3f84c4c-d05c-4bf1-bd7c-790781ad0fe3.webp" />
 <figcaption>
 <p><span class="caption-text">The Layer Properties panel demonstrates that this OpenDroneMap-generated GeoTIFF lacks internal Overviews.</span><a class="headerlink" href="#id3" title="Link to this image"></a></p>
 </figcaption>
--- a/arguments/camera-lens/index.html
+++ b/arguments/camera-lens/index.html
@ -518,7 +518,7 @@
 <section id="auto-rectilinear-data">
 <h3><code class="docutils literal notranslate"><span class="pre">auto</span></code> : Rectilinear Data<a class="headerlink" href="#auto-rectilinear-data" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id2">
-<img alt="Rectilinear data rendered by ``auto`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077336-ae79a958-a953-4376-86fd-430d0e5457f2.png" />
+<img alt="Rectilinear data rendered by ``auto`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077336-ae79a958-a953-4376-86fd-430d0e5457f2.webp" />
 <figcaption>
 <p><span class="caption-text">This Point Cloud shows a proper reconstruction via the <code class="docutils literal notranslate"><span class="pre">auto</span></code> (<code class="docutils literal notranslate"><span class="pre">brown</span></code>) Camera Lens Model, which is appropriate for this sensor.</span><a class="headerlink" href="#id2" title="Link to this image"></a></p>
 </figcaption>
@ -527,7 +527,7 @@
 <section id="brown-rectilinear-data">
 <h3><code class="docutils literal notranslate"><span class="pre">brown</span></code> : Rectilinear Data<a class="headerlink" href="#brown-rectilinear-data" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id3">
-<img alt="Rectilinear data rendered by ``brown`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077753-580a174e-7572-4315-8801-224ce097d9fc.png" />
+<img alt="Rectilinear data rendered by ``brown`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077753-580a174e-7572-4315-8801-224ce097d9fc.webp" />
 <figcaption>
 <p><span class="caption-text">As in the prior example, this Point Cloud is reconstructed via the <code class="docutils literal notranslate"><span class="pre">brown</span></code> Camera Lens Model.</span><a class="headerlink" href="#id3" title="Link to this image"></a></p>
 </figcaption>
@ -536,7 +536,7 @@
 <section id="fisheye-rectilinear-data">
 <h3><code class="docutils literal notranslate"><span class="pre">fisheye</span></code> : Rectilinear Data<a class="headerlink" href="#fisheye-rectilinear-data" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id4">
-<img alt="Rectilinear data rendered by ``fisheye`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077826-53d459fe-5e4e-4b10-8e70-fbddf775c4f7.png" />
+<img alt="Rectilinear data rendered by ``fisheye`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077826-53d459fe-5e4e-4b10-8e70-fbddf775c4f7.webp" />
 <figcaption>
 <p><span class="caption-text">In this Point Cloud reconstruction, severe bowling and other artifacts have been introduced via the use of the wrong Camera Lens Model.</span><a class="headerlink" href="#id4" title="Link to this image"></a></p>
 </figcaption>
@ -545,7 +545,7 @@
 <section id="perspective-rectilinear-data">
 <h3><code class="docutils literal notranslate"><span class="pre">perspective</span></code> : Rectilinear Data<a class="headerlink" href="#perspective-rectilinear-data" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id5">
-<img alt="Rectilinear data rendered by ``perspective`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077485-699f9e61-72a6-45f2-990f-f5748b6ee99f.png" />
+<img alt="Rectilinear data rendered by ``perspective`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127077485-699f9e61-72a6-45f2-990f-f5748b6ee99f.webp" />
 <figcaption>
 <p><span class="caption-text">This Point Cloud rendered well, very similar to the <code class="docutils literal notranslate"><span class="pre">auto</span></code> and <code class="docutils literal notranslate"><span class="pre">brown</span></code> examples. One may see artifacts in the <code class="docutils literal notranslate"><span class="pre">perspective</span></code> Camera Lens Model in very large collections, or over very flat/homogenus terrain (agricultural fields). In such cases, forcing <code class="docutils literal notranslate"><span class="pre">brown</span></code> may help.</span><a class="headerlink" href="#id5" title="Link to this image"></a></p>
 </figcaption>
@ -554,7 +554,7 @@
 <section id="spherical-rectilinear-data">
 <h3><code class="docutils literal notranslate"><span class="pre">spherical</span></code> : Rectilinear Data<a class="headerlink" href="#spherical-rectilinear-data" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id6">
-<img alt="Rectilinear data rendered by ``spherical`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127078960-27e35cbb-a378-4d0d-92e2-42dbfd1edd7c.png" />
+<img alt="Rectilinear data rendered by ``spherical`` Camera Lens Model" src="https://user-images.githubusercontent.com/19295950/127078960-27e35cbb-a378-4d0d-92e2-42dbfd1edd7c.webp" />
 <figcaption>
 <p><span class="caption-text">This Point Cloud failed to reconstruct properly due to the manual selection of the <code class="docutils literal notranslate"><span class="pre">fisheye</span></code> Camera Lens Model. Similar failures to reconstruct can often indicate the wrong manual selection, or in edge cases, wrong <code class="docutils literal notranslate"><span class="pre">auto</span></code> selection of the Camera Lens Model, and you are advised to try another Model that is more appropriate.</span><a class="headerlink" href="#id6" title="Link to this image"></a></p>
 </figcaption>
--- a/arguments/cog/index.html
+++ b/arguments/cog/index.html
@ -515,19 +515,19 @@
 <section id="true-cog">
 <h3>True: <code class="docutils literal notranslate"><span class="pre">--cog</span></code><a class="headerlink" href="#true-cog" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id2">
-<img alt="GDAL Info showing LAYOUT=COG" src="https://user-images.githubusercontent.com/19295950/127079824-c85fa5a9-842a-4f28-a380-b6404aac7ef2.png" />
+<img alt="GDAL Info showing LAYOUT=COG" src="https://user-images.githubusercontent.com/19295950/127079824-c85fa5a9-842a-4f28-a380-b6404aac7ef2.webp" />
 <figcaption>
 <p><span class="caption-text">The Raster Information tool in QGIS can print information from gdalinfo which can be used to confirm the conformance of a GeoTIFF to the COG spec.</span><a class="headerlink" href="#id2" title="Link to this image"></a></p>
 </figcaption>
 </figure>
 <figure class="align-default" id="id3">
-<img alt="QGIS Layer Properties showing Internal Overviews" src="https://user-images.githubusercontent.com/19295950/138731905-d10483bd-b91b-4f63-bfb4-89c0f50bf74b.png" />
+<img alt="QGIS Layer Properties showing Internal Overviews" src="https://user-images.githubusercontent.com/19295950/138731905-d10483bd-b91b-4f63-bfb4-89c0f50bf74b.webp" />
 <figcaption>
 <p><span class="caption-text">The Layer Properties panel can show that there are in fact internal overviews. Keep in mind that not every GeoTIFF has internal overviews, but every COG must.</span><a class="headerlink" href="#id3" title="Link to this image"></a></p>
 </figcaption>
 </figure>
 <figure class="align-default" id="id4">
-<img alt="QGIS Layer Properties showing an on-disk file size of 8.78 MB" src="https://user-images.githubusercontent.com/19295950/138733095-fb5f07ef-fbb0-48f4-8401-25cbf5294b9d.png" />
+<img alt="QGIS Layer Properties showing an on-disk file size of 8.78 MB" src="https://user-images.githubusercontent.com/19295950/138733095-fb5f07ef-fbb0-48f4-8401-25cbf5294b9d.webp" />
 <figcaption>
 <p><span class="caption-text">Note that the on-disk file size is 8.78 MB for the COG due to the presence of internal overviews when compared to the 6.30 MB of the non-COG GeoTIFF below.</span><a class="headerlink" href="#id4" title="Link to this image"></a></p>
 </figcaption>
@ -536,19 +536,19 @@
 <section id="false-null">
 <h3>False: <code class="docutils literal notranslate"><span class="pre">null</span></code><a class="headerlink" href="#false-null" title="Link to this heading"></a></h3>
 <figure class="align-default" id="id5">
-<img alt="GDAL Info not showing LAYOUT=COG" src="https://user-images.githubusercontent.com/19295950/127080115-7e09ba30-140f-402d-b00a-8bb0c7bc72ff.png" />
+<img alt="GDAL Info not showing LAYOUT=COG" src="https://user-images.githubusercontent.com/19295950/127080115-7e09ba30-140f-402d-b00a-8bb0c7bc72ff.webp" />
 <figcaption>
 <p><span class="caption-text">The Raster Information tool in QGIS does not show LAYOUT=COG, which indicates that this GeoTIFF does not meet the COG spec.</span><a class="headerlink" href="#id5" title="Link to this image"></a></p>
 </figcaption>
 </figure>
 <figure class="align-default" id="id6">
-<img alt="QGIS Layer Properties not showing Internal Overviews" src="https://user-images.githubusercontent.com/19295950/138732051-d227c98d-10a5-46de-ac99-8c5ffb0a12b2.png" />
+<img alt="QGIS Layer Properties not showing Internal Overviews" src="https://user-images.githubusercontent.com/19295950/138732051-d227c98d-10a5-46de-ac99-8c5ffb0a12b2.webp" />
 <figcaption>
 <p><span class="caption-text">The Layer Properties panel shows that the GeoTIFF lacks all levels of Internal Pyramids.</span><a class="headerlink" href="#id6" title="Link to this image"></a></p>
 </figcaption>
 </figure>
 <figure class="align-default" id="id7">
-<img alt="QGIS Layer Properties showing an on-disk file size of 6.30 MB" src="https://user-images.githubusercontent.com/19295950/138733132-a9c4f8b4-673a-426b-a665-bde5e89e4de3.png" />
+<img alt="QGIS Layer Properties showing an on-disk file size of 6.30 MB" src="https://user-images.githubusercontent.com/19295950/138733132-a9c4f8b4-673a-426b-a665-bde5e89e4de3.webp" />
 <figcaption>
 <p><span class="caption-text">Note that the on-disk file size is 6.30 MB for the COG due to the lack of internal overviews when compared to the 8.78 MB of the COG GeoTIFF above.</span><a class="headerlink" href="#id7" title="Link to this image"></a></p>
 </figcaption>
--- a/cs/.doctrees/arguments/align.doctree
+++ b/cs/.doctrees/arguments/align.doctree
--- a/cs/.doctrees/arguments/auto-boundary.doctree
+++ b/cs/.doctrees/arguments/auto-boundary.doctree
--- a/cs/.doctrees/arguments/boundary.doctree
+++ b/cs/.doctrees/arguments/boundary.doctree
--- a/cs/.doctrees/arguments/build-overviews.doctree
+++ b/cs/.doctrees/arguments/build-overviews.doctree
--- a/cs/.doctrees/arguments/camera-lens.doctree
+++ b/cs/.doctrees/arguments/camera-lens.doctree
--- a/cs/.doctrees/arguments/cog.doctree
+++ b/cs/.doctrees/arguments/cog.doctree
--- a/cs/.doctrees/environment.pickle
+++ b/cs/.doctrees/environment.pickle
--- a/cs/.doctrees/flowchart.doctree
+++ b/cs/.doctrees/flowchart.doctree
--- a/cs/.doctrees/index.doctree
+++ b/cs/.doctrees/index.doctree
--- a/cs/.doctrees/installation.doctree
+++ b/cs/.doctrees/installation.doctree
--- a/cs/.doctrees/large.doctree
+++ b/cs/.doctrees/large.doctree
--- a/cs/.doctrees/map-accuracy.doctree
+++ b/cs/.doctrees/map-accuracy.doctree
--- a/cs/.doctrees/multispectral.doctree
+++ b/cs/.doctrees/multispectral.doctree
--- a/cs/.doctrees/outputs.doctree
+++ b/cs/.doctrees/outputs.doctree
--- a/cs/.doctrees/tutorials.doctree
+++ b/cs/.doctrees/tutorials.doctree
--- a/cs/_images/Background_animation.webp
+++ b/cs/_images/Background_animation.webp
--- a/cs/_images/EDL_animation.webp
+++ b/cs/_images/EDL_animation.webp
--- a/cs/_images/FOV_animation.webp
+++ b/cs/_images/FOV_animation.webp
--- a/cs/_images/UR_3D.webp
+++ b/cs/_images/UR_3D.webp
--- a/cs/_images/abs_accuracy.webp
+++ b/cs/_images/abs_accuracy.webp
--- a/cs/_images/align_pc.webp
+++ b/cs/_images/align_pc.webp
--- a/cs/_images/bioskeys.webp
+++ b/cs/_images/bioskeys.webp
--- a/cs/_images/camera_animation.webp
+++ b/cs/_images/camera_animation.webp
--- a/cs/_images/cameras.webp
+++ b/cs/_images/cameras.webp
--- a/cs/_images/clipping.webp
+++ b/cs/_images/clipping.webp
--- a/cs/_images/clipping_animation.webp
+++ b/cs/_images/clipping_animation.webp
--- a/cs/_images/clusterodm.webp
+++ b/cs/_images/clusterodm.webp
--- a/cs/_images/congratulations.webp
+++ b/cs/_images/congratulations.webp
--- a/cs/_images/digitalsurfacemodel.webp
+++ b/cs/_images/digitalsurfacemodel.webp
--- a/cs/_images/dockeradvanced.webp
+++ b/cs/_images/dockeradvanced.webp
--- a/cs/_images/dockericon.webp
+++ b/cs/_images/dockericon.webp
--- a/Show More
+++ b/Show More