update language files in locale

source/locale/ar/LC_MESSAGES/gcp.po

@@ -9,9 +9,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: OpenDroneMap 0.9.10\n"
+"Project-Id-Version: OpenDroneMap 2.0.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-21 17:01-0400\n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
 "PO-Revision-Date: 2020-07-21 21:10+0000\n"
 "Last-Translator: Khadija Abdulla <khastylez@gmail.com>, 2020\n"
 "Language-Team: Arabic (https://www.transifex.com/americanredcross/teams/111882/ar/)\n"
@@ -35,13 +35,73 @@ msgstr ""
 "نقاط التحكم الأرضية مفيدة لتصحيح التشوهات في البيانات والإشارة إلى البيانات "
 "لمعرفة أنظمة الإحداثيات."
 
-# 8452104a74d646fd98667e75940154f9
+# ad17511e7ca64fbda395e4f953e80eea
 #: ../../../gcp.rst:7
+msgid ""
+"A Ground Control Point (GCP) is a position measurement made on the ground, "
+"typically using a high precision GPS. (Toffanin 2019)"
+msgstr ""
+
+# 3ea9ac611d3a42a78eb928b9cebb8fe7
+#: ../../../gcp.rst:9
+msgid ""
+"Ground control points can be set existing structures like pavement corners, "
+"lines on a parking lot or contrasting color floor tiles, otherwise can be "
+"set using targets placed on the ground."
+msgstr ""
+
+# 7e9458665b944639b07049fb14aaa585
+#: ../../../gcp.rst:11
+msgid ""
+"Targets can be purchased or build with an ample variety of materials ranging"
+" from bucket lids to floor tiles."
+msgstr ""
+
+# 58d694776d2944069f23706d57db7f03
+#: ../../../gcp.rst:15
+msgid "Recommended practices for GCP setting"
+msgstr ""
+
+# be9453643db74c3dbce9cb60114879b8
+#: ../../../gcp.rst:17
+msgid ""
+"Keep ground control points visible for all camera locations. Consider the "
+"expected ground sampling distance, illumination, vegetation, buildings and "
+"all the existing obstacles."
+msgstr ""
+
+# b8ca322401f44845bcd07bab7d07c0a6
+#: ../../../gcp.rst:19
+msgid ""
+"Procure an evenly horizontal distribution of the GCPs within the project, "
+"covering high and low elevations. A minimum of 5 GCP works for most of the "
+"jobs, and for larger projects 8 – 10 are sufficient. Locate some points near"
+" the corners and others in the center, considering that GCP spacing should "
+"be larger than the image footprint so that you can’t see more than one GCP "
+"in a single image."
+msgstr ""
+
+# ac223f7550cd411da9e36fd8784fba34
+#: ../../../gcp.rst:21
+msgid ""
+"In order to ensure each GCP are found in at least 5 images, separate the "
+"points 10 to 30 meters from the perimeter of the project. This distance is "
+"dependent of the overlapping, so increasing overlapping should reduce the "
+"required distance from the perimeter."
+msgstr ""
+
+# 7e516e234f5d48b6bdf2452c90949a1e
+#: ../../../gcp.rst:25
+msgid "GCP file format"
+msgstr ""
+
+# 8452104a74d646fd98667e75940154f9
+#: ../../../gcp.rst:27
 msgid "The format of the GCP file is simple."
 msgstr "تنسيق ملف GCP بسيط"
 
 # dce0e96292f14671b20009aff56908eb
-#: ../../../gcp.rst:9
+#: ../../../gcp.rst:29
 msgid ""
 "The first line should contain the name of the projection used for the geo "
 "coordinates. This can be specified either as a PROJ string (e.g. ``+proj=utm"
@@ -55,7 +115,7 @@ msgstr ""
 "``WGS84 UTM 1[N|S]`` value (eg. ``WGS84 UTM 16N``)"
 
 # b2b962c0b86148d0baa20170f21a4809
-#: ../../../gcp.rst:10
+#: ../../../gcp.rst:30
 msgid ""
 "Subsequent lines are the X, Y & Z coordinates, your associated pixels, the "
 "image filename and optional extra fields, separated by tabs or spaces:"
@@ -64,27 +124,27 @@ msgstr ""
 "الصورة والحقول الإضافية الاختيارية ، مفصولة بعلامات تبويب أو مسافات:"
 
 # b14a4632f09d452987da341b4761ee93
-#: ../../../gcp.rst:11
+#: ../../../gcp.rst:31
 msgid "Elevation values can be set to \"NaN\" to indicate no value"
 msgstr "مكن ضبط قيم الارتفاع على \"NaN\" للإشارة إلى عدم وجود قيمة"
 
 # 326fc2b4a246402887eec024ee7dc44b
-#: ../../../gcp.rst:12
+#: ../../../gcp.rst:32
 msgid "The 7th column (optional) typically contains the label of the GCP."
 msgstr "يحتوي العمود السابع (اختياري) يحتوي عادة GCP تسمية."
 
 # 7e516e234f5d48b6bdf2452c90949a1e
-#: ../../../gcp.rst:14
+#: ../../../gcp.rst:34
 msgid "GCP file format::"
 msgstr "تنسيق ملف GCP"
 
 # cfc779a9cd644757ac87736911a5cb2c
-#: ../../../gcp.rst:20
+#: ../../../gcp.rst:40
 msgid "Example::"
 msgstr "مثال::"
 
 # af0d955959494dfea9d3d9efbb90d333
-#: ../../../gcp.rst:27
+#: ../../../gcp.rst:47
 msgid ""
 "If you supply a GCP file called ``gcp_list.txt`` then ODM will automatically"
 " detect it. If it has another name you can specify using ``--gcp <path>``. "
@@ -100,7 +160,7 @@ msgstr ""
 "استخدام هذه المعلومات مع ملف gcp ، يمكنك تحديد \"--force-gps\"."
 
 # bbde94c6d77e4ebcb74ecec6b26d4752
-#: ../../../gcp.rst:29
+#: ../../../gcp.rst:49
 msgid ""
 "`This post has some information about placing Ground Control Targets before "
 "a flight <http://diydrones.com/profiles/blogs/ground-control-points-gcps-"
@@ -116,7 +176,7 @@ msgstr ""
 "صور على الأقل ** ، وأن تعثر على 5 كائنات على الأقل."
 
 # 6b99ba39e0ba4be98be0cf9089458f19
-#: ../../../gcp.rst:31
+#: ../../../gcp.rst:51
 msgid ""
 "Sharp corners are good picks for GCPs. You should also place/find the GCPs "
 "evenly around your survey area."
@@ -125,14 +185,14 @@ msgstr ""
 "نقاط المراقبة الحرجة بشكل متساوٍ حول منطقة المسح."
 
 # 2022c1e3d9074c80bc5988fb77630231
-#: ../../../gcp.rst:33
+#: ../../../gcp.rst:53
 msgid ""
 "The ``gcp_list.txt`` file must be created in the base of your project "
 "folder."
 msgstr "يجب إنشاء ملف `` gcp_list.txt '' في قاعدة مجلد المشروع."
 
 # d053ffc6a0b44e60be90864b1d0ad399
-#: ../../../gcp.rst:35
+#: ../../../gcp.rst:55
 msgid ""
 "For good results your file should have a minimum of 15 lines after the "
 "header (5 points with 3 images to each point)."
@@ -141,32 +201,32 @@ msgstr ""
 "(5 نقاط مع 3 صور لكل نقطة)."
 
 # 9712bfa7df5343f8b383155a9eee015c
-#: ../../../gcp.rst:39
+#: ../../../gcp.rst:59
 msgid "User Interfaces"
 msgstr "واجهات المستخدم"
 
 # 58a11feafc7641fca1250a9e80a9e9a2
-#: ../../../gcp.rst:41
+#: ../../../gcp.rst:61
 msgid "You can use one of two user interfaces for creating GCP files:"
 msgstr "يمكنك استخدام واحدة من واجهات المستخدم لإنشاء ملفات GCP:"
 
 # 84afe5e0d2964247b972da99da981b86
