Image processing/it: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(→‎Introduzione generale: inizio traduzione)
mNo edit summary
Line 4: Line 4:
=== Introduzione generale ===
=== Introduzione generale ===


'''Numeri digitali e valori fisici (reflection/radiance-at-sensor):'''
'''Numeri digitali e valori fisici (riflessione/radianza-al-sensore):'''


Le immagini da satellite sono comunemente fornite come numeri digitali (Digital Numbers - DN) per minimizzare il volume di memoria, cioè il  valore fisico analogico campionato in origine (colore, temperatura, etc) è archiviato come una rappresentazione discreta in 8-16 bit. Per esempio, i dati Landsat vengono memorizzati come valori a 8bit (cioè in un intervallo da 0 a 255); i dati di altri satelliti possono essere memorizzati a 10 o 16 bit. Having data stored in DN, it implies that these data are not yet the observed ground reality.
Le immagini da satellite sono comunemente fornite come numeri digitali (Digital Numbers - DN) per minimizzare il volume di memoria, cioè il  valore fisico analogico campionato in origine (colore, temperatura, etc) è memorizzato come una rappresentazione discreta in 8-16 bit. Per esempio, i dati Landsat vengono memorizzati come valori a 8bit (cioè in un intervallo da 0 a 255); i dati di altri satelliti possono essere memorizzati a 10 o 16 bit.
<!--Having data stored in DN, it implies that these data are not yet the observed ground reality.-->
<!-- I dati in DN sono|non descrivono ancora la realtà osservata al suolo.-->
<!-- I dati in DN sono|non descrivono ancora la realtà osservata al suolo.-->
Tali dati son detti "at-satellite", per esempio, la quantità di energia rilevata dal sensore della piattaforma satellitale è codificata in 8 o più bit. Questa energia è detta radianza-al-sensore<!--radiance-at-sensor-->. Per ottenere valori fisici dai DN, i fornitori di immagini satellitali usano un'equazione di trasformazione lineare <tt>(y = a * x + b)</tt> per codificare radiance-at-sensor in valori da 8 a 16 bit. I DN si possono riconvertire in valori fisici applicando la formula inversa <tt>(x = (y - b) / a)</tt>.
<!--Avere i dati in forma di DN comporta che questi dati non sono ancora la realtà osservata al suolo-->
I dati in forma di DN non sono ancora dati reali rilevati al suolo.
Tali dati sono detti "al satellite"; per esempio, la quantità di energia rilevata dal sensore della piattaforma satellitare è codificata in 8 o più bit. Questa energia è detta radianza al sensore<!--radiance-at-sensor-->. Al fine di ottenere valori fisici dai DN, i fornitori di immagini satellitari usano un'equazione di trasformazione lineare <tt>(y = a * x + b)</tt> per codificare la radianza al sensore in valori da 8 a 16 bit. I DN si possono riconvertire in valori fisici applicando la formula inversa <tt>(x = (y - b) / a)</tt>.





Revision as of 17:00, 15 September 2013

This page is in progress of translating to Italiano from English.

Introduzione

Introduzione generale

Numeri digitali e valori fisici (riflessione/radianza-al-sensore):

Le immagini da satellite sono comunemente fornite come numeri digitali (Digital Numbers - DN) per minimizzare il volume di memoria, cioè il valore fisico analogico campionato in origine (colore, temperatura, etc) è memorizzato come una rappresentazione discreta in 8-16 bit. Per esempio, i dati Landsat vengono memorizzati come valori a 8bit (cioè in un intervallo da 0 a 255); i dati di altri satelliti possono essere memorizzati a 10 o 16 bit. I dati in forma di DN non sono ancora dati reali rilevati al suolo. Tali dati sono detti "al satellite"; per esempio, la quantità di energia rilevata dal sensore della piattaforma satellitare è codificata in 8 o più bit. Questa energia è detta radianza al sensore. Al fine di ottenere valori fisici dai DN, i fornitori di immagini satellitari usano un'equazione di trasformazione lineare (y = a * x + b) per codificare la radianza al sensore in valori da 8 a 16 bit. I DN si possono riconvertire in valori fisici applicando la formula inversa (x = (y - b) / a).


Il modulo di GRASS GIS i.landsat.toar trasforma facilmente i DN Landsat in radiance-at-sensor. Il modulo equivalente per i dati ASTER è i.aster.toar. Per altri satelliti si può usare r.mapcalc.


Reflection/radiance-at-sensor and surface reflectance

When radiance-at-sensor has been obtained, still the atmosphere influences the signal as recorded at the sensor. This atmospheric interaction with the sun energy reflected back into space by ground/vegetation/soil needs to be corrected. There are two ways to apply atmospheric correction for satellite imagery. The simple way for Landsat is with i.landsat.toar, using the DOS correction method. The more accurate way is using i.atcorr (which works for many satellite sensors). The atmospherically corrected sensor data represent surface reflectance, which ranges theoretically from 0 % to 100 %. Note that this level of data correction is the proper level of correction to calculate vegetation indices.

Image processing in GRASS GIS

Satellite imagery and orthophotos (aerial photographs) are handled in GRASS as raster maps and specialized tasks are performed using the imagery (i.*) modules. All general operations are handled by the raster modules.

  • Data import is generally handled by the r.in.gdal module

