OTB, the ORFEO Toolbox is a library of image processing algorithms developed by CNES in the frame of the ORFEO Accompaniment Program. OTB is based on the medical image processing library ITK, http://www.itk.org, and offers particular functionalities for remote sensing image processing in general and for high spatial resolution images in particular.
Many of these functionalities are provided by ITK and have been tested and documented for the use with remote sensing data.
You can get more information on OTB on the web at http://www.orfeo-toolbox.org.
ORFEO stands for Optical and Radar Federated Earth Observation. In 2001 a cooperation program was set between France and Italy to develop ORFEO, an Earth observation dual system with metric resolution: Italy is in charge of COSMO-Skymed the radar component development, and France of PLEIADES the optic component.
The PLEIADES optic component is composed of two ”small satellites” (mass of one ton) offering a spatial resolution at nadir of 0.7 m and a field of view of 20 km. Their great agility enables a daily access all over the world, essentially for defense and civil security applications, and a coverage capacity necessary for the cartography kind of applications at scales better than those accessible to SPOT family satellites. Moreover, PLEIADES have stereoscopic acquisition capacity to meet the fine cartography needs, notably in urban regions, and to bring more information when used with aerial photography.
The ORFEO ”targeted” acquisition capacities made it a system particularly adapted to defense or civil security missions, as well as critical geophysical phenomena survey such as volcanic eruptions, which require a priority use of the system resources.
With respect to the constraints of the Franco-Italian agreement, cooperation have been set up for the PLEIADES optical component with Sweden, Belgium, Spain and Austria.
At the PLEIADES HR web site: http://smsc.cnes.fr/PLEIADES/.
Beside the Pleiades (PHR) and Cosmo-Skymed (CSK) systems developments forming ORFEO, the dual and bilateral system (France - Italy) for Earth Observation, the ORFEO Accompaniment Program was set up, to prepare, accompany and promote the use and the exploitation of the images derived from these sensors.
The creation of a preparatory program is needed because of :
This program was initiated by CNES mid-2003 and will last until mid 2013. It consists in two parts, between which it is necessary to keep a strong interaction:
This Accompaniment Program uses simulated data (acquired during airborne campaigns) and satellite images quite similar to Pleiades (as QuickBird and Ikonos), used in a communal way on a set of special sites. The validation of specified products and services will be realized with Pleiades data
Apart from the initial cooperation with Italy, the ORFEO Accompaniment Program enlarged to Belgium, with integration of Belgian experts in the different WG as well as a participation to the methodological part.
Go to the following web site: http://smsc.cnes.fr/PLEIADES/A_prog_accomp.htm.
The French Centre National d’…tudes Spatiales, CNES, initiated the ORFEO Toolbox and is responsible for the specification of the library. CNES funds the industrial development contracts and research contracts needed for the evolution of OTB.
OTB is distributed under a CeCILL free software license:
http://www.cecill.info/licences/Licence_CeCILL_V2-en.html which is recognized by the Free Software Foundation. It can be considered similar to the GNU GPL license.
No. The license gives you the option to distribute your application if you want to. You do not have to exercise this option in the license.
No. The CeCILL license impose only to distribute the source of the application to your users.
The CeCILL license or the GNU GPL license.
OTB can be used internally (”in-house”) without restriction, but only redistributed in other software that is under the CeCILL license. Moreover you need to distribute the source of your application to your users and only them.
Anybody can download the OTB at no cost.
Go to http://www.orfeo-toolbox.org and follow the ”download OTB” link. You will have access to the OTB source code, to the Software User’s Guide and to the Cookbook of the last release. Binary packages are also provided for the current version. OTB and Monteverdi are also integrated in OSGeo-Live since version 4.5. You can find more information about the project at http://live.osgeo.org/. Moreover you can found the last release of Monteverdi and OTB applications through the OSGeo4W installer.
You can get the current development version, as our repository is public, using Mercurial (available at http://www.selenic.com/mercurial). Be aware that, even if the golden rule is what is committed will compile, this is not always the case. Changes are usually more than ten per day.
The first time, you can get the source code using:
Then you can build OTB as usual using this directory as the source (refer to build instructions).
Later if you want to update your source, from the OTB source directory, just do:
A simple make in your OTB binary directory will be enough to update the library (recompiling only the necessary stuff).
All information about OTB compilation can be found into the related section. We present here only the special issues which can be encountered.
On some Debian and Ubuntu versions, the system GDAL library and its tiff internal symbol might conflict with the system Tiff library (bugs.debian.org/558733). This is most likely the case if you get odd segmentation fault whenever trying to open a tiff image. This symbol clash happens when using OTB. A workaround to the issue has been provided in GDAL sources, but is available in the 1.9.0 release.
The recommended procedure is to get this recent source and build GDAL from sources, with the following configure command:
See section 2.2.2 of Software Guide for more information on this issue.
The internal version of libkml cannot be compiled when using an external build of ITK. See http://bugs.orfeo-toolbox.org/view.php?id=879 for more details.
To workaround the problem, either use an external build of libkml (it is provided on most systems), or use an internal build of ITK by setting to OFF the CMake variable OTB_USE_EXTERNAL_ITK.
To build OTB on Windows, we highly recommend using OSGeo4W which provides all the necessary dependencies.
Currently it is not possible to build OTB in Debug when using the dependencies provided by OSGeo4W. If you want to build OTB in Debug for Windows, you will need to build and install manually each dependency needed by OTB. You should use the same compiler for all the dependencies, as much as possible.
Therefore, we highly recommend you to use OSGeo4W shell environment to build OTB. You can use the 32 or 64 bit installer, since OSGeo4W provides all the necessary dependencies in the two cases. Please follow carefully the procedure provided in the Software Guide.
Typically, when using the dependencies provided by OSGeo4W, compile OTB in Release or RelWithDebInfo mode.
OTB presents a large set of features and it is not always easy to start using it. After the installation, you can proceed to the tutorials (in the Software Guide). This should give you a quick overview of the possibilities of OTB and will teach you how to build your own programs. You can also found some information in the OTB Cookbook in which we provide some recipes about remote sensing with OTB.
The maximum physical space a user can allocate depends on her platform. Therefore, image allocation in OTB is restricted by image dimension, size, pixel type and number of bands.
Fortunately, thanks to the streaming mechanism implemented within OTB’s pipeline (actually ITK’s), this limitation can be bypassed. The use of the otb::ImageFileWriter at the end of the pipeline, will seamlessly break the large, problematic data into small pieces whose allocation is possible. These pieces are processed one after the other, so that there is not allocation problem anymore. We are often working with images of 25000×25000 pixels.
For the streaming to work, all the filters in the pipeline must be streaming capable (this is the case for most of the filters in OTB). The output image format also need to be streamable (not PNG or JPEG, but TIFF or ENVI formats, for instance).
The class otb::ImageFileWriter manage the steaming process following two strategies: by tile or by strip. Different size configuration for these two strategies are available into the interface. The default mode use the information about how the file is streamed on the disk and will try to minimize the memory consumption along the pipeline. More information can be found into the documentation of the class.
Yes. There is a discussion group at http://groups.google.com/group/otb-users/ where you can get help on the set up and the use of OTB.
The main source of documentation is the OTB Software Guide which can be downloaded at http://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf. It contains tenths of commented examples and a tutorial which should be a good starting point for any new OTB user. The code source for these examples is distributed with the toolbox. Another information source is the on-line API documentation which is available at http://www.orfeo-toolbox.org/doxygen.
You can also find some information about how to use Monteverdi, Monteverdi2 and the OTB-Applications into the Cookbook at http://www.orfeo-toolbox.org/CookBook/.
There are many ways to join us in the OTB adventure. The more people contribute, the better the library is for everybody!
First, you can send an email to the user mailing list (email@example.com) to let us know what functionality you would like to introduce in OTB. If the functionality seems important for the OTB users, we will then discuss on how to retrieve your code, make the necessary adaptions, check with you that the results are correct and finally include it in the next release.
You can also run the nightly tests so we have a wider range of platforms to detect bugs earlier. Look at section 31.8.
You can also find more information about how to contribute at http://orfeo-toolbox.org/otb/contribute.html
Besides the satisfaction of contributing to an open source project, we will include the references to relevant papers in the software guide. Having algorithms published in the form of reproducible research helps science move faster and encourages people who needs your algorithms to use them.
You will also benefit from the strengths of OTB: multi-platform, streaming and threading, etc.
All functionalities which are useful for remote sensing data are of interest. As OTB is a library, it should be generic algorithms: change, detection, fusion, object detection, segmentation, interpolation, etc.
More specific applications can be contributed using the framework directly in the Applications directory of OTB.
OTB is an ever changing library, it is quite active and have scores of changes per day from different people. It would be a headache to make sure that the brand new improvement that you introduced didn’t break anything, if we didn’t have automated tests. You also have to take into account differences in OS, compilers, options, versions of external libraries, etc. By running the tests and submitting it to the dashboard, you will help us detect problems and fix them early.
For each class, at minimum there is a test which tries to instantiate it and another one which uses the class. The output of each test (image, text file, binary file) is controlled against a baseline to make sure that the result hasn’t changed.
All OTB tests source code are available in the directory Testing and are also good examples on how to use the different classes.
There is more than 2500 tests for OTB and it takes from 20 minutes to 3 hours to run all the test, mainly depending on your compilation options (Release mode does make a difference) and of course your hardware.
To run the tests, you first have to make sure that you set the option BUILD_TESTING to ON before building the library. If you want to modify it, just rerun ccmake, change the option, then make.
For some of the tests, you also need the test data and the baselines (see 31.8.3).
Once OTB is built with the tests, you just have to go to the binary directory where you built OTB and run ctest -N to have a list of all the tests. Just using ctest will run all the tests. To select a subset, you can do ctest -R Kml to run all tests related to kml files or ctest -I 1,10 to run tests from 1 to 10.
Data used for the tests are also versioned using Mercurial (see 31.3.3).
You can get the base doing:
This is about 1 GB of data, so it will take a while, but you have to do it only once, as after, a simple
will update you to the latest version of the repository.
You can also easily synchronize the directory you retrieve between different computers on your network, so you don’t have to get it several times from the main server. Check out Mercurial capabilities.
Once you know how to run the tests, you can also help us to detect the bugs or configuration problems specific to your configuration. As mentioned before, the possible combinations between OS, compiler, options, external libraries version is too big to be tested completely, but the more the better.
You just have to launch ctest with the -D Experimental switch. Hence:
And you will be able to see the result at
If you are interested in setting up a nightly test (automatically launched every night), please contact us and we will give you the details.
OTB’s version numbers have 3 digits. The first one is for major versions, the second one is for minor versions and the last one is for bugfixes.
The first version was 1.0.0 in July 2006. Version 1.2.0, 1.4.0 and 1.6.0 were released in between. The 2.0.0 major version was released in December 2007. The 2.2.0, 2.4.0 and 2.6.0 (Halloween) in June, July and November 2008 respectively. The 2.8.0 (Gong Xi Fa Cai) came out in January 2009, the 3.0.0 (Manh„ de Carnaval) in May 2009, the 3.2.0 (62∘38′35′′S 60∘14′31′′W) in January 2010, the 3.4.0 (Perl A Rebours) in July 2010, the 3.6.0 (California Dreamin’) in October 2010, the 3.8.0 (Pack Ice) in December 2010, the 3.10.0 (FeliÁ aniversari) in June 2011, the 3.12.0 (Πλϵlαϵζ) in February 2012, the 3.14.0 (Happy) in July 2012, the 3.14.1 in October 2012, the 3.16 () in February 2013 , the 3.18 (Seven years of Coding) in July 2013, the 3.18.1 in July 2013 and the 3.20 in November 2013 (... (and one more for the road)).
The current one is 4.0.0.
A major version of the library implies the addition of high-level functionalities as for instance image registration, object recognition, etc.
A minor version is released when low-level functionalities are available within one major functionality, as for instance a new change detector, a new feature extractor, etc.
A bugfix version is released when significant bugs are identified and fixed.
We plan to release two major new OTB version once a year. You can find some information into the roadmap section of the wiki
There is no detailed plan about the availability of OTB new features, since OTB’s content depends on ongoing research work and on feedback from thematic users of the ORFEO Accompaniment Program.
Nevertheless, the main milestones for the OTB development are the following:
You can find more information in the RELEASE_NOTES.txt.