-#: ../../../gcp.rst:43
+#: ../../../gcp.rst:63
 msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
 msgstr "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
 
 # 60450f4c04ca4bac9bd654bd2ba83c35
-#: ../../../gcp.rst:44
+#: ../../../gcp.rst:64
 msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
 msgstr "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
 
 # 397f2777c59948cc8c50fe7aaee405e1
-#: ../../../gcp.rst:48
+#: ../../../gcp.rst:68
 msgid "POSM GCPi"
 msgstr "POSM GCPi"
 
 # 927593a77dc84e74b137c4d439df6825
-#: ../../../gcp.rst:50
+#: ../../../gcp.rst:70
 msgid ""
 "The POSM GCPi is loaded by default on WebODM. An example is available at "
 "`the WebODM Demo <http://demo.webodm.org/plugins/posm-gcpi/>`_. To use this "
@@ -177,7 +237,7 @@ msgstr ""
 "المعروفة للتحكم الأرضي ، يمكن للمرء القيام بما يلي: "
 
 # b9a43cb0966f427fae9039e6aa420d36
-#: ../../../gcp.rst:52
+#: ../../../gcp.rst:72
 msgid ""
 "Create a GCP list that only includes gcp name (this is the label that will "
 "be seen in the GCP interface), x, y, and z, with a header with a proj4 "
@@ -189,7 +249,7 @@ msgstr ""
 "النظام ، مثل UTM. يجب أن يبدو شيء مثل هذا:"
 
 # c193a1ce8f7a4da2b796010be7fc9521
-#: ../../../gcp.rst:63
+#: ../../../gcp.rst:83
 msgid ""
 "Then one can load this GCP list into the interface, load the images, and "
 "place each of the GCPs in the image."
@@ -198,12 +258,12 @@ msgstr ""
 " في الصورة."
 
 # ece94c1e7c6c44698893e57cf6c10c92
-#: ../../../gcp.rst:67
+#: ../../../gcp.rst:87
 msgid "GCP Editor Pro"
 msgstr "GCP Editor Pro"
 
 # 31a2f2c5d1614505b9b11f063ed8f8af
-#: ../../../gcp.rst:69
+#: ../../../gcp.rst:89
 msgid ""
 "This app needs to be installed separately or can be loaded as a WebODM "
 "plugin from `https://github.com/uav4geo/GCPEditorPro "
@@ -214,14 +274,14 @@ msgstr ""
 "<https://github.com/uav4geo/GCPEditorPro>`_"
 
 # 400a7b772b064992b58e256c4a86d802
-#: ../../../gcp.rst:71
+#: ../../../gcp.rst:91
 msgid ""
 "Create a CSV file that includes the gcp name, northing, easting and "
 "elevation."
 msgstr "أنشئ ملف CSV يتضمن اسم gcp والشمال والشرق والارتفاع."
 
 # e3be97e2b1d442f99df0adde4e1752cb
-#: ../../../gcp.rst:80
+#: ../../../gcp.rst:100
 msgid ""
 "Then import the CSV from the main screen and type ``+proj=utm +zone=37 "
 "+south +ellps=WGS84 +datum=WGS84 +units=m +no_defs`` in the ``EPSG/PROJ`` "
@@ -231,7 +291,7 @@ msgstr ""
 "+ellps=WGS84 +datum=WGS84 +units=m +no_defs`` in the ``EPSG/PROJ`` صندوق."
 
 # e90ba38338ef409792e454d071bbcc16
-#: ../../../gcp.rst:82
+#: ../../../gcp.rst:102
 msgid ""
 "The following screen will display a map from where to select the GCPs to tag"
 " and import the respective images."
@@ -239,8 +299,20 @@ msgstr ""
 "سيتم عرض الشاشة التالية خريطة من أين تختار GCP وضع علامة على الصور ذات الصلة"
 " واستيرادها."
 
+# 9712bfa7df5343f8b383155a9eee015c
+#: ../../../gcp.rst:106
+msgid "References"
+msgstr ""
+
+# 00d0a4cc5f3441b09095b9e4c3d1805f
+#: ../../../gcp.rst:108
+msgid ""
+"Toffanin, Piero. `Open Drone Map: The Missing Guide. "
+"<https://odmbook.com/>`_ MasseranoLabs LLC, 2019."
+msgstr ""
+
 # 23911fa0503e4bb58ddc99f41c10b797
-#: ../../../gcp.rst:85
+#: ../../../gcp.rst:111
 msgid ""
 "`Help edit these docs! "
 "<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"

source/locale/ar/LC_MESSAGES/map-accuracy.po

@@ -0,0 +1,254 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2020, OpenDroneMap
+# This file is distributed under the same license as the OpenDroneMap package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+# 
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: OpenDroneMap 2.0.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
+"PO-Revision-Date: 2020-10-15 13:38+0000\n"
+"Language-Team: Arabic (https://www.transifex.com/americanredcross/teams/111882/ar/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ar\n"
+"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
+
+# d4e2d7d317d34b208e768f689ad692b0
+#: ../../../map-accuracy.rst:3
+msgid "Map accuracy"
+msgstr ""
+
+# 674abb654cf7448cac13ea47971e80d2
+#: ../../../map-accuracy.rst:5
+msgid ""
+"Accuracy can be defined as the degree or closeness to which the information "
+"on a map matches the values in the real world. Therefore, when we refer to "
+"accuracy, we are talking about quality of data and about number of errors "
+"contained in a certain dataset (Pascual 2011)."
+msgstr ""
+
+# c23ea9314c134c8ba5671054b7e3c057
+#: ../../../map-accuracy.rst:8
+msgid "**Relative or Local accuracy**"
+msgstr ""
+
+# 35f3324c29ea443497c2fdcd80a55145
+#: ../../../map-accuracy.rst:10
+msgid ""
+"Local or relative accuracy can be defined as the degree to which de "
+"distances between two points on a map correspond to the actually distances "
+"between those points in the real world."
+msgstr ""
+
+# 5463e74ce3b246a4a690fcc476f95536
+#: ../../../map-accuracy.rst:12
+msgid ""
+"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)."
+msgstr ""
+
+# 1d4253e1796842319b7dcbd23384343c
+#: ../../../map-accuracy.rst:18
+msgid ""
+"*Figure 1. Model showing high relative accuracy but misplaced according to "
+"its real world position*"
+msgstr ""
+
+# 754655b1d1d840fbbc8c2d8980a876fb
+#: ../../../map-accuracy.rst:22
+msgid "**Absolute or global Accuracy**"
+msgstr ""
+
+# e5e01529bd0c499aa456f620a7022ef5
+#: ../../../map-accuracy.rst:24
+msgid ""
+"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."
+msgstr ""
+
+# 9d73ff2d96b14f37b5f6166e2baf2695
+#: ../../../map-accuracy.rst:30
+msgid ""
+"*Figure 2. Model showing high relative and absolute accuracy. Placed "
+"correctly according to its real world position*"
+msgstr ""
+
+# b73218309c99474abc6119f6bfffdf61
+#: ../../../map-accuracy.rst:33
+msgid "**An Accuracy level for each project**"
+msgstr ""
+
+# 1cccb608cda9412c9545ad6c5094fa64
+#: ../../../map-accuracy.rst:35
+msgid ""
+"Each project has specific accuracy needs to be met. For instance assessing "
+"the progress in a construction site or measuring an area affected by a fire "
+"does not require the use of GCP, since absolute accuracy will not impact the"
+" decision making process. In the other hand, there are tasks on which "
+"accuracy is critical, for example project compliance evaluations and land "
+"title surveying, which require a higher relative and absolute accuracy."
+msgstr ""
+
+# cc37e2d221b5438597d9284f2f6b18ff
+#: ../../../map-accuracy.rst:39
+msgid "What to expect"
+msgstr ""
+
+# 0a236f8f8a584a588a68484240ee6551
+#: ../../../map-accuracy.rst:41
+msgid ""
+"In general terms, one can expect the relative accuracy to be in the order of"
+" 1 to 3 times the average GSD for the dataset. And as for the absolute "
+"accuracy, one must consider that it is dependent of the GPS unit mounted in "
+"the UAV but the horizontal accuracy of a standard GPS is usually in the "
+"range of 2 to 6 meters and the vertical accuracy between 3 to 4 times the "
+"horizontal accuracy."
+msgstr ""
+
+# 60659f189c6143b6bd94cb23d28105d6
+#: ../../../map-accuracy.rst:43
+msgid ""
+"When using GCP, absolute accuracy can be improved to 2.5 times GSD for the "
+"horizontal accuracy and 4 times the GSD for the vertical accuracy "
+"(Madawalagama 2016)."
+msgstr ""
+
+# 7f9656e94e544adf807d480168874da7
+#: ../../../map-accuracy.rst:45
+msgid ""
+"At a GSD of 1cm, the accuracy is to that of the RTK GNSS, and is within "
+"1:200 scales according to NSDI & FGDC mapping accuracy standards during sub-"
+"optimal conditions (Barry 2013)."
+msgstr ""
+
+# 3e9dd6b536884dd38b143069f710f1ab
+#: ../../../map-accuracy.rst:49
+msgid "Aspects impacting map accuracy"
+msgstr ""
+
+# fedd030db34543209cfa5ee6ef5e6196
+#: ../../../map-accuracy.rst:51
+msgid "**Weather**"
+msgstr ""
+
+# dd1b686e9e6b413c96a22b6509f9d88d
+#: ../../../map-accuracy.rst:53
+msgid ""
+"Weather conditions have direct impact in the photogrammetry results, so it "
+"is important to consider cloud coverage, wind speed, humidity, sun’s "
+"altitude and other factors influencing the UAV stability and terrain "
+"illumination."
+msgstr ""
+
+# dd609d1a79b64f2590b9d786fa83e5f1
+#: ../../../map-accuracy.rst:55
+msgid "**Cameras**"
+msgstr ""
+
+# c3cb5f9cfee84481a72bfcb66a85f17b
+#: ../../../map-accuracy.rst:57
+msgid ""
+"Bigger and better sensors produce less noise and more clearly focused "
+"images. Also consider that rolling shutter cameras produce distorted images "
+"when the UAV is moving, so global or mechanical shutter cameras are advised "
+"for mapping jobs."
+msgstr ""
+
+# e4f17c5a5c184b5691fa3a8c08bb8543
+#: ../../../map-accuracy.rst:60
+msgid "**Flight altitude**"
+msgstr ""
+
+# e6a7b31d71664586a04a8fdd54f2001d
+#: ../../../map-accuracy.rst:62
+msgid ""
+"The higher the flight altitude, the larger the image footprint and GSD. The "
+"resulting larger GSD the accuracy will be decreased as there will be less "
+"detail in the recognizable features. When a smaller GSD is required an "
+"altitude of 3 to 4 times the height of the highest point is recommended."
+msgstr ""
+
+# 1555b7ec782a49c6a7460f0e32d578e0
+#: ../../../map-accuracy.rst:65
+msgid "**Flight speed**"
+msgstr ""
+
+# 2eb90c4a9e41400d94a560217cfc9e96
+#: ../../../map-accuracy.rst:67
+msgid ""
+"Flight speed have special effect in cameras equipped with rolling shutter, "
+"while those equipped with global or mechanical shutter tends to reduce this "
+"effect. UAV equipped with RTK positioning systems are also affected with the"
+" speed, but with hover at each photo taken, you can get very good accuracy. "
+"If instead you are moving during each photo take, the accuracy is going to "
+"be limited by two factors: the speed at which you are moving multiplied by "
+"the 1 second increments of RTK (Mather 2020)."
+msgstr ""
+
+# d2ef9f75f3624fd18cc2d2e7e0f9afee
+#: ../../../map-accuracy.rst:72
+msgid "References"
+msgstr ""
+
+# 9b8c9e6151824c24a592ec6ae333ff61
+#: ../../../map-accuracy.rst:74
+msgid ""
+"Barry, P., & Coakley, R. «Accuracy of UAV photogrammetry compared with "
+"Network RTK GPS.» Baseline Surveys. 2013. "
+"http://uav.ie/PDF/Accuracy_UAV_compare_RTK_GPS.pdf  (accessed 10 13, 2020)."
+msgstr ""
+
+# 54475a5460a74936b892b63f462125f9
+#: ../../../map-accuracy.rst:76
+msgid ""
+"Drone Deploy. How Do I Use Ground Control Points?: A guide to using ground "
+"control points with drone mapping software. 5 8, 2017. "
+"https://www.dronedeploy.com/blog/what-are-ground-control-points-gcps/ "
+"(accessed 7 9, 2020)."
+msgstr ""
+
+# 3c130fce6ff74f019cbe7244f8138545
+#: ../../../map-accuracy.rst:78
+msgid ""
+"Madawalagama, S.L., Munasinghe, N., Dampegama, S.D.P.J. and Samarakoon, L. "
+"«Low-cost aerial mapping with consumer grade.» 37th Asian Conference on "
+"Remote Sensing. Colombo, Sri Lanka, 2016."
+msgstr ""
+
+# 151ceb4c0fd84418b73fd6a3717038e3
+#: ../../../map-accuracy.rst:80
+msgid ""
+"Mather, Stephen. OpenDroneMap. 30 de Marzo de 2020. "
+"https://community.opendronemap.org/t/the-accuracy-of-webodm-using-rtk-"
+"uavs/3937 (accessed 10 12, 2020)."
+msgstr ""
+
+# 6f51c9cc28e6453ab07e036fa6e37a03
+#: ../../../map-accuracy.rst:82
+msgid ""
+"Pascual, Manuel S. GIS Lounge: GIS Data: A Look at Accuracy, Precision, and "
+"Types of Errors. 11 6, 2011. https://www.gislounge.com/gis-data-a-look-at-"
+"accuracy-precision-and-types-of-errors/ (accessed 07 09, 2020)."
+msgstr ""
+
+# 0bc80ba7d78f4075b5ea484cdbdb767f
+#: ../../../map-accuracy.rst:84
+msgid ""
+"Pix4D. «What is accuracy in an aerial mapping project?» Pix4D. 25 de 05 de "
+"2019. https://www.pix4d.com/blog/accuracy-aerial-mapping (accessed 10 13, "
+"2020)."
+msgstr ""
+
+# ef00360d240e421696b89cd720808a3e
+#: ../../../map-accuracy.rst:87
+msgid ""
+"`Help edit these docs! "
+"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
+msgstr ""

source/locale/en/pot/gcp.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: OpenDroneMap 2.0.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-10-05 12:56-0400\n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -27,131 +27,181 @@ msgid "Ground control points are useful for correcting distortions in the data a
 msgstr ""
 
 #: ../../../gcp.rst:7
+# ad17511e7ca64fbda395e4f953e80eea
+msgid "A Ground Control Point (GCP) is a position measurement made on the ground, typically using a high precision GPS. (Toffanin 2019)"
+msgstr ""
+
+#: ../../../gcp.rst:9
+# 3ea9ac611d3a42a78eb928b9cebb8fe7
+msgid "Ground control points can be set existing structures like pavement corners, lines on a parking lot or contrasting color floor tiles, otherwise can be set using targets placed on the ground."
+msgstr ""
+
+#: ../../../gcp.rst:11
+# 7e9458665b944639b07049fb14aaa585
+msgid "Targets can be purchased or build with an ample variety of materials ranging from bucket lids to floor tiles."
+msgstr ""
+
+#: ../../../gcp.rst:15
+# 58d694776d2944069f23706d57db7f03
+msgid "Recommended practices for GCP setting"
+msgstr ""
+
+#: ../../../gcp.rst:17
+# be9453643db74c3dbce9cb60114879b8
+msgid "Keep ground control points visible for all camera locations. Consider the expected ground sampling distance, illumination, vegetation, buildings and all the existing obstacles."
+msgstr ""
+
+#: ../../../gcp.rst:19
+# b8ca322401f44845bcd07bab7d07c0a6
+msgid "Procure an evenly horizontal distribution of the GCPs within the project, covering high and low elevations. A minimum of 5 GCP works for most of the jobs, and for larger projects 8 – 10 are sufficient. Locate some points near the corners and others in the center, considering that GCP spacing should be larger than the image footprint so that you can’t see more than one GCP in a single image."
+msgstr ""
+
+#: ../../../gcp.rst:21
+# ac223f7550cd411da9e36fd8784fba34
+msgid "In order to ensure each GCP are found in at least 5 images, separate the points 10 to 30 meters from the perimeter of the project. This distance is dependent of the overlapping, so increasing overlapping should reduce the required distance from the perimeter."
+msgstr ""
+
+#: ../../../gcp.rst:25
+# 7e516e234f5d48b6bdf2452c90949a1e
+msgid "GCP file format"
+msgstr ""
+
+#: ../../../gcp.rst:27
 # 8452104a74d646fd98667e75940154f9
 msgid "The format of the GCP file is simple."
 msgstr ""
 
