mirror
/
OpenDroneMap-docs
kopia lustrzana https://github.com/OpenDroneMap/docs
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

clean out po files prior to transifex integration

pull/51/head
danbjoseph 2020-07-21 15:12:50 -04:00
rodzic f7ccabfaaa
commit 49101a1557
108 zmienionych plików z 1863 dodań i 22938 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

34
source/locale/ar/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/ar/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/ar/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/ar/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/ar/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/ar/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/ar/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/ar/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/ar/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/ar/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/ar/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/ar/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

30
source/locale/en/arguments.pot 100644
Wyświetl plik

@ -0,0 +1,30 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../arguments.rst:382
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

142
source/locale/en/contributing.pot 100644
Wyświetl plik

@ -0,0 +1,142 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../contributing.rst:6
msgid "OpenDroneMap relies on community contributions. You can contribute in many ways, even if you are not a programmer."
msgstr ""
#: ../../contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../contributing.rst:11
msgid "If you are looking to get involved, are stuck on a problem, or want to reach out, `the forum <https://community.opendronemap.org/>`_ is a great place to start. You may find your questions already answered or else you can find other useful tips and resources. You can also contribute your open access datasets for others to explore. It is a good place go before submitting bug reports or getting in touch with developers before writing a new feature."
msgstr ""
#: ../../contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../contributing.rst:16
msgid "Bugs are tracked as Github issues. Please create an issue in the repository and tag it with the Bug tag."
msgstr ""
#: ../../contributing.rst:18
msgid "Explain the problem and include additional details to help maintainers reproduce the problem:"
msgstr ""
#: ../../contributing.rst:20
msgid "**Use a clear and descriptive title** for the issue to identify the problem."
msgstr ""
#: ../../contributing.rst:21
msgid "**Describe the exact steps which reproduce the problem** in as many details as possible. For example, start by explaining how you run ODM (Docker, Vagrant, etc), e.g. which command exactly you used in the terminal. When listing steps, **don't just say what you did, but explain how you did it.**"
msgstr ""
#: ../../contributing.rst:22
msgid "**Provide specific examples to demonstrate the steps.** Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use `Markdown code blocks <https://help.github.com/articles/markdown-basics/#multiple-lines>`_."
msgstr ""
#: ../../contributing.rst:23
msgid "**Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior."
msgstr ""
#: ../../contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../contributing.rst:25
msgid "**Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use `this tool to record GIFs on macOS and Windows <http://www.cockos.com/licecap/>`_, and `this tool <https://github.com/colinkeenan/silentcast>`_ or `this one <https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../contributing.rst:26
msgid "**If the problem is related to performance,** please post your machine's specs (host and guest machine)."
msgstr ""
#: ../../contributing.rst:27
msgid "**If the problem wasn't triggered by a specific action,** describe what you were doing before the problem happened and share more information using the guidelines below."
msgstr ""
#: ../../contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../contributing.rst:31
msgid "**Which version of ODM are you using?** A stable release? a clone of master?"
msgstr ""
#: ../../contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../contributing.rst:33
msgid "**Are you running ODM in a virtual machine or Docker?** If so, which VM software are you using and which operating systems and versions are used for the host and the guest?"
msgstr ""
#: ../../contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../contributing.rst:71
msgid "Include screenshots and animated GIFs in your pull request whenever possible."
msgstr ""
#: ../../contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../contributing.rst:77
msgid "Use os.tmpdir() rather than /tmp when you need to reference the temporary directory."
msgstr ""
#: ../../contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../contributing.rst:81
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""

54
source/locale/en/flying.pot 100644
Wyświetl plik

@ -0,0 +1,54 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../flying.rst:4
msgid "The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has guidelines on `flying for UAV mapping <https://uav-guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../flying.rst:6
msgid "`Choosing the right UAV <https://uav-guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../flying.rst:8
msgid "`Choosing the right sensor <https://uav-guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../flying.rst:10
msgid "`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../flying.rst:12
msgid "The guidelines are intended for drone mapping projects on islands, but have general use for all drone mappers."
msgstr ""
#: ../../flying.rst:14
msgid "See also DroneDeploy's guide on `Making Successful Maps <https://support.dronedeploy.com/docs/making-successful-maps>`_, which provides great tips on mission planning."
msgstr ""
#: ../../flying.rst:16
msgid "Finally, lens distortion is a challenge in projects requiring accurate 3D data. See our section in these docs on `Camera Calibration <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../flying.rst:18
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""

130
source/locale/en/gcp.pot 100644
Wyświetl plik

@ -0,0 +1,130 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../gcp.rst:5
msgid "Ground control points are useful for correcting distortions in the data and referencing the data to know coordinate systems."
msgstr ""
#: ../../gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../gcp.rst:9
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
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
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../gcp.rst:27
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
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
msgid "Sharp corners are good picks for GCPs. You should also place/find the GCPs evenly around your survey area."
msgstr ""
#: ../../gcp.rst:33
msgid "The ``gcp_list.txt`` file must be created in the base of your project folder."
msgstr ""
#: ../../gcp.rst:35
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
msgid "User Interfaces"
msgstr ""
#: ../../gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../gcp.rst:50
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
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
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
msgid "GCP Editor Pro"
msgstr ""
#: ../../gcp.rst:69
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
msgid "Create a CSV file that includes the gcp name, northing, easting and elevation."
msgstr ""
#: ../../gcp.rst:80
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
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
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

26
source/locale/en/index.pot 100644
Wyświetl plik

@ -0,0 +1,26 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../index.rst:43
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

589
source/locale/en/installation.pot 100644
Wyświetl plik

@ -0,0 +1,589 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../installation.rst:6
msgid "This section is excerpted and modified with permission from `OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero Toffanin."
msgstr ""
#: ../../installation.rst:8
msgid "Until recently OpenDroneMap was the term used to refer to a single command line application (what is now known as the ODM project). With the recent development of a web interface, an API and other tools, OpenDroneMap has become an ecosystem of various applications to process, analyze and display aerial data. This ecosystem is made of several components:"
msgstr ""
#: ../../installation.rst:14
msgid "**ODM** is the processing engine, which can be used from the command line. It takes images as input and produces a variety of outputs, including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../installation.rst:20
msgid "**NodeODM** is a light-weight API built on top of ODM. It allows users and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../installation.rst:26
msgid "**WebODM** is a friendly user interface that includes a map viewer, a 3D viewer, user logins, a plugin system and many other features that are expected of modern drone mapping platforms"
msgstr ""
#: ../../installation.rst:32
msgid "**CloudODM** is a small command line client to communicate with ODM via the NodeODM API"
msgstr ""
#: ../../installation.rst:38
msgid "**PyODM** is a Python SDK for creating tasks via the NodeODM API. We cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../installation.rst:44
msgid "**ClusterODM** is a load balancer for connecting together multiple NodeODM instances"
msgstr ""
#: ../../installation.rst:46
msgid "ODM, NodeODM and WebODM are available on all major platforms (Windows, macOS and Linux) via a program called docker, which is required to run the software. Docker offers a way to run “containers”. Containers are packaged copies of an entire system, its software and its dependencies. These containers run within a virtual environment. On Linux this virtual environment is available from the operating system and is very efficient. On macOS and Windows the containers run within a VM, so there’s a bit of a overhead. but it’s still very suitable for running the software. Once installed users do not have to worry much about docker, as it operates (almost) transparently."
msgstr ""
#: ../../installation.rst:48
msgid "Without docker it would not be possible to run ODM on Windows or macOS. On these platforms ODM cannot run natively. Future development efforts are being focused on leveraging the new Windows Subsystem for Linux (WSL) and the possibility to make a native port of all dependencies to macOS, which is going to make the installation much easier."
msgstr ""
#: ../../installation.rst:50
msgid "On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software natively. However, because there’s very little performance penalty for running docker on Linux and docker is straightforward to setup on this platform, we don’t recommend it. On Linux the advantages of containerization far outweigh a tiny performance penalty. With docker users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../installation.rst:63
msgid "No more than 100-200 images can be processed with the above specifications (the software will run out of memory). Recommended requirements are:"
msgstr ""
#: ../../installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../installation.rst:69
msgid "The above will allow for a few hundred images to be processed without too many issues. A CPU with more cores will allow for faster processing, while a graphics card (GPU) currently has no impact on performance. For processing more images, add more disk space and RAM linearly to the number of images you need to process."
msgstr ""
#: ../../installation.rst:75
msgid "Installation"
msgstr ""
#: ../../installation.rst:77
msgid "We recommend people use `docker <https://www.docker.com>`_ for running ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../installation.rst:80
msgid "Windows"
msgstr ""
#: ../../installation.rst:82
msgid "To run OpenDroneMap you need at least Windows 7. Previous versions of Windows are not supported."
msgstr ""
#: ../../installation.rst:86
#: ../../installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../installation.rst:88
msgid "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."
msgstr ""
#: ../../installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../installation.rst:96
msgid "On Windows 7 to see if you have virtualization enabled you can use the `Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../installation.rst:99
msgid "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”)."
msgstr ""
#: ../../installation.rst:105
msgid "*Common keys to press at computer startup to access the boot menu for various PC vendors*"
msgstr ""
#: ../../installation.rst:108
#: ../../installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../installation.rst:115
msgid "For Python 3, make sure you check **Add Python 3.x to PATH** during the installation."
msgstr ""
#: ../../installation.rst:121
msgid "*Don’t forget to add the Python executable to your PATH (so that you can run commands with it)*"
msgstr ""
#: ../../installation.rst:123
msgid "Then, only if you are on Windows 10 Home, Windows 8 (any version) or Windows 7 (any version), install:"
msgstr ""
#: ../../installation.rst:125
msgid "Docker Toolbox: https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../installation.rst:127
msgid "If you are on Windows 10 Professional or a newer version, you should install instead:"
msgstr ""
#: ../../installation.rst:129
msgid "Docker for Windows: https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../installation.rst:131
msgid "Please do **NOT** install both docker programs. They are different and will create a mess if they are both installed."
msgstr ""
#: ../../installation.rst:133
msgid "After installing docker, launch it from the Desktop icon that is created from the installation (**Docker Quickstart** in the case of Docker Toolbox, **Docker for Windows** for Docker for Windows). This is important, do not skip this step. If there are errors, follow the prompts on screen to fix them."
msgstr ""
#: ../../installation.rst:136
#: ../../installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../installation.rst:138
msgid "Docker on Windows works by running a VM in the background (think of a VM as a “computer emulator”). This VM has a certain amount of memory allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../installation.rst:140
msgid "If you installed Docker Toolbox (see below if you installed Docker for Windows instead):"
msgstr ""
#: ../../installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../installation.rst:143
msgid "Right click the **default** VM and press **Close (ACPI Shutdown)** to stop the machine"
msgstr ""
#: ../../installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../installation.rst:145
msgid "Move the **Base Memory** slider from the **System** paneland allocate 60-70% of all available memory, optionally adding 50% of the available processors from the **Processor** tab also"
msgstr ""
#: ../../installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../installation.rst:159
msgid "From the panel, click **Advanced** and use the sliders to allocate 60-70% of available memory and use half of all available CPUs."
msgstr ""
#: ../../installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../installation.rst:181
msgid "In **Target Directory** click browse and navigate to a folder of your choosing (create one if necessary)"
msgstr ""
#: ../../installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../installation.rst:198
msgid "Go to the **Repository** menu, then click **Create Desktop Icon**. This will allow you to come back to this application easily in the future."
msgstr ""
#: ../../installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../installation.rst:203
msgid "From Git Gui, go to the **Repository** menu, then click **Git Bash**. From the command line terminal type:"
msgstr ""
#: ../../installation.rst:209
msgid "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:"
msgstr ""
#: ../../installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../installation.rst:217
msgid "If you are using Docker for Windows, open a web browser to http://localhost:8000"
msgstr ""
#: ../../installation.rst:218
msgid "If you are using Docker Toolbox, find the IP address to connect to by typing:"
msgstr ""
#: ../../installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../installation.rst:230
msgid "Then connect to http://192.168.1.100:8000 (replacing the IP address with the proper one)."
msgstr ""
#: ../../installation.rst:233
msgid "macOS"
msgstr ""
#: ../../installation.rst:235
msgid "Most modern (post 2010) Mac computers running macOS Sierra 10.12 or higher can run OpenDroneMap using docker, as long as hardware virtualization is supported (see below)."
msgstr ""
#: ../../installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../installation.rst:252
msgid "If the result is *kern.hv_support: 1*, then your Mac is supported! Continue with Step 2."
msgstr ""
#: ../../installation.rst:254
msgid "If the result is *kern.hv_support: 0*, unfortunately it means your Mac is too old to run OpenDroneMap. :("
msgstr ""
#: ../../installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../installation.rst:264
msgid "After installing docker you should find an icon that looks like a whale in the task bar."
msgstr ""
#: ../../installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../installation.rst:272
msgid "You can verify that docker is running properly by opening the **Terminal** app and typing:"
msgstr ""
#: ../../installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../installation.rst:296
msgid "If you get a “bash: git: command not found”, try to restart your **Terminal** app and double-check for any errors during the install process."
msgstr ""
#: ../../installation.rst:301
msgid "Docker on macOS works by running a VM in the background (think of it as a “computer emulator”). This VM has a certain amount of memory allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../installation.rst:305
msgid "Adjust the CPUs slider to use half of all available CPUs and the memory to use 60-70% of all available memory"
msgstr ""
#: ../../installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../installation.rst:325
#: ../../installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../installation.rst:328
msgid "Linux"
msgstr ""
#: ../../installation.rst:330
msgid "OpenDroneMap can run on any Linux distribution that supports docker. According to `docker’s documentation website <https://docs.docker.com/install/>`_ the officially supported distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries available for others. If you have to pick a distribution solely for running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../installation.rst:337
msgid "Docker"
msgstr ""
#: ../../installation.rst:338
msgid "Git"
msgstr ""
#: ../../installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../installation.rst:340
msgid "Pip"
msgstr ""
#: ../../installation.rst:342
msgid "We cannot possibly cover the installation process for every Linux distribution out there, so we’ll limit the instructions to those that are distributions officially supported by docker. In all cases it’s just a matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../installation.rst:347
#: ../../installation.rst:359
#: ../../installation.rst:370
#: ../../installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../installation.rst:390
msgid "In addition to the three programs above, the dockercompose script is also needed. Sometimes it’s already installed with docker, but sometimes it isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../installation.rst:431
msgid "The cool thing about using docker is that 99% of the tasks you’ll ever need to perform while using WebODM can be done via the ./webodm.sh script. You have already encountered one of them:"
msgstr ""
#: ../../installation.rst:437
msgid "which takes care of starting WebODM and setting up a default processing node (node-odm-1). If you want to stop WebODM, you can already guess what the command is:"
msgstr ""
#: ../../installation.rst:443
msgid "There are several other commands you can use, along with different flags. Flags are parameters passed to the ./webodm.sh command and are typically prefixed with “–”. The **port** flag for example instructs WebODM to use a different network port:"
msgstr ""
#: ../../installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../installation.rst:468
msgid "`The community forum <https://community.opendronemap.org>`_ is a great place to ask for help if you get stuck during any of the installation steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../installation.rst:473
msgid "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."
msgstr ""
#: ../../installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../installation.rst:481
msgid "Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" node already configured for you to use. This is a NodeODM node and has been created automatically by WebODM. This node is running on the same machine as WebODM."
msgstr ""
#: ../../installation.rst:483
msgid "If you’ve made it this far, congratulations! Now it’s time to start processing some data."
msgstr ""
#: ../../installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../installation.rst:492
msgid "**Optionally:** If you have another computer, you can repeat the installation process (install docker, git, python, etc.) and launch a new NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../installation.rst:498
msgid "The above command asks docker to launch a new container using the opendronemap/nodeodm image from Docker Hub (the latest version of NodeODM), using port 3000, setting a maximum number of concurrent tasks to 1 and to protect the node from unauthorized access using the password \"secret\"."
msgstr ""
#: ../../installation.rst:500
msgid "From WebODM you can then press the **Add New** button under **Processing Nodes**. For the **hostname/IP** field type the IP of the second computer. For the **port** field type “3000”. For the **token** field type “secret”. You can also add an optional **label** for your node, such as “second computer”. Then press **Save**."
msgstr ""
#: ../../installation.rst:502
msgid "If everything went well, you should now have two processing nodes! You will be able to process multiple tasks in parallel using two different machines."
msgstr ""
#: ../../installation.rst:504
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""

