kopia lustrzana https://github.com/OpenDroneMap/docs
commit
eddfd66d89
|
@ -144,7 +144,7 @@ While a process is running, it is also possible to list the tasks, and view the
|
|||
Autoscaling ClusterODM
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
CloudODM also includes the option to autoscale on multiple platforms, including, to date, Amazon and Digital Ocean. This allows users to reduce costs associated with always-on instances as well as being able to scale processing based on demand.
|
||||
ClusterODM also includes the option to autoscale on multiple platforms, including, to date, Amazon and Digital Ocean. This allows users to reduce costs associated with always-on instances as well as being able to scale processing based on demand.
|
||||
|
||||
To setup autoscaling you must:
|
||||
|
||||
|
@ -193,8 +193,8 @@ The 3D textured meshes are currently not being merged as part of the workflow (o
|
|||
|
||||
GCPs are fully supported, however, there needs to be at least 3 GCP points on each submodel for the georeferencing to take place. If a submodel has fewer than 3 GCPs, a combination of the remaining GCPs + EXIF data will be used instead (which is going to be less accurate). We recommend using the ``image_groups.txt`` file to accurately control the submodel split when using GCPs.
|
||||
|
||||
Aknowledgments
|
||||
--------------
|
||||
Acknowledgments
|
||||
---------------
|
||||
Huge props to Pau and the folks at Mapillary for their amazing contributions to OpenDroneMap through their OpenSfM code, which is a key component of the split-merge pipeline. We look forward to further pushing the limits of OpenDroneMap and seeing how big a dataset we can process.
|
||||
|
||||
`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_
|
||||
|
|
|
@ -39,7 +39,7 @@ To mitigate this effect, there are a few options but the simplest are as follows
|
|||
:height: 480
|
||||
:width: 640
|
||||
|
||||
As this approach to flying can be take longer than typical flights, a pilot or team can fly a small area using the above approach. OpenDroneMap will generate a calibration file called cameras.json that then can be imported to be used to calibrate another flight that is more efficiently but, from a self calibration perspective, less accurately.
|
||||
As this approach to flying can be take longer than typical flights, a pilot or team can fly a small area using the above approach. OpenDroneMap will generate a calibration file called cameras.json that then can be imported to be used to calibrate another flight that is more efficiently flown.
|
||||
|
||||
Vertically separated flight lines also improve accuracy, but less so than a camera that is forward facing by 5°.
|
||||
|
||||
|
|
Ładowanie…
Reference in New Issue