-#: ../../../gcp.rst:9
+#: ../../../gcp.rst:29
 # dce0e96292f14671b20009aff56908eb
 msgid "The first line should contain the name of the projection used for the geo coordinates. This can be specified either as a PROJ string (e.g. ``+proj=utm +zone=10 +ellps=WGS84 +datum=WGS84 +units=m +no_defs``), EPSG code (e.g. ``EPSG:4326``) or as a ``WGS84 UTM <zone>[N|S]`` value (eg. ``WGS84 UTM 16N``)"
 msgstr ""
 
-#: ../../../gcp.rst:10
+#: ../../../gcp.rst:30
 # b2b962c0b86148d0baa20170f21a4809
 msgid "Subsequent lines are the X, Y & Z coordinates, your associated pixels, the image filename and optional extra fields, separated by tabs or spaces:"
 msgstr ""
 
-#: ../../../gcp.rst:11
+#: ../../../gcp.rst:31
 # b14a4632f09d452987da341b4761ee93
 msgid "Elevation values can be set to \"NaN\" to indicate no value"
 msgstr ""
 
-#: ../../../gcp.rst:12
+#: ../../../gcp.rst:32
 # 326fc2b4a246402887eec024ee7dc44b
 msgid "The 7th column (optional) typically contains the label of the GCP."
 msgstr ""
 
-#: ../../../gcp.rst:14
+#: ../../../gcp.rst:34
 # 7e516e234f5d48b6bdf2452c90949a1e
 msgid "GCP file format::"
 msgstr ""
 
-#: ../../../gcp.rst:20
+#: ../../../gcp.rst:40
 # cfc779a9cd644757ac87736911a5cb2c
 msgid "Example::"
 msgstr ""
 
-#: ../../../gcp.rst:27
+#: ../../../gcp.rst:47
 # af0d955959494dfea9d3d9efbb90d333
 msgid "If you supply a GCP file called ``gcp_list.txt`` then ODM will automatically detect it. If it has another name you can specify using ``--gcp <path>``. If you have a gcp file and want to do georeferencing with exif instead, then you can specify ``--use-exif``. If you have high precision GPS measurements in your images (RTK) and want to use that information along with a gcp file, you can specify ``--force-gps``."
 msgstr ""
 
-#: ../../../gcp.rst:29
+#: ../../../gcp.rst:49
 # bbde94c6d77e4ebcb74ecec6b26d4752
 msgid "`This post has some information about placing Ground Control Targets before a flight <http://diydrones.com/profiles/blogs/ground-control-points-gcps-for-aerial-photography>`_, but if you already have images, you can find your own points in the images post facto. It's important that you find high-contrast objects that are found in **at least** 3 photos, and that you find a minimum of 5 objects."
 msgstr ""
 
-#: ../../../gcp.rst:31
+#: ../../../gcp.rst:51
 # 6b99ba39e0ba4be98be0cf9089458f19
 msgid "Sharp corners are good picks for GCPs. You should also place/find the GCPs evenly around your survey area."
 msgstr ""
 
-#: ../../../gcp.rst:33
+#: ../../../gcp.rst:53
 # 2022c1e3d9074c80bc5988fb77630231
 msgid "The ``gcp_list.txt`` file must be created in the base of your project folder."
 msgstr ""
 
-#: ../../../gcp.rst:35
+#: ../../../gcp.rst:55
 # d053ffc6a0b44e60be90864b1d0ad399
 msgid "For good results your file should have a minimum of 15 lines after the header (5 points with 3 images to each point)."
 msgstr ""
 
-#: ../../../gcp.rst:39
+#: ../../../gcp.rst:59
 # 9712bfa7df5343f8b383155a9eee015c
 msgid "User Interfaces"
 msgstr ""
 
-#: ../../../gcp.rst:41
+#: ../../../gcp.rst:61
 # 58a11feafc7641fca1250a9e80a9e9a2
 msgid "You can use one of two user interfaces for creating GCP files:"
 msgstr ""
 
-#: ../../../gcp.rst:43
+#: ../../../gcp.rst:63
 # 84afe5e0d2964247b972da99da981b86
 msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
 msgstr ""
 
-#: ../../../gcp.rst:44
+#: ../../../gcp.rst:64
 # 60450f4c04ca4bac9bd654bd2ba83c35
 msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
 msgstr ""
 
-#: ../../../gcp.rst:48
+#: ../../../gcp.rst:68
 # 397f2777c59948cc8c50fe7aaee405e1
 msgid "POSM GCPi"
 msgstr ""
 
-#: ../../../gcp.rst:50
+#: ../../../gcp.rst:70
 # 927593a77dc84e74b137c4d439df6825
 msgid "The POSM GCPi is loaded by default on WebODM. An example is available at `the WebODM Demo <http://demo.webodm.org/plugins/posm-gcpi/>`_. To use this with known ground control XYZ values, one would do the following:"
 msgstr ""
 
-#: ../../../gcp.rst:52
+#: ../../../gcp.rst:72
 # b9a43cb0966f427fae9039e6aa420d36
 msgid "Create a GCP list that only includes gcp name (this is the label that will be seen in the GCP interface), x, y, and z, with a header with a proj4 string of your GCPs (make sure they are in a planar coordinate system, such as UTM. It should look something like this:"
 msgstr ""
 
-#: ../../../gcp.rst:63
+#: ../../../gcp.rst:83
 # c193a1ce8f7a4da2b796010be7fc9521
 msgid "Then one can load this GCP list into the interface, load the images, and place each of the GCPs in the image."
 msgstr ""
 
-#: ../../../gcp.rst:67
+#: ../../../gcp.rst:87
 # ece94c1e7c6c44698893e57cf6c10c92
 msgid "GCP Editor Pro"
 msgstr ""
 
-#: ../../../gcp.rst:69
+#: ../../../gcp.rst:89
 # 31a2f2c5d1614505b9b11f063ed8f8af
 msgid "This app needs to be installed separately or can be loaded as a WebODM plugin from `https://github.com/uav4geo/GCPEditorPro <https://github.com/uav4geo/GCPEditorPro>`_"
 msgstr ""
 
-#: ../../../gcp.rst:71
+#: ../../../gcp.rst:91
 # 400a7b772b064992b58e256c4a86d802
 msgid "Create a CSV file that includes the gcp name, northing, easting and elevation."
 msgstr ""
 
-#: ../../../gcp.rst:80
+#: ../../../gcp.rst:100
 # e3be97e2b1d442f99df0adde4e1752cb
 msgid "Then import the CSV from the main screen and type ``+proj=utm +zone=37 +south +ellps=WGS84 +datum=WGS84 +units=m +no_defs`` in the ``EPSG/PROJ`` box."
 msgstr ""
 
-#: ../../../gcp.rst:82
+#: ../../../gcp.rst:102
 # e90ba38338ef409792e454d071bbcc16
 msgid "The following screen will display a map from where to select the GCPs to tag and import the respective images."
 msgstr ""
 
-#: ../../../gcp.rst:85
+#: ../../../gcp.rst:106
+# 9712bfa7df5343f8b383155a9eee015c
+msgid "References"
+msgstr ""
+
+#: ../../../gcp.rst:108
+# 00d0a4cc5f3441b09095b9e4c3d1805f
+msgid "Toffanin, Piero. `Open Drone Map: The Missing Guide. <https://odmbook.com/>`_ MasseranoLabs LLC, 2019."
+msgstr ""
+
+#: ../../../gcp.rst:111
 # 23911fa0503e4bb58ddc99f41c10b797
 msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
 msgstr ""