190
source/locale/en/large.pot 100644
Wyświetl plik

@ -0,0 +1,190 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../large.rst:6
msgid "Starting with ODM version ``0.6.0`` you can split up very large datasets into manageable chunks (called submodels), running the pipeline on each chunk, and then producing merged DEMs, orthophotos and point clouds. The process is referred to as \"split-merge\"."
msgstr ""
#: ../../large.rst:8
msgid "Why might you use the split-merge pipeline? If you have a very large number of images in your dataset, split-merge will help make the processing more manageable on a large machine (it will require less memory). If you have many machines all connected to the same network you can also process the submodels in parallel, thus allowing for horizontal scaling and processing thousands of images more quickly."
msgstr ""
#: ../../large.rst:10
msgid "Split-merge works in WebODM out of the box as long as the processing nodes support split-merge, by enabling the ``--split`` option when creating a new task."
msgstr ""
#: ../../large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../large.rst:15
msgid "Image calibration is recommended (but not required) for large datasets because error propagation due to image distortion could cause a bowl effect on the models. Calibration instructions can be found at `Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../large.rst:21
msgid "Bowling effect on point cloud over 13,000+ image dataset collected by World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, Tanzania."
msgstr ""
#: ../../large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../large.rst:26
msgid "Splitting a dataset into more manageable submodels and sequentially processing all submodels on the same machine is easy! Just use ``--split`` and ``--split-overlap`` to decide the the average number of images per submodels and the overlap (in meters) between submodels respectively"
msgstr ""
#: ../../large.rst:32
msgid "If you already know how you want to split the dataset, you can provide that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../large.rst:34
msgid "The grouping can be provided by adding a file named image_groups.txt in the main dataset folder. The file should have one line per image. Each line should have two words: first the name of the image and second the name of the group it belongs to. For example::"
msgstr ""
#: ../../large.rst:42
msgid "will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../large.rst:48
msgid "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>`_."
msgstr ""
#: ../../large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../large.rst:63
msgid "Then on each machine you want to use for processing, launch a NodeODM instance via"
msgstr ""
#: ../../large.rst:69
msgid "Connect via telnet to ClusterODM and add the IP addresses/port of the machines running NodeODM"
msgstr ""
#: ../../large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../large.rst:86
msgid "At this point, simply use the ``--sm-cluster`` option to enable distributed split-merge"
msgstr ""
#: ../../large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../large.rst:95
msgid "When connected via telnet, it is possible to interrogate what is happening on the cluster. For example, we can use the command HELP to find out available commands"
msgstr ""
#: ../../large.rst:118
msgid "If, for example, the NodeODM instance wasn't active when ClusterODM started, we might list nodes and see something as follows"
msgstr ""
#: ../../large.rst:125
msgid "To address this, we can start up our local node (if not already started), and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../large.rst:137
msgid "While a process is running, it is also possible to list the tasks, and view the task output"
msgstr ""
#: ../../large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../large.rst:147
msgid "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."
msgstr ""
#: ../../large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../large.rst:161
msgid "Create a configuration file for `DigitalOcean <https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_ or `Amazon Web Services <https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../large.rst:177
msgid "You should always have at least one static NodeODM node attached to ClusterODM, even if you plan to use the autoscaler for all processing. If you setup auto scaling, you can't have zero nodes and rely 100% on the autoscaler. You need to attach a NodeODM node to act as the \"reference node\" otherwise ClusterODM will not know how to handle certain requests (for the forwarding the UI, for validating options prior to spinning up an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM node and lock it"
msgstr ""
#: ../../large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../large.rst:190
msgid "Limitations"
msgstr ""
#: ../../large.rst:192
msgid "The 3D textured meshes are currently not being merged as part of the workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../large.rst:194
msgid "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."
msgstr ""
#: ../../large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../large.rst:198
msgid "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."
msgstr ""
#: ../../large.rst:200
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

58
source/locale/en/multispectral.pot 100644
Wyświetl plik

@ -0,0 +1,58 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:09-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"
#: ../../multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../multispectral.rst:4
msgid "Since version 0.9.9 ODM has basic support for radiometric normalization, which is able to generate reflectance orthophotos from multispectral cameras. Multispectral cameras capture multiple shots of the scene using different band sensors."
msgstr ""
#: ../../multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../multispectral.rst:9
msgid "While we aim to support as many cameras as possible, multispectral support has been developed using the following cameras, so they will work better:"
msgstr ""
#: ../../multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../multispectral.rst:14
msgid "Other cameras might also work. You can help us expand this list by `sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ captured with other cameras."
msgstr ""
#: ../../multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../multispectral.rst:19
msgid "Process all the images from all bands at once (do not separate the bands into multiple folders) and pass the `--radiometric-calibration` parameter to enable radiometric normalization. If the images are part of a multi-camera setup, the resulting orthophoto will have N bands, one for each camera (+ alpha)."
msgstr ""
#: ../../multispectral.rst:25
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

102
source/locale/en/outputs.pot 100644
Wyświetl plik

@ -0,0 +1,102 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../outputs.rst:9
msgid "``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The georeferenced point cloud in different file formats"
msgstr ""
#: ../../outputs.rst:15
msgid "*Point cloud over State University Zanzibar, courtesy of* `Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-56b4044a/>`_"
msgstr ""
#: ../../outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../outputs.rst:21
msgid "``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh ``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and textured surface mesh"
msgstr ""
#: ../../outputs.rst:24
msgid "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``"
msgstr ""
#: ../../outputs.rst:30
msgid "*Textured mesh courtesy of* `OpenDroneMap <https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../outputs.rst:35
msgid "``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../outputs.rst:37
msgid "``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use it in QGIS as a raster layer."
msgstr ""
#: ../../outputs.rst:43
msgid "*Orthophoto over State University Zanzibar, courtesy of* `Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-56b4044a/>`_"
msgstr ""
#: ../../outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../outputs.rst:48
msgid "DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are used. See `tutorial on elevation models <https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-models>`_ for more options in creating."
msgstr ""
#: ../../outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../outputs.rst:59
msgid "*Digital surface model over State University Zanzibar, courtesy of* `Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-56b4044a/>`_"
msgstr ""
#: ../../outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../outputs.rst:109
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""

58
source/locale/en/requesting-features.pot 100644
Wyświetl plik

@ -0,0 +1,58 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../requesting-features.rst:4
msgid "All software needs user feedback and feature requests, to grow and maintain alignment with the needs of its users."
msgstr ""
#: ../../requesting-features.rst:7
msgid "OpenDroneMap is FOSS software. Free and open source (FOSS) projects are interesting from the inside and outside: from the outside, successful ones feel like they should be able to do anything, and it’s hard to know what a reasonable request is. From the inside of a project, they can feel very resource constrained: largely by time, money, and opportunity overload."
msgstr ""
#: ../../requesting-features.rst:13
msgid "A feature request can be submitted as issues on the applicable Github repository (e.g., `WebODM <https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM <https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply as a discussion topic on `the community forum <https://community.opendronemap.org/>`_. Try to start by searching these sources to see if someone else has already brought it up. Sometimes a feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../requesting-features.rst:19
msgid "And importantly, the trick is to listen: if someone within the project says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE IT\" (or possibly a combination of the three) then there are two answers that work really well in response:"
msgstr ""
#: ../../requesting-features.rst:23
msgid "*Ok. I didn’t know it was a big feature request! I hope someone comes along with the necessary resources. As a community member, I would be happy to be an early user and tester!*"
msgstr ""
#: ../../requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../requesting-features.rst:27
msgid "*Let’s figure out if we can put together the resources to get this done! Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../requesting-features.rst:29
msgid "We are glad you are excited to see new features added to the project. Some new features need support, and some are easier to implement. We'll do our best to help you understand where your request falls, and we appreciate any support you can provide."
msgstr ""
#: ../../requesting-features.rst:33
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-features.rst>`_"
msgstr ""

78
source/locale/en/resources.pot 100644
Wyświetl plik

@ -0,0 +1,78 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../resources.rst:5
msgid "For Users"
msgstr ""
#: ../../resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../resources.rst:11
msgid "`README page for NodeODM <https://github.com/OpenDroneMap/node-OpenDroneMap>`_"
msgstr ""
#: ../../resources.rst:12
msgid "`Ground Control Points Format Specification <https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../resources.rst:21
msgid "NodeODM API specification: https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../resources.rst:22
msgid "Overview of the ODM pipeline: http://community.opendronemap.org/t/where-can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../resources.rst:23
msgid "We keep a `section in our forum dedicated to research papers <http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. This is a valuable place where to read more about state of the art research related to structure from motion, multi-view stereo, meshing, texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../resources.rst:26
msgid "`Help edit these docs! <https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

406
source/locale/en/tutorials.pot 100644
Wyświetl plik

