Professional Documents
Culture Documents
Manual de Usuario Tollbox Prisma
Manual de Usuario Tollbox Prisma
INTRODUCTION
PRISMA Toolbox is a tool that manipulates very big SAR (CSK and CSG missions)
and hyperspectral (PRISMA mission) images. It is particularly focused on
hyperspectral PRISMA mission images (see section 2).
PRISMA Toolbox is a project derived by the Planetek’s PrismaToolbox system, with
upgradings realized under the ASI-Planetek contract MePA n. 3321592.
PRISMA Toolbox allows to create, configure and execute massively parallel
processing tasks (specific for satellite imagery or science data) on big datasets on a
high-end multi monitor desktop workstation by leveraging the power of a proprietary
map/reduce framework.
Its modern Human Machine Interface enables the user to easily interact with
algorithms, image data and unstructured metadata and exploit the power of
heterogeneous computing devices such as modern multi-core CPUs, Graphics
Processing Units (GPUs) and Accelerators (FPGA and ASICs with OpenCL support).
Great efforts were also made on designing a fluid, responsive and performant image
visualization engine, based on industry standard technologies such as C++11, modern
OpenGL and Qt5 toolkit.
PRISMA Toolbox supports simultaneous visualization of different images that can be
navigated in co-registration mode, providing real-time graphical operation on them.
Therefore, thanks to its high performance visualization and processing capabilities
PRISMA Toolbox is ready for use in production environment for manipulating HDF5,
JPG, PNG and TIFF data sources.
The advantages that PRISMA Toolbox can provide to the user are:
- an accurate and generic coordinate conversion engine, given its capability to
handle many different coordinate spaces: the user can load data sets and attributes
from hierarchical and generic data files (HDF5, HDF-EOS, TIFF, JPEG,FITS)
- more processing power and interaction speed by exploiting the use of
heterogeneous computing and parallel processing techniques: the user is able to
visualize and process big images and data sets executing processing and visualization
algorithms on multicore CPUs and discrete GPUs, thanks to a proprietary acceleration
engine integrating Khronos OpenGL and OpenCL Application Programming Interface
(API) for parallel applications
- load ~4GiB image from disk to memory in less than 15s
- create image pyramids on the fly, within-memory caching of tiles
- maximise the use of Solid State Disks
- execute real-time image filtering at about 400fps on GPU
2. PRISMA PRODUCTS
PRISMA sensor provides a swath width of 30 km at nadir. Data takes shall be
programmed with a along track integer multiple of 30 km lengths. Maximum data
take length is equal to 1800 km. All products cover a standard scene with size 30x30
km2 as a result of segmentation of longer data take strips.
The PRISMA Mission delivers products up to Level 2. The processing logic is
sketched below.
2.1.1. Level-0
The Level-0 Product is not delivered to users.
The Level-0 Product is deciphered decompressed raw image data in Instrument
Source Packet (ISP) format. It is the basis of all subsequent processing tasks and it is
permanently archived.
2.1.2. Level-1
It is obtained formatting raw image data in arrays and by the application of
radiometric calibration and channels co-registration to provide TOA radiances starting
from L0. An approximate geometric model is also evaluated allowing any pixel to be
located on a WGS84 ellipsoid.
The following layers are included in Level-1 Product:
- Radiometrically Calibrated HYPER land-observation frames list, with relevant
attributes;
- Radiometrically Calibrated PAN land-observation frames list, with relevant
attributes;
- Radiometrically Calibrated Coregistered HYPER land-observation frames list,
with relevant attributes;
- Radiometrically Calibrated Coregistered PAN land-observation frames list, with
relevant attributes.
Figure 2-2: L1 Product structure
Each folder represents a HDF5 group containing datasets.
Raster hyperspectral and panchromatic data are stored in (PRS_L1_HCO,
PRS_L1_HRC) and (PRS_L1_PRC, PRS_L1_PCO), respectively. The suffix RC and
CO are used to distinguish between Radiometrically Calibrated and Coregistered
radiances.
The /Info/Housekeeping Group contains frame-dependent HK payload parameters.
The /Info/Ancillary Group contains frame-dependent ancillary parameters (e.g. star-
trackers and GPS data).
2.1.3. Level-2B
It is obtained by applying the atmospheric corrections (Rayleigh scattering, gaseous
absorption, water absorption, aerosol scattering) to the L1 product to generate at-
surface radiance.
The following layers are included in Level-2B Product:
- At-surface radiance HYPER land-observation frames list, with relevant
attributes;
- At-surface radiance PAN land-observation frames list, with relevant attributes;
2.1.4. Level-2C
It is obtained by applying the atmospheric corrections needed for L2B product
generation, integrating the radiance-to-reflectance conversion, in order to provide
surface reflectance and maps rlated to atmospheric constituents.
The following layers are included in Level-2C Product:
- Surface reflectance HYPER land-observation frames list, with relevant
attributes;
- Surface reflectance PAN land-observation frames list, with relevant attributes;
- Aerosol Optical Thickness map @550nm;
- Water Vapour content map;
- Cloud Optical Thickness;
- Angstrom exponent between 550/705 nm
Figure 2-4: L2C Product Structure
Raster hyperspectral and panchromatic data are stored in PRS_L2C_HCO and
PRS_L2C_PCO, respectively. Maps used for atmospheric correction are stored in
dedicated groups:
GROUP DESCRIPTION
PRS_L2C_AEX Angstrom Exponent Map
PRS_L2C_AOT Aerosol Optical Thickness Map
PRS_L2C_COT Cloud Optical Thickness Map
PRS_L2C_WVM Water Vapour Map
Table 2-2: L2C Product Maps
2.1.5. Level-2D
It is obtained by applying geometric correction with GCP (optionally) and DTM to
the processing steps needed for L2C product generation, to provide surface
reflectance projected on a cartographic UTM reference system.
The following layers are included in Level-2D Product:
- Geocoded surface reflectance HYPER land-observation frames list, with relevant
attributes;
- Geocoded surface reflectance PAN land-observation frames list, with relevant
attributes;
Figure 2-5: L2D Product structure
· _File_
- _Open_ action, to open a file
- _Exit_ action, which is the unique return point of the SW
· _Tools_
- _GeoLocation_ show an on-line geolocated map (see 3.2.1 section)
· _Windows_
- _Console _ show application console (see 3.2.2 section)
- _Configuration_ show application configuration (see 3.2.3 section)
- _Log_ show application logs (see 3.2.4 section)
· _Help_
- _Contact Support _ show application console (see 3.2.2 section)
- _On-Line Help_ show Help on-line (see 3.2.6 section)
3.2.1. GeoLocation
View a geolocated map (via the google maps service) centralized to the last position
explored by one of the 2 workspaces.
This widget offers experimental features that are still being evaluated for future
improvements.
Figure 3-5: GeoLocation panel
Next table details the meaning for all controls on panel.
Control Description
Show/Modify actual Latitude/Longitude map center
coordinate
Show/Modify visualized map type:
§ roadmap: displays the default road map view
§ satellite: displays Google Earth satellite images
§ terrain: displays a physical map based on terrain
information
§ hybrid: displays a mixture of normal and satellite
views
Table 3-1: GeoLocation panel controls
3.2.2. Console
Figure 3-6: Console panel
3.2.3. Configuration
The Configuration Settings Panel is organized to set and view the main configuration
settings of PRISMA Toolbox.
3.2.4. Log
Control Description
Load log file selecting it from filesystem
On opening at the first time show actual application file log
path displayed on table.
All application logs are stored on log folder; the filename
has this naming convention:
PrismaToolbox_<YYYYMMDD>_<hhmmss>_<PID>.log
From combo-box it is possible to select and show an old
application log or select the actual render-server sub-
process log that has this naming convetion:
render-server_<YYYYMMDD>_<hhmmss>_<PID>.log
where PID is the PRISMA Toolbox PID
Control Description
_Title_ Edit an introductive title for request
Show/Modify actual Type Support Request:
§ Generic: for generic request
§ Bug: to report possible application
problems encountered
§ Suggestion: to give the user the
opportunity to suggest possible
improvements or additions of features
Edit the body request to detail the request
and help the PRISMA Toolbox
_Body_
development team understand how to
support it
Browse optionally the file system and select
a generic file (e.g. a screenshot image) with
a file of maximum 5MB to attach at support
request
Select to let the user choose whether or not
to attach the application logs to the support
request
_Submit_ Submit edited custom support request
Table 3-3: Contact Support panel controls
3.2.6. Help
3.3.2. HDF
This tab can be used in order to open products to be analysed for visual inspection or
metadata browsing and plotting. This is the entry-point for displaying datasets on
workspaces.
Figure 3-14: HDF tab
Next table details the meaning for all controls on panel.
Control Description
This button permits to open on HDF product: this action opens the
_Open_ window _Select Input File_ to browse file-system for the product to
check (see Opened product section for details)
This button enable the selected product on PRISMA HDF tab (see
_Active_
section 3.3.4 for details)
_Close All_ This button close all opened products and clear list view
This button exports the selected dataset (e.g. IMG) in another format:
EPS for plotting on plotter devices, JPEG, or tagged graphical format
_Save As_
(TGA or TGX). A window appears for selecting folder destination and
name of file (with the right extension)
_Show on This buttons display the selected dataset (e.g. IMG) on one of the two
WS-A_ workspaces (see section 0 for details)
_Show on
WS-B_
This button shows Plotter window (see Plot of nodes section for
_Plot_
details)
3.3.3. Messages
The _Messages_ tab collects information, warning and errors generated by the tool. It
includes for same instance, information about the message text, tag of the source that
has generated message and the type of message.
This button closes actual opened product and remove it from list on
_Close_
HDF tab (see section 3.3.2)
_Reload RGB_ This button reload on Workspace A the product RGB image
Control Description
_Product This sub-tab gives an overview of selected product (see details on Product
Overview_ Overview section).
This sub-tab lists the attributes contained on root of selected product (see details
_Attributes_
on Attributes section).
_Band This sub-tab contains a preview for selected band (see details on Band Preview
Preview_ section).
color of pixel (if active dataset on workspace isn’t complex or real type)
pixel's row (R) index (ranging from 0 to ImageHeight-1)
pixel's column (C) index (ranging from 0 to ImageWidth-1)
pixel’s value (v) with Real and Imaginary parts; Imaginary part is visible only for
complex image
pixel’s latitude (La) evaluated in-line
pixel’s longitude (Lo) evaluated in-line
height (H), in meters, evaluated in-line on the product’s DEM
_coreg_ checkbox for Workspaces coregistration
On moving on workspace or editing the R/C values the geodetic coordinate La/Lo/H
is computed on the fly, as well as editing the geodetic coordinate La/Lo/H (when this
service is enabled) the R/C image coordinate is automatically calculated and the
image is centered at that coordinate and in this case the _coreg_ checkbox is also
activated.
By activating the _coreg_ checkbox (when it is enabled), the images in the
Workspaces are geodetically co-registered and the navigation in one of the two moves
the center on the other.
Following figure shows a possible scenario for PRISMA L2D products: a co-
registrated view of the PAN and RGB layers can be set flagging the _coreg_
checkbox in the Pixel Info panel and detaching Workspaces in separated windows by
_Detach_ buttons.
Figure 3-31: Co-registered visualization for PAN-RGB views in PRISMA L2D
products
Next image shows an example of possible use case for co-registration functionality by
opening a SAR image (CSG mission, GTC_B type) in Workspace A and the PAN
(chromatic) of a PRISMA L2D image on Workspace B and, at the same time, opening
the geolocated map (see for details 3.2.1 section) automatically co-registered with the
2 Workspaces images.
Figure 3-32: co-registration example
Image Workspaces.
PAN
color of pixel (if active dataset on workspace isn’t complex or real type)
pixel's row (R) index (ranging from 0 to ImageHeight-1)
pixel's column (C) index (ranging from 0 to ImageWidth-1)
pixel’s value (v) with Real and Imaginary parts; Imaginary part is visible only for
complex image
pixel’s latitude (La) evaluated in-line
pixel’s longitude (Lo) evaluated in-line
height (H), in meters, evaluated in-line on the product’s DEM
_coreg_ checkbox for Workspaces coregistration
On moving on workspace or editing the R/C values the geodetic coordinate La/Lo/H
is computed on the fly, as well as editing the geodetic coordinate La/Lo/H (when this
service is enabled) the R/C image coordinate is automatically calculated and the
image is centered at that coordinate and in this case the _coreg_ checkbox is also
activated.
By activating the _coreg_ checkbox (when it is enabled), the images in the
Workspaces are geodetically co-registered and the navigation in one of the two moves
the center on the other.
Following figure shows a possible scenario for PRISMA L2D products: a co-
registrated view of the PAN and RGB layers can be set flagging the _coreg_
checkbox in the Pixel Info panel and detaching Workspaces in separated windows by
_Detach_ buttons.
Figure 3-31: Co-registered visualization for PAN-RGB views in PRISMA L2D
products
Next image shows an example of possible use case for co-registration functionality by
opening a SAR image (CSG mission, GTC_B type) in Workspace A and the PAN
(chromatic) of a PRISMA L2D image on Workspace B and, at the same time, opening
the geolocated map (see for details 3.2.1 section) automatically co-registered with the
2 Workspaces images.
Figure 3-32: co-registration example
Image Workspaces.
Product Bands
When the product is opened at the first time, all bands contained on VNIR/SWIR
Cube datasets are pre-processed on the fly to make their exploration more fluid and
responsive.
All bands are presented in 2 ways deactivating or activating the checkbox above the
list of bands:
· separated and ordered in their owner's cube
color of pixel (if active dataset on workspace isn’t complex or real type)
pixel's row (R) index (ranging from 0 to ImageHeight-1)
pixel's column (C) index (ranging from 0 to ImageWidth-1)
pixel’s value (v) with Real and Imaginary parts; Imaginary part is visible only for
complex image
pixel’s latitude (La) evaluated in-line
pixel’s longitude (Lo) evaluated in-line
height (H), in meters, evaluated in-line on the product’s DEM
_coreg_ checkbox for Workspaces coregistration
On moving on workspace or editing the R/C values the geodetic coordinate La/Lo/H
is computed on the fly, as well as editing the geodetic coordinate La/Lo/H (when this
service is enabled) the R/C image coordinate is automatically calculated and the
image is centered at that coordinate and in this case the _coreg_ checkbox is also
activated.
By activating the _coreg_ checkbox (when it is enabled), the images in the
Workspaces are geodetically co-registered and the navigation in one of the two moves
the center on the other.
Following figure shows a possible scenario for PRISMA L2D products: a co-
registrated view of the PAN and RGB layers can be set flagging the _coreg_
checkbox in the Pixel Info panel and detaching Workspaces in separated windows by
_Detach_ buttons.
color of pixel (if active dataset on workspace isn’t complex or real type)
pixel's row (R) index (ranging from 0 to ImageHeight-1)
pixel's column (C) index (ranging from 0 to ImageWidth-1)
pixel’s value (v) with Real and Imaginary parts; Imaginary part is visible only for
complex image
pixel’s latitude (La) evaluated in-line
pixel’s longitude (Lo) evaluated in-line
height (H), in meters, evaluated in-line on the product’s DEM
_coreg_ checkbox for Workspaces coregistration
On moving on workspace or editing the R/C values the geodetic coordinate La/Lo/H
is computed on the fly, as well as editing the geodetic coordinate La/Lo/H (when this
service is enabled) the R/C image coordinate is automatically calculated and the
image is centered at that coordinate and in this case the _coreg_ checkbox is also
activated.
By activating the _coreg_ checkbox (when it is enabled), the images in the
Workspaces are geodetically co-registered and the navigation in one of the two moves
the center on the other.
Following figure shows a possible scenario for PRISMA L2D products: a co-
registrated view of the PAN and RGB layers can be set flagging the _coreg_
checkbox in the Pixel Info panel and detaching Workspaces in separated windows by
_Detach_ buttons.
When a MultiLayer dataset is shown via HDF tab it is possible to view the plotting of
Pixel Info
Figure 3-30: Pixel Info panel
A Pixel Info panel is displayed above both the workspaces. It summarizes the
information on the pixel at cursor position. Specifically, it includes:
color of pixel (if active dataset on workspace isn’t complex or real type)
pixel's row (R) index (ranging from 0 to ImageHeight-1)
pixel's column (C) index (ranging from 0 to ImageWidth-1)
pixel’s value (v) with Real and Imaginary parts; Imaginary part is visible only for
complex image
pixel’s latitude (La) evaluated in-line
pixel’s longitude (Lo) evaluated in-line
height (H), in meters, evaluated in-line on the product’s DEM
_coreg_ checkbox for Workspaces coregistration
On moving on workspace or editing the R/C values the geodetic coordinate La/Lo/H
is computed on the fly, as well as editing the geodetic coordinate La/Lo/H (when this
service is enabled) the R/C image coordinate is automatically calculated and the
image is centered at that coordinate and in this case the _coreg_ checkbox is also
activated.
By activating the _coreg_ checkbox (when it is enabled), the images in the
Workspaces are geodetically co-registered and the navigation in one of the two moves
the center on the other.
Following figure shows a possible scenario for PRISMA L2D products: a co-
registrated view of the PAN and RGB layers can be set flagging the _coreg_
checkbox in the Pixel Info panel and detaching Workspaces in separated windows by
_Detach_ buttons.
Figure 3-31: Co-registered visualization for PAN-RGB views in PRISMA L2D
products
Next image shows an example of possible use case for co-registration functionality by
opening a SAR image (CSG mission, GTC_B type) in Workspace A and the PAN
(chromatic) of a PRISMA L2D image on Workspace B and, at the same time, opening
the geolocated map (see for details 3.2.1 section) automatically co-registered with the
2 Workspaces images.
Figure 3-32: co-registration example
Image Workspaces
Once a data product is selected for the analysis, the workspaces will show
loaded/selected data, as they are in the product for real datatypes, or in a detected
form, evaluated in-line, for complex datatypes.
the quick-look evaluated in-line on actual data is shown in the top one (on the left for
Workspace A, on the right for Workspace B)
a lens centered on the cursor (with a fixed zoom level equal to 2x) is shown in lower
window (on the left for Workspace A, on the right for Workspace B)
These additional windows can be toggled on/off by means of the F11 keyboard key.