source/locale/en/pot/index.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: OpenDroneMap 2.0.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-10-05 12:56-0400\n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -21,7 +21,7 @@ msgstr ""
 msgid "Welcome to OpenDroneMap's documentation"
 msgstr ""
 
-#: ../../../index.rst:45
+#: ../../../index.rst:46
 # 2b86dd77c9ca4fdbb3e5c3a362287930
 msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
 msgstr ""

source/locale/en/pot/map-accuracy.pot

@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2020, OpenDroneMap
+# This file is distributed under the same license as the OpenDroneMap package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: OpenDroneMap 2.0.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../../map-accuracy.rst:3
+# d4e2d7d317d34b208e768f689ad692b0
+msgid "Map accuracy"
+msgstr ""
+
+#: ../../../map-accuracy.rst:5
+# 674abb654cf7448cac13ea47971e80d2
+msgid "Accuracy can be defined as the degree or closeness to which the information on a map matches the values in the real world. Therefore, when we refer to accuracy, we are talking about quality of data and about number of errors contained in a certain dataset (Pascual 2011)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:8
+# c23ea9314c134c8ba5671054b7e3c057
+msgid "**Relative or Local accuracy**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:10
+# 35f3324c29ea443497c2fdcd80a55145
+msgid "Local or relative accuracy can be defined as the degree to which de distances between two points on a map correspond to the actually distances between those points in the real world."
+msgstr ""
+
+#: ../../../map-accuracy.rst:12
+# 5463e74ce3b246a4a690fcc476f95536
+msgid "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)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:18
+# 1d4253e1796842319b7dcbd23384343c
+msgid "*Figure 1. Model showing high relative accuracy but misplaced according to its real world position*"
+msgstr ""
+
+#: ../../../map-accuracy.rst:22
+# 754655b1d1d840fbbc8c2d8980a876fb
+msgid "**Absolute or global Accuracy**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:24
+# e5e01529bd0c499aa456f620a7022ef5
+msgid "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."
+msgstr ""
+
+#: ../../../map-accuracy.rst:30
+# 9d73ff2d96b14f37b5f6166e2baf2695
+msgid "*Figure 2. Model showing high relative and absolute accuracy. Placed correctly according to its real world position*"
+msgstr ""
+
+#: ../../../map-accuracy.rst:33
+# b73218309c99474abc6119f6bfffdf61
+msgid "**An Accuracy level for each project**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:35
+# 1cccb608cda9412c9545ad6c5094fa64
+msgid "Each project has specific accuracy needs to be met. For instance assessing the progress in a construction site or measuring an area affected by a fire does not require the use of GCP, since absolute accuracy will not impact the decision making process. In the other hand, there are tasks on which accuracy is critical, for example project compliance evaluations and land title surveying, which require a higher relative and absolute accuracy."
+msgstr ""
+
+#: ../../../map-accuracy.rst:39
+# cc37e2d221b5438597d9284f2f6b18ff
+msgid "What to expect"
+msgstr ""
+
+#: ../../../map-accuracy.rst:41
+# 0a236f8f8a584a588a68484240ee6551
+msgid "In general terms, one can expect the relative accuracy to be in the order of 1 to 3 times the average GSD for the dataset. And as for the absolute accuracy, one must consider that it is dependent of the GPS unit mounted in the UAV but the horizontal accuracy of a standard GPS is usually in the range of 2 to 6 meters and the vertical accuracy between 3 to 4 times the horizontal accuracy."
+msgstr ""
+
+#: ../../../map-accuracy.rst:43
+# 60659f189c6143b6bd94cb23d28105d6
+msgid "When using GCP, absolute accuracy can be improved to 2.5 times GSD for the horizontal accuracy and 4 times the GSD for the vertical accuracy (Madawalagama 2016)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:45
+# 7f9656e94e544adf807d480168874da7
+msgid "At a GSD of 1cm, the accuracy is to that of the RTK GNSS, and is within 1:200 scales according to NSDI & FGDC mapping accuracy standards during sub-optimal conditions (Barry 2013)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:49
+# 3e9dd6b536884dd38b143069f710f1ab
+msgid "Aspects impacting map accuracy"
+msgstr ""
+
+#: ../../../map-accuracy.rst:51
+# fedd030db34543209cfa5ee6ef5e6196
+msgid "**Weather**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:53
+# dd1b686e9e6b413c96a22b6509f9d88d
+msgid "Weather conditions have direct impact in the photogrammetry results, so it is important to consider cloud coverage, wind speed, humidity, sun’s altitude and other factors influencing the UAV stability and terrain illumination."
+msgstr ""
+
+#: ../../../map-accuracy.rst:55
+# dd609d1a79b64f2590b9d786fa83e5f1
+msgid "**Cameras**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:57
+# c3cb5f9cfee84481a72bfcb66a85f17b
+msgid "Bigger and better sensors produce less noise and more clearly focused images. Also consider that rolling shutter cameras produce distorted images when the UAV is moving, so global or mechanical shutter cameras are advised for mapping jobs."
+msgstr ""
+
+#: ../../../map-accuracy.rst:60
+# e4f17c5a5c184b5691fa3a8c08bb8543
+msgid "**Flight altitude**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:62
+# e6a7b31d71664586a04a8fdd54f2001d
+msgid "The higher the flight altitude, the larger the image footprint and GSD. The resulting larger GSD the accuracy will be decreased as there will be less detail in the recognizable features. When a smaller GSD is required an altitude of 3 to 4 times the height of the highest point is recommended."
+msgstr ""
+
+#: ../../../map-accuracy.rst:65
+# 1555b7ec782a49c6a7460f0e32d578e0
+msgid "**Flight speed**"
+msgstr ""
+
+#: ../../../map-accuracy.rst:67
+# 2eb90c4a9e41400d94a560217cfc9e96
+msgid "Flight speed have special effect in cameras equipped with rolling shutter, while those equipped with global or mechanical shutter tends to reduce this effect. UAV equipped with RTK positioning systems are also affected with the speed, but with hover at each photo taken, you can get very good accuracy. If instead you are moving during each photo take, the accuracy is going to be limited by two factors: the speed at which you are moving multiplied by the 1 second increments of RTK (Mather 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:72
+# d2ef9f75f3624fd18cc2d2e7e0f9afee
+msgid "References"
+msgstr ""
+
+#: ../../../map-accuracy.rst:74
+# 9b8c9e6151824c24a592ec6ae333ff61
+msgid "Barry, P., & Coakley, R. «Accuracy of UAV photogrammetry compared with Network RTK GPS.» Baseline Surveys. 2013. http://uav.ie/PDF/Accuracy_UAV_compare_RTK_GPS.pdf  (accessed 10 13, 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:76
+# 54475a5460a74936b892b63f462125f9
+msgid "Drone Deploy. How Do I Use Ground Control Points?: A guide to using ground control points with drone mapping software. 5 8, 2017. https://www.dronedeploy.com/blog/what-are-ground-control-points-gcps/ (accessed 7 9, 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:78
+# 3c130fce6ff74f019cbe7244f8138545
+msgid "Madawalagama, S.L., Munasinghe, N., Dampegama, S.D.P.J. and Samarakoon, L. «Low-cost aerial mapping with consumer grade.» 37th Asian Conference on Remote Sensing. Colombo, Sri Lanka, 2016."
+msgstr ""
+
+#: ../../../map-accuracy.rst:80
+# 151ceb4c0fd84418b73fd6a3717038e3
+msgid "Mather, Stephen. OpenDroneMap. 30 de Marzo de 2020. https://community.opendronemap.org/t/the-accuracy-of-webodm-using-rtk-uavs/3937 (accessed 10 12, 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:82
+# 6f51c9cc28e6453ab07e036fa6e37a03
+msgid "Pascual, Manuel S. GIS Lounge: GIS Data: A Look at Accuracy, Precision, and Types of Errors. 11 6, 2011. https://www.gislounge.com/gis-data-a-look-at-accuracy-precision-and-types-of-errors/ (accessed 07 09, 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:84
+# 0bc80ba7d78f4075b5ea484cdbdb767f
+msgid "Pix4D. «What is accuracy in an aerial mapping project?» Pix4D. 25 de 05 de 2019. https://www.pix4d.com/blog/accuracy-aerial-mapping (accessed 10 13, 2020)."
+msgstr ""
+
+#: ../../../map-accuracy.rst:87
+# ef00360d240e421696b89cd720808a3e
+msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
+msgstr ""
+

