Giter Club home page Giter Club logo

webodm's Introduction

ODM Logo

An open source command line toolkit for processing aerial drone imagery. ODM turns simple 2D images into:

  • Classified Point Clouds
  • 3D Textured Models
  • Georeferenced Orthorectified Imagery
  • Georeferenced Digital Elevation Models

images-diag

The application is available for Windows, Mac and Linux and it works from the command line, making it ideal for power users, scripts and for integration with other software.

If you would rather not type commands in a shell and are looking for a friendly user interface, check out WebODM.

Quickstart

The easiest way to run ODM on is via docker. To install docker, see docs.docker.com. Once you have docker installed and working, you can run ODM by placing some images (JPEGs or TIFFs) in a folder named “images” (for example C:\Users\youruser\datasets\project\images or /home/youruser/datasets/project/images) and simply run from a Command Prompt / Terminal:

# Windows
docker run -ti --rm -v c:/Users/youruser/datasets:/datasets opendronemap/odm --project-path /datasets project

# Mac/Linux
docker run -ti --rm -v /home/youruser/datasets:/datasets opendronemap/odm --project-path /datasets project

You can pass additional parameters by appending them to the command:

docker run -ti --rm -v /datasets:/datasets opendronemap/odm --project-path /datasets project [--additional --parameters --here]

For example, to generate a DSM (--dsm) and increase the orthophoto resolution (--orthophoto-resolution 2) :

docker run -ti --rm -v /datasets:/datasets opendronemap/odm --project-path /datasets project --dsm --orthophoto-resolution 2

Viewing Results

When the process finishes, the results will be organized as follows:

|-- images/
    |-- img-1234.jpg
    |-- ...
|-- opensfm/
    |-- see mapillary/opensfm repository for more info
|-- odm_meshing/
    |-- odm_mesh.ply                    # A 3D mesh
|-- odm_texturing/
    |-- odm_textured_model.obj          # Textured mesh
    |-- odm_textured_model_geo.obj      # Georeferenced textured mesh
|-- odm_georeferencing/
    |-- odm_georeferenced_model.laz     # LAZ format point cloud
|-- odm_orthophoto/
    |-- odm_orthophoto.tif              # Orthophoto GeoTiff

You can use the following free and open source software to open the files generated in ODM:

  • .tif (GeoTIFF): QGIS
  • .laz (Compressed LAS): CloudCompare
  • .obj (Wavefront OBJ), .ply (Stanford Triangle Format): MeshLab

Note! Opening the .tif files generated by ODM in programs such as Photoshop or GIMP might not work (they are GeoTIFFs, not plain TIFFs). Use QGIS instead.

API

ODM can be made accessible from a network via NodeODM.

Documentation

See http://docs.opendronemap.org for tutorials and more guides.

Forum

We have a vibrant community forum. You can search it for issues you might be having with ODM and you can post questions there. We encourage users of ODM to participate in the forum and to engage with fellow drone mapping users.

Windows Setup

ODM can be installed natively on Windows. Just download the latest setup from the releases page. After opening the ODM Console you can process datasets by typing:

run C:\Users\youruser\datasets\project  [--additional --parameters --here]

GPU Acceleration

ODM has support for doing SIFT feature extraction on a GPU, which is about 2x faster than the CPU on a typical consumer laptop. To use this feature, you need to use the opendronemap/odm:gpu docker image instead of opendronemap/odm and you need to pass the --gpus all flag:

docker run -ti --rm -v c:/Users/youruser/datasets:/datasets --gpus all opendronemap/odm:gpu --project-path /datasets project

When you run ODM, if the GPU is recognized, in the first few lines of output you should see:

[INFO]    Writing exif overrides
[INFO]    Maximum photo dimensions: 4000px
[INFO]    Found GPU device: Intel(R) OpenCL HD Graphics
[INFO]    Using GPU for extracting SIFT features

The SIFT GPU implementation is CUDA-based, so should work with most NVIDIA graphics cards of the GTX 9xx Generation or newer.

If you have an NVIDIA card, you can test that docker is recognizing the GPU by running:

docker run --rm --gpus all nvidia/cuda:10.0-base nvidia-smi

If you see an output that looks like this:

Fri Jul 24 18:51:55 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.82       Driver Version: 440.82       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |

You're in good shape!

See https://github.com/NVIDIA/nvidia-docker and https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#docker for information on docker/NVIDIA setup.

Native Install (Ubuntu 21.04)

You can run ODM natively on Ubuntu 21.04 (although we don't recommend it):

git clone https://github.com/OpenDroneMap/ODM
cd ODM
bash configure.sh install

You can then process datasets with ./run.sh /datasets/odm_data_aukerman

Native Install (MacOS)

You can run ODM natively on Intel/ARM MacOS.

First install:

  • Xcode 13 (not 14, there's currently a bug)
  • Homebrew

Then Run:

git clone https://github.com/OpenDroneMap/ODM
cd ODM
bash configure_macos.sh install

You can then process datasets with ./run.sh /datasets/odm_data_aukerman

This could be improved in the future. Helps us create a Homebrew formula.

Updating a native installation

When updating to a newer version of native ODM, it is recommended that you run:

bash configure.sh reinstall

to ensure all the dependent packages and modules get updated.

Build Docker Images From Source

If you want to rebuild your own docker image (if you have changed the source code, for example), from the ODM folder you can type:

docker build -t my_odm_image --no-cache .

When building your own Docker image, if image size is of importance to you, you should use the --squash flag, like so:

docker build --squash -t my_odm_image .

This will clean up intermediate steps in the Docker build process, resulting in a significantly smaller image (about half the size).

Experimental flags need to be enabled in Docker to use the --squash flag. To enable this, insert the following into the file /etc/docker/daemon.json:

{
   "experimental": true
}

After this, you must restart docker.

Video Support

Starting from version 3.0.4, ODM can automatically extract images from video files (.mp4, .mov, .lrv, .ts). Just place one or more video files into the images folder and run the program as usual. Subtitles files (.srt) with GPS information are also supported. Place .srt files in the images folder, making sure that the filenames match. For example, my_video.mp4 ==> my_video.srt (case-sensitive).

Developers

Help improve our software! We welcome contributions from everyone, whether to add new features, improve speed, fix existing bugs or add support for more cameras. Check our code of conduct, the contributing guidelines and how decisions are made.

Installation and first run

For Linux users, the easiest way to modify the software is to make sure docker is installed, clone the repository and then run from a shell:

$ DATA=/path/to/datasets ./start-dev-env.sh

Where /path/to/datasets is a directory where you can place test datasets (it can also point to an empty directory if you don't have test datasets).

Run configure to set up the required third party libraries:

(odmdev) [user:/code] master+* ± bash configure.sh reinstall

You can now make changes to the ODM source. When you are ready to test the changes you can simply invoke:

(odmdev) [user:/code] master+* ± ./run.sh --project-path /datasets mydataset

Stop dev container

 docker  stop odmdev

To come back to dev environement

change your_username to your username

docker start odmdev
docker exec -ti odmdev bash
su your_username

If you have questions, join the developer's chat at https://community.opendronemap.org/c/developers-chat/21

  1. Try to keep commits clean and simple
  2. Submit a pull request with detailed changes and test results
  3. Have fun!

Troubleshooting

The dev environment makes use of opendronemap/nodeodm by default. You may want to run docker pull opendronemap/nodeodm before running ./start-dev-env.sh to avoid using an old cached version.

In order to make a clean build, remove ~/.odm-dev-home and ODM/.setupdevenv.

Credits

ODM makes use of several libraries and other awesome open source projects to perform its tasks. Among them we'd like to highlight:

Citation

OpenDroneMap Authors ODM - A command line toolkit to generate maps, point clouds, 3D models and DEMs from drone, balloon or kite images. OpenDroneMap/ODM GitHub Page 2020; https://github.com/OpenDroneMap/ODM

Trademark

See Trademark Guidelines

webodm's People

Contributors

abizem avatar bluecamel avatar chris-bateman avatar danbjoseph avatar dependabot[bot] avatar diegoaces avatar gromain avatar hedo88th avatar holycowmp3 avatar islamheggy avatar kathenae avatar kikislater avatar manand881 avatar mateo3d avatar mojodna avatar nchamo avatar okaluza avatar patrickelectric avatar pierotofy avatar pmumby avatar projectbarks avatar pyup-bot avatar saijin-naib avatar saricicekibrahim avatar smathermather avatar tariqislam avatar usplm avatar vesnikos avatar vinsonliux avatar w-toguchi83 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

webodm's Issues

Processing error

Hi there
I am not sure if this error is related to webODM or the processig node

My setup is two different AWS instance (t2.medium) one running WebODM and the second one running Node-ODM, both installed with Dockers

Killed
[ERROR]   quitting cause: 
	/code/SuperBuild/install/bin/pmvs2 /var/www/data/813e7f99-16a8-4ec7-b5d8-edaa958957aa/pmvs/recon0/ option-0000
returned with code 35072.

any help will be very helpful

Upload Issue

if the upload is quicker than you are at providing a name / clicking "Save" then you are stuck where you cannot submit the job anymore ...

Python 2 or 3?

Before the project proceeds any further I would like to ask the developers which version of python the would consider using?

I would opt for python 3 as in my experience I see python 2 being slowly phased out in favor of 3 and virtually all geospatial libraries now they providing support for it.

Thoughts?

GCP interface integration

I currently skipped the parts of code to handle GCP files. This will need to be added at some point.

System Messaging

WebODM should keep a log of operations, such as when a task started getting processed, whether a task succeeded, whether a task failed and display these information in the menu bar.

Task Processing

WebODM should facilitate the creation and management of tasks.

Tasks represent processing steps required to convert a stack of photos (or video) into various ODM outputs.

Tasks contain these pieces of metadata:

  • ...
  • created timestamp
  • updated timestamp

Volumetric Measurements

It would be cool to have the ability to measure volumes directly from the map.

I think this could be approached in the following way:

  1. Load 3D points, cast them to polygonZ collection, use http://postgis.net/docs/ST_DelaunayTriangles.html to generate a TIN
  2. Create stored procedure that given a list of 2D points:

Should also add the possibility to specify a "Cut" or "Fill" property for concave/convex cases.

Error messages on install

Installed the Docker image on Windows 10 64-bit. In the terminal window are repeated error messages:

[##mwebapp exit with code 127 (where ## is an integer in the range 31 through 36)
No such file or directory[0m /usr/ bin/env: bash
No such file or directory/usr/ bin/env: bash
No such file or directory/usr/ bin/env: bash
(repeated a total of 10 times)

Looking at the webapp container log in Kitematic, the "No such file or directory/usr/ bin/env: bash" also shows up 11 times.

Took a while, but figured out how to open up the WebApp. Am processing a simple task, and it seems to be working. So are those error messages of concern?

Mission Planning

WebODM should facilitate the planning of missions.

Input:

  • area(s) to cover (polygon) - if multiple areas, treat as multiple missions?
  • angle(s) to take photos
  • altitude
  • hazards (is this a thing handled by mission planning software?)
  • camera specs
  • desired overlap
  • ...

Output:

  • 3D linestring representing flight path
  • [flight planning output]
  • ...

GDALRaster.transform increases file size

Geotiffs created using GDALRaster.transform result in large files because of lack of compression. Perhaps where necessary we should call gdal_translate -co compress=DEFLATE input.tif output.tif (or the equivalent using the python API).

Unit Test nodeodm/client_api.py

Suggested approach since it involves communication with a third party component (node-OpenDroneMap).

  1. Create python server stub from node-OpenDroneMap's OpenAPI definition (swagger.json).
  2. Call client_api.py methods to test results.

Keeping track of state history

Leaving the dashboard and pressing the back button on the browser currently loses the application's state. This should be fixed with something like react-history.

Switch to Python 3

Once library requirements have been assessed, change Python version from 2 to 3.

Should Celery be used here?

In regard to a discussion which began here: #40 (review)

Is scheduler.py code reinventing the wheel (functionality that already exists in Celery)?

In essence it [the code] is replicating some of the Celery features (it is a task processing queue). What is driving me to re-implement this mechanism is that so far, the task processing involves more than a single processing step (think input images in ---> assets out). Maybe I'm over-thinking it, but so far I found these cases where Celery does not seem like it would fare so well.

  1. Input images in --> assets are not what I expected. I should be able to restart the process without re-sending the images, just by changing the processing options

  2. Console output: how to retrieve real-time console output from the opendronemap process?

  3. How to protect processing nodes (authentication) without making it difficult to setup? Ideally a processing node should be (optionally) protected by a static token, or a userID/password combination that generates a temporary token. The docs here hint at using public/private key exchange for security: http://docs.celeryproject.org/en/latest/userguide/security.html (I'm not sure I'd want to go down that route)

Create Docker Startup Script

Some people are experiencing issues using Docker when rebuilding images.

A script should be created to handle the following tasks:

  • Start WebODM
  • Stop WebODM
  • Rebuild From Scratch Images, ignoring cache and removing the proper volumes.

postgresql-9.5-postgis-2.3 installation failed

Hi,

I upgraded my system to Ubuntu 16.10, and I can't get WebODM to run.
I'm getting this error :
E: Version '2.3.0+dfsg-2.pgdg80+1' for 'postgresql-9.5-postgis-2.3' was not found E: Version '2.3.0+dfsg-2.pgdg80+1' for 'postgresql-9.5-postgis-2.3-scripts' was not found E: Version '2.3.0+dfsg-2.pgdg80+1' for 'postgis' was not found ERROR: Service 'db' failed to build: The command '/bin/sh -c apt-get update && apt-get install -y --no-install-recommends postgresql-$PG_MAJOR-postgis-$POSTGIS_MAJOR=$POSTGIS_VERSION postgresql-$PG_MAJOR-postgis-$POSTGIS_MAJOR-scripts=$POSTGIS_VERSION postgis=$POSTGIS_VERSION && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

Should I change something in the db/Dockerfile ?

Thank you.

Use React

The dashboard is going to be a client side app using React that uses the API.

Elevation Model

It would be cool to have the ability to display an automatically generated elevation model along with the orthophoto.

@smathermather how would you go about generating an elevation model from the current outputs of opendronemap (lastools come to mind, but they aren't OSS)?

Task stuck on running

Processing the odm_data_bellus dataset with --resize-to 1800 option, the task remains stuck on running. node-OpenDroneMap successfully processed the images.

Fail when run start.sh

Ciao Piero,

Iḿ trying run WebODM from start.sh, but the following errors are listed :

emilio@emilio-laptop:/opt/WebODM$ ./start.sh
Building asssets...
Hash: bcdca8dde46cb9609cf5
Version: webpack 1.13.3
Time: 52662ms
Asset Size Chunks Chunk Names
main-bcdca8dde46cb9609cf5.js 1.9 MB 0 [emitted] main
css/main.css 41.3 kB 0 [emitted] main
[0] multi main 28 bytes {0} [built]
+ 255 hidden modules

WARNING in .//leaflet-measure/dist/leaflet-measure.js
Critical dependencies:
1:113-120 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
@ ./
/leaflet-measure/dist/leaflet-measure.js 1:113-120
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 6 hidden modules
Child extract-text-webpack-plugin:
+ 5 hidden modules
Child extract-text-webpack-plugin:
+ 14 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Child extract-text-webpack-plugin:
+ 2 hidden modules
Running migrations
Traceback (most recent call last):
File "manage.py", line 22, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/init.py", line 367, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/dist-packages/django/core/management/init.py", line 341, in execute
django.setup()
File "/usr/local/lib/python2.7/dist-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models(all_models)
File "/usr/local/lib/python2.7/dist-packages/django/apps/config.py", line 199, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/opt/WebODM/app/models.py", line 23, in
from nodeodm.models import ProcessingNode
File "/opt/WebODM/nodeodm/models.py", line 10, in
from .api_client import ApiClient
File "/opt/WebODM/nodeodm/api_client.py", line 9, in
from urllib.parse import urlunparse
ImportError: No module named parse
Unhandled exception in thread started by <function wrapper at 0x7fbf61b15848>
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/django/utils/autoreload.py", line 226, in wrapper
fn(args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/runserver.py", line 113, in inner_run
autoreload.raise_last_exception()
File "/usr/local/lib/python2.7/dist-packages/django/utils/autoreload.py", line 249, in raise_last_exception
six.reraise(
_exception)
File "/usr/local/lib/python2.7/dist-packages/django/utils/autoreload.py", line 226, in wrapper
fn(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models(all_models)
File "/usr/local/lib/python2.7/dist-packages/django/apps/config.py", line 199, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/opt/WebODM/app/models.py", line 23, in
from nodeodm.models import ProcessingNode
File "/opt/WebODM/nodeodm/models.py", line 10, in
from .api_client import ApiClient
File "/opt/WebODM/nodeodm/api_client.py", line 9, in
from urllib.parse import urlunparse
ImportError: No module named parse

Grazie mille.

Emilio Bruno

User Interface

The WebODM user interface needs to surface the following functionality:

  • task management - creation and status
  • model display - allow orthophotos + 3D models to be browsed
  • cluster management - ???
  • mission planning - is there existing FOSS for this?
  • documentation

@pierotofy can you clarify what you're thinking around cluster management?

I'm also thinking that model display and mission planning might be better suited as their own applications, integrating with the WebODM API according to their needs.

Thoughts?

2D Model Display

ODM-generated orthophotos should be browsable using a Leaflet-like interface.

Needs:

  • TMS endpoint as TileJSON or a standard URL template
  • geographic extent (potentially in TileJSON)
  • zoom extent (potentially in TileJSON)
  • ...

Ability to overwrite default settings.

An ability to overwrite the default settings is usefull in numerous occasions.

This can be implemented easily by appending :

try:
from .local_settings import *
except ImportError:
pass

ofcourse local_settings.py should be added in .gitignore as well

Add default node-OpenDroneMap instance in Docker compose

Many people are experiencing issues setting up a processing node manually using docker (because of the intricacies of docker).

I will add a docker-compose file and supporting configuration to setup automatically a processing node as part of the docker compose up command.

Communication with node-OpenDroneMap

In the next few weeks I'll dedicate some time to write the code necessary to create new ProcessingNode instances and have them communicate with https://github.com/pierotofy/node-OpenDroneMap. I will likely spend some time tweaking node-OpenDroneMap to take care of authorization issues and to make the process of setting up new `ProcessingNode instances easy.

After careful evaluation, I think I will not add Celery as discussed in chat to the mix; the additional complexity added by Celery does not seem to simplify much the problem of distributing tasks to multiple nodes. This is particularly true because the number of processing tasks that we can expect are not many, so I think a simpler cron-like lib, with some custom logic, a priority queue and basic error handling/retry will serve the purpose (hopefully) better.

Worker Process

Need to create a thread / cronjob that performs the following:

  • Checks for tasks that need to be processed, and starts processing
  • Updates processing node info

Processing of lots of images fails in timeout

File "C:\Users\piero\Desktop\WebODM\nodeodm\api_client.py", line 64, in new_task
data={'name': name, 'options': json.dumps(options)}).json()
File "C:\Users\piero\webodm\lib\site-packages\requests\api.py", line 110, in post
return request('post', url, data=data, json=json, **kwargs)
File "C:\Users\piero\webodm\lib\site-packages\requests\api.py", line 56, in request
return session.request(method=method, url=url, **kwargs)
File "C:\Users\piero\webodm\lib\site-packages\requests\sessions.py", line 475, in request
resp = self.send(prep, **send_kwargs)
File "C:\Users\piero\webodm\lib\site-packages\requests\sessions.py", line 596, in send
r = adapter.send(request, **kwargs)
File "C:\Users\piero\webodm\lib\site-packages\requests\adapters.py", line 473, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', TimeoutError(10060, 'A connection attempt failed because the connected party did not properly respond a

requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', TimeoutError(10060, 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond', None, 10060, None))

Newbie Help

Hi! Such a great work! I'm very interested in the project, however I can't managed to make it work yet. When I launch the web interface and add a task, system says "There are no processing nodes available. Make sure at least one of them is reachable.". How can I create a processing node? I thought this was already included with this interface, but I was mistaken. Is there any tutorial available or walktrough process from the image loading to the final orthomosaic? A little help would be nice. Thanks in advance! Cheers!

Remove Fixtures, create base test class

Fixtures are a little problematic due to the fact that we catch signals and have first run initialization commands that do not play well with fixtures.

  1. Remove test_projects and test_users
  2. Create base class for tests that calls boot code
  3. Make all tests inherit from such base class
  4. Create test data programmatically via .create()

Free Processing Nodes Volunteer Network

At some point it could be beneficial to create a basic infrastructure for allowing people to donate server resources to process maps.

It could be as simple as having volunteers install the processing software, having a sign-up form, a web page with the list of volunteers, and some code to check which nodes are online.

Install - step 13 run curl failure

Ran into this issue while running docker-compose up

Step 13 : RUN curl --silent --location https://deb.nodesource.com/setup_6.x | sudo bash -
 ---> Running in 6537e09cc0d5
/bin/sh: 1: sudo: not found
ERROR: Service 'webapp' failed to build: The command '/bin/sh -c curl --silent --location https://deb.nodesource.com/setup_6.x | sudo bash -' returned a non-zero code: 127

My specs:

  • Ubuntu 14.04 server
dmb2@OpenDroneMap:~/WebODM$ docker version
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 22:00:36 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 22:00:36 2016
 OS/Arch:      linux/amd64
dmb2@OpenDroneMap:~/WebODM$ docker-compose --version
docker-compose version 1.8.1, build 878cff1

One Click Installer

Although this is something to do toward the end, the Docker command line is still too confusing for many GIS technicians; there's going to be a need for a graphical installer.

Image Upload + Project/Task creation

Somewhat linked to #21, there's going to be a button for uploading images directly from the dashboard. This will in turn automatically create the first project and task. These are all shortcuts for the sake of ease of use, and a more in depth project and task management UI will be created.

Docker

I'm currently working to add support for initializing a working environment in Docker. This will make it easier for people to contribute and will allow users to get started more quickly.

Will also add instructions in the readme.

API

WebODM should implement the following endpoints:

  • authorization
  • list projects (Project) ☑️
    • [filtered by User] ☑️
    • [filtered by Group]
    • [filtered by geographic extent]
  • list tasks (Task) ☑️
  • create tasks (Task) ☑️
  • update tasks (Task) ☑️
  • list/add/change processing nodes ☑️
  • ability to start/stop processing a Task☑️
  • get project info ☑️
    • TileJSON / equivalent
    • 3D model stuff
  • create project ☑️
  • create mission
  • get mission info
  • ...

3D Model Display

ODM-generated 3D models should be browsable using a Cesium-like interface.

Needs display and manipulation of the following:

  • Point clouds
  • Textured Mesh

Show image previews

Once a task is done being processed, it would be nice for the user to see a preview and orthophoto extent information directly on the dashboard panel without opening the map.

Check CSS styling for admin area

Some formatting issues are still present in the administration area (due to collision with the bootstrap theme and the default admin CSS).

The admin area should be checked and fixes should be applied where necessary.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.