WebODM

A free, user-friendly, extendable application and API for drone image processing. Generate georeferenced maps, point clouds and textured 3D models from aerial images. It uses OpenDroneMap for processing.

If you know Python, web technologies (JS, HTML, CSS, etc.) or both, make a fork, contribute something that interests you, and make a pull request! All ideas are considered and people of all skill levels are welcome. See the Contributing document for more information.

Getting Started

• Install the following applications (if they are not installed already):

• Docker
• Python
• Git

• From the Docker Quickstart Terminal (Windows) or from the command line (OSX / Linux) type:

git clone https://github.com/OpenDroneMap/WebODM
cd WebODM
pip install docker-compose
./webodm.sh start

• If you're on Windows find the IP of your Docker machine by running this command from your Docker Quickstart Terminal:

docker-machine ip

Linux / OSX, users can connect to 127.0.0.1.

• Open a Web Browser to http://<yourDockerMachineIp>:8000
• Log in with the default credentials: "admin:admin"

To stop WebODM press CTRL+C or run:

./webodm.sh stop

To update WebODM to the latest version use:

./webodm.sh update

We recommend that you read the Docker Documentation to familiarize with the application lifecycle, setup and teardown, or for more advanced uses. Look at the contents of the webodm.sh script to understand what commands are used to launch WebODM.

If you are getting a MemoryError while processing the images, make sure that your Docker environment has enough RAM allocated. http://stackoverflow.com/a/39720010

Add More Processing Nodes

WebODM can be linked to one or more processing nodes running node-OpenDroneMap. The default configuration already includes a "node-odm-1" processing node which runs on the same machine as WebODM, just to help you get started. As you become more familiar with WebODM, you might want to install processing nodes on separate machines.

Run it natively

If you want to run WebODM natively, you will need to install:

• PostgreSQL (>= 9.5)
• PostGIS 2.3
• Python 3.5
• GDAL (>= 2.1)

On Linux, make sure you have:

apt-get install binutils libproj-dev gdal-bin

On Windows use the OSGeo4W installer to install GDAL. MacOS users can use:

brew install postgres postgis

Then these steps should be sufficient to get you up and running:

git clone https://github.com/OpenDroneMap/WebODM

Create a WebODM\webodm\local_settings.py file containing:

DATABASES = {
    'default': {
        'ENGINE': 'django.contrib.gis.db.backends.postgis',
        'NAME': 'webodm_dev',
        'USER': 'postgres',
        'PASSWORD': 'postgres',
        'HOST': 'localhost',
        'PORT': '5432',
    }
}

Then:

pip install -r requirements.txt
sudo npm install -g webpack
npm install
webpack
chmod +x start.sh && ./start.sh

If you are getting a rt_raster_gdal_warp: Could not create GDAL transformation object for output dataset creation, make sure that your PostGIS installation has PROJ support:

SELECT PostGIS_Full_Version();

You may also need to set the environment variable PROJSO to the .so or .dll projection library your PostGIS is using. This just needs to have the name of the file. So for example on Windows, you would in Control Panel -> System -> Environment Variables add a system variable called PROJSO and set it to libproj.dll (if you are using proj 4.6.1). You'll have to restart your PostgreSQL service/daemon after this change. http://postgis.net/docs/manual-2.0/RT_ST_Transform.html

Roadmap

• User Registration / Authentication
• UI mockup
• Task Processing
• 2D Map Display
• 3D model display
• Cluster management and setup.
• Mission Planner
• API
• Documentation
• Android Mobile App
• iOS Mobile App
• Processing Nodes Volunteer Network
• Unit Testing

Terminology

• 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, 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. 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.