source/locale/sw/LC_MESSAGES/gcp.po

@@ -10,9 +10,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: OpenDroneMap 0.9.10\n"
+"Project-Id-Version: OpenDroneMap 2.0.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-07-21 17:01-0400\n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
 "PO-Revision-Date: 2020-07-21 21:10+0000\n"
 "Last-Translator: Khadija Abdulla <khastylez@gmail.com>, 2020\n"
 "Language-Team: Swahili (https://www.transifex.com/americanredcross/teams/111882/sw/)\n"
@@ -36,13 +36,73 @@ msgstr ""
 "Ground control points ni muhimu kurekebisha mzunguko wa taarifa na "
 "kumbukumbu data ili kujua mfumo wa muunganiko."
 
-# 8452104a74d646fd98667e75940154f9
+# ad17511e7ca64fbda395e4f953e80eea
 #: ../../../gcp.rst:7
+msgid ""
+"A Ground Control Point (GCP) is a position measurement made on the ground, "
+"typically using a high precision GPS. (Toffanin 2019)"
+msgstr ""
+
+# 3ea9ac611d3a42a78eb928b9cebb8fe7
+#: ../../../gcp.rst:9
+msgid ""
+"Ground control points can be set existing structures like pavement corners, "
+"lines on a parking lot or contrasting color floor tiles, otherwise can be "
+"set using targets placed on the ground."
+msgstr ""
+
+# 7e9458665b944639b07049fb14aaa585
+#: ../../../gcp.rst:11
+msgid ""
+"Targets can be purchased or build with an ample variety of materials ranging"
+" from bucket lids to floor tiles."
+msgstr ""
+
+# 58d694776d2944069f23706d57db7f03
+#: ../../../gcp.rst:15
+msgid "Recommended practices for GCP setting"
+msgstr ""
+
+# be9453643db74c3dbce9cb60114879b8
+#: ../../../gcp.rst:17
+msgid ""
+"Keep ground control points visible for all camera locations. Consider the "
+"expected ground sampling distance, illumination, vegetation, buildings and "
+"all the existing obstacles."
+msgstr ""
+
+# b8ca322401f44845bcd07bab7d07c0a6
+#: ../../../gcp.rst:19
+msgid ""
+"Procure an evenly horizontal distribution of the GCPs within the project, "
+"covering high and low elevations. A minimum of 5 GCP works for most of the "
+"jobs, and for larger projects 8 – 10 are sufficient. Locate some points near"
+" the corners and others in the center, considering that GCP spacing should "
+"be larger than the image footprint so that you can’t see more than one GCP "
+"in a single image."
+msgstr ""
+
+# ac223f7550cd411da9e36fd8784fba34
+#: ../../../gcp.rst:21
+msgid ""
+"In order to ensure each GCP are found in at least 5 images, separate the "
+"points 10 to 30 meters from the perimeter of the project. This distance is "
+"dependent of the overlapping, so increasing overlapping should reduce the "
+"required distance from the perimeter."
+msgstr ""
+
+# 7e516e234f5d48b6bdf2452c90949a1e
+#: ../../../gcp.rst:25
+msgid "GCP file format"
+msgstr ""
+
+# 8452104a74d646fd98667e75940154f9
+#: ../../../gcp.rst:27
 msgid "The format of the GCP file is simple."
 msgstr "Muundo wa GCP file ni mwepesi."
 
 # dce0e96292f14671b20009aff56908eb
-#: ../../../gcp.rst:9
+#: ../../../gcp.rst:29
 msgid ""
 "The first line should contain the name of the projection used for the geo "
 "coordinates. This can be specified either as a PROJ string (e.g. ``+proj=utm"
@@ -57,7 +117,7 @@ msgstr ""
 "``WGS84 UTM 16N``)"
 
 # b2b962c0b86148d0baa20170f21a4809
-#: ../../../gcp.rst:10
+#: ../../../gcp.rst:30
 msgid ""
 "Subsequent lines are the X, Y & Z coordinates, your associated pixels, the "
 "image filename and optional extra fields, separated by tabs or spaces:"
@@ -66,27 +126,27 @@ msgstr ""
 "file na njia za taarifa za ziada, zilizotenganishwa na kichupo au nafasi:"
 
 # b14a4632f09d452987da341b4761ee93
-#: ../../../gcp.rst:11
+#: ../../../gcp.rst:31
 msgid "Elevation values can be set to \"NaN\" to indicate no value"
 msgstr "Thamani ya muinuko inaweza kuwekwa \"NaN\" kuonesha hapana kitu"
 
 # 326fc2b4a246402887eec024ee7dc44b
-#: ../../../gcp.rst:12
+#: ../../../gcp.rst:32
 msgid "The 7th column (optional) typically contains the label of the GCP."
 msgstr "safu ya 7  (chaguo) kawaida inachukua lebo ya GCP."
 
 # 7e516e234f5d48b6bdf2452c90949a1e
-#: ../../../gcp.rst:14
+#: ../../../gcp.rst:34
 msgid "GCP file format::"
 msgstr "Muundo wa GCP faili::"
 
 # cfc779a9cd644757ac87736911a5cb2c
-#: ../../../gcp.rst:20
+#: ../../../gcp.rst:40
 msgid "Example::"
 msgstr "Mfano::"
 
 # af0d955959494dfea9d3d9efbb90d333
-#: ../../../gcp.rst:27
+#: ../../../gcp.rst:47
 msgid ""
 "If you supply a GCP file called ``gcp_list.txt`` then ODM will automatically"
 " detect it. If it has another name you can specify using ``--gcp <path>``. "
@@ -103,7 +163,7 @@ msgstr ""
 "pamoja na gcp faili, unaweza kutumia ``--force-gps``."
 
 # bbde94c6d77e4ebcb74ecec6b26d4752
-#: ../../../gcp.rst:29
+#: ../../../gcp.rst:49
 msgid ""
 "`This post has some information about placing Ground Control Targets before "
 "a flight <http://diydrones.com/profiles/blogs/ground-control-points-gcps-"
@@ -120,7 +180,7 @@ msgstr ""
 "matano."
 
 # 6b99ba39e0ba4be98be0cf9089458f19
-#: ../../../gcp.rst:31
+#: ../../../gcp.rst:51
 msgid ""
 "Sharp corners are good picks for GCPs. You should also place/find the GCPs "
 "evenly around your survey area."
@@ -129,7 +189,7 @@ msgstr ""
 " GCP hata katika eneo lako la utafiti."
 
 # 2022c1e3d9074c80bc5988fb77630231
-#: ../../../gcp.rst:33
+#: ../../../gcp.rst:53
 msgid ""
 "The ``gcp_list.txt`` file must be created in the base of your project "
 "folder."
@@ -138,7 +198,7 @@ msgstr ""
 "project yako."
 
 # d053ffc6a0b44e60be90864b1d0ad399
-#: ../../../gcp.rst:35
+#: ../../../gcp.rst:55
 msgid ""
 "For good results your file should have a minimum of 15 lines after the "
 "header (5 points with 3 images to each point)."
@@ -147,32 +207,32 @@ msgstr ""
 " (point 5 pamoja na picha 3 kwa kila point)."
 
 # 9712bfa7df5343f8b383155a9eee015c
-#: ../../../gcp.rst:39
+#: ../../../gcp.rst:59
 msgid "User Interfaces"
 msgstr "interface ya mtumiaji"
 
 # 58a11feafc7641fca1250a9e80a9e9a2
-#: ../../../gcp.rst:41
+#: ../../../gcp.rst:61
 msgid "You can use one of two user interfaces for creating GCP files:"
 msgstr "Unaweza kutumia moja kati ya interface mbili kutengeneza GCP faili:"
 
 # 84afe5e0d2964247b972da99da981b86
