From 99efdc01037be695e1d06b8d193c62b65b158c74 Mon Sep 17 00:00:00 2001 From: Piero Toffanin Date: Tue, 16 Aug 2016 17:08:53 -0500 Subject: [PATCH] Update README.md Removed repeated word --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a233a455..626aa205 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ A web interface for [OpenDroneMap](https://github.com/OpenDroneMap/OpenDroneMap) - `Project`: A collection of tasks (successfully processed, failed, waiting to be executed, etc.) - `Task`: A collection of input aerial images and an optional set of output results derived from the images, including an orthophoto, a georeferenced model and a textured model. A `Task`'s output is processed by OpenDroneMap. - - `ProcessingNode`: An instance usually running on a separate VM instance, or on a separate machine which accepts aerial images, runs OpenDroneMap and returns the processed results (orthophoto, georeferenced model, etc.). Each node communicates with WebODM via a lightweight API such as [node-OpenDroneMap](https://www.github.com/pierotofy/node-OpenDroneMap). WebODM manages the distribution of `Task` to different `ProcessingNode` instances. + - `ProcessingNode`: An instance usually running on a separate VM, or on a separate machine which accepts aerial images, runs OpenDroneMap and returns the processed results (orthophoto, georeferenced model, etc.). Each node communicates with WebODM via a lightweight API such as [node-OpenDroneMap](https://www.github.com/pierotofy/node-OpenDroneMap). WebODM manages the distribution of `Task` to different `ProcessingNode` instances. - `ImageUpload`: aerial images. - `Mission`: A flight path and other information (overlap %, angle, ...) associated with a particular `Task`.