|
|
|
|
@ -1,3 +1,10 @@
|
|
|
|
|
..
|
|
|
|
|
AUTO-GENERATED by extract_odm_strings.py! DO NOT EDIT!
|
|
|
|
|
This file is automatically matched to the arguments in the ODM code.
|
|
|
|
|
If you want to add more details to a command, edit a
|
|
|
|
|
.rst file in arguments_edit/<argument>.rst
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Options and Flags
|
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
|
|
@ -68,7 +75,7 @@ Options and Flags
|
|
|
|
|
Path to the file containing the ground control points used for georeferencing. The file needs to use the following format: EPSG:<code> or <+proj definition>geo_x geo_y geo_z im_x im_y image_name [gcp_name] [extra1] [extra2]Default: ``None``
|
|
|
|
|
|
|
|
|
|
:ref:`geo<geo>` <path string>
|
|
|
|
|
Path to the image geolocation file containing camera coordinates and orientation angles used for georeferencing. The file has the following format. First line: EPSG:<code> or <+proj definition> Subsequent lines: image_name geo_x geo_y geo_z [omega (degrees)] [phi (degrees)] [kappa (degrees)] [horz accuracy (meters)] [vert accuracy (meters)] By default only camera coordinates are used and orientation angles are ignored. In order to use camera orientation angles as well, set option ``sfm-algorithm`` to ``triangulation``. Default: ``None``
|
|
|
|
|
Path to the image geolocation file containing the camera center coordinates used for georeferencing. Note that omega/phi/kappa are currently not supported (you can set them to 0). The file needs to use the following format: EPSG:<code> or <+proj definition>image_name geo_x geo_y geo_z [omega (degrees)] [phi (degrees)] [kappa (degrees)] [horz accuracy (meters)] [vert accuracy (meters)]Default: ``None``
|
|
|
|
|
|
|
|
|
|
: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: ``10``
|
|
|
|
|
@ -79,11 +86,8 @@ Options and Flags
|
|
|
|
|
:ref:`ignore-gsd<ignore-gsd>`
|
|
|
|
|
Ignore Ground Sampling Distance (GSD). GSD caps the maximum resolution of image outputs and resizes images when necessary, resulting in faster processing and lower memory usage. Since GSD is an estimate, sometimes ignoring it can result in slightly better image output quality. Default: ``False``
|
|
|
|
|
|
|
|
|
|
:ref:`matcher-distance<matcher-distance>` <integer>
|
|
|
|
|
Distance threshold in meters to find pre-matching images based on GPS exif data. Set both matcher-neighbors and this to 0 to skip pre-matching. Default: ``0``
|
|
|
|
|
|
|
|
|
|
:ref:`matcher-neighbors<matcher-neighbors>` <integer>
|
|
|
|
|
Number of nearest images to pre-match based on GPS exif data. Set to 0 to skip pre-matching. Neighbors works together with Distance parameter, set both to 0 to not use pre-matching. Default: ``8``
|
|
|
|
|
Number of nearest images to pre-match based on GPS exif data. Set to 0 to skip pre-matching. Default: ``8``
|
|
|
|
|
|
|
|
|
|
:ref:`matcher-type<matcher-type>` bow | bruteforce | flann
|
|
|
|
|
Matcher algorithm, Fast Library for Approximate Nearest Neighbors or Bag of Words. FLANN is slower, but more stable. BOW is faster, but can sometimes miss valid matches. BRUTEFORCE is very slow but robust.. Default: ``flann``
|
|
|
|
|
@ -178,8 +182,8 @@ Options and Flags
|
|
|
|
|
:ref:`resize-to<resize-to>` <integer>
|
|
|
|
|
Legacy option (use --feature-quality instead). Resizes images by the largest side for feature extraction purposes only. Set to -1 to disable. This does not affect the final orthophoto resolution quality and will not resize the original images. Default: ``2048``
|
|
|
|
|
|
|
|
|
|
:ref:`sfm-algorithm <incremental | triangulation>`
|
|
|
|
|
Selects the structure from motion algorithm. If set to ``incremental`` then orientation angles in both EXIF data and geolocation files are ignored. To use these angles for georeferencing, set to ``triangulation``. Default: ``incremental``
|
|
|
|
|
:ref:`sfm-algorithm<sfm-algorithm>` incremental | triangulation
|
|
|
|
|
Choose the structure from motion algorithm. For aerial datasets, if camera GPS positions and angles are available, triangulation can generate better results. . Default: ``incremental``
|
|
|
|
|
|
|
|
|
|
:ref:`skip-3dmodel<skip-3dmodel>`
|
|
|
|
|
Skip generation of a full 3D model. This can save time if you only need 2D results such as orthophotos and DEMs. Default: ``False``
|
|
|
|
|
@ -187,6 +191,9 @@ Options and Flags
|
|
|
|
|
:ref:`skip-band-alignment<skip-band-alignment>`
|
|
|
|
|
When processing multispectral datasets, ODM will automatically align the images for each band. If the images have been postprocessed and are already aligned, use this option. Default: ``False``
|
|
|
|
|
|
|
|
|
|
:ref:`skip-orthophoto<skip-orthophoto>`
|
|
|
|
|
Skip generation of the orthophoto. This can save time if you only need 3D results or DEMs. Default: ``False``
|
|
|
|
|
|
|
|
|
|
:ref:`skip-report<skip-report>`
|
|
|
|
|
Skip generation of PDF report. This can save time if you don't need a report. Default: ``False``
|
|
|
|
|
|
|
|
|
|
|
Dan Joseph