@ -0,0 +1,406 @@
# 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 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-21 15:08-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"
#: ../../tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../tutorials.rst:17
msgid "Without any parameter tweaks, ODM chooses a good compromise between quality, speed and memory usage. If you want to get higher quality results, you need to tweak some parameters:"
msgstr ""
#: ../../tutorials.rst:19
msgid "``--orthophoto-resolution`` is the resolution of the orthophoto in cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../tutorials.rst:20
msgid "``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and speed optimizations that directly affect the orthophoto. Using this flag will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../tutorials.rst:21
msgid "``--texturing-nadir-weight`` should be increased to ``29-32`` in urban areas to reconstruct better edges of roofs. It should be decreased to ``0-6`` in grassy / flat areas."
msgstr ""
#: ../../tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../tutorials.rst:23
msgid "``--mesh-size`` should be increased to `300000-600000` and `--mesh-octree-depth`` should be increased to `10-11` in urban areas to recreate better buildings / roofs."
msgstr ""
#: ../../tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../tutorials.rst:29
msgid "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."
msgstr ""
#: ../../tutorials.rst:35
msgid "*Bowling effect on point cloud over 13,000+ image dataset collected by World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, Tanzania.*"
msgstr ""
#: ../../tutorials.rst:37
msgid "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°."
msgstr ""
#: ../../tutorials.rst:45
msgid "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."
msgstr ""
#: ../../tutorials.rst:47
msgid "Alternatively, the following experimental method can be applied: fly with much lower overlap, but two *crossgrid* flights (sometimes called crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../tutorials.rst:49
msgid "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."
msgstr ""
#: ../../tutorials.rst:50
msgid "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."
msgstr ""
#: ../../tutorials.rst:56
msgid "Vertically separated flight lines also improve accuracy, but less so than a camera that is forward facing by 5°."
msgstr ""
#: ../../tutorials.rst:62
msgid "From James and Robson (2014), `CC BY 4.0 <https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../tutorials.rst:68
msgid "By default ODM does not create 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."
msgstr ""
#: ../../tutorials.rst:74
msgid "For DTM generation, a Simple Morphological Filter (smrf) is used to classify points in ground vs. non-ground and only the ground points are used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../tutorials.rst:76
msgid "``--smrf-scalar`` scaling value. Increase this parameter for terrains with lots of height variation."
msgstr ""
#: ../../tutorials.rst:77
msgid "``--smrf-slope`` slope parameter, which is a measure of \"slope tolerance\". Increase this parameter for terrains with lots of height variation. Should be set to something higher than 0.1 and not higher than 1.2."
msgstr ""
#: ../../tutorials.rst:78
msgid "``--smrf-threshold`` elevation threshold. Set this parameter to the minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../tutorials.rst:79
msgid "``--smrf-window`` window radius parameter (in meters) that corresponds to the size of the largest feature (building, trees, etc.) to be removed. Should be set to a value higher than 10."
msgstr ""
#: ../../tutorials.rst:81
msgid "Changing these options can affect the result of DTMs significantly. The best source to read to understand how the parameters affect the output is to read the original paper `An improved simple morphological filter for the terrain classification of airborne LIDAR data <https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_ (PDF freely available)."
msgstr ""
#: ../../tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../tutorials.rst:85
msgid "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."
msgstr ""
#: ../../tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../tutorials.rst:93
msgid "``--dem-resolution`` which sets the output resolution of the DEM raster (cm/pixel)"
msgstr ""
#: ../../tutorials.rst:94
msgid "``--dem-gapfill-steps`` which determines the number of progressive DEM layers to use. For urban scenes increasing this value to `4-5` can help produce better interpolation results in the areas that are left empty by the SMRF filter."
msgstr ""
#: ../../tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../tutorials.rst:104
msgid "Since many users employ docker to deploy OpenDroneMap, it can be useful to understand some basic commands in order to interrogate the docker instances when things go wrong, or we are curious about what is happening. Docker is a containerized environment intended, among other things, to make it easier to deploy software independent of the local environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../tutorials.rst:111
msgid "We can start by listing available docker machines on the current machine we are running as follows:"
msgstr ""
#: ../../tutorials.rst:120
msgid "If we want to see machines that may not be running but still exist, we can add the `-a` flag:"
msgstr ""
#: ../../tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../tutorials.rst:135
msgid "Using either the `CONTAINER ID` or the name, we can access any logs available on the machine as follows:"
msgstr ""
#: ../../tutorials.rst:141
msgid "This is likely to be unwieldy large, but we can use a pipe `|` character and other tools to extract just what we need from the logs. For example we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../tutorials.rst:157
msgid "Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys will now help us navigate through the logs. The lower case letter `Q` will let us escape back to the command line."
msgstr ""
#: ../../tutorials.rst:159
msgid "We can also extract just the end of the logs using the `tail` commmand as follows:"
msgstr ""
#: ../../tutorials.rst:170
msgid "The value `-5` tells the tail command to give us just the last 5 lines of the logs."
msgstr ""
#: ../../tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../tutorials.rst:175
msgid "Sometimes we need to go a little deeper in our exploration of the process for OpenDroneMap. For this, we can get direct command line access to the machines. For this, we can use `docker exec` to execute a `bash` command line shell in the machine of interest as follows:"
msgstr ""
#: ../../tutorials.rst:179
msgid "::"
msgstr ""
#: ../../tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../tutorials.rst:186
msgid "Docker has a lamentable use of space and by default does not clean up excess data and machines when processes are complete. This can be advantageous if we need to access a process that has since terminated, but carries the burden of using increasing amounts of storage over time. Maciej Łebkowski has an `excellent overview of how to manage excess disk usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../tutorials.rst:197
msgid "`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be effectively set up locally—it takes a fairly powerful machine to process large datasets—so a cloud machine can sometimes be the answer for people in the field. However, bandwidth is a problem in many low-income settings. This constraint can’t be solved completely, but the following method does a reasonable job of reducing the bandwidth needed to process drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../tutorials.rst:205
msgid "Here we present a tricky but workable process to create an OpenDroneMap cloud machine (*not* CloudODM, mind you, just a cloud-based instance of ODM that you run from the command line) and use it to remotely process large photo sets. It requires familiarity with Unix command line use, ssh, a Digital Ocean account (Amazon AWS would work as well, possibly with slight differences in the setup), and a moderate level of general computer literacy. If you aren’t fairly computer-savvy and willing to fuss with a slightly tricky setup, `CloudODM <https://www.opendronemap.org/cloudodm/>`__ is what you should be looking at."
msgstr ""
#: ../../tutorials.rst:216
msgid "The whole process is mostly targeted at someone flying substantial missions in an African or similar location looking to process data ASAP while still in a field setting. Therefore it emphasizes a workflow intended to reduce bandwidth/data transfer, rather than just the simplest way of running ODM."
msgstr ""
#: ../../tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../tutorials.rst:228
msgid "Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost about $20/month. Less than 4GB of RAM and the install will probably fail. When we actually run the ODM process we’ll resize it to a much larger—and more expensive—cloud machine, but between runs you can downsize it between runs to the second-cheapest droplet which costs only $10/month (the cheapest droplet, at $5/month, comes with such a small drive that you can’t downsize back to it)."
msgstr ""
#: ../../tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../tutorials.rst:238
msgid "Create a user with sudo privileges. `Digital Ocean’s insanely good documentation <https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our case we set up a user called ``odm``, so connecting to it is via the command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 address of your server). If you want to follow this example closely, *do* use the username ``odm``; then your install path will be ``/home/odm/ODM/`` and will match all of the examples in this document. -When you log into the server, it will offer you the option to upgrade to Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and ``sudo apt upgrade`` to ensure your server isn’t dangerously without updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../tutorials.rst:253
msgid "Download and install ODM on it from the `ODM Github <https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the following commands:"
msgstr ""
#: ../../tutorials.rst:263
msgid "If you do this from the default home folder of your user (i.e. ``odm``) the path to the install will be ``/home/odm/ODM`` (abbreviated as ``~/ODM/``)."
msgstr ""
#: ../../tutorials.rst:266
msgid "There are some environmental variables that need to be set. Open the ~/.bashrc file on your machine and add the following 3 lines at the end (From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file can be opened with ``nano ~/.bashrc`` (or whatever text editor you use in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path to the location where you extracted OpenDroneMap if you didn’t do everything exactly as in our example (for example if you used a different username in your server setup):"
msgstr ""
#: ../../tutorials.rst:281
msgid "Note that the ODM github readme contains a slight error, the install directory name will be ODM, not OpenDroneMap (you’ll see this if you compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../tutorials.rst:285
msgid "In order to prevent a crash wherein the split-merge process fails to locate its own executable, we add the following lines to ``~/.bashrc`` (adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../tutorials.rst:295
msgid "Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean jargon) big enough to manage your project. Rule of thumb seems to be 10 times the size of your raw image set; we’ve got a 100GB image set and set up a 1000GB volume (once the run is done you should be able to get rid of most of this expensive drive capacity, but it’s needed to complete the process). Set up the volume, attach it to your droplet, and `configure its mount point <https://www.digitalocean.com/docs/volumes/how-to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../tutorials.rst:308
msgid "Now push your images onto the server. You can use `Secure Copy (scp) <https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r /path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../tutorials.rst:312
msgid "This pushes the entire folder full of images (that’s what the ``-r`` option does, “recursive”) into the remote location (in our example, into the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../tutorials.rst:316
msgid "This will take some bandwidth. No way around the size of the files.\\ `1 <#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../tutorials.rst:322
msgid "ODM requires the directories on the machine to be set up just so. The critical bits are the install folder (if you installed as above, it’s ``/home/odm/ODM/``) and the project folder (i.e. ``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../tutorials.rst:327
msgid "ODM’s settings.yaml file specifies a single parent directory containing all projects. This is what goes in the project path line of the settings.yaml file (slightly confusingly, this is actually the *parent* directory of the individual project directories, which are specified by the project name parameter when calling ODM). Edit settings.yaml and set the project_path parameter to (as per our example setup) ``/mnt/odmdata/``, which in this case points to the Volume we created. Individual project directories are created within that."
msgstr ""
#: ../../tutorials.rst:336
msgid "Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain the gcp_list.txt file, the image_groups.txt file, and the images folder for each project``\\`"
msgstr ""
#: ../../tutorials.rst:339
msgid "The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all of the images. If you set it up like this, the images don’t get re-copied because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../tutorials.rst:343
msgid "If you’ve got images with GPS info on them (as from an Ebee), use exiftool to massage the GPS information ``exiftool \"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll need to install exiftool. The command for that is probably ``sudo apt install libimage-exiftool-perl``."
msgstr ""
#: ../../tutorials.rst:348
msgid "Modify settings.yaml to specify the parent directory of the project folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure the images are in the correct spot, i.e. ``/mnt/odmdata/myproject/images`` and the other ancillary files (gcp_list.txt and image_groups.txt) are in the root folder ``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../tutorials.rst:354
msgid "if you have the images in separate folders for individual AOI blocks or flights (which you will if your flight management was organized), you can create an image_groups.txt file with the incantations ``for i in *; do cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> image_groups.txt; done;``. That should create a file with the correct structure: a list of all image files and a “group name” after each one (which in this case will simply be the name of the folder it came from). Then move all of the image files into a single directory called images in the project root dir (so ``/mnt/odmdata/myproject/images/``). The image_groups.txt file will allow ODM to keep track of which images belong to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../tutorials.rst:372
msgid "Shut down and resize your machine to an appropriately monstrous number of CPUs and amount of memory. I use the memory-optimized machine with 24 dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds up fast, it’s over $1000/month). Restart, and get to work quickly so as not to waste expensive big-droplet time."
msgstr ""
#: ../../tutorials.rst:377
msgid "Launch the ODM process via ssh using nohup (so that if you’re cut off, processing will continue)"
msgstr ""
#: ../../tutorials.rst:380
msgid "Alternately you can use GNU screen to launch the process from a screen session which won’t stop if your connection is interrupted; launch ``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-attach. But using screen won’t get you a log file of all of the console output unless you do something specific to capture that, while nohup gives you a file with all of the console output, including error messages, for free."
msgstr ""
#: ../../tutorials.rst:387
msgid "Note: as of 2020-03 the normal incantation ``python run.py -i /path/to/image/folder project_name`` seems *not* to work; the ``-i`` or ``--image`` parameter causes a weird error. So we drop the -i parameter, and rely on the project directory line in the settings.yaml file to direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../tutorials.rst:398
msgid "This points ODM at the folder (in this example) ``/mnt/odmdata/myproject/``. Provided the image_groups.txt and gcp_list.txt are in this folder, the images are in ``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../tutorials.rst:405
msgid "Note that this assumes you have an image_groups.txt file. If not, this ``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` is literally a random number that will be ignored after the image_groups.txt file is loaded (I think it normally controls how many groups it splits a set of images into, but in our case we’re assuming the images are already grouped sensibly). If you don’t have a large dataset (>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../tutorials.rst:420
msgid "You may want to keep an eye on htop (to get a sense of the resource usage so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../tutorials.rst:427
msgid "As soon as processing is done, shut down the machine and resize it back down to the inexpensive minimum capacity."
msgstr ""
#: ../../tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../tutorials.rst:430
msgid "If you want to save download bandwidth, you can compress the orthophoto using GDAL. Don’t add overviews, do that on your local machine to avoid making the file bigger before downloading it."
msgstr ""
#: ../../tutorials.rst:438
msgid "Download using scp: ``scp odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif`` (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../tutorials.rst:442
msgid "Once you get the file on your local computer, you can use QGIS to add overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average /path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../tutorials.rst:446
msgid "You can archive the odm_texturing, odm_georeferencing, and odm-dem folders using tar to make them easier to download in one piece (and maybe smaller)."
msgstr ""

34
source/locale/es/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/es/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/es/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/es/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/es/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/es/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/es/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/es/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/es/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/es/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/es/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/es/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/fr/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/fr/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/fr/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/fr/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/fr/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/fr/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/fr/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/fr/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/fr/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/fr/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/fr/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/fr/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/it/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/it/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/it/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/it/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/it/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/it/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/it/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/it/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/it/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/it/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/it/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/it/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/ja/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/ja/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/ja/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/ja/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/ja/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/ja/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/ja/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/ja/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/ja/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/ja/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/ja/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/ja/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/ko/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/ko/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/ko/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/ko/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/ko/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/ko/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/ko/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/ko/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/ko/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/ko/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/ko/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/ko/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/nl/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr ""
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr ""
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr ""

196
source/locale/nl/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,196 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr ""
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr ""
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr ""
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr ""
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr ""
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr ""
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr ""
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr ""
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr ""
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr ""
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr ""
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr ""
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr ""
#: ../../source/contributing.rst:81
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
#~ msgid "How to contribute"
#~ msgstr ""

78
source/locale/nl/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,78 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr ""
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
#~ msgid "Flying tips"
#~ msgstr ""

181
source/locale/nl/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,181 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr ""
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr ""
#: ../../source/gcp.rst:9
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 ""
#: ../../source/gcp.rst:10
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 ""
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr ""
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr ""
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr ""
#: ../../source/gcp.rst:27
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 ""
#: ../../source/gcp.rst:29
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 ""
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
#: ../../source/gcp.rst:35
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 ""
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr ""
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr ""
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr ""
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr ""
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr ""
#: ../../source/gcp.rst:50
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 ""
#: ../../source/gcp.rst:52
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 ""
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr ""
#: ../../source/gcp.rst:69
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 ""
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
#: ../../source/gcp.rst:80
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 ""
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""

30
source/locale/nl/LC_MESSAGES/index.po
Wyświetl plik

@ -1,30 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/index.rst:8
msgid "Welcome to OpenDroneMap's documentation"
msgstr ""
#: ../../source/index.rst:40
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/index.rst>`_"
msgstr ""

785
source/locale/nl/LC_MESSAGES/installation.po
Wyświetl plik

@ -1,785 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/installation.rst:4
msgid "Installation and Getting Started"
msgstr ""
#: ../../source/installation.rst:6
msgid ""
"This section is excerpted and modified with permission from "
"`OpenDroneMap: The Missing Guide <https://odmbook.com>`_, by Piero "
"Toffanin."
msgstr ""
#: ../../source/installation.rst:8
msgid ""
"Until recently OpenDroneMap was the term used to refer to a single "
"command line application (what is now known as the ODM project). With "
"the recent development of a web interface, an API and other tools, "
"OpenDroneMap has become an ecosystem of various applications to process, "
"analyze and display aerial data. This ecosystem is made of several "
"components:"
msgstr ""
#: ../../source/installation.rst:14
msgid ""
"**ODM** is the processing engine, which can be used from the command "
"line. It takes images as input and produces a variety of outputs, "
"including point clouds, 3D models and orthophotos"
msgstr ""
#: ../../source/installation.rst:20
msgid ""
"**NodeODM** is a light-weight API built on top of ODM. It allows users "
"and applications to access the functions of ODM over a computer network"
msgstr ""
#: ../../source/installation.rst:26
msgid ""
"**WebODM** is a friendly user interface that includes a map viewer, a 3D "
"viewer, user logins, a plugin system and many other features that are "
"expected of modern drone mapping platforms"
msgstr ""
#: ../../source/installation.rst:32
msgid ""
"**CloudODM** is a small command line client to communicate with ODM via "
"the NodeODM API"
msgstr ""
#: ../../source/installation.rst:38
msgid ""
"**PyODM** is a Python SDK for creating tasks via the NodeODM API. We "
"cover it in more detail in the “Automated Processing With Python” chapter"
msgstr ""
#: ../../source/installation.rst:44
msgid ""
"**ClusterODM** is a load balancer for connecting together multiple "
"NodeODM instances"
msgstr ""
#: ../../source/installation.rst:46
msgid ""
"ODM, NodeODM and WebODM are available on all major platforms (Windows, "
"macOS and Linux) via a program called docker, which is required to run "
"the software. Docker offers a way to run “containers”. Containers are "
"packaged copies of an entire system, its software and its dependencies. "
"These containers run within a virtual environment. On Linux this virtual "
"environment is available from the operating system and is very efficient."
" On macOS and Windows the containers run within a VM, so there’s a bit of"
" a overhead. but it’s still very suitable for running the software. Once "
"installed users do not have to worry much about docker, as it operates "
"(almost) transparently."
msgstr ""
#: ../../source/installation.rst:48
msgid ""
"Without docker it would not be possible to run ODM on Windows or macOS. "
"On these platforms ODM cannot run natively. Future development efforts "
"are being focused on leveraging the new Windows Subsystem for Linux (WSL)"
" and the possibility to make a native port of all dependencies to macOS, "
"which is going to make the installation much easier."
msgstr ""
#: ../../source/installation.rst:50
msgid ""
"On Ubuntu Linux 16.04 it’s feasible to run all OpenDroneMap software "
"natively. However, because there’s very little performance penalty for "
"running docker on Linux and docker is straightforward to setup on this "
"platform, we don’t recommend it. On Linux the advantages of "
"containerization far outweigh a tiny performance penalty. With docker "
"users also get easy one-step updates of the software, so that’s nice."
msgstr ""
#: ../../source/installation.rst:54
msgid "Hardware Recommendations"
msgstr ""
#: ../../source/installation.rst:56
msgid "The bare minimum requirements for running the software are:"
msgstr ""
#: ../../source/installation.rst:59
msgid "64bit CPU manufactured on or after 2010"
msgstr ""
#: ../../source/installation.rst:60
msgid "20 GB of disk space"
msgstr ""
#: ../../source/installation.rst:61
msgid "4 GB RAM"
msgstr ""
#: ../../source/installation.rst:63
msgid ""
"No more than 100-200 images can be processed with the above "
"specifications (the software will run out of memory). Recommended "
"requirements are:"
msgstr ""
#: ../../source/installation.rst:65
msgid "Latest Generation CPU"
msgstr ""
#: ../../source/installation.rst:66
msgid "100 GB of disk space"
msgstr ""
#: ../../source/installation.rst:67
msgid "16 GB RAM"
msgstr ""
#: ../../source/installation.rst:69
msgid ""
"The above will allow for a few hundred images to be processed without too"
" many issues. A CPU with more cores will allow for faster processing, "
"while a graphics card (GPU) currently has no impact on performance. For "
"processing more images, add more disk space and RAM linearly to the "
"number of images you need to process."
msgstr ""
#: ../../source/installation.rst:75
msgid "Installation"
msgstr ""
#: ../../source/installation.rst:77
msgid ""
"We recommend people use `docker <https://www.docker.com>`_ for running "
"ODM, whether you are on Windows, macOS or Linux."
msgstr ""
#: ../../source/installation.rst:80
msgid "Windows"
msgstr ""
#: ../../source/installation.rst:82
msgid ""
"To run OpenDroneMap you need at least Windows 7. Previous versions of "
"Windows are not supported."
msgstr ""
#: ../../source/installation.rst:86 ../../source/installation.rst:238
msgid "Step 1. Check Virtualization Support"
msgstr ""
#: ../../source/installation.rst:88
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:94
msgid "*Virtualization should be enabled*"
msgstr ""
#: ../../source/installation.rst:96
msgid ""
"On Windows 7 to see if you have virtualization enabled you can use the "
"`Microsoft® Hardware-Assisted Virtualization Detection Tool <http:// "
"www.microsoft.com/en-us/download/details.aspx?id=592>`_ instead."
msgstr ""
#: ../../source/installation.rst:99
msgid ""
"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”)."
msgstr ""
#: ../../source/installation.rst:105
msgid ""
"*Common keys to press at computer startup to access the boot menu for "
"various PC vendors*"
msgstr ""
#: ../../source/installation.rst:108 ../../source/installation.rst:257
msgid "Step 2. Install Requirements"
msgstr ""
#: ../../source/installation.rst:110
msgid "First, you’ll need to install:"
msgstr ""
#: ../../source/installation.rst:112
msgid "Git: https://git-scm.com/downloads"
msgstr ""
#: ../../source/installation.rst:113
msgid "Python (latest version 3): https://www.python.org/downloads/windows/"
msgstr ""
#: ../../source/installation.rst:115
msgid ""
"For Python 3, make sure you check **Add Python 3.x to PATH** during the "
"installation."
msgstr ""
#: ../../source/installation.rst:121
msgid ""
"*Don’t forget to add the Python executable to your PATH (so that you can "
"run commands with it)*"
msgstr ""
#: ../../source/installation.rst:123
msgid ""
"Then, only if you are on Windows 10 Home, Windows 8 (any version) or "
"Windows 7 (any version), install:"
msgstr ""
#: ../../source/installation.rst:125
msgid ""
"Docker Toolbox: "
"https://github.com/docker/toolbox/releases/download/v18.09.3/DockerToolbox-18.09.3.exe"
msgstr ""
#: ../../source/installation.rst:127
msgid ""
"If you are on Windows 10 Professional or a newer version, you should "
"install instead:"
msgstr ""
#: ../../source/installation.rst:129
#, python-format
msgid ""
"Docker for Windows: "
"https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe"
msgstr ""
#: ../../source/installation.rst:131
msgid ""
"Please do **NOT** install both docker programs. They are different and "
"will create a mess if they are both installed."
msgstr ""
#: ../../source/installation.rst:133
msgid ""
"After installing docker, launch it from the Desktop icon that is created "
"from the installation (**Docker Quickstart** in the case of Docker "
"Toolbox, **Docker for Windows** for Docker for Windows). This is "
"important, do not skip this step. If there are errors, follow the prompts"
" on screen to fix them."
msgstr ""
#: ../../source/installation.rst:136 ../../source/installation.rst:299
msgid "Step 3. Check Memory and CPU Allocation"
msgstr ""
#: ../../source/installation.rst:138
msgid ""
"Docker on Windows works by running a VM in the background (think of a VM "
"as a “computer emulator”). This VM has a certain amount of memory "
"allocated and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:140
msgid ""
"If you installed Docker Toolbox (see below if you installed Docker for "
"Windows instead):"
msgstr ""
#: ../../source/installation.rst:142
msgid "Open the **VirtualBox Manager** application"
msgstr ""
#: ../../source/installation.rst:143
msgid ""
"Right click the **default** VM and press **Close (ACPI Shutdown)** to "
"stop the machine"
msgstr ""
#: ../../source/installation.rst:144
msgid "Right click the **default** VM and press **Settings...**"
msgstr ""
#: ../../source/installation.rst:145
#, python-format
msgid ""
"Move the **Base Memory** slider from the **System** paneland allocate "
"60-70% of all available memory, optionally adding 50% of the available "
"processors from the **Processor** tab also"
msgstr ""
#: ../../source/installation.rst:151
msgid "*VirtualBox default VM settings*"
msgstr ""
#: ../../source/installation.rst:153
msgid "Then press **OK**, right click the **default** VM and press **Start**."
msgstr ""
#: ../../source/installation.rst:155
msgid "If you installed Docker for Windows instead:"
msgstr ""
#: ../../source/installation.rst:157
msgid "Look in the system tray and right click the “white whale” icon."
msgstr ""
#: ../../source/installation.rst:158
msgid "From the menu, press **Settings...**"
msgstr ""
#: ../../source/installation.rst:159
#, python-format
msgid ""
"From the panel, click **Advanced** and use the sliders to allocate 60-70%"
" of available memory and use half of all available CPUs."
msgstr ""
#: ../../source/installation.rst:160
msgid "Press **Apply**."
msgstr ""
#: ../../source/installation.rst:166
msgid "*Step 1 Docker icon*"
msgstr ""
#: ../../source/installation.rst:172
msgid "*Step 3 & 4 Docker settings*"
msgstr ""
#: ../../source/installation.rst:175
msgid "Step 4. Download WebODM"
msgstr ""
#: ../../source/installation.rst:177
msgid "Open the **Git Gui** program that comes installed with Git. From there:"
msgstr ""
#: ../../source/installation.rst:179
msgid "When Git Gui opens, click 'Clone Existing Repository' option"
msgstr ""
#: ../../source/installation.rst:180
msgid "In **Source Location** type: https://github.com/OpenDroneMap/WebODM"
msgstr ""
#: ../../source/installation.rst:181
msgid ""
"In **Target Directory** click browse and navigate to a folder of your "
"choosing (create one if necessary)"
msgstr ""
#: ../../source/installation.rst:182
msgid "Press **Clone**"
msgstr ""
#: ../../source/installation.rst:188
msgid "*Git Gui*"
msgstr ""
#: ../../source/installation.rst:190
msgid "If the download succeeded, you should now see this window:"
msgstr ""
#: ../../source/installation.rst:196
msgid "*Git Gui after successful download (clone)*"
msgstr ""
#: ../../source/installation.rst:198
msgid ""
"Go to the **Repository** menu, then click **Create Desktop Icon**. This "
"will allow you to come back to this application easily in the future."
msgstr ""
#: ../../source/installation.rst:201
msgid "Step 4. Launch WebODM"
msgstr ""
#: ../../source/installation.rst:203
msgid ""
"From Git Gui, go to the **Repository** menu, then click **Git Bash**. "
"From the command line terminal type:"
msgstr ""
#: ../../source/installation.rst:209
msgid ""
"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:"
msgstr ""
#: ../../source/installation.rst:215
msgid "*Console output after starting WebODM for the first time*"
msgstr ""
#: ../../source/installation.rst:217
msgid ""
"If you are using Docker for Windows, open a web browser to "
"http://localhost:8000"
msgstr ""
#: ../../source/installation.rst:218
msgid ""
"If you are using Docker Toolbox, find the IP address to connect to by "
"typing:"
msgstr ""
#: ../../source/installation.rst:224
msgid "You should get a result like the following:"
msgstr ""
#: ../../source/installation.rst:230
msgid ""
"Then connect to http://192.168.1.100:8000 (replacing the IP address with "
"the proper one)."
msgstr ""
#: ../../source/installation.rst:233
msgid "macOS"
msgstr ""
#: ../../source/installation.rst:235
msgid ""
"Most modern (post 2010) Mac computers running macOS Sierra 10.12 or "
"higher can run OpenDroneMap using docker, as long as hardware "
"virtualization is supported (see below)."
msgstr ""
#: ../../source/installation.rst:240
msgid "Open a Terminal window and type:"
msgstr ""
#: ../../source/installation.rst:246
msgid "You will get a response similar to the following:"
msgstr ""
#: ../../source/installation.rst:252
msgid ""
"If the result is *kern.hv_support: 1*, then your Mac is supported! "
"Continue with Step 2."
msgstr ""
#: ../../source/installation.rst:254
msgid ""
"If the result is *kern.hv_support: 0*, unfortunately it means your Mac is"
" too old to run OpenDroneMap. :("
msgstr ""
#: ../../source/installation.rst:259
msgid "There are only two programs to install:"
msgstr ""
#: ../../source/installation.rst:261
msgid "Docker: https://download.docker.com/mac/stable/Docker.dmg"
msgstr ""
#: ../../source/installation.rst:262
msgid "Git: https://sourceforge.net/projects/git-osx-installer/files/"
msgstr ""
#: ../../source/installation.rst:264
msgid ""
"After installing docker you should find an icon that looks like a whale "
"in the task bar."
msgstr ""
#: ../../source/installation.rst:270
msgid "*Docker app running*"
msgstr ""
#: ../../source/installation.rst:272
msgid ""
"You can verify that docker is running properly by opening the "
"**Terminal** app and typing:"
msgstr ""
#: ../../source/installation.rst:278
msgid "Which should return"
msgstr ""
#: ../../source/installation.rst:284
msgid "To verify that git is installed, simply type:"
msgstr ""
#: ../../source/installation.rst:290
msgid "Which should return something similar to the following:"
msgstr ""
#: ../../source/installation.rst:296
msgid ""
"If you get a “bash: git: command not found”, try to restart your "
"**Terminal** app and double-check for any errors during the install "
"process."
msgstr ""
#: ../../source/installation.rst:301
msgid ""
"Docker on macOS works by running a VM in the background (think of it as a"
" “computer emulator”). This VM has a certain amount of memory allocated "
"and WebODM can only use as much memory as it’s allocated."
msgstr ""
#: ../../source/installation.rst:303
msgid "Right click the whale icon from the task bar and click **Preferences**..."
msgstr ""
#: ../../source/installation.rst:304
msgid "Select the **Advanced** tab"
msgstr ""
#: ../../source/installation.rst:305
#, python-format
msgid ""
"Adjust the CPUs slider to use half of all available CPUs and the memory "
"to use 60-70% of all available memory"
msgstr ""
#: ../../source/installation.rst:306
msgid "Press **Apply & Restart**"
msgstr ""
#: ../../source/installation.rst:312
msgid "*Docker advanced settings*"
msgstr ""
#: ../../source/installation.rst:315
msgid "Step 4. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:317
msgid "From a **Terminal** type:"
msgstr ""
#: ../../source/installation.rst:325 ../../source/installation.rst:426
msgid "Then open a web browser to http://localhost:8000."
msgstr ""
#: ../../source/installation.rst:328
msgid "Linux"
msgstr ""
#: ../../source/installation.rst:330
msgid ""
"OpenDroneMap can run on any Linux distribution that supports docker. "
"According to `docker’s documentation website "
"<https://docs.docker.com/install/>`_ the officially supported "
"distributions are CentOS, Debian, Ubuntu and Fedora, with static binaries"
" available for others. If you have to pick a distribution solely for "
"running OpenDroneMap, Ubuntu is the recommended way to go."
msgstr ""
#: ../../source/installation.rst:333
msgid "Step 1. Install Requirements"
msgstr ""
#: ../../source/installation.rst:335
msgid "There are four programs that need to be installed:"
msgstr ""
#: ../../source/installation.rst:337
msgid "Docker"
msgstr ""
#: ../../source/installation.rst:338
msgid "Git"
msgstr ""
#: ../../source/installation.rst:339
msgid "Python (2 or 3)"
msgstr ""
#: ../../source/installation.rst:340
msgid "Pip"
msgstr ""
#: ../../source/installation.rst:342
msgid ""
"We cannot possibly cover the installation process for every Linux "
"distribution out there, so we’ll limit the instructions to those that are"
" distributions officially supported by docker. In all cases it’s just a "
"matter of opening a terminal prompt and typing a few commands."
msgstr ""
#: ../../source/installation.rst:345
msgid "Install on Ubuntu / Debian"
msgstr ""
#: ../../source/installation.rst:347 ../../source/installation.rst:359
#: ../../source/installation.rst:370 ../../source/installation.rst:381
msgid "Commands to type:"
msgstr ""
#: ../../source/installation.rst:357
msgid "Install on CentOS / RHEL"
msgstr ""
#: ../../source/installation.rst:368
msgid "Install on Fedora"
msgstr ""
#: ../../source/installation.rst:379
msgid "Install on Arch"
msgstr ""
#: ../../source/installation.rst:388
msgid "Step 2. Check Additional Requirements"
msgstr ""
#: ../../source/installation.rst:390
msgid ""
"In addition to the three programs above, the dockercompose script is also"
" needed. Sometimes it’s already installed with docker, but sometimes it "
"isn’t. To verify if it’s installed try to type:"
msgstr ""
#: ../../source/installation.rst:396
msgid "You should see somethings similar to the following:"
msgstr ""
#: ../../source/installation.rst:402
msgid "If instead you get something similar to the following:"
msgstr ""
#: ../../source/installation.rst:408
msgid "you can install it by using pip:"
msgstr ""
#: ../../source/installation.rst:416
msgid "Step 3. Download and Launch WebODM"
msgstr ""
#: ../../source/installation.rst:418
msgid "From a terminal type:"
msgstr ""
#: ../../source/installation.rst:429
msgid "Basic Commands and Troubleshooting"
msgstr ""
#: ../../source/installation.rst:431
#, python-format
msgid ""
"The cool thing about using docker is that 99% of the tasks you’ll ever "
"need to perform while using WebODM can be done via the ./webodm.sh "
"script. You have already encountered one of them:"
msgstr ""
#: ../../source/installation.rst:437
msgid ""
"which takes care of starting WebODM and setting up a default processing "
"node (node-odm-1). If you want to stop WebODM, you can already guess what"
" the command is:"
msgstr ""
#: ../../source/installation.rst:443
msgid ""
"There are several other commands you can use, along with different flags."
" Flags are parameters passed to the ./webodm.sh command and are typically"
" prefixed with “–”. The **port** flag for example instructs WebODM to use"
" a different network port:"
msgstr ""
#: ../../source/installation.rst:449
msgid "Other useful commands are listed below:"
msgstr ""
#: ../../source/installation.rst:468
msgid ""
"`The community forum <https://community.opendronemap.org>`_ is a great "
"place to ask for help if you get stuck during any of the installation"
" steps and for general questions on using the ./webodm.sh script."
msgstr ""
#: ../../source/installation.rst:471
msgid "Hello, WebODM!"
msgstr ""
#: ../../source/installation.rst:473
msgid ""
"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."
msgstr ""
#: ../../source/installation.rst:479
msgid "*WebODM Dashboard*"
msgstr ""
#: ../../source/installation.rst:481
msgid ""
"Notice that under the **Processing Nodes** menu there’s a \"node-odm-1\" "
"node already configured for you to use. This is a NodeODM node and has "
"been created automatically by WebODM. This node is running on the same "
"machine as WebODM."
msgstr ""
#: ../../source/installation.rst:483
msgid ""
"If you’ve made it this far, congratulations! Now it’s time to start "
"processing some data."
msgstr ""
#: ../../source/installation.rst:490
msgid "Running on more than one machine"
msgstr ""
#: ../../source/installation.rst:492
msgid ""
"**Optionally:** If you have another computer, you can repeat the "
"installation process (install docker, git, python, etc.) and launch a new"
" NodeODM node by typing from a Terminal/Git Bash window:"
msgstr ""
#: ../../source/installation.rst:498
msgid ""
"The above command asks docker to launch a new container using the "
"opendronemap/nodeodm image from Docker Hub (the latest version of "
"NodeODM), using port 3000, setting a maximum number of concurrent tasks "
"to 1 and to protect the node from unauthorized access using the password "
"\"secret\"."
msgstr ""
#: ../../source/installation.rst:500
msgid ""
"From WebODM you can then press the **Add New** button under **Processing "
"Nodes**. For the **hostname/IP** field type the IP of the second "
"computer. For the **port** field type “3000”. For the **token** field "
"type “secret”. You can also add an optional **label** for your node, such"
" as “second computer”. Then press **Save**."
msgstr ""
#: ../../source/installation.rst:502
msgid ""
"If everything went well, you should now have two processing nodes! You "
"will be able to process multiple tasks in parallel using two different "
"machines."
msgstr ""
#: ../../source/installation.rst:504
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/installation.rst>`_"
msgstr ""
#~ msgid "In **Source Location** type: https://github.com/Open-DroneMap/WebODM"
#~ msgstr ""

275
source/locale/nl/LC_MESSAGES/large.po
Wyświetl plik

@ -1,275 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/large.rst:4
msgid "Splitting Large Datasets"
msgstr ""
#: ../../source/large.rst:6
msgid ""
"Starting with ODM version ``0.6.0`` you can split up very large datasets "
"into manageable chunks (called submodels), running the pipeline on each "
"chunk, and then producing merged DEMs, orthophotos and point clouds. The "
"process is referred to as \"split-merge\"."
msgstr ""
#: ../../source/large.rst:8
msgid ""
"Why might you use the split-merge pipeline? If you have a very large "
"number of images in your dataset, split-merge will help make the "
"processing more manageable on a large machine (it will require less "
"memory). If you have many machines all connected to the same network you "
"can also process the submodels in parallel, thus allowing for horizontal "
"scaling and processing thousands of images more quickly."
msgstr ""
#: ../../source/large.rst:10
msgid ""
"Split-merge works in WebODM out of the box as long as the processing "
"nodes support split-merge, by enabling the ``--split`` option when "
"creating a new task."
msgstr ""
#: ../../source/large.rst:13
msgid "Calibrate images"
msgstr ""
#: ../../source/large.rst:15
msgid ""
"Image calibration is recommended (but not required) for large datasets "
"because error propagation due to image distortion could cause a bowl "
"effect on the models. Calibration instructions can be found at "
"`Calibrate Images <tutorials.html#calibrating-the-camera>`_."
msgstr ""
#: ../../source/large.rst:21
msgid ""
"Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania."
msgstr ""
#: ../../source/large.rst:24
msgid "Local Split-Merge"
msgstr ""
#: ../../source/large.rst:26
msgid ""
"Splitting a dataset into more manageable submodels and sequentially "
"processing all submodels on the same machine is easy! Just use "
"``--split`` and ``--split-overlap`` to decide the the average number of "
"images per submodels and the overlap (in meters) between submodels "
"respectively"
msgstr ""
#: ../../source/large.rst:32
msgid ""
"If you already know how you want to split the dataset, you can provide "
"that information and it will be used instead of the clustering algorithm."
msgstr ""
#: ../../source/large.rst:34
msgid ""
"The grouping can be provided by adding a file named image_groups.txt in "
"the main dataset folder. The file should have one line per image. Each "
"line should have two words: first the name of the image and second the "
"name of the group it belongs to. For example::"
msgstr ""
#: ../../source/large.rst:42
msgid ""
"will create 3 submodels. Make sure to pass ``--split-overlap 0`` if you "
"manually provide a ``image_groups.txt`` file."
msgstr ""
#: ../../source/large.rst:46
msgid "Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:48
msgid ""
"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>`_."
msgstr ""
#: ../../source/large.rst:55
msgid "Getting Started with Distributed Split-Merge"
msgstr ""
#: ../../source/large.rst:57
msgid "The first step is start ClusterODM"
msgstr ""
#: ../../source/large.rst:63
msgid ""
"Then on each machine you want to use for processing, launch a NodeODM "
"instance via"
msgstr ""
#: ../../source/large.rst:69
msgid ""
"Connect via telnet to ClusterODM and add the IP addresses/port of the "
"machines running NodeODM"
msgstr ""
#: ../../source/large.rst:84
msgid "Make sure you are running version ``1.5.1`` or higher of the NodeODM API."
msgstr ""
#: ../../source/large.rst:86
msgid ""
"At this point, simply use the ``--sm-cluster`` option to enable "
"distributed split-merge"
msgstr ""
#: ../../source/large.rst:93
msgid "Understanding the Cluster"
msgstr ""
#: ../../source/large.rst:95
msgid ""
"When connected via telnet, it is possible to interrogate what is "
"happening on the cluster. For example, we can use the command HELP to "
"find out available commands"
msgstr ""
#: ../../source/large.rst:118
msgid ""
"If, for example, the NodeODM instance wasn't active when ClusterODM "
"started, we might list nodes and see something as follows"
msgstr ""
#: ../../source/large.rst:125
msgid ""
"To address this, we can start up our local node (if not already started),"
" and then perform a ``NODE UPDATE``"
msgstr ""
#: ../../source/large.rst:135
msgid "Accessing the Logs"
msgstr ""
#: ../../source/large.rst:137
msgid ""
"While a process is running, it is also possible to list the tasks, and "
"view the task output"
msgstr ""
#: ../../source/large.rst:145
msgid "Autoscaling ClusterODM"
msgstr ""
#: ../../source/large.rst:147
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:149
msgid "To setup autoscaling you must:"
msgstr ""
#: ../../source/large.rst:151
msgid "Have a functioning version of NodeJS installed and then install ClusterODM"
msgstr ""
#: ../../source/large.rst:159
msgid "Make sure docker-machine is installed."
msgstr ""
#: ../../source/large.rst:160
msgid "Setup a S3-compatible bucket for storing results."
msgstr ""
#: ../../source/large.rst:161
msgid ""
"Create a configuration file for `DigitalOcean "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/digitalocean.md>`_"
" or `Amazon Web Services "
"<https://github.com/OpenDroneMap/ClusterODM/blob/master/docs/aws.md>`_."
msgstr ""
#: ../../source/large.rst:163
msgid "You can then launch ClusterODM with"
msgstr ""
#: ../../source/large.rst:169
msgid "You should see something similar to following messages in the console"
msgstr ""
#: ../../source/large.rst:177
#, python-format
msgid ""
"You should always have at least one static NodeODM node attached to "
"ClusterODM, even if you plan to use the autoscaler for all processing. If"
" you setup auto scaling, you can't have zero nodes and rely 100% on the "
"autoscaler. You need to attach a NodeODM node to act as the \"reference "
"node\" otherwise ClusterODM will not know how to handle certain requests "
"(for the forwarding the UI, for validating options prior to spinning up "
"an instance, etc.). For this purpose, you should add a \"dummy\" NodeODM "
"node and lock it"
msgstr ""
#: ../../source/large.rst:187
msgid "This way all tasks will be automatically forwarded to the autoscaler."
msgstr ""
#: ../../source/large.rst:190
msgid "Limitations"
msgstr ""
#: ../../source/large.rst:192
msgid ""
"The 3D textured meshes are currently not being merged as part of the "
"workflow (only point clouds, DEMs and orthophotos are)."
msgstr ""
#: ../../source/large.rst:194
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:197
msgid "Acknowledgments"
msgstr ""
#: ../../source/large.rst:198
msgid ""
"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."
msgstr ""
#: ../../source/large.rst:200
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/large.rst>`_"
msgstr ""

77
source/locale/nl/LC_MESSAGES/multispectral.po
Wyświetl plik

@ -1,77 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/multispectral.rst:2
msgid "Multispectral Support"
msgstr ""
#: ../../source/multispectral.rst:4
msgid ""
"Since version 0.9.9 ODM has basic support for radiometric normalization, "
"which is able to generate reflectance orthophotos from multispectral "
"cameras. Multispectral cameras capture multiple shots of the scene using "
"different band sensors."
msgstr ""
#: ../../source/multispectral.rst:7
msgid "Hardware"
msgstr ""
#: ../../source/multispectral.rst:9
msgid ""
"While we aim to support as many cameras as possible, multispectral "
"support has been developed using the following cameras, so they will work"
" better:"
msgstr ""
#: ../../source/multispectral.rst:11
msgid "`MicaSense RedEdge-MX and Altum <https://www.micasense.com/>`_"
msgstr ""
#: ../../source/multispectral.rst:12
msgid "`Sentera 6X <https://sentera.com/6x/>`_"
msgstr ""
#: ../../source/multispectral.rst:14
msgid ""
"Other cameras might also work. You can help us expand this list by "
"`sharing datasets <https://community.opendronemap.org/c/datasets/10>`_ "
"captured with other cameras."
msgstr ""
#: ../../source/multispectral.rst:17
msgid "Usage"
msgstr ""
#: ../../source/multispectral.rst:19
msgid ""
"Process all the images from all bands at once (do not separate the bands "
"into multiple folders) and pass the `--radiometric-calibration` parameter"
" to enable radiometric normalization. If the images are part of a multi-"
"camera setup, the resulting orthophoto will have N bands, one for each "
"camera (+ alpha)."
msgstr ""
#: ../../source/multispectral.rst:25
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/multispectral.rst>`_"
msgstr ""

141
source/locale/nl/LC_MESSAGES/outputs.po
Wyświetl plik

@ -1,141 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/outputs.rst:2
msgid "OpenDroneMap Outputs"
msgstr ""
#: ../../source/outputs.rst:4
msgid "Listed below are some of the useful outputs ODM produces."
msgstr ""
#: ../../source/outputs.rst:7
msgid "Point Cloud"
msgstr ""
#: ../../source/outputs.rst:9
msgid ""
"``odm_georeferencing/odm_georeferenced_model.ply/laz/csv`` -- The "
"georeferenced point cloud in different file formats"
msgstr ""
#: ../../source/outputs.rst:15
msgid ""
"*Point cloud over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:19
msgid "3D Textured Model"
msgstr ""
#: ../../source/outputs.rst:21
msgid ""
"``odm_texturing/odm_textured_model.obj`` -- The textured surface mesh "
"``odm_texturing/odm_textured_model_geo.obj`` -- The georeferenced and "
"textured surface mesh"
msgstr ""
#: ../../source/outputs.rst:24
msgid ""
"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``"
msgstr ""
#: ../../source/outputs.rst:30
msgid ""
"*Textured mesh courtesy of* `OpenDroneMap "
"<https://twitter.com/opendronemap>`_"
msgstr ""
#: ../../source/outputs.rst:33
msgid "Orthophoto"
msgstr ""
#: ../../source/outputs.rst:35
msgid ""
"``odm_orthophoto/odm_orthphoto.png`` -- The orthophoto, but this is a "
"simple png, which doesn't have any georeferencing information"
msgstr ""
#: ../../source/outputs.rst:37
msgid ""
"``odm_orthophoto/odm_orthphoto.tif`` -- GeoTIFF Orthophoto. You can use "
"it in QGIS as a raster layer."
msgstr ""
#: ../../source/outputs.rst:43
msgid ""
"*Orthophoto over State University Zanzibar, courtesy of* `Khadija "
"Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:46
msgid "DTM/DSM"
msgstr ""
#: ../../source/outputs.rst:48
msgid ""
"DTM/DSM will only be created if the ``--dtm`` or ``--dsm`` options are "
"used. See `tutorial on elevation models "
"<https://docs.opendronemap.org/tutorials.html#creating-digital-elevation-"
"models>`_ for more options in creating."
msgstr ""
#: ../../source/outputs.rst:50
msgid "Data will be stored in:"
msgstr ""
#: ../../source/outputs.rst:52
msgid "``odm_dem/dtm.tif``"
msgstr ""
#: ../../source/outputs.rst:53
msgid "``odm_dem/dsm.tif``"
msgstr ""
#: ../../source/outputs.rst:59
msgid ""
"*Digital surface model over State University Zanzibar, courtesy of* "
"`Khadija Abdullah Ali <https://www.linkedin.com/in/khadija-abdulla-ali-"
"56b4044a/>`_"
msgstr ""
#: ../../source/outputs.rst:62
msgid "List of all outputs"
msgstr ""
#: ../../source/outputs.rst:109
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/outputs.rst>`_"
msgstr ""
#~ msgid ""
#~ "*Textured mesh over State University "
#~ "Zanzibar, courtesy of* `Khadija Abdullah "
#~ "Ali <https://www.linkedin.com/in/khadija-abdulla-"
#~ "ali-56b4044a/>`_"
#~ msgstr ""

92
source/locale/nl/LC_MESSAGES/requesting-features.po
Wyświetl plik

@ -1,92 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/requesting-features.rst:2
msgid "How To Request Features"
msgstr ""
#: ../../source/requesting-features.rst:4
msgid ""
"All software needs user feedback and feature requests, to grow and "
"maintain alignment with the needs of its users."
msgstr ""
#: ../../source/requesting-features.rst:7
msgid ""
"OpenDroneMap is FOSS software. Free and open source (FOSS) projects are "
"interesting from the inside and outside: from the outside, successful "
"ones feel like they should be able to do anything, and it’s hard to know "
"what a reasonable request is. From the inside of a project, they can feel"
" very resource constrained: largely by time, money, and opportunity "
"overload."
msgstr ""
#: ../../source/requesting-features.rst:13
msgid ""
"A feature request can be submitted as issues on the applicable Github "
"repository (e.g., `WebODM "
"<https://github.com/OpenDroneMap/WebODM/issues>`_ or `ODM "
"<https://github.com/OpenDroneMap/ODM/issues>`_ or similar) or more simply"
" as a discussion topic on `the community forum "
"<https://community.opendronemap.org/>`_. Try to start by searching these "
"sources to see if someone else has already brought it up. Sometimes a "
"feature is already in the works, or has at least been discussed."
msgstr ""
#: ../../source/requesting-features.rst:19
msgid ""
"And importantly, the trick is to listen: if someone within the project "
"says: \"This is a big lift, we need MONEY or TIME or SOMEONE TO HELP CODE"
" IT\" (or possibly a combination of the three) then there are two answers"
" that work really well in response:"
msgstr ""
#: ../../source/requesting-features.rst:23
msgid ""
"*Ok. I didn’t know it was a big feature request! I hope someone comes "
"along with the necessary resources. As a community member, I would be "
"happy to be an early user and tester!*"
msgstr ""
#: ../../source/requesting-features.rst:25
msgid "or"
msgstr ""
#: ../../source/requesting-features.rst:27
msgid ""
"*Let’s figure out if we can put together the resources to get this done! "
"Here’s what I can contribute toward it: …*"
msgstr ""
#: ../../source/requesting-features.rst:29
msgid ""
"We are glad you are excited to see new features added to the project. "
"Some new features need support, and some are easier to implement. We'll "
"do our best to help you understand where your request falls, and we "
"appreciate any support you can provide."
msgstr ""
#: ../../source/requesting-features.rst:33
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/requesting-"
"features.rst>`_"
msgstr ""

95
source/locale/nl/LC_MESSAGES/resources.po
Wyświetl plik

@ -1,95 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/resources.rst:2
msgid "Additional References"
msgstr ""
#: ../../source/resources.rst:5
msgid "For Users"
msgstr ""
#: ../../source/resources.rst:7
msgid "The following resources are a good place to start:"
msgstr ""
#: ../../source/resources.rst:9
msgid "`README page for ODM <https://github.com/OpenDroneMap/OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:10
msgid "`README page for WebODM <https://github.com/OpenDroneMap/WebODM>`_"
msgstr ""
#: ../../source/resources.rst:11
msgid ""
"`README page for NodeODM <https://github.com/OpenDroneMap/node-"
"OpenDroneMap>`_"
msgstr ""
#: ../../source/resources.rst:12
msgid ""
"`Ground Control Points Format Specification "
"<https://github.com/mapillary/OpenSfM/blob/master/doc/source/gcp.rst>`_"
msgstr ""
#: ../../source/resources.rst:13
msgid "`OpenDroneMap: The Missing Guide <https://odmbook.com/>`_"
msgstr ""
#: ../../source/resources.rst:16
msgid "For Developers"
msgstr ""
#: ../../source/resources.rst:18
msgid "In addition to user resources, we recommend to also read the following:"
msgstr ""
#: ../../source/resources.rst:20
msgid "WebODM documentation: https://docs.webodm.org"
msgstr ""
#: ../../source/resources.rst:21
msgid ""
"NodeODM API specification: "
"https://github.com/OpenDroneMap/NodeODM/blob/master/docs/index.adoc"
msgstr ""
#: ../../source/resources.rst:22
msgid ""
"Overview of the ODM pipeline: http://community.opendronemap.org/t/where-"
"can-i-find-background-information-on-the-concepts-of-odm/665/2"
msgstr ""
#: ../../source/resources.rst:23
msgid ""
"We keep a `section in our forum dedicated to research papers "
"<http://community.opendronemap.org/c/ideas-proposals/research-papers>`_. "
"This is a valuable place where to read more about state of the art "
"research related to structure from motion, multi-view stereo, meshing, "
"texturing, etc. which can be used to improve the software."
msgstr ""
#: ../../source/resources.rst:26
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/api.rst>`_"
msgstr ""

815
source/locale/nl/LC_MESSAGES/tutorials.po
Wyświetl plik

@ -1,815 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/tutorials.rst:5
msgid "Tutorials"
msgstr ""
#: ../../source/tutorials.rst:7
msgid "Below you will find instructions for some common use cases."
msgstr ""
#: ../../source/tutorials.rst:11
msgid "Creating High Quality Orthophotos"
msgstr ""
#: ../../source/tutorials.rst:17
msgid ""
"Without any parameter tweaks, ODM chooses a good compromise between "
"quality, speed and memory usage. If you want to get higher quality "
"results, you need to tweak some parameters:"
msgstr ""
#: ../../source/tutorials.rst:19
msgid ""
"``--orthophoto-resolution`` is the resolution of the orthophoto in "
"cm/pixel. Decrease this value for a higher resolution result."
msgstr ""
#: ../../source/tutorials.rst:20
msgid ""
"``--ignore-gsd`` is a flag that instructs ODM to skip certain memory and "
"speed optimizations that directly affect the orthophoto. Using this flag "
"will increase runtime and memory usage, but may produce sharper results."
msgstr ""
#: ../../source/tutorials.rst:21
msgid ""
"``--texturing-nadir-weight`` should be increased to ``29-32`` in urban "
"areas to reconstruct better edges of roofs. It should be decreased to "
"``0-6`` in grassy / flat areas."
msgstr ""
#: ../../source/tutorials.rst:22
msgid "``--texturing-data-term`` should be set to `area` in forest areas."
msgstr ""
#: ../../source/tutorials.rst:23
msgid ""
"``--mesh-size`` should be increased to `300000-600000` and `--mesh-"
"octree-depth`` should be increased to `10-11` in urban areas to recreate "
"better buildings / roofs."
msgstr ""
#: ../../source/tutorials.rst:27
msgid "Calibrating the Camera"
msgstr ""
#: ../../source/tutorials.rst:29
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:35
msgid ""
"*Bowling effect on point cloud over 13,000+ image dataset collected by "
"World Bank Tanzania over the flood prone Msimbasi Basin, Dar es Salaam, "
"Tanzania.*"
msgstr ""
#: ../../source/tutorials.rst:37
msgid ""
"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°."
msgstr ""
#: ../../source/tutorials.rst:45
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:47
msgid ""
"Alternatively, the following experimental method can be applied: fly with"
" much lower overlap, but two *crossgrid* flights (sometimes called "
"crosshatch) separated by 20° with a 5° forward facing camera."
msgstr ""
#: ../../source/tutorials.rst:49
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:50
#, python-format
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:56
msgid ""
"Vertically separated flight lines also improve accuracy, but less so than"
" a camera that is forward facing by 5°."
msgstr ""
#: ../../source/tutorials.rst:62
msgid ""
"From James and Robson (2014), `CC BY 4.0 "
"<https://creativecommons.org/licenses/by/4.0>`_"
msgstr ""
#: ../../source/tutorials.rst:66
msgid "Creating Digital Elevation Models"
msgstr ""
#: ../../source/tutorials.rst:68
msgid ""
"By default ODM does not create 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."
msgstr ""
#: ../../source/tutorials.rst:74
msgid ""
"For DTM generation, a Simple Morphological Filter (smrf) is used to "
"classify points in ground vs. non-ground and only the ground points are "
"used. The ``smrf`` filter can be controlled via several parameters:"
msgstr ""
#: ../../source/tutorials.rst:76
msgid ""
"``--smrf-scalar`` scaling value. Increase this parameter for terrains "
"with lots of height variation."
msgstr ""
#: ../../source/tutorials.rst:77
msgid ""
"``--smrf-slope`` slope parameter, which is a measure of \"slope "
"tolerance\". Increase this parameter for terrains with lots of height "
"variation. Should be set to something higher than 0.1 and not higher than"
" 1.2."
msgstr ""
#: ../../source/tutorials.rst:78
msgid ""
"``--smrf-threshold`` elevation threshold. Set this parameter to the "
"minimum height (in meters) that you expect non-ground objects to be."
msgstr ""
#: ../../source/tutorials.rst:79
msgid ""
"``--smrf-window`` window radius parameter (in meters) that corresponds to"
" the size of the largest feature (building, trees, etc.) to be removed. "
"Should be set to a value higher than 10."
msgstr ""
#: ../../source/tutorials.rst:81
msgid ""
"Changing these options can affect the result of DTMs significantly. The "
"best source to read to understand how the parameters affect the output is"
" to read the original paper `An improved simple morphological filter for "
"the terrain classification of airborne LIDAR data "
"<https://www.researchgate.net/publication/258333806_An_Improved_Simple_Morphological_Filter_for_the_Terrain_Classification_of_Airborne_LIDAR_Data>`_"
" (PDF freely available)."
msgstr ""
#: ../../source/tutorials.rst:83
msgid "Overall the ``--smrf-threshold`` option has the biggest impact on results."
msgstr ""
#: ../../source/tutorials.rst:85
msgid ""
"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."
msgstr ""
#: ../../source/tutorials.rst:91
msgid "Two other important parameters affect DEM generation:"
msgstr ""
#: ../../source/tutorials.rst:93
msgid ""
"``--dem-resolution`` which sets the output resolution of the DEM raster "
"(cm/pixel)"
msgstr ""
#: ../../source/tutorials.rst:94
msgid ""
"``--dem-gapfill-steps`` which determines the number of progressive DEM "
"layers to use. For urban scenes increasing this value to `4-5` can help "
"produce better interpolation results in the areas that are left empty by "
"the SMRF filter."
msgstr ""
#: ../../source/tutorials.rst:96
msgid "Example of how to generate a DTM::"
msgstr ""
#: ../../source/tutorials.rst:102
msgid "Using Docker"
msgstr ""
#: ../../source/tutorials.rst:104
msgid ""
"Since many users employ docker to deploy OpenDroneMap, it can be useful "
"to understand some basic commands in order to interrogate the docker "
"instances when things go wrong, or we are curious about what is "
"happening. Docker is a containerized environment intended, among other "
"things, to make it easier to deploy software independent of the local "
"environment. In this way, it is similar to virtual machines."
msgstr ""
#: ../../source/tutorials.rst:106
msgid "A few simple commands can make our docker experience much better."
msgstr ""
#: ../../source/tutorials.rst:109
msgid "Listing Docker Machines"
msgstr ""
#: ../../source/tutorials.rst:111
msgid ""
"We can start by listing available docker machines on the current machine "
"we are running as follows:"
msgstr ""
#: ../../source/tutorials.rst:120
msgid ""
"If we want to see machines that may not be running but still exist, we "
"can add the `-a` flag:"
msgstr ""
#: ../../source/tutorials.rst:133
msgid "Accessing logs on the instance"
msgstr ""
#: ../../source/tutorials.rst:135
msgid ""
"Using either the `CONTAINER ID` or the name, we can access any logs "
"available on the machine as follows:"
msgstr ""
#: ../../source/tutorials.rst:141
msgid ""
"This is likely to be unwieldy large, but we can use a pipe `|` character "
"and other tools to extract just what we need from the logs. For example "
"we can move through the log slowly using the `more` command:"
msgstr ""
#: ../../source/tutorials.rst:157
msgid ""
"Pressing `Enter` or `Space`, arrow keys or `Page Up` or `Page Down` keys "
"will now help us navigate through the logs. The lower case letter `Q` "
"will let us escape back to the command line."
msgstr ""
#: ../../source/tutorials.rst:159
msgid ""
"We can also extract just the end of the logs using the `tail` commmand as"
" follows:"
msgstr ""
#: ../../source/tutorials.rst:170
msgid ""
"The value `-5` tells the tail command to give us just the last 5 lines of"
" the logs."
msgstr ""
#: ../../source/tutorials.rst:173
msgid "Command line access to instances"
msgstr ""
#: ../../source/tutorials.rst:175
msgid ""
"Sometimes we need to go a little deeper in our exploration of the process"
" for OpenDroneMap. For this, we can get direct command line access to the"
" machines. For this, we can use `docker exec` to execute a `bash` command"
" line shell in the machine of interest as follows:"
msgstr ""
#: ../../source/tutorials.rst:179
msgid "::"
msgstr ""
#: ../../source/tutorials.rst:178
msgid "> docker exec -ti 2518817537ce bash root@2518817537ce:/code#"
msgstr ""
#: ../../source/tutorials.rst:181
msgid "Now we are logged into our docker instance and can explore the machine."
msgstr ""
#: ../../source/tutorials.rst:184
msgid "Cleaning up after Docker"
msgstr ""
#: ../../source/tutorials.rst:186
msgid ""
"Docker has a lamentable use of space and by default does not clean up "
"excess data and machines when processes are complete. This can be "
"advantageous if we need to access a process that has since terminated, "
"but carries the burden of using increasing amounts of storage over time. "
"Maciej Łebkowski has an `excellent overview of how to manage excess disk "
"usage in docker <https://lebkowski.name/docker-volumes/>`_."
msgstr ""
#: ../../source/tutorials.rst:190
msgid "Using ODM from low-bandwidth location"
msgstr ""
#: ../../source/tutorials.rst:193
msgid "What is this and who is it for?"
msgstr ""
#: ../../source/tutorials.rst:195
msgid "Via Ivan Gayton's: [repo](https://github.com/ivangayton/GDAL_scripts/)"
msgstr ""
#: ../../source/tutorials.rst:197
msgid ""
"`OpenDroneMap <https://www.opendronemap.org/>`__ can’t always be "
"effectively set up locally—it takes a fairly powerful machine to process "
"large datasets—so a cloud machine can sometimes be the answer for people "
"in the field. However, bandwidth is a problem in many low-income "
"settings. This constraint can’t be solved completely, but the following "
"method does a reasonable job of reducing the bandwidth needed to process "
"drone imagery datasets on the cloud from African locations."
msgstr ""
#: ../../source/tutorials.rst:205
msgid ""
"Here we present a tricky but workable process to create an OpenDroneMap "
"cloud machine (*not* CloudODM, mind you, just a cloud-based instance of "
"ODM that you run from the command line) and use it to remotely process "
"large photo sets. It requires familiarity with Unix command line use, "
"ssh, a Digital Ocean account (Amazon AWS would work as well, possibly "
"with slight differences in the setup), and a moderate level of general "
"computer literacy. If you aren’t fairly computer-savvy and willing to "
"fuss with a slightly tricky setup, `CloudODM "
"<https://www.opendronemap.org/cloudodm/>`__ is what you should be looking"
" at."
msgstr ""
#: ../../source/tutorials.rst:216
msgid ""
"The whole process is mostly targeted at someone flying substantial "
"missions in an African or similar location looking to process data ASAP "
"while still in a field setting. Therefore it emphasizes a workflow "
"intended to reduce bandwidth/data transfer, rather than just the simplest"
" way of running ODM."
msgstr ""
#: ../../source/tutorials.rst:223
msgid "Steps"
msgstr ""
#: ../../source/tutorials.rst:226
msgid "Install"
msgstr ""
#: ../../source/tutorials.rst:228
msgid ""
"Create a Digital Ocean droplet with at least 4GB of RAM. That’ll cost "
"about $20/month. Less than 4GB of RAM and the install will probably fail."
" When we actually run the ODM process we’ll resize it to a much "
"larger—and more expensive—cloud machine, but between runs you can "
"downsize it between runs to the second-cheapest droplet which costs only "
"$10/month (the cheapest droplet, at $5/month, comes with such a small "
"drive that you can’t downsize back to it)."
msgstr ""
#: ../../source/tutorials.rst:236
msgid "Should be an Ubuntu 16.04 instance to ensure dependency compatibility"
msgstr ""
#: ../../source/tutorials.rst:238
msgid ""
"Create a user with sudo privileges. `Digital Ocean’s insanely good "
"documentation <https://www.digitalocean.com/community/tutorials/initial-"
"server-setup-with-ubuntu-16-04>`__ can help you figure this out. In our "
"case we set up a user called ``odm``, so connecting to it is via the "
"command ``ssh odm@xxx.xxx.xxx.xxx`` (where the x’s stand for the IPv4 "
"address of your server). If you want to follow this example closely, *do*"
" use the username ``odm``; then your install path will be "
"``/home/odm/ODM/`` and will match all of the examples in this document. "
"-When you log into the server, it will offer you the option to upgrade to"
" Ubuntu 18.04, a more recent version. Don’t. ODM native install doesn’t "
"work smoothly on 18.04. Go ahead and execute ``sudo apt update`` and "
"``sudo apt upgrade`` to ensure your server isn’t dangerously without "
"updates, but stay with Ubuntu 16.04."
msgstr ""
#: ../../source/tutorials.rst:253
msgid ""
"Download and install ODM on it from the `ODM Github "
"<https://github.com/OpenDroneMap/ODM>`__ (regular, not WebODM) with the "
"following commands:"
msgstr ""
#: ../../source/tutorials.rst:263
msgid ""
"If you do this from the default home folder of your user (i.e. ``odm``) "
"the path to the install will be ``/home/odm/ODM`` (abbreviated as "
"``~/ODM/``)."
msgstr ""
#: ../../source/tutorials.rst:266
msgid ""
"There are some environmental variables that need to be set. Open the "
"~/.bashrc file on your machine and add the following 3 lines at the end "
"(From `the ODM github <https://github.com/OpenDroneMap/ODM>`__). The file"
" can be opened with ``nano ~/.bashrc`` (or whatever text editor you use "
"in lieu of nano). Be sure to replace ``/home/odm/`` with the correct path"
" to the location where you extracted OpenDroneMap if you didn’t do "
"everything exactly as in our example (for example if you used a different"
" username in your server setup):"
msgstr ""
#: ../../source/tutorials.rst:281
msgid ""
"Note that the ODM github readme contains a slight error, the install "
"directory name will be ODM, not OpenDroneMap (you’ll see this if you "
"compare the above instructions to the ones on the ODM GitHub)."
msgstr ""
#: ../../source/tutorials.rst:285
msgid ""
"In order to prevent a crash wherein the split-merge process fails to "
"locate its own executable, we add the following lines to ``~/.bashrc`` "
"(adjust paths if you’ve set things up differently from our example):"
msgstr ""
#: ../../source/tutorials.rst:295
msgid ""
"Now you’ll need a second cloud hard drive (a “Volume” in Digital Ocean "
"jargon) big enough to manage your project. Rule of thumb seems to be 10 "
"times the size of your raw image set; we’ve got a 100GB image set and set"
" up a 1000GB volume (once the run is done you should be able to get rid "
"of most of this expensive drive capacity, but it’s needed to complete the"
" process). Set up the volume, attach it to your droplet, and `configure "
"its mount point <https://www.digitalocean.com/docs/volumes/how-"
"to/mount/>`__ (in this example we’re setting it to ``/mnt/odmdata/``)."
msgstr ""
#: ../../source/tutorials.rst:306
msgid "Prep data and project"
msgstr ""
#: ../../source/tutorials.rst:308
msgid ""
"Now push your images onto the server. You can use `Secure Copy (scp) "
"<https://en.wikipedia.org/wiki/Secure_copy>`__ like so: ``scp -r "
"/path/to/my/imagefolder odm@xxx.xxx.xxx.xxx:/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:312
msgid ""
"This pushes the entire folder full of images (that’s what the ``-r`` "
"option does, “recursive”) into the remote location (in our example, into "
"the volume we attached to the cloud machine at ``/mnt/odmdata/``."
msgstr ""
#: ../../source/tutorials.rst:316
msgid ""
"This will take some bandwidth. No way around the size of the files.\\ `1 "
"<#footnote1>`__, \\ `2 <#footnote2>`__\\"
msgstr ""
#: ../../source/tutorials.rst:320
msgid "Directory structure"
msgstr ""
#: ../../source/tutorials.rst:322
msgid ""
"ODM requires the directories on the machine to be set up just so. The "
"critical bits are the install folder (if you installed as above, it’s "
"``/home/odm/ODM/``) and the project folder (i.e. "
"``/mnt/odmdata/myproject/``)"
msgstr ""
#: ../../source/tutorials.rst:327
msgid ""
"ODM’s settings.yaml file specifies a single parent directory containing "
"all projects. This is what goes in the project path line of the "
"settings.yaml file (slightly confusingly, this is actually the *parent* "
"directory of the individual project directories, which are specified by "
"the project name parameter when calling ODM). Edit settings.yaml and set "
"the project_path parameter to (as per our example setup) "
"``/mnt/odmdata/``, which in this case points to the Volume we created. "
"Individual project directories are created within that."
msgstr ""
#: ../../source/tutorials.rst:336
msgid ""
"Individual project directories, i.e. ``/mnt/odmdata/myproject/`` contain "
"the gcp_list.txt file, the image_groups.txt file, and the images folder "
"for each project``\\`"
msgstr ""
#: ../../source/tutorials.rst:339
msgid ""
"The images folder, i.e. ``/mnt/odmdata/myproject/images/`` contains all "
"of the images. If you set it up like this, the images don’t get re-copied"
" because they’re already in the directory that ODM wants them in."
msgstr ""
#: ../../source/tutorials.rst:343
msgid ""
"If you’ve got images with GPS info on them (as from an Ebee), use "
"exiftool to massage the GPS information ``exiftool "
"\"-GPSDOP<GPSZAccuracy\" .``.\\ `3 <#footnote3>`__\\ To do so you’ll "
"need to install exiftool. The command for that is probably ``sudo apt "
"install libimage-exiftool-perl``."
msgstr ""
#: ../../source/tutorials.rst:348
msgid ""
"Modify settings.yaml to specify the parent directory of the project "
"folder (in this case the Volume we created, ``/mnt/odmdata/``). Make sure"
" the images are in the correct spot, i.e. "
"``/mnt/odmdata/myproject/images`` and the other ancillary files "
"(gcp_list.txt and image_groups.txt) are in the root folder "
"``/mnt/odmdata/myproject/``"
msgstr ""
#: ../../source/tutorials.rst:354
msgid ""
"if you have the images in separate folders for individual AOI blocks or "
"flights (which you will if your flight management was organized), you can"
" create an image_groups.txt file with the incantations ``for i in *; do "
"cd $i; for j in *; do echo \"$j $i\" >> ../$i.txt; done; cd ../; done;`` "
"and ``cd ../``, ``for i in myproject/*.txt; do cat $i >> "
"image_groups.txt; done;``. That should create a file with the correct "
"structure: a list of all image files and a “group name” after each one "
"(which in this case will simply be the name of the folder it came from). "
"Then move all of the image files into a single directory called images in"
" the project root dir (so ``/mnt/odmdata/myproject/images/``). The "
"image_groups.txt file will allow ODM to keep track of which images belong"
" to the same batch, even though they’re all in a single directory."
msgstr ""
#: ../../source/tutorials.rst:370
msgid "Resize droplet, pull pin, run away"
msgstr ""
#: ../../source/tutorials.rst:372
msgid ""
"Shut down and resize your machine to an appropriately monstrous number of"
" CPUs and amount of memory. I use the memory-optimized machine with 24 "
"dedicated vCPUs and 192GB of RAM (which costs about $1.60/hr—which adds "
"up fast, it’s over $1000/month). Restart, and get to work quickly so as "
"not to waste expensive big-droplet time."
msgstr ""
#: ../../source/tutorials.rst:377
msgid ""
"Launch the ODM process via ssh using nohup (so that if you’re cut off, "
"processing will continue)"
msgstr ""
#: ../../source/tutorials.rst:380
msgid ""
"Alternately you can use GNU screen to launch the process from a screen "
"session which won’t stop if your connection is interrupted; launch "
"``screen``, and use ``<ctrl> a <ctrl> d`` to detach, ``screen -r`` to re-"
"attach. But using screen won’t get you a log file of all of the console "
"output unless you do something specific to capture that, while nohup "
"gives you a file with all of the console output, including error "
"messages, for free."
msgstr ""
#: ../../source/tutorials.rst:387
msgid ""
"Note: as of 2020-03 the normal incantation ``python run.py -i "
"/path/to/image/folder project_name`` seems *not* to work; the ``-i`` or "
"``--image`` parameter causes a weird error. So we drop the -i parameter, "
"and rely on the project directory line in the settings.yaml file to "
"direct ODM to the right place. Now using (including a split-merge):"
msgstr ""
#: ../../source/tutorials.rst:398
msgid ""
"This points ODM at the folder (in this example) "
"``/mnt/odmdata/myproject/``. Provided the image_groups.txt and "
"gcp_list.txt are in this folder, the images are in "
"``/mnt/odmdata/myproject/images/``, and the project path in settings.yaml"
" is ``/mnt/odmdata/`` it will not waste time and space copying images."
msgstr ""
#: ../../source/tutorials.rst:405
msgid ""
"Note that this assumes you have an image_groups.txt file. If not, this "
"``-split-overlap 0`` will probably fuck things up, and the ``--split 1`` "
"is literally a random number that will be ignored after the "
"image_groups.txt file is loaded (I think it normally controls how many "
"groups it splits a set of images into, but in our case we’re assuming the"
" images are already grouped sensibly). If you don’t have a large dataset "
"(>1000 images), omit the ``--split`` and ``--split-overlap`` options."
msgstr ""
#: ../../source/tutorials.rst:414
msgid "Follow the progress using tail (so that you’ll know when it’s done)"
msgstr ""
#: ../../source/tutorials.rst:420
msgid ""
"You may want to keep an eye on htop (to get a sense of the resource usage"
" so that in future you can only spin up a machine as large as necessary)"
msgstr ""
#: ../../source/tutorials.rst:425
msgid "After it finishes (assuming you survive that long)"
msgstr ""
#: ../../source/tutorials.rst:427
msgid ""
"As soon as processing is done, shut down the machine and resize it back "
"down to the inexpensive minimum capacity."
msgstr ""
#: ../../source/tutorials.rst:429
msgid "Start the machine back up, and log in via ssh."
msgstr ""
#: ../../source/tutorials.rst:430
msgid ""
"If you want to save download bandwidth, you can compress the orthophoto "
"using GDAL. Don’t add overviews, do that on your local machine to avoid "
"making the file bigger before downloading it."
msgstr ""
#: ../../source/tutorials.rst:438
msgid ""
"Download using scp: ``scp "
"odm@xxx.xxx.xxx.xxx:/mnt/odmdata/myproject/odm_orthophoto/odm_orthophoto.tif``"
" (or grab the compressed version you created in the last step)"
msgstr ""
#: ../../source/tutorials.rst:442
msgid ""
"Once you get the file on your local computer, you can use QGIS to add "
"overviews (“pyramids”) or use the GDAL command ``gdaladdo -r average "
"/path/to/image.tif 2 4 8 16 32 64 128 256 512 1024``."
msgstr ""
#: ../../source/tutorials.rst:446
msgid ""
"You can archive the odm_texturing, odm_georeferencing, and odm-dem "
"folders using tar to make them easier to download in one piece (and maybe"
" smaller)."
msgstr ""
#~ msgid ""
#~ "``--ignore-gsd`` is a flag that "
#~ "instructs ODM to skip certain memory "
#~ "and speed optimizations that directly "
#~ "affect the orthophoto. Using this flag"
#~ " will increase runtime and memory "
#~ "usage, but will produce sharper results."
#~ msgstr ""
#~ msgid "Ground Control Points"
#~ msgstr ""
#~ msgid ""
#~ "Ground control points are useful for "
#~ "correcting distortions in the data and"
#~ " referencing the data to know "
#~ "coordinate systems."
#~ msgstr ""
#~ msgid "The format of the GCP file is simple."
#~ msgstr ""
#~ msgid ""
#~ "The header line is a description "
#~ "of a UTM coordinate system, which "
#~ "must be written as a proj4 string."
#~ " http://spatialreference.org/ is a good "
#~ "resource for finding that information. "
#~ "Please note that currently angular "
#~ "coordinates (like lat/lon) DO NOT work."
#~ msgstr ""
#~ msgid ""
#~ "Subsequent lines are the X, Y &"
#~ " Z coordinates, your associated pixels "
#~ "and the image filename:"
#~ msgstr ""
#~ msgid "GCP file format::"
#~ msgstr ""
#~ msgid "e.g. for the Langley dataset::"
#~ msgstr ""
#~ 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``."
#~ msgstr ""
#~ 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 ""
#~ msgid ""
#~ "Sharp corners are good picks for "
#~ "GCPs. You should also place/find the "
#~ "GCPs evenly around your survey area."
#~ msgstr ""
#~ msgid ""
#~ "The ``gcp_list.txt`` file must be "
#~ "created in the base of your "
#~ "project folder."
#~ msgstr ""
#~ 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 ""
#~ msgid "Ground Control Points Interface"
#~ msgstr ""
#~ msgid ""
#~ "WebODM has a GCP interface, and "
#~ "example of which can be seen on"
#~ " `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 ""
#~ 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 ""
#~ msgid ""
#~ "Then one can load this GCP list"
#~ " into the interface, load the images,"
#~ " and place each of the GCPs in"
#~ " the image."
#~ msgstr ""
#~ msgid ""
#~ "`Help edit these docs! "
#~ "<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
#~ msgstr ""

