diff --git a/Documentation/Cookbook/Art/HyperspectralImages/cuprite_rgb.png b/Documentation/Cookbook/Art/HyperspectralImages/cuprite_rgb.png
new file mode 100644
index 0000000000000000000000000000000000000000..8bd8050d9fb6e359b51bc4a0ef1d5ace7fef58da
Binary files /dev/null and b/Documentation/Cookbook/Art/HyperspectralImages/cuprite_rgb.png differ
diff --git a/Documentation/Cookbook/Art/HyperspectralImages/hyperspectralUnmixing_rgb.png b/Documentation/Cookbook/Art/HyperspectralImages/hyperspectralUnmixing_rgb.png
new file mode 100644
index 0000000000000000000000000000000000000000..043bb4d4b5bc13e3cdd2a37fece4a918c7febbca
Binary files /dev/null and b/Documentation/Cookbook/Art/HyperspectralImages/hyperspectralUnmixing_rgb.png differ
diff --git a/Documentation/Cookbook/Art/HyperspectralImages/pavia.png b/Documentation/Cookbook/Art/HyperspectralImages/pavia.png
new file mode 100644
index 0000000000000000000000000000000000000000..f9a4f8eca62e6314551f9a912a60ae1deda2c5d2
Binary files /dev/null and b/Documentation/Cookbook/Art/HyperspectralImages/pavia.png differ
diff --git a/Documentation/Cookbook/Art/HyperspectralImages/rx_detection.png b/Documentation/Cookbook/Art/HyperspectralImages/rx_detection.png
new file mode 100644
index 0000000000000000000000000000000000000000..37447a23545a59be4f4f2bccd0be4eadb7adc09d
Binary files /dev/null and b/Documentation/Cookbook/Art/HyperspectralImages/rx_detection.png differ
diff --git a/Documentation/Cookbook/Art/HyperspectralImages/rx_score.png b/Documentation/Cookbook/Art/HyperspectralImages/rx_score.png
new file mode 100644
index 0000000000000000000000000000000000000000..6af9dcd431eac41e2d28949f986f1930129b8005
Binary files /dev/null and b/Documentation/Cookbook/Art/HyperspectralImages/rx_score.png differ
diff --git a/Documentation/Cookbook/rst/Recipes.rst b/Documentation/Cookbook/rst/Recipes.rst
index 7697809f3459b7957bf62005df9294b23dd25fd9..775519aed63550894ede287b4341b607be72f86a 100644
--- a/Documentation/Cookbook/rst/Recipes.rst
+++ b/Documentation/Cookbook/rst/Recipes.rst
@@ -18,3 +18,4 @@ and demonstrate how they can be applied.
recipes/pbclassif.rst
recipes/featextract.rst
recipes/stereo.rst
+ recipes/hyperspectral.rst
diff --git a/Documentation/Cookbook/rst/recipes/hyperspectral.rst b/Documentation/Cookbook/rst/recipes/hyperspectral.rst
new file mode 100644
index 0000000000000000000000000000000000000000..9e89886fdf2fe302a99b22bee85e1650a60d712f
--- /dev/null
+++ b/Documentation/Cookbook/rst/recipes/hyperspectral.rst
@@ -0,0 +1,188 @@
+Hyperspectral image processing
+==============================
+
+Hyperspectral sensors produce images with hundreds of narrow spectral bands
+within the visible, near-infrared, mid-infrared and short wave infrared portions
+of the electromagnetic spectrum. This means that an entire spectrum is acquired
+at each point. The richness of this information is useful in many applications,
+like geology and agriculture.
+
+This section presents OTB applications for hyperspectral image processing.
+
+
+Unmixing
+--------
+
+Because of the low spatial resolution of hyperspectral sensors, microscopic
+material mixing and multiple scattering, measured spectra are a mixture
+of the spectra of the materials actually in the scene. Thus, pixels are assumed
+to be mixtures of a few materials, called endmembers. In this section the mixing
+is assumed to be linear, i.e.
+
+.. math::
+ R = A.S + N
+
+where, if `l` is the number of bands of the hyperspectral image, `n` the number of pixels
+and `k` the number of endmember:
+
+- :math:`R` is the matrix of observed pixel, of size `l.n`
+- :math:`A` is the endmember matrix, of size `l.k`
+- :math:`S` is the abundance matrix, of size `k.n`
+- :math:`N` is the noise matrix, of size `l.n`
+
+The unmixing problem is to estimate matrices `A` and `S` from `R`.
+The following presents an example of hyperspectral unmixing on a scene composed
+of several geological materials. The scene is an extract from the Cuprite dataset
+acquired by the AVIRIS sensor. The extract is available here_ and the whole dataset
+can be retrieved from AVIRIS_ NASA site.
+
+
+.. figure:: ../Art/HyperspectralImages/cuprite_rgb.png
+ :width: 70%
+ :align: center
+
+ Cuprite image considered, here bands 16, 100 and 180 are displayed.
+
+
+As the number of endmembers of the input image is unknown, the first step
+of the hyperspectral unmixing is to estimate this number. Here a HFC virtual
+dimensionality algorithm is used.
+
+::
+
+ otbcli_EndmemberNumberEstimation -in inputImage.tif
+ -algo vd
+ -algo.vd.far 1e-5
+
+This algorithm uses a Neyman-Pearson statistical test on the difference between
+the eigenvalues of the covariance matrix and those of the correlation matrice to estimate the
+number of endmembers. If the difference between the eigenvalues for one component is null, this
+means that no endmember is contributing to the correlation eigenvalue in addition to noise
+for that particular component, since the noise energy is represented by the
+covariance eigenvalue. The output of the algorithm is:
+
+::
+
+ Output parameters value:
+ number: 19
+
+The next step of the hyperspectral is to estimate the endmembers. This can
+be done using the Vertex Component Analysis algorithm (VCA).
+
+::
+
+ otbcli_VertexComponentAnalysis -in inputImage.tif
+ -ne 19
+ -outendm endmembers.tif
+
+The output of the application is an image containing `k` pixels, each pixel
+representing an endmember.
+
+This algorithm is based on the research of the endmembers among the data.
+This means that a minimum of one pure pixel must be associated with each endmembers.
+The rationale behind this idea is that the hyperspectral mixed data is contained
+in a simplex of dimension `k`, where the endmembers are the vertices of the simplex.
+This algorithm is widely used in hyperspectral unmixing because of its low algorithmic
+complexity and the fact that the endmembers estimation is unbiased in absence of noise.
+However if the pure pixel hypothesis is not respected, there will be an estimation
+error on the endmembers.
+
+The last step of the unmixing is to estimates the abundance matrix using an
+optimization algorithm.
+
+::
+
+ otbcli_HyperspectralUnmixing -in inputImage.tif
+ -ie endmembers.tif
+ -out unmixedImage.tif
+ -ua ucls
+
+Here an unconstrained least square algorithm has been used. The resulting abundance
+image is shown below:
+
+.. figure:: ../Art/HyperspectralImages/hyperspectralUnmixing_rgb.png
+ :width: 70%
+ :align: center
+
+ Resulting unmixed image, here the first three bands are displayed.
+
+
+Anomaly detection
+-----------------
+
+An anomaly is an element that is not expected to be found in a scene. The unusual element
+is likely different from its environment and its presence is in the minority scene. Typically,
+a rock in a field, a wooden hut in a forest are anomalies that can be desired to detect using
+hyperspectral imagery. Here an anomaly detection algorithm, the local Rx
+detector, will be used to detect small objects in urban environment. The input image
+has been acquired over Pavia_ University by the ROSIS sensor and has 103 spectral bands.
+
+.. figure:: ../Art/HyperspectralImages/pavia.png
+ :width: 70%
+ :align: center
+
+ Hyperspectral image of the Pavia university, here bands 50, 30 and 10 are displayed.
+
+
+A first optional step is to reduce the dimensionality of the input image in order to
+reduce the size of spectral data while maintaining information related to
+anomalies, here a Principal Component Analysis algorithm is used.
+
+::
+
+ otbcli_DimensionalityReduction -in inputImage.tif
+ -out reducedData.tif
+ -method pca
+ -nbcomp 10
+
+
+As the local Rx needs to compute and invert a correlation matrix on each pixel, applying dimensionality reduction
+as a preprocessing step will significantly reduce the computational cost of the algorithm.
+
+The local Rx detection use a sliding window to compute an anomaly score on each pixel.
+This window consists of two sub windows, of radius `ir` and `er`, with `ir < er`,
+and centered on the pixel of interest. The local Rx score is computed by comparing the
+center pixel with the pixel belonging to the annulus.
+
+::
+
+ otbcli_LocalRxDetection -in reducedData.tif
+ -out RxScore.tif
+ -ir 1
+ -er 5
+
+Here anomalies are supposed to be small, hence a small internal radius should be chosen e.g.
+`ir=1`. Also as the environment is urban, and because the sensor has a low spatial resolution,
+the statistic of the background varies rapidly with the distance,
+so the external radius should not be too big, here `er=5` has been chosen.
+These parameters really depend on the input image and on the objects of interest.
+
+A threshold can then be applied on the resulting score image to produce an
+anomaly map.
+
+::
+
+ otbcli_BandMath -il RxScore.tif
+ -out anomalyMap.tif
+ -exp "im1b1>100"
+
+
+The value of the threshold depends on how sensitive the anomaly detector should be.
+
+.. |image_1| image:: ../Art/HyperspectralImages/rx_score.png
+
+.. |image_2| image:: ../Art/HyperspectralImages/rx_detection.png
+
+
+.. _Figure1:
+
++---------------------------+---------------------------+
+| |image_1| | |image_2| |
++---------------------------+---------------------------+
+
+ Left: Computed Rx score, right: detected anomalies (in red)
+
+
+.. _here: http://www.ehu.eus/ccwintco/index.php/Hyperspectral_Remote_Sensing_Scenes#Cuprite
+.. _AVIRIS: https://aviris.jpl.nasa.gov/
+.. _Pavia: http://www.ehu.eus/ccwintco/index.php/Hyperspectral_Remote_Sensing_Scenes#Pavia_University_scene
diff --git a/Modules/Applications/AppHyperspectral/app/otbHyperspectralUnmixing.cxx b/Modules/Applications/AppHyperspectral/app/otbHyperspectralUnmixing.cxx
index 0444e858d6f464a0907d956377035d87dcbb1b41..594a1827b3e9eca98e716313af4558c12292c8d9 100644
--- a/Modules/Applications/AppHyperspectral/app/otbHyperspectralUnmixing.cxx
+++ b/Modules/Applications/AppHyperspectral/app/otbHyperspectralUnmixing.cxx
@@ -179,7 +179,7 @@ private:
endMember2Matrix->Update();
MatrixType endMembersMatrix = endMember2Matrix->GetMatrix();
- otbAppLogINFO("Endmembers matrix : " << endMembersMatrix);
+ otbAppLogDEBUG("Endmembers matrix : " << endMembersMatrix);
/*
* Unmix