-#: ../../../gcp.rst:43
+#: ../../../gcp.rst:63
 msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
 msgstr "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
 
 # 60450f4c04ca4bac9bd654bd2ba83c35
-#: ../../../gcp.rst:44
+#: ../../../gcp.rst:64
 msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
 msgstr "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
 
 # 397f2777c59948cc8c50fe7aaee405e1
-#: ../../../gcp.rst:48
+#: ../../../gcp.rst:68
 msgid "POSM GCPi"
 msgstr "POSM GCPi"
 
 # 927593a77dc84e74b137c4d439df6825
-#: ../../../gcp.rst:50
+#: ../../../gcp.rst:70
 msgid ""
 "The POSM GCPi is loaded by default on WebODM. An example is available at "
 "`the WebODM Demo <http://demo.webodm.org/plugins/posm-gcpi/>`_. To use this "
@@ -183,7 +243,7 @@ msgstr ""
 "thamani hii ijulikanayo na udhibiti wa ardhi XYZ, Moja itafanya ifuatavyo:"
 
 # b9a43cb0966f427fae9039e6aa420d36
-#: ../../../gcp.rst:52
+#: ../../../gcp.rst:72
 msgid ""
 "Create a GCP list that only includes gcp name (this is the label that will "
 "be seen in the GCP interface), x, y, and z, with a header with a proj4 "
@@ -196,7 +256,7 @@ msgstr ""
 "Lazima ionekane ka hivi:"
 
 # c193a1ce8f7a4da2b796010be7fc9521
-#: ../../../gcp.rst:63
+#: ../../../gcp.rst:83
 msgid ""
 "Then one can load this GCP list into the interface, load the images, and "
 "place each of the GCPs in the image."
@@ -205,12 +265,12 @@ msgstr ""
 "weka kila GCP katika picha."
 
 # ece94c1e7c6c44698893e57cf6c10c92
-#: ../../../gcp.rst:67
+#: ../../../gcp.rst:87
 msgid "GCP Editor Pro"
 msgstr "GCP Editor Pro"
 
 # 31a2f2c5d1614505b9b11f063ed8f8af
-#: ../../../gcp.rst:69
+#: ../../../gcp.rst:89
 msgid ""
 "This app needs to be installed separately or can be loaded as a WebODM "
 "plugin from `https://github.com/uav4geo/GCPEditorPro "
@@ -221,7 +281,7 @@ msgstr ""
 "<https://github.com/uav4geo/GCPEditorPro>`_"
 
 # 400a7b772b064992b58e256c4a86d802
-#: ../../../gcp.rst:71
+#: ../../../gcp.rst:91
 msgid ""
 "Create a CSV file that includes the gcp name, northing, easting and "
 "elevation."
@@ -229,7 +289,7 @@ msgstr ""
 "Tengeneza CSV faili litalochukua jina la gcp, kaskazini, kusini na muinuko."
 
 # e3be97e2b1d442f99df0adde4e1752cb
-#: ../../../gcp.rst:80
+#: ../../../gcp.rst:100
 msgid ""
 "Then import the CSV from the main screen and type ``+proj=utm +zone=37 "
 "+south +ellps=WGS84 +datum=WGS84 +units=m +no_defs`` in the ``EPSG/PROJ`` "
@@ -240,7 +300,7 @@ msgstr ""
 "``EPSG/PROJ``."
 
 # e90ba38338ef409792e454d071bbcc16
-#: ../../../gcp.rst:82
+#: ../../../gcp.rst:102
 msgid ""
 "The following screen will display a map from where to select the GCPs to tag"
 " and import the respective images."
@@ -248,8 +308,20 @@ msgstr ""
 "Screen zifuatazo zitaonesha ramani kutoka sehemu na kuiita GCP kwa jina na "
 "kuita picha nyengine zilipo."
 
+# 9712bfa7df5343f8b383155a9eee015c
+#: ../../../gcp.rst:106
+msgid "References"
+msgstr ""
+
+# 00d0a4cc5f3441b09095b9e4c3d1805f
+#: ../../../gcp.rst:108
+msgid ""
+"Toffanin, Piero. `Open Drone Map: The Missing Guide. "
+"<https://odmbook.com/>`_ MasseranoLabs LLC, 2019."
+msgstr ""
+
 # 23911fa0503e4bb58ddc99f41c10b797
-#: ../../../gcp.rst:85
+#: ../../../gcp.rst:111
 msgid ""
 "`Help edit these docs! "
 "<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"

source/locale/sw/LC_MESSAGES/installation.po

@@ -4,8 +4,8 @@
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
-# danbjoseph <danbjoseph@gmail.com>, 2020
 # Khadija Abdulla <khastylez@gmail.com>, 2020
+# danbjoseph <danbjoseph@gmail.com>, 2020
 # 
 #, fuzzy
 msgid ""
@@ -14,7 +14,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2020-10-05 12:56-0400\n"
 "PO-Revision-Date: 2020-07-21 21:10+0000\n"
-"Last-Translator: Khadija Abdulla <khastylez@gmail.com>, 2020\n"
+"Last-Translator: danbjoseph <danbjoseph@gmail.com>, 2020\n"
 "Language-Team: Swahili (https://www.transifex.com/americanredcross/teams/111882/sw/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -159,6 +159,12 @@ msgid ""
 " far outweigh a tiny performance penalty. With docker users also get easy "
 "one-step updates of the software, so that’s nice."
 msgstr ""
+"Katika Ubuntu Linux 18.04 inawezekana kurun OpenDroneMap software zote "
+"wenyewe. Hata hivyo, kwa sababu kuna kuongezeka ufanisi kwa kufanya kazi "
+"docker kwenye Linux na docker ina njia nyepesi ya kupangilia katika platform"
+" hii, hatushauri hio. Katika Linux ya faida ya chombo kisichozidi uwezowe "
+"uliopewa. Kwa watumiaji wa docker pia wanapata urahisi katika kupangilia "
+"kuapdate software, kwa hio ni vizuri."
 
 # 359d8630ea1647e097be5d4b34eb3ce4
 #: ../../../installation.rst:54

source/locale/sw/LC_MESSAGES/map-accuracy.po

@@ -0,0 +1,254 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2020, OpenDroneMap
+# This file is distributed under the same license as the OpenDroneMap package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+# 
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: OpenDroneMap 2.0.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2020-10-15 09:34-0400\n"
+"PO-Revision-Date: 2020-10-15 13:38+0000\n"
+"Language-Team: Swahili (https://www.transifex.com/americanredcross/teams/111882/sw/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: sw\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+
+# d4e2d7d317d34b208e768f689ad692b0
+#: ../../../map-accuracy.rst:3
+msgid "Map accuracy"
+msgstr ""
+
+# 674abb654cf7448cac13ea47971e80d2
+#: ../../../map-accuracy.rst:5
+msgid ""
+"Accuracy can be defined as the degree or closeness to which the information "
+"on a map matches the values in the real world. Therefore, when we refer to "
+"accuracy, we are talking about quality of data and about number of errors "
+"contained in a certain dataset (Pascual 2011)."
+msgstr ""
+
+# c23ea9314c134c8ba5671054b7e3c057
+#: ../../../map-accuracy.rst:8
+msgid "**Relative or Local accuracy**"
+msgstr ""
+
+# 35f3324c29ea443497c2fdcd80a55145
+#: ../../../map-accuracy.rst:10
+msgid ""
+"Local or relative accuracy can be defined as the degree to which de "
+"distances between two points on a map correspond to the actually distances "
+"between those points in the real world."
+msgstr ""
+
+# 5463e74ce3b246a4a690fcc476f95536
+#: ../../../map-accuracy.rst:12
+msgid ""
+"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)."
+msgstr ""
+
+# 1d4253e1796842319b7dcbd23384343c
+#: ../../../map-accuracy.rst:18
+msgid ""
+"*Figure 1. Model showing high relative accuracy but misplaced according to "
+"its real world position*"
+msgstr ""
+
+# 754655b1d1d840fbbc8c2d8980a876fb
+#: ../../../map-accuracy.rst:22
+msgid "**Absolute or global Accuracy**"
+msgstr ""
+
+# e5e01529bd0c499aa456f620a7022ef5
+#: ../../../map-accuracy.rst:24
+msgid ""
+"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."
+msgstr ""
+
+# 9d73ff2d96b14f37b5f6166e2baf2695
+#: ../../../map-accuracy.rst:30
+msgid ""
+"*Figure 2. Model showing high relative and absolute accuracy. Placed "
+"correctly according to its real world position*"
+msgstr ""
+
+# b73218309c99474abc6119f6bfffdf61
+#: ../../../map-accuracy.rst:33
+msgid "**An Accuracy level for each project**"
+msgstr ""
+
+# 1cccb608cda9412c9545ad6c5094fa64
+#: ../../../map-accuracy.rst:35
+msgid ""
+"Each project has specific accuracy needs to be met. For instance assessing "
+"the progress in a construction site or measuring an area affected by a fire "
+"does not require the use of GCP, since absolute accuracy will not impact the"
+" decision making process. In the other hand, there are tasks on which "
+"accuracy is critical, for example project compliance evaluations and land "
+"title surveying, which require a higher relative and absolute accuracy."
+msgstr ""
+
+# cc37e2d221b5438597d9284f2f6b18ff
+#: ../../../map-accuracy.rst:39
+msgid "What to expect"
+msgstr ""
+
+# 0a236f8f8a584a588a68484240ee6551
+#: ../../../map-accuracy.rst:41
+msgid ""
+"In general terms, one can expect the relative accuracy to be in the order of"
+" 1 to 3 times the average GSD for the dataset. And as for the absolute "
+"accuracy, one must consider that it is dependent of the GPS unit mounted in "
+"the UAV but the horizontal accuracy of a standard GPS is usually in the "
+"range of 2 to 6 meters and the vertical accuracy between 3 to 4 times the "
+"horizontal accuracy."
+msgstr ""
+
+# 60659f189c6143b6bd94cb23d28105d6
+#: ../../../map-accuracy.rst:43
+msgid ""
+"When using GCP, absolute accuracy can be improved to 2.5 times GSD for the "
+"horizontal accuracy and 4 times the GSD for the vertical accuracy "
+"(Madawalagama 2016)."
+msgstr ""
+
+# 7f9656e94e544adf807d480168874da7
+#: ../../../map-accuracy.rst:45
+msgid ""
+"At a GSD of 1cm, the accuracy is to that of the RTK GNSS, and is within "
+"1:200 scales according to NSDI & FGDC mapping accuracy standards during sub-"
+"optimal conditions (Barry 2013)."
+msgstr ""
+
+# 3e9dd6b536884dd38b143069f710f1ab
+#: ../../../map-accuracy.rst:49
+msgid "Aspects impacting map accuracy"
+msgstr ""
+
+# fedd030db34543209cfa5ee6ef5e6196
+#: ../../../map-accuracy.rst:51
+msgid "**Weather**"
+msgstr ""
+
+# dd1b686e9e6b413c96a22b6509f9d88d
+#: ../../../map-accuracy.rst:53
+msgid ""
+"Weather conditions have direct impact in the photogrammetry results, so it "
+"is important to consider cloud coverage, wind speed, humidity, sun’s "
+"altitude and other factors influencing the UAV stability and terrain "
+"illumination."
+msgstr ""
+
+# dd609d1a79b64f2590b9d786fa83e5f1
+#: ../../../map-accuracy.rst:55
+msgid "**Cameras**"
+msgstr ""
+
+# c3cb5f9cfee84481a72bfcb66a85f17b
+#: ../../../map-accuracy.rst:57
+msgid ""
+"Bigger and better sensors produce less noise and more clearly focused "
+"images. Also consider that rolling shutter cameras produce distorted images "
+"when the UAV is moving, so global or mechanical shutter cameras are advised "
+"for mapping jobs."
+msgstr ""
+
+# e4f17c5a5c184b5691fa3a8c08bb8543
+#: ../../../map-accuracy.rst:60
+msgid "**Flight altitude**"
+msgstr ""
+
+# e6a7b31d71664586a04a8fdd54f2001d
+#: ../../../map-accuracy.rst:62
+msgid ""
+"The higher the flight altitude, the larger the image footprint and GSD. The "
+"resulting larger GSD the accuracy will be decreased as there will be less "
+"detail in the recognizable features. When a smaller GSD is required an "
+"altitude of 3 to 4 times the height of the highest point is recommended."
+msgstr ""
+
+# 1555b7ec782a49c6a7460f0e32d578e0
+#: ../../../map-accuracy.rst:65
+msgid "**Flight speed**"
+msgstr ""
+
+# 2eb90c4a9e41400d94a560217cfc9e96
+#: ../../../map-accuracy.rst:67
+msgid ""
+"Flight speed have special effect in cameras equipped with rolling shutter, "
+"while those equipped with global or mechanical shutter tends to reduce this "
+"effect. UAV equipped with RTK positioning systems are also affected with the"
+" speed, but with hover at each photo taken, you can get very good accuracy. "
+"If instead you are moving during each photo take, the accuracy is going to "
+"be limited by two factors: the speed at which you are moving multiplied by "
+"the 1 second increments of RTK (Mather 2020)."
+msgstr ""
+
+# d2ef9f75f3624fd18cc2d2e7e0f9afee
+#: ../../../map-accuracy.rst:72
+msgid "References"
+msgstr ""
+
+# 9b8c9e6151824c24a592ec6ae333ff61
+#: ../../../map-accuracy.rst:74
+msgid ""
+"Barry, P., & Coakley, R. «Accuracy of UAV photogrammetry compared with "
+"Network RTK GPS.» Baseline Surveys. 2013. "
+"http://uav.ie/PDF/Accuracy_UAV_compare_RTK_GPS.pdf  (accessed 10 13, 2020)."
+msgstr ""
+
+# 54475a5460a74936b892b63f462125f9
+#: ../../../map-accuracy.rst:76
+msgid ""
+"Drone Deploy. How Do I Use Ground Control Points?: A guide to using ground "
+"control points with drone mapping software. 5 8, 2017. "
+"https://www.dronedeploy.com/blog/what-are-ground-control-points-gcps/ "
+"(accessed 7 9, 2020)."
+msgstr ""
+
+# 3c130fce6ff74f019cbe7244f8138545
+#: ../../../map-accuracy.rst:78
+msgid ""
+"Madawalagama, S.L., Munasinghe, N., Dampegama, S.D.P.J. and Samarakoon, L. "
+"«Low-cost aerial mapping with consumer grade.» 37th Asian Conference on "
+"Remote Sensing. Colombo, Sri Lanka, 2016."
+msgstr ""
+
+# 151ceb4c0fd84418b73fd6a3717038e3
+#: ../../../map-accuracy.rst:80
+msgid ""
+"Mather, Stephen. OpenDroneMap. 30 de Marzo de 2020. "
+"https://community.opendronemap.org/t/the-accuracy-of-webodm-using-rtk-"
+"uavs/3937 (accessed 10 12, 2020)."
+msgstr ""
+
+# 6f51c9cc28e6453ab07e036fa6e37a03
+#: ../../../map-accuracy.rst:82
+msgid ""
+"Pascual, Manuel S. GIS Lounge: GIS Data: A Look at Accuracy, Precision, and "
+"Types of Errors. 11 6, 2011. https://www.gislounge.com/gis-data-a-look-at-"
+"accuracy-precision-and-types-of-errors/ (accessed 07 09, 2020)."
+msgstr ""
+
+# 0bc80ba7d78f4075b5ea484cdbdb767f
+#: ../../../map-accuracy.rst:84
+msgid ""
+"Pix4D. «What is accuracy in an aerial mapping project?» Pix4D. 25 de 05 de "
+"2019. https://www.pix4d.com/blog/accuracy-aerial-mapping (accessed 10 13, "
+"2020)."
+msgstr ""
+
+# ef00360d240e421696b89cd720808a3e
+#: ../../../map-accuracy.rst:87
+msgid ""
+"`Help edit these docs! "
+"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
+msgstr ""