Escolar Documentos
Profissional Documentos
Cultura Documentos
NEST has been conceived for reading, post-processing, analyzing and visualizing data from the following
satellite missions:
Third Party Mission SAR-data: ALOS PALSAR, JERS SAR, TerraSAR-X, Radarsat-1 and 2,
Cosmo-Skymed.
It provides both basic and advanced tools for the SAR user community:
NEST shares the same core architecture with the BEAM toolbox, developed for analysis of optical data.
Fully Open Source under the GNU GPL
Portable Java implementation allows use on multiple hardware platforms and operating systems
Modular Easy changes and upgrades
Extensible API to allow users to add modules to extend capability of NEST
2. View metadata
In the Products tab, click in the Identification folder of each image. Here you will see information taken
from the metadata files, including the mission, product type, acquisition date and time, track and orbit.
Now click on the Metadata folder and view the SPH (Specific Product Header) and MPH (Main Product
Header) files by double clicking on their names and viewing the contents in the main window. These files
contain more metadata. There is also an Abstracted Metadata section which automatically updates
whenever changes occur in the image file (e.g. pixel spacing, calibration, etc.).
3. View geographical coverage of both images
Select View / Tool Windows / Bam World Map and the following map will appear showing the footprints of
the images calculated from the metadata.
Although a subset has now been created (and a new entry created in the products view) this is still a virtual
image file, it has not yet been saved to disk. To save the subset, select the subset in the products view and
then click File / Save. The product will be saved in the NEST / BEAM internal DIMAP format, and the file will
be saved in the Processed Products folder of the project directory (unless you specify otherwise). Perform
the same steps for the archive image, cropping approximately the same corresponding area and saving the
image in BEAM DIMAP format.
In the Project window, notice the subset products in the Processed Products folder.
Save the project by clicking on File / Save.
5. Orthorectification
We will now orthorectify the images with a DEM. Select one of the subset images in the Products View.
Then select Geometry / Terrain Correction / Range-Doppler Terrain Correction. In the I/O Parameters
tab of the Terrain-Correction window, ensure the Save as checkbox is selected. In the Processing
Parameters tab select the Amplitude band in the Source Bands list (click on Amplitude so it becomes
highlighted). Select the SRTM 3Sec GeoTiff as the Digital Elevation Model. Then click Run. Repeat the
process for the other subset image.
Transparency slider will enable you to adjust the transparency of one band on top of the other. Inspect the
differences between the two bands by zooming, panning and changing the transparency of the image
channels.
In order to view the differences between the archive and crisis image in one layer we will create an RGB
image view. To do this we first need to ensure there are 3 channels from which to create an RGB image.
Select Utilities / Create Band by Band Maths In the Band Maths window select Edit Expression In
the Band Maths Expression Editor select the 2004 image band. Then click OK.
In the stack there are now 3 bands: one of the crisis image and two of the archive. We can now create an
RGB image. click on View / Open RGB Image View Select the 2008 image as Red and the 2004 image
as both Green and Blue. This combination will enable us to distinguish between areas that are flooded and
permanent water bodies. In areas that are flooded, the red channel will be dark but the green and blue
channels will be bright, therefore the pixels should appear bright cyan. Permanent water bodies will be dark
in all the channels. All other areas should be a shade of grey as the backscatter intensity should be the
same. However, in this case the images are not from the same track, therefore there will be greater
differences between the image backscatter even in areas where they should be the same (due to the
different look angles).
Good threshold values for flooded areas could be < 800 for the crisis image and > 900 for the archive image.
This will mask flooded pixels, without classifying permanent water bodies as flooded areas.
To apply these thresholds we will use the ROI tools. Open one of the bands of the stacked image. Select
View / Tool Windows / Mask/ROI Manager.
A New Logical Band Maths Expression window appears. In this window select the Show bands
checkbox, and then type the following expression in the Expression box, clicking on the band name in the
Data sources list to include the band names in the expression:
To mask only the flooded area and to avoid the edges containing regions not covered by both images, we
will apply the mask only to the part where both images overlap. Click on the polygon drawing tool, and
draw a polygon, by left clicking on the mouse, that covers the area where there is coverage of both images.
Double click to close the polygon.
Now in the Mask/ROI Manager window, select both the mask and the geometry rows, and then click on the
symbol to create a new mask containing the intersection of the selected masks.
Export the view as a Google Earth KMZ file, and view it in Google Earth.
To count the number of pixels covered by the floods, click on the on the Open product information button
in the main toolbar. In the window that appears, click on the Statistics tab, select Use ROI-Mask and
then click on Compute. You will now see some information about the Region Of Interest (ROI) including the
number of pixels, the percentage of image pixels within the ROI, etc.
Knowing the size of the image pixel (see range spacing and azimuth spacing in metadata) and knowing how
many pixels are masked as flood, it is possible to calculate the size of the affected area. What is the extent
of the flooding?