Screenshots

Importing

The wxGUI offers a convenient tool for single map and bulk import:

Satellite Data

Ocean Color

Sea Surface Temperature (SST)

High Resolution Data

See also, various Whitepapers on High Resolution Satellite Imagery

Orthophotos

Preprocessing

See also NASA LaRC Satellite Overpass Predictor

Geometric preprocessing/Georectification

A multi-band image may be grouped and georectified with a single set of ground control points (i.group, i.target, i.rectify).

See also the Georeferencing wiki page

Radiometric preprocessing

Correction for atmospheric effects

Visit the dedicated page on Atmospheric correction

Related Modules

Correction for topographic/terrain effects

In rugged terrain, such correction might be useful to minimize negative effects.

  • simple "cosine correction" using r.sunmask, r.mapcalc (tends to overshoot when slopes are high)
  • In i.topo.corr the following correction methods are implemented: cosine, minnaert, percent, c-factor.
    • Note, that for the sun's zenith (in degrees) parameter, the equation "Sun's Zenith = 90 - Sun's Elevation" is generally valid

Cloud removal

Image classification

See the dedicated Image classification page.

Image segmentation

  • i.smap: Performs contextual image classification using sequential maximum a posteriori (SMAP) estimation.
  • r.seg: Performs image segmentation and discontinuity detection (based on the Mumford-Shah variational model).
  • i.segment: Image Segmentation

Filtering

Fourier Transform

Canonical Component Analysis

Principal Component Analysis

Texture

A series of commonly used texture measures (derived from the Grey Level Co-occurrence Matrix, GLCM), also called Haralick's texture features are available:

  • r.texture: In case of panchromatic maps or limited amount of channels, it is often recommended to generate synthetic channels through texture analysis

See here and here for the formulas to calculate texture. See also canopy texture mapping.

Spectral unmixing

Time series analysis

Enhancements

Radiometric Enhancements

Geometric Enhancements - Image Fusion - Pansharpening - Image Segmentation

Image fusion and Pansharpening:

  • i.rgb.his and i.his.rgb: can be used for image fusion
  • i.fusion.brovey: image fusion of pan-chromatic and color channels
  • i.pansharpen: Image fusion algorithms to sharpen multispectral with high-res panchromatic channels (GRASS 7)

Segmentation:

  • r.seg which performs image segmentation and discontinuity detection (based on the Mumford-Shah variational model). The module generates a piece-wise smooth approximation of the input raster map and a raster map of the discontinuities of the output approximation. The discontinuities of the output approximation are preserved from being smoothed. (Addons)
  • i.segment: Identifies segments (objects) from imagery data (GRASS 7)

Optimal channel selection for color composites

Stereo anaglyphs

Ideas collection for improving GRASS' Image processing capabilities

Below modules need some tuning before being added to GRASS 6. Volunteers welcome.

Spectral unmixing ideas

  • Make use of the Spectral Python (SPy) which is a pure Python module for processing hyperspectral image data

Spectral angle mapping ideas

Geocoding ideas

Image matching ideas

  • i.points.auto: automated search of GCPs based on FFT correlation (as improved i.points)
Reference: M. Neteler, D. Grasso, I. Michelazzi, L. Miori, S. Merler, and C. Furlanello, 2005: An integrated toolbox for image registration, fusion and classification. International Journal of Geoinformatics, 1(1), pp. 51-61 PDF

Image classification ideas

Stereo ideas

This is stand-alone stereo modeling software (DEM extraction etc). Waits for integration into GRASS.

Bundle block adjustment

Needed to orthorectify a series aerial images taken sequentially with overlap. "Histoical" method which is nowadays interesting for UAV flights with octocopters and such.

Automatec GPC search could be done by "auto-sift".

Available: Octave code which prepares input to an i.ortho.photo batch job (contact Markus Neteler).

Lidar LAS format

LAS Tools by M. Isenburg, Howard Butler et al.: http://www.liblas.org

   las2txt | r.in.xyz in=- fs=" "

Update: r.in.lidar and v.in.lidar implemented by Markus Metz (GRASS 7)

(see LIDAR)

Improving the existing code

It might be sensible to merge the various image libraries:

  • GRASS 6 standard libs:
    • lib/imagery/: standard lib, in use (i.* except for i.points3, i.rectify3, see below)
    • imagery/i.ortho.photo/libes/: standard lib, in use (i.ortho.photo, photo.*)
  • GRASS 5 (! only) image3 lib:
    • libes/image3/: never finished improvement which integrated the standard lib and the ortho lib. Seems to provide also ortho rectification for satellite data (i.points3, i.rectify3)
  • GRASS 5/6 image proc commands:
    • merge of i.points, i.vpoints, i.points3 (see above)
    • merge of i.rectify and i.rectify3 (see above)
    • addition of new resampling algorithms such as bilinear, cubic convolution (take from r.proj or r.resamp.aggreg) (done 10/2010)
    • add other warping methods (maybe lanczos or thin splines from GDAL?): Addons#i.warp
    • implement/finish linewise ortho-rectification of satellite data

Bibliography