34
source/locale/sw/LC_MESSAGES/arguments.po
Wyświetl plik

@ -1,34 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:01+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/arguments.rst:4
msgid "Options and Flags"
msgstr "Chagizi na Bendera"
#: ../../source/arguments.rst:6
msgid "Arguments::"
msgstr "Hoja"
#: ../../source/arguments.rst:289
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"
msgstr "kwa msaada kurekebisha kitabu! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/using.rst>`_"

226
source/locale/sw/LC_MESSAGES/contributing.po
Wyświetl plik

@ -1,226 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/contributing.rst:4
msgid "How To Contribute"
msgstr "Jinsi ya kushiriki"
#: ../../source/contributing.rst:6
msgid ""
"OpenDroneMap relies on community contributions. You can contribute in "
"many ways, even if you are not a programmer."
msgstr ""
"OpenDroneMap inategemea na ushiriki wa kijamii. unaweza kushiriki kwa "
"njia nyingi, hata ukiwa sio programa."
#: ../../source/contributing.rst:9
msgid "Community Forum"
msgstr "Jukwaa la kijamii"
#: ../../source/contributing.rst:11
msgid ""
"If you are looking to get involved, are stuck on a problem, or want to "
"reach out, `the forum <https://community.opendronemap.org/>`_ is a great "
"place to start. You may find your questions already answered or else you "
"can find other useful tips and resources. You can also contribute your "
"open access datasets for others to explore. It is a good place go before "
"submitting bug reports or getting in touch with developers before writing"
" a new feature."
msgstr ""
"Ikiwa unataka kushiriki, katika matatizo yalioshinda, au yanayotaka "
"kutatuliwa, jukwaa <https://community.opendronemap.org/>`_ ni zuri "
"sehemu ya kuanzia. unaweza kupata maswali yaliojibiwa au unaweza "
"kupata njia zitakazokusaidia au rasilimali. Pia unaweza kushiriki "
"data zako za wazi kwa wengine kutumia. Ni sehemu nzuri kabla kutuma "
"makosa au kutumia pamoja na wasanifu kuandika vitu vipya."
#: ../../source/contributing.rst:14
msgid "Reporting Bugs"
msgstr "Kuwasilisha Bugs"
#: ../../source/contributing.rst:16
msgid ""
"Bugs are tracked as Github issues. Please create an issue in the "
"repository and tag it with the Bug tag."
msgstr ""
"Bugs ni kufuatilia kama suala la Github. Tafadhali tengeneza "
"kitu ndani sehemu ya kuhifadhi na lebo na makosa"
#: ../../source/contributing.rst:18
msgid ""
"Explain the problem and include additional details to help maintainers "
"reproduce the problem:"
msgstr ""
"Elezea tatizo na uambatanishe maelezo ya ziada kuwasaidia "
"wanaotengeneza kugundua tatizo.:
#: ../../source/contributing.rst:20
msgid ""
"**Use a clear and descriptive title** for the issue to identify the "
"problem."
msgstr ""
"**Tumia njia fupi na madainayojieleza** kwa kitu kuonesha tatizo."
#: ../../source/contributing.rst:21
msgid ""
"**Describe the exact steps which reproduce the problem** in as many "
"details as possible. For example, start by explaining how you run ODM "
"(Docker, Vagrant, etc), e.g. which command exactly you used in the "
"terminal. When listing steps, **don't just say what you did, but explain "
"how you did it.**"
msgstr ""
"**Elezea hatua sahihi ambayo inazalisha tatizo** kwa undani wote "
"iwezekanavyo. Mfano,anza kwa kuelezea vipi unawasha ODM (Docker, "
"Vagrant, etc), e.g ni camand gani unatumia ndani ya taminali. "
"Wakati unasikiliza hatua, **usiseme tu umefanya, lakini elezea "
"ni vipi umefanya.**"
#: ../../source/contributing.rst:22
msgid ""
"**Provide specific examples to demonstrate the steps.** Include links to "
"files or GitHub projects, or copy/pasteable snippets, which you use in "
"those examples. If you're providing snippets in the issue, use `Markdown "
"code blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
msgstr ""
"**Andaa mfano maalum kuonesha njia.**Ikiwemo kiunganishi kwenye mafaili "
"au GitHub project, au sehemu copy/pasteable, ambayoumeitumia katika "
"mifano yote. Ikiwa umetoa dondoo khwenye hili, tumia `Markdown code "
"blocks <https://help.github.com/articles/markdown-basics/#multiple-"
"lines>`_."
#: ../../source/contributing.rst:23
msgid ""
"**Describe the behavior you observed after following the steps** and "
"point out what exactly is the problem with that behavior."
msgstr ""
"**Elezea tabia uligundua baada ya hatua zifuatazo** na onyesha kitu "
"husika ni tatizo kwa tabia hio."
#: ../../source/contributing.rst:24
msgid "**Explain which behavior you expected to see instead and why.**"
msgstr "**Elezea ni tabia ipi unategemea kuiona kutokea na kwa nini.**"
#: ../../source/contributing.rst:25
msgid ""
"**Include screenshots and animated GIFs** which show you following the "
"described steps and clearly demonstrate the problem. You can use `this "
"tool to record GIFs on macOS and Windows "
"<http://www.cockos.com/licecap/>`_, and `this tool "
"<https://github.com/colinkeenan/silentcast>`_ or `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
msgstr ""
"**Ikiwemo screenshots na animated GIF** ambayo inakuonesha "
"hatua za maelezo yafuatayo na maelezo sahihi ya matatizo. "
"Unaweza kutumia `Kifaa hichi cha kurekodi GIFs kwa macOS na Windows "
"<http://www.cockos.com/licecap/>`_, na `this tool "
"<https://github.com/colinkeenan/silentcast>`_ au `this one "
"<https://github.com/GNOME/byzanz>`_ on Linux."
#: ../../source/contributing.rst:26
msgid ""
"**If the problem is related to performance,** please post your machine's "
"specs (host and guest machine)."
msgstr ""
"** Ikiwa tatizo linaendana na utendaji kazi, ** tafadhali tuma mashine "
"yako maalum (host na guest mashine)."
#: ../../source/contributing.rst:27
msgid ""
"**If the problem wasn't triggered by a specific action,** describe what "
"you were doing before the problem happened and share more information "
"using the guidelines below."
msgstr ""
"**Ikiwa tatizo halijaoneshwa kwa kitendo maalum,**eleze nini ulifanya "
"kabla tatizo halijatoke na sambaza maelezo kutumia maelekezo yafuatayo."
#: ../../source/contributing.rst:29
msgid "Include details about your configuration and environment:"
msgstr "Ikiwemo undani juu ya configuration and environment: "
#: ../../source/contributing.rst:31
msgid ""
"**Which version of ODM are you using?** A stable release? a clone of "
"master?"
msgstr ""
"**Ni vashani ya ODM unayotumia?** Imetolewa sahihi? ni baabara ya "
"master?"
#: ../../source/contributing.rst:32
msgid "**What's the name and version of the OS you're using?**"
msgstr "** Ni jina gani na version ya OS unayotumia?**"
#: ../../source/contributing.rst:33
msgid ""
"**Are you running ODM in a virtual machine or Docker?** If so, which VM "
"software are you using and which operating systems and versions are used "
"for the host and the guest?"
msgstr ""
"**Unatumia ODM katika virtual mashine au Docker?** Ikiwa ni hivyo, ni VM "
"software unayotumia na opereting system gani na tolea unalotumia kwa "
"host na guest?"
#: ../../source/contributing.rst:36
msgid "Template For Submitting Bug Reports"
msgstr "Kigezo kwa kuwasilisha maelezo ya bug"
#: ../../source/contributing.rst:69
msgid "Pull Requests"
msgstr "Tatua maombi"
#: ../../source/contributing.rst:71
msgid ""
"Include screenshots and animated GIFs in your pull request whenever "
"possible."
msgstr ""
"Ikiwemo screenshots na animated GIFs katika kutatua maombi yako "
"iwezekanavyo.
#: ../../source/contributing.rst:72
msgid "Follow the PEP8 Python Style Guide."
msgstr "Fuata PEP8 Python Style Guide."
#: ../../source/contributing.rst:73
msgid "End files with a newline."
msgstr "Malizia file kwa mstari mpya."
#: ../../source/contributing.rst:76
msgid "Avoid platform-dependent code:"
msgstr "Epuka platform-dependent code:"
#: ../../source/contributing.rst:75
msgid "Use require('fs-plus').getHomeDirectory() to get the home directory."
msgstr ""
#: ../../source/contributing.rst:76
msgid "Use path.join() to concatenate filenames."
msgstr "Tumia path.join() kwa kuunganisha majina."
#: ../../source/contributing.rst:77
msgid ""
"Use os.tmpdir() rather than /tmp when you need to reference the temporary"
" directory."
msgstr ""
"Tumia os.tmpdir() kuliko /tmp ukihitaji kumbukumbu ya anuani ya muda "
"mfupi."
#: ../../source/contributing.rst:79
msgid "Using a plain return when returning explicitly at the end of a function."
msgstr "Tumia return tupu wakati return ya urahisi mwisho wa kazi."
#: ../../source/contributing.rst:79
msgid "Not return null, return undefined, null, or undefined"
msgstr "Sio return null, return undefined, null, au undefined,"
#: ../../source/contributing.rst:81
msgid ""
"`kwa msaada kurekebisha kitabu! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
msgstr ""
"`kwa msaada kurekebisha kitabu! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
#~ msgid "How to contribute"
#~ msgstr "Jinsi ya kushuriki"

89
source/locale/sw/LC_MESSAGES/flying.po
Wyświetl plik

@ -1,89 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/flying.rst:2
msgid "Flying Tips"
msgstr "Kidokeza cha kurusha ndege nyuki"
#: ../../source/flying.rst:4
msgid ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ has "
"guidelines on `flying for UAV mapping <https://uav-"
"guidelines.openaerialmap.org/>`_:"
msgstr ""
"The `Humanitarian OpenStreetMap team <https://www.hotosm.org/>`_ ina "
"muongozo juu ya `kurusha UAV kwa ramani <https://uav-"
"guidelines.openaerialmap.org/>`_:"
#: ../../source/flying.rst:6
msgid ""
"`Choosing the right UAV <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
msgstr ""
"`Chakua UAV sahihi <https://uav-"
"guidelines.openaerialmap.org/pages/05-choosing-the-right-uav/>`_"
#: ../../source/flying.rst:8
msgid ""
"`Choosing the right sensor <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
msgstr ""
"`Chagua sensa sahihi <https://uav-"
"guidelines.openaerialmap.org/pages/06-choosing-the-sensor/>`_"
#: ../../source/flying.rst:10
msgid ""
"`Mission preparation <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
msgstr ""
"`Kuandaa mission <https://uav-guidelines.openaerialmap.org/pages/07"
"-preparing-for-the-uav-mission/>`_"
#: ../../source/flying.rst:12
msgid ""
"The guidelines are intended for drone mapping projects on islands, but "
"have general use for all drone mappers."
msgstr ""
"Muongozo umekusudiwa kwa drone project za visiwa, lakini ina matumizi "
"kwa ujumla ya watengeza ramani kwa drone."
#: ../../source/flying.rst:14
msgid ""
"See also DroneDeploy's guide on `Making Successful Maps "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, which "
"provides great tips on mission planning."
msgstr ""
"Angalia pia DroneDeploy's muongozo juu ya `Kutengeza ramani yenye mafanikio "
"<https://support.dronedeploy.com/docs/making-successful-maps>`_, ambayo "
"inaelezea mambo muhimu juu ya kuandaa mission."
#: ../../source/flying.rst:16
msgid ""
"Finally, lens distortion is a challenge in projects requiring accurate 3D"
" data. See our section in these docs on `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."
msgstr ""
"Mwisho, mvurugio lenzi ni changamoto katika project kuchukua data za 3B "
"sahihi. Angalia kipande chetu katika kitabu hiki cha `Camera Calibration "
"<tutorials.html#calibrating-the-camera>`_."`
#: ../../source/flying.rst:18
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/flying.rst>`_"
msgstr ""
"`kwa msaada kurekebisha kitabu! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"
#~ msgid "Flying tips"
#~ msgstr ""

215
source/locale/sw/LC_MESSAGES/gcp.po
Wyświetl plik

@ -1,215 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2020, OpenDroneMap
# This file is distributed under the same license as the OpenDroneMap
# package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenDroneMap 0.9.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-07-06 21:47+0000\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"
"Generated-By: Babel 2.6.0\n"
#: ../../source/gcp.rst:3
msgid "Ground Control Points"
msgstr "Ground Control POints"
#: ../../source/gcp.rst:5
msgid ""
"Ground control points are useful for correcting distortions in the data "
"and referencing the data to know coordinate systems."
msgstr ""
"Ground control points ni muhimu kurekebisha mzunguko wa taarifa "
"na kumbukumbu data ili kujua mfumo wa muunganiko."
#: ../../source/gcp.rst:7
msgid "The format of the GCP file is simple."
msgstr "Mfangilio wa GCP file ni mwepesi."
#: ../../source/gcp.rst:9
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 ""
"Mstari wa mwanzo lazima ubebe jina la muelekeo uliotumika kwa muunganiko "
"wa eneo. Hii inaweza kurahisisha vile vile kama ni PROJ string (e.g "
"``+proj=utm +zone=10 +ellps=WGS84 +datum=WGS84 +units=m +no_defs``), EPSG"
" code (e.g. ``EPSG:4326``) au kama ``WGS84 UTM <zone>[N|S]`` thamani (eg. "
"``WGS84 UTM 16N``)"
#: ../../source/gcp.rst:10
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 ""
"Mstari wa mbele ni muungano wa X, Y & Z, muungano elementi picha wa jina "
"la file na njia za taarifa za ziada,zilizotenganishwa na kichupo au nafasi:"
#: ../../source/gcp.rst:11
msgid "Elevation values can be set to \"NaN\" to indicate no value"
msgstr ""
"Thamani ya muinuko inaweza kuwekwa \"NaN\" kuonesha hapana kitu"
#: ../../source/gcp.rst:12
msgid "The 7th column (optional) typically contains the label of the GCP."
msgstr "7th column (optional) kawaida inachukua lebo ya GCP."
#: ../../source/gcp.rst:14
msgid "GCP file format::"
msgstr "Mpangilio wa GCP faili::"
#: ../../source/gcp.rst:20
msgid "Example::"
msgstr "Mfano::"
#: ../../source/gcp.rst:27
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 ""
" Ikiwa utagawa GCP faili liitwalo ``gcp_list.txt`` kisha ODM wenyewe "
"itafuta hilo. Ikiwa lina jina jengine unaweza kuonesha kutumia "
"``--gcp <path>``. Ikiwa una gcp faili na unataka kufanya "
"georeferensing pamoja na exif file baada yake, unaweza kukadiria "
"``--use-exif``. Ikiwa una usahihi mkubwa wa vipimo vya GPS katika "
"(RTK) picha zako na unataka kutumia maelezo hayo pamoja n gcp faili,"
" inaweza kutumia ``--force-gps``."
#: ../../source/gcp.rst:29
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 ""
" `Posti hii ina baadhi ya maelezo kuhusu kuweka Ground Control Target "
"kabla ya flight <http://diydrones.com/profiles/blogs/ground-control-"
"points-gcps-for-aerial-photography>`_, lakini tayari una picha, "
"unaweza kiutafuta alama yako mwenyewe katika picha ulizonazo, unaweza "
"kutautisha eneo ambalo linapatikana ndani ya **at least** picha 3, "
"na hapo utapata kiasi maeneo matano."
#: ../../source/gcp.rst:31
msgid ""
"Sharp corners are good picks for GCPs. You should also place/find the "
"GCPs evenly around your survey area."
msgstr ""
"Pembe zilizokaa vizuri ni nzuri kuchagua kwa GCP. Pia unaweza "
"kuweka/kutafuta GCP hata katika eneo lako la utafiti."
#: ../../source/gcp.rst:33
msgid ""
"The ``gcp_list.txt`` file must be created in the base of your project "
"folder."
msgstr ""
"Faili la ``gcp_list.txt`` lazima litengenezwe wakati ukitengeza "
folder la project yako."
#: ../../source/gcp.rst:35
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 ""
"Kwa matokeo mazuri faili lako liwe na mistari iziozidi 15 baada ya "
"ufunguzi (point 5 pamoja na picha 3 kwa kila point).
#: ../../source/gcp.rst:39
msgid "User Interfaces"
msgstr "User Interfaces"
#: ../../source/gcp.rst:41
msgid "You can use one of two user interfaces for creating GCP files:"
msgstr "Unaweza kutumia moja kati ya interface mbili kutengeneza GCP faili:"
#: ../../source/gcp.rst:43
msgid "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
msgstr "`POSM GCPi <https://github.com/posm/posm-gcpi>`_"
#: ../../source/gcp.rst:44
msgid "`GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
msgstr "GCP Editor Pro <https://github.com/uav4geo/GCPEditorPro>`_"
#: ../../source/gcp.rst:48
msgid "POSM GCPi"
msgstr "POSM GCPi"
#: ../../source/gcp.rst:50
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 ""
"POSM GCPi linabebwa na chaguo msingi la WebODM. Mfano unapatikana "
"katika onesho la WebODM http://demo.webodm.org/plugins/posm-gcpi/>`_. "
"Kutumia hii ijulikanayo ground control XYZ value, Moja itafanya ifuatavyo:"
#: ../../source/gcp.rst:52
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 ""
"Tengeneza idadi ya GCP ambazo zitakuwa na majina gcp (hii itaandikwa "
"amabyo itaonekana katika kiwasilishi cha GCP),x,y,na z, pamoja na "
"utangulizicha proj4 string ya GCP yako (hakikisha zipo katika mfumo "
"wa ramani, kama UTM.Lazima ionekane ka hivi:"
#: ../../source/gcp.rst:63
msgid ""
"Then one can load this GCP list into the interface, load the images, and "
"place each of the GCPs in the image."
msgstr ""
"Kisha inaweza pakia idadi ya GCP hii katika kiwasilishwa,pakia picha, "
"na weka kila GCP katika picha."
#: ../../source/gcp.rst:67
msgid "GCP Editor Pro"
msgstr "GCP Editor Pro"
#: ../../source/gcp.rst:69
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 ""
"Aplication nii inahitaji kuingizwa tofauti au inaweza kuingizwa kama "
"WebODM plugin kutoka `https://github.com/uav4geo/GCPEditorPro "
"<https://github.com/uav4geo/GCPEditorPro>`_"
#: ../../source/gcp.rst:71
msgid ""
"Create a CSV file that includes the gcp name, northing, easting and "
"elevation."
msgstr ""
"Tengeneza CSV faili litalochukua jina la gcp, kaskazini, kusini na "
"muinuko."
#: ../../source/gcp.rst:80
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 ""
"Kisha ingiza CSV kutoka screen kuu na andika ``+proj=utm +zone=37 "
"+south +ellps=WGS84 +datum=WGS84 +units=m +no_defs`` in the ``EPSG/PROJ``"
" box."
#: ../../source/gcp.rst:82
msgid ""
"The following screen will display a map from where to select the GCPs to "
"tag and import the respective images."
msgstr ""
"Screen zifuatazo zitaonesha ramani kutoka sehemu na kuiita GCP kwa jina "
"na kuita picha nyengine zilipo."
#: ../../source/gcp.rst:85
msgid ""
"`Help edit these docs! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/tutorials.rst>`_"
msgstr ""
"`kwa msaada kurekebisha kitabu! "
"<https://github.com/OpenDroneMap/docs/blob/publish/source/contributing.rst>`_"

Some files were not shown because too many files have changed in this diff Show More