5. FOREWORD
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 program1 is needed because of:
• the new capabilities and performances of the ORFEO systems (optical and radar high resolu-
tion, access capability, data quality, possibility to acquire simultaneously in optic and radar),
• the implied need of new methodological developments : new processing methods, or adapta-
tion of existing methods,
• the need to realise those new developments in very close cooperation with the final users for
better integration of new products in their systems.
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:
• A Thematic part,
• A Methodological part.
The Thematic part covers a large range of applications (civil and defence), and aims at specifying and
validating value added products and services required by end users. This part includes consideration
about products integration in the operational systems or processing chains. It also includes a careful
thought on intermediary structures to be developed to help non-autonomous users. Lastly, this part
aims at raising future users awareness, through practical demonstrations and validations.
1http://smsc.cnes.fr/PLEIADES/A prog accomp.htm
6. iv
The Methodological part objective is the definition and the development of tools for the operational
exploitation of the submetric optic and radar images (tridimensional aspects, changes detection,
texture analysis, pattern matching, optic radar complementarities). It is mainly based on R&D
studies and doctorate and post-doctorate researches.
In this context, CNES2 decided to develop the ORFEO ToolBox (OTB), a set of algorithms encapsu-
lated in a software library. The goals of the OTB is to capitalise a methological savoir faire in order
to adopt an incremental development approach aiming to efficiently exploit the results obtained in
the frame of methodological R&D studies.
All the developments are based on FLOSS (Free/Libre Open Source Software)
or existing CNES developments. OTB is distributed under the C´eCILL licence,
http://www.cecill.info/licences/Licence_CeCILL_V2-en.html.
OTB is implemented in C++ and is mainly based on ITK3 (Insight Toolkit).
2http://www.cnes.fr
3http://www.itk.org
37. CHAPTER
ONE
WELCOME
Welcome to the ORFEO ToolBox (OTB) Software Guide.
This document presents the essential concepts used in OTB. It will guide you through the road
of learning and using OTB. The Doxygen documentation for the OTB application programming
interface is available on line at http://orfeo-toolbox.sourceforge.net/Doxygen/html.
1.1 Organization
This software guide is divided into several parts, each of which is further divided into several chap-
ters. Part I is a general introduction to OTB, with—in the next chapter—a description of how to
install the ORFEO Toolbox on your computer. Part I also introduces basic system concepts such
as an overview of the system architecture, and how to build applications in the C++ programming
language. Part II is a short guide with gradual difficulty to get you start programming with OTB.
Part III describes the system from the user point of view. Dozens of examples are used to illustrate
important system features. Part IV is for the OTB developer. It explains how to create your own
classes and extend the system.
1.2 How to Learn OTB
There are two broad categories of users of OTB. First are class developers, those who create classes
in C++. The second, users, employ existing C++ classes to build applications. Class developers
must be proficient in C++, and if they are extending or modifying OTB, they must also be familiar
with OTB’s internal structures and design (material covered in Part IV).
The key to learning how to use OTB is to become familiar with its palette of objects and the ways
of combining them. We recommend that you learn the system by studying the examples and then,
if you are a class developer, study the source code. Start by the first few tutorials in Part II to get
38. 4 Chapter 1. Welcome
familiar with the build process and the general program organization, follow by reading Chapter 3,
which provides an overview of some of the key concepts in the system, and then review the exam-
ples in Part III. You may also wish to compile and run the dozens of examples distributed with the
source code found in the directory OTB/Examples. (Please see the file OTB/Examples/README.txt
for a description of the examples contained in the various subdirectories.) There are also several
hundreds of tests found in the source distribution in OTB/Testing/Code, most of which are mini-
mally documented testing code. However, they may be useful to see how classes are used together
in OTB, especially since they are designed to exercise as much of the functionality of each class as
possible.
1.3 Software Organization
The following sections describe the directory contents, summarize the software functionality in each
directory, and locate the documentation and data.
1.3.1 Obtaining the Software
Periodic releases of the software are available on the OTB Web site. These official releases are
available a few times a year and announced on the ORFEO Web pages and mailing lists.
This software guide assumes that you are working with the latest official OTB release (available on
the OTB Web site).
1.4 Downloading OTB
OTB can be downloaded without cost from the following web site:
http://www.orfeo-toolbox.org/
In order to track the kind of applications for which OTB is being used, you will be asked to complete
a form prior to downloading the software. The information you provide in this form will help
developers to get a better idea of the interests and skills of the toolkit users.
Once you fill out this form you will have access to the download page. This page can be book
marked to facilitate subsequent visits to the download site without having to complete any form
again.
Then choose the tarball that better fits your system. The options are .zip and .tgz files. The
first type is better suited for MS-Windows while the second one is the preferred format for UNIX
systems.
39. 1.4. Downloading OTB 5
Once you unzip or untar the file, a directory called OTB will be created in your disk and you will be
ready for starting the configuration process described in Section 2.2.3 on page 18.
You can also get the current version following instructions in Section 32.3.3, on page 667.
1.4.1 Join the Mailing List
It is strongly recommended that you join the users mailing list. This is one of the primary resources
for guidance and help regarding the use of the toolkit. You can subscribe to the users list online at
http://groups.google.com/group/otb-users
The otb-users mailing list is also the best mechanism for expressing your opinions about the toolbox
and to let developers know about features that you find useful, desirable or even unnecessary. OTB
developers are committed to creating a self-sustaining open-source OTB community. Feedback from
users is fundamental to achieving this goal.
1.4.2 Directory Structure
To begin your OTB odyssey, you will first need to know something about OTB’s software organiza-
tion and directory structure. It is helpful to know enough to navigate through the code base to find
examples, code, and documentation.
OTB is organized into several different modules. There are three: the OTB, OTB-Documents and
OTB-Wrapping modules. The source code, examples and applications are found in the OTB module;
documentation, tutorials, and material related to the design and marketing of OTB are found in
OTB-Documents; and resources to wrap OTB classes into other languages (such as Java or Python)
are available from OTB-Wrapping. Usually you will work with the OTB module unless you are a
developer, are teaching a course, or are looking at the details of various design documents.
The OTB module contains the following subdirectories:
• OTB/Code—the heart of the software; the location of the majority of the source code.
• OTB/Applications—a set of applications modules that can be launched in different ways
(command-line, graphical interface, Python/Java), refer to the OTB Cookbook for more infor-
mation
• OTB/CMake—internal files used during the configuration process
• OTB/Copyright—the copyright information of OTB and all the dependencies included in the
OTB source tree
• OTB/Examples—a suite of simple, well-documented examples used by this guide and to il-
lustrate important OTB concepts.
40. 6 Chapter 1. Welcome
• OTB/Testing—a large number of small programs used to test OTB. These examples tend to
be minimally documented but may be useful to demonstrate various system concepts.
• OTB/Utilities—supporting software for the OTB source code. For example, libraries such
as ITK.GDAL.
The source code directory structure—found in OTB/Code—is important to understand since other
directory structures (such as the Testing directory) shadow the structure of the OTB/Code directory.
• OTB/Code/ApplicationEngine—the core library for building applications based on OTB
• OTB/Code/Common—core classes, macro definitions, typedefs, and other software constructs
central to OTB.
• OTB/Code/BasicFilters—basic image processing filters.
• OTB/Code/Fusion—image fusion algorithms, as for instance, pansharpening.
• OTB/Code/FeatureExtraction—the location of many feature extraction algorithms.
• OTB/Code/ChangeDetection—a set of remote sensing image change detection algorithms.
• OTB/Code/DisparityMap—tools for estimating disparities – deformations – between im-
ages.
• OTB/Code/Fuzzy—fuzzy logic based algorithms, with Dempster-Shaffer theory related
classes
• OTB/Code/GeospatialAnalysis—classes allowing to connect to geospatial database like
PostGIS.
• OTB/Code/Gui—very basic widgets for building graphical user interfaces, such as progress
bars for filters, etc.
• OTB/Code/Hyperspectral—hyperspectral images analysis
• OTB/Code/IO—classes that support the reading and writing of data.
• OTB/Code/Learning—several functionnalities for supervised learning and classification.
• OTB/Code/Markov—implementation of Markov Random Fields regularization and segmen-
tation.
• OTB/Code/MultiScale—a set of functionalities for multiscale image analysis and synthesis.
• OTB/Code/MultiTemporal—time series interpolation related algorithms
• OTB/Code/OBIA—Object Based Image Analysis filters and data structures
• OTB/Code/ObjectDetection—Object detection chain based on local feature extraction
41. 1.4. Downloading OTB 7
• OTB/Code/Projections—classes allowing to deal with sensor models and cartographic pro-
jections.
• OTB/Code/Radiometry—classes allowing to compute vegetation indices and radiometric
corrections.
• OTB/Code/SARPolarimetry—some add-ons for SAR polarimetry synthesis and analysis.
• OTB/Code/Segmentation—several functionnalities for image segmentation.
• OTB/Code/Simulation—Sensor simulator
• OTB/Code/SpatialReasoning—several functionnalities high level image analysis using
spatial reasoning techniques.
• OTB/Code/Testing—internal classes used in the used in the testing framework
• OTB/Code/Visualization—utilities for simple image visualization.
• OTB/Code/Wrappers—wrappers of applications in several access points (command-line, QT
Gui, SWIG...).
The OTB-Documents module contains the following subdirectories:
• OTB-Documents/CourseWare—material related to teaching OTB.
• OTB-Documents/Latex—LATEX styles to produce this work as well as other documents.
• OTB-Documents/SoftwareGuide—LATEX files used to create this guide. (Note that the code
found in OTB/Examples is used in conjunction with these LATEX files.)
1.4.3 Documentation
Besides this text, there are other documentation resources that you should be aware of.
Doxygen Documentation. The Doxygen documentation is an essential resource when working
with OTB. These extensive Web pages describe in detail every class and method in the
system. The documentation also contains inheritance and collaboration diagrams, listing
of event invocations, and data members. The documentation is heavily hyper-linked to
other classes and to the source code. The Doxygen documentation is available on-line at
http://www.orfeo-toolbox.org/doxygen/.
Header Files. Each OTB class is implemented with a .h and .cxx/.txx file (.txx file for templated
classes). All methods found in the .h header files are documented and provide a quick way to
find documentation for a particular method. (Indeed, Doxygen uses the header documentation
to produces its output.)
42. 8 Chapter 1. Welcome
1.4.4 Data
The OTB Toolkit was designed to support the ORFEO Acompaniment Program and its associated
data. This data is available at http://smsc.cnes.fr/PLEIADES/index.htm.
1.5 The OTB Community and Support
OTB was created from its inception as a collaborative, community effort. Research, teaching, and
commercial uses of the toolkit are expected. If you would like to participate in the community, there
are a number of possibilities.
• Users may actively report bugs, defects in the system API, and/or submit feature requests.
Currently the best way to do this is through the OTB users mailing list.
• Developers may contribute classes or improve existing classes. If you are a developer, you
may request permission to join the OTB developers mailing list. Please do so by sending
email to otb “at” cnes.fr. To become a developer you need to demonstrate both a level of
competence as well as trustworthiness. You may wish to begin by submitting fixes to the OTB
users mailing list.
• Research partnerships with members of the ORFEO Acompaniment Program are encouraged.
CNES will encourage the use of OTB in proposed work and research projects.
• Educators may wish to use OTB in courses. Materials are being developed for this purpose,
e.g., a one-day, conference course and semester-long graduate courses. Watch the OTB web
pages or check in the OTB-Documents/CourseWare directory for more information.
1.6 A Brief History of OTB
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 program1 is needed because of :
• the new capabilities and performances of the ORFEO systems (optical and radar high resolu-
tion, access capability, data quality, possibility to acquire simultaneously in optic and radar),
• the implied need of new methodological developments : new processing methods, or adapta-
tion of existing methods,
1http://smsc.cnes.fr/PLEIADES/A prog accomp.htm
43. 1.6. A Brief History of OTB 9
• the need to realise those new developments in very close cooperation with the final users for
better integration of new products in their systems.
This program was initiated by CNES mid-2003 and will last until 2010 at least It consists in two
parts, between which it is necessary to keep a strong interaction :
• A Thematic part
• A Methodological part.
The Thematic part covers a large range of applications (civil and defence ones), and aims at spec-
ifying and validating value added products and services required by end users. This part includes
consideration about products integration in the operational systems or processing lines. It also in-
cludes a careful thought on intermediary structures to be developed to help non-autonomous users.
Lastly, this part aims at raising future users awareness, through practical demonstrations and valida-
tions.
The Methodological part objective is the definition and the development of tools for the operational
exploitation of the future submetric optic and radar images (tridimensional aspects, change detec-
tion, texture analysis, pattern matching, optic radar complementarities). It is mainly based on R&D
studies and doctorate and post-doctorate research.
In this context, CNES2 decided to develop the ORFEO ToolBox (OTB), a set of algorithms encapsu-
lated in a software library. The goals of the OTB is to capitalise a methological savoir faire in order
to adopt an incremental development approach aimin to efficiently exploit the results obtained in the
frame of methodological R&D studies.
All the developments are based on FLOSS (Free/Libre Open Source Software) or existing CNES
developments.
OTB is implemented in C++ and is mainly based on ITK3 (Insight Toolkit):
• ITK is used as the core element of OTB
• OTB classes inherit from ITK classes
• The software development procedure of OTB is strongly inspired from ITK’s (Extreme Pro-
gramming, test-based coding, Generic Programming, etc.)
• The documentation production procedure is the same as for ITK
• Several chapters of the Software Guide are litterally copied from ITK’s Software Guide (with
permission).
• Many examples are taken from ITK.
2http://www.cnes.fr
3http://www.itk.org
44. 10 Chapter 1. Welcome
1.6.1 ITK’s history
In 1999 the US National Library of Medicine of the National Institutes of Health awarded six
three-year contracts to develop an open-source registration and segmentation toolkit, that eventu-
ally came to be known as the Insight Toolkit (ITK) and formed the basis of the Insight Software
Consortium. ITK’s NIH/NLM Project Manager was Dr. Terry Yoo, who coordinated the six prime
contractors composing the Insight consortium. These consortium members included three com-
mercial partners—GE Corporate R&D, Kitware, Inc., and MathSoft (the company name is now
Insightful)—and three academic partners—University of North Carolina (UNC), University of Ten-
nessee (UT) (Ross Whitaker subsequently moved to University of Utah), and University of Penn-
sylvania (UPenn). The Principle Investigators for these partners were, respectively, Bill Lorensen
at GE CRD, Will Schroeder at Kitware, Vikram Chalana at Insightful, Stephen Aylward with Luis
Ib´a˜nez at UNC (Luis is now at Kitware), Ross Whitaker with Josh Cates at UT (both now at Utah),
and Dimitri Metaxas at UPenn (now at Rutgers). In addition, several subcontractors rounded out the
consortium including Peter Raitu at Brigham & Women’s Hospital, Celina Imielinska and Pat Mol-
holt at Columbia University, Jim Gee at UPenn’s Grasp Lab, and George Stetten at the University of
Pittsburgh.
In 2002 the first official public release of ITK was made available.
45. CHAPTER
TWO
INSTALLATION
This section describes the process for installing OTB on your system. OTB is a toolbox, and as such,
once it is installed in your computer, provides by default a set of useful libraries. You can use these
libraries to build your own applications based on it. What OTB does provide, besides the toolbox,
is a large set of test files and examples that will introduce you to OTB concepts and will show you
how to use OTB in your own projects.
Since the release 3.12, OTB embeds a specific framework to generate applications in a more user-
friendly way. If you activate the specific option BUILD APPLICATIONS, OTB builds for each appli-
cation one shared library (also known as plugin). This plugin can be auto-loaded into appropriate
tools without recompiling, and is able to fully describe its own parameters, behaviour and documen-
tation.
The tools to use these plugins can be extended, but OTB is shipped with the following:
• A command-line launcher,
• A graphical launcher, with an auto-generated Qt interface, providing ergonomic parameters
setting, display of documentation, and progress reporting,
• A C and SWIG interface, which means that any application can be loaded, set up and executed
into a high-level language such as Python for instance.
The classical OTB powered applications are still available and will still be maintained:
Monteverdi An integrated application giving graphical access to a lot of OTB functionalities.
OTB-Wrapping Calling OTB from Python or Java (see chapter 34).
There are two ways to install OTB on your system: installing from a binary distribution, or compiling
from sources (Table 2.1). What you need depends on your system, and on what you intend to do.
46. 12 Chapter 2. Installation
OTB library and
internal applica-
tions
Monteverdi Wrapping (Java
and Python)
Any platform Build from source
(see section 2.2)
Build from source
(see section 2.2)
Build from source
(see section 2.2)
Windows 2000/X-
P/Vista/Seven
OSGeo4W installer
for internal applica-
tions
Windows or OS-
Geo4W installer
(see section 2.1.1)
OSGeo4W installer
(see section 2.1.1)
MacOS X 10.6 and
higher
MacPorts (see sec-
tion 2.1.2)
app’s DMG file (see
section 2.1.2)
Ubuntu Linux
10.04 and higher
(32/64 bits)
APT repository (see
section 2.1.3)
APT repository (see
section 2.1.3)
OpenSuse 11.X
and higher (32/64
bits)
RPM package (see
section 2.1.3)
RPM package (see
section 2.1.3)
CentOS 6.X and
higher (32/64 bits)
RPM package (see
section 2.1.3)
RPM package (see
section 2.1.3)
RPM package (see
section 2.1.3)
Table 2.1: Available installation procedures with respect to system configuration and target usage
2.1 Installing binary packages
2.1.1 Windows 2000/XP/Vista/Seven
For Windows 2000/XP/Vista/Seven users, there is a classical standalone installation program for
Monteverdi, available from the OTB download page. There are another way to install Monteverdi
directly through through OSGeo4W. With this new way, you can install other OTB packages as
described in the following paragraph.
Since version 3.12, we provide OTB packages through OSGeo4W for Windows 2000/XP/Vista/-
Seven users. Packages for the OTB applications, Monteverdi and OTB-Wrapping are available
directly in the OSGeo4W installer with the following names:
• otb-bin for command line and QT applications
• otb-python for python applications
• otb-monteverdi for the Monteverdi application
• otb-wrapping for low level Python/Java bindings.
Follow the instructions in the installer and select the packages you want to add. The installer will
proceed with the installation of selected packages and all their dependencies. In the case of otb-
monteverdi, Monteverdi will be directly installed in the OSGeo4W repository and a shortcut will
47. 2.1. Installing binary packages 13
be added to your desktop and in the start menu (in the OSGeo4W folder). You can now use directly
Monteverdi from your desktop, from the start menu and from an OSGeo4W shell with command
monteverdi. For the otb-bin packages, it will be available directly in the OSGeo4W shell, for
example run
otbgui_BandMath.
We recommended to use this way to install internal applications of OTB on Windows. If you want
to use the otb-python package, for example in QGIS, please following the install note found in the
OTB wiki. You can simply check from an OSGeo4W shell the list of available applications:
python
import otbApplication
print str( otbApplication.Registry.GetAvailableApplications() )
For more information you can read the OTB Cookbook which provides useful information about
these OTB applications.
2.1.2 MacOS X
Orfeo Toolbox is now available on MacPorts. The port name is called orfeotoolbox. You can follow
the MacPorts documentation to install MacPorts first, then install the orfeotoolbox port.
A standard DMG package is available for Monteverdi for MacOS X 10.8. Please go the the
OTB download page. Click on the file to launch Monteverdi.
2.1.3 Linux
Ubuntu 10.04 and higher
For Ubuntu 10.04 and higher, OTB, OTB applications, Monteverdi and OTB-Wrapping packages
may be available as Debian packages through APT repositories.
Since release 3.14.1, OTB packages are available in the ubuntugis-unstable repository.
You can add it by using these command-lines:
sudo aptitude install add-apt-repository
sudo apt-add-repository ppa:ubuntugis/ubuntugis-unstable
Now run:
sudo aptitude update
48. 14 Chapter 2. Installation
If you want only OTB libraries, please use:
sudo aptitude install libotb
If you want OTB Applications, please use:
sudo aptitude install otb-bin otb-bin-qt python-otb
If you want monteverdi application, please use:
sudo aptitude install monteverdi
If you want Python/Java wrapping, please use:
sudo aptitude install otb-wrapping-python otb-wrapping-java
If you are using Synaptic, you can add the repositories, update and install the packages through the
graphical interface.
For further informations about Ubuntu packages go to ubuntugis-unstable launchpad page and click
on Read about installing.
Moreover, nightly builds for all OTB projects are also available through APT repositories. However
you should use it carefully. If you are using apt command-line tools, use these command-lines to
add the otb repository to apt sources:
sudo aptitude install add-apt-repository
sudo add-apt-repository ppa:otb/orfeotoolbox-nightly
Now run:
sudo aptitude update
As with the previous cases, select which packages you will install.
sudo aptitude install libotb otb-bin otb-bin-qt python-otb monteverdi
Be careful not to add the two repositories, since they may cause incompatibilities.
apt-add-repository will try to retrieve the GPG keys of the repositories to certify the origin of the
packages. If you are behind a http proxy, this step won’t work and apt-add-repository will stall and
eventually quit. You can temporarily ignore this error and proceed with the update step. Following
this, aptitude update will issue a warning about a signature problem. This warning won’t prevent
you from installing the packages.
49. 2.1. Installing binary packages 15
OpenSuse 11.X and higher
For OpenSuse 11.X and higher, OTB, Monteverdi and OTB-Wrapping packages are available
through zypper.
First, you need to add the appropriate repositories with these command-lines (please replace 11.4
by your OpenSuse version):
sudo zypper ar
http://download.opensuse.org/repositories/games/openSUSE_11.4/ Games
sudo zypper ar
http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.4/ GEO
sudo zypper ar
http://download.opensuse.org/repositories/home:/tzotsos/openSUSE_11.4/ tzotsos
Now run:
sudo zypper refresh
sudo zypper install OrfeoToolbox
sudo zypper install OrfeoToolbox-devel
sudo zypper install Monteverdi
sudo zypper install OrfeoToolbox-python
Alternatively you can use the One-Click Installer from the openSUSE Download page or add the
above repositories and install through Yast Package Management.
In case you wish to test the latest version of the packages, you can run:
sudo zypper refresh
sudo zypper install OrfeoToolbox-beta
sudo zypper install OrfeoToolbox-beta-devel
sudo zypper install Monteverdi-beta
There is also support for the recently introduced ’rolling’ openSUSE distribution named ’Tumble-
weed’. For Tumbleweed you need to add the following repositories with these command-lines:
sudo zypper ar
http://download.opensuse.org/repositories/games/openSUSE_Tumbleweed/ Games
sudo zypper ar
http://download.opensuse.org/repositories/Application:/Geo/openSUSE_Tumbleweed/ GEO
sudo zypper ar
http://download.opensuse.org/repositories/home:/tzotsos/openSUSE_Tumbleweed/ tzotsos
and then add the OTB packages as shown above.
50. 16 Chapter 2. Installation
CentOS 5.5
Since 3.12 version, OTB packages (OTB, monteverdi) are available on CentOS 5.5 distribution.
In the following lines, we will describe the way to install OTB and monteverdi packages on this
distribution. If you want use OTB-Wrapping, please following the instructions found in this file.
Preliminary steps (common to all packages):
1. Configure your system to pass through your HTTP(S) proxy,
2. Add required extra repositories: EPEL, ELGIS and centosplus,
can be found in the previous file.
So if you want OTB and monteverdi packages, you need to install a standard RPM packages which
is available on OTB website:
wget http://www.orfeo-toolbox.org/packages/centos/5.5/i386/3.11.0/
gdal-1.8.0-5.i386.rpm
yum --nogpgcheck install gdal-1.8.0-5.i386.rpm
We can now get and install (replace version number by the current):
1. OTB libraries and applications package:
wget http://www.orfeo-toolbox.org/packages/centos/5.5/i386/3.11.0/
OrfeoToolbox-3.11.0-1.i386.rpm
yum --nogpgcheck install OrfeoToolbox-3.11.0-1.i386.rpm
2. monteverdi package:
wget http://www.orfeo-toolbox.org/packages/centos/5.5/i386/3.11.0/
Monteverdi-1.9.0-0.i386.rpm
yum --nogpgcheck install Monteverdi-1.9.0-0.i386.rpm
2.2 Building from sources
OTB has been developed and tested across different combinations of operating systems, compil-
ers, and hardware platforms including MS-Windows, Linux on Intel-compatible hardware and Mac
OSX. It is known to work with the following compilers: