The access to the CAM Component is performed by using a client machine connected to the CAM server via a common web browser. We recommend the use of Netscape 7 or Internet explorer 5 or higher.

In order to access to CAM, the user shall launch its own browser on the client machine at the page:

http://www.cosmo-skymed.it

The following images provide the UGS main home page.

Figure 1: Main window

The page is mainly divided in two frames:

The left frame shows the menu bar
The central frames shows introducing information related to Cosmo-SkyMed Mission

Back to Index

1.3 Access to ancillary information

The CAM allows both registered and unregistered users to browse some ancillary information such as mission information, bulletin board and so on.

The left menu bar provides the following links/tools organized in three groups:

· User

· Info

· Language

User contains:

· Username/Password: text box to insert login data

· Login button: allows to login to the system for registered users

· Registration link: allows to submit a registration request (for unregistered user)

Info contains:

· CSW Home page: such link provides access to the Cosmo Web Site, containing general information about the Cosmo-SkyMed mission

Language contains:

· Language combo box

Note that the interface is actually provided both in English, Italian and French language. You can switch language simply selecting the item in the list box.

Figure 2: Language switch command

Back to Index

1.4 Login and Logout

The service request definition is allowed only to registered users. In order to be registered the user has to send a registration request through the link provided on the right of the login button.

In the following paragraph the procedures to login and logout into and from the system are described.

Back to Index

In the menu frame, into the login box, the user has to fill fields named “Username” and “password” respectively with assigned username and password. The password is always shown with wild char in order to assure privacy of the content.

In order to complete the login procedure the user has to click on the login button.

Figure 4: Logged user main page

A new menu is loaded with new entries.

Namely they are:

· Log out: used to log out from the system and return to main page as an anonymous user

· Profile: used to monitor and manage the user profile parameters such as personal address, phone number etc.

· Services: used to submit new service request

· Orders: used to monitor the status of each saved order and to estimate/submit orders

· Reports: used to service request reports.

· Home: used to return to the homepage

· Help: link to the CAM user manual

When a user is logged a message on the top-left is shown with the message “welcome <username>” where the username is the one provided in the login window.

Back to Index

1.4.2 Logout

It is possible to logout at anytime.

In order to perform the logout operation, the user clicks on “logout” menu entry on the upper menu bar.

The UGS home page is loaded again and the operator is on UGS home page as anonymous user.

Back to Index

1.4.3 Session timeout

User session has a duration of 60 minutes after that, on any operation required the system responds with a notification of an invalid session message.

Back to Index

1.5 Profile management

The profile parameters can be visualised and modified.

In order to access to profile visualisation functionality, the user has to select the “profile” entry on the upper menu bar

The page with the user parameters is shown.

Figure 5: User profile information

The user can decide to modify entered parameters by pressing the “ModifyProfile” button. A new page is loaded as shown in following image:

Figure 6: Profile management window

Modified parameters can be saved by pressing the “SaveProfile” button.

In order to cancel parameters modification, it is possible to select a menu entry on the right toolbar.

Back to Index

1.6 Service Browsing

Figure 7: Service Browsing

CAM Human Machine Interface provides graphical tools for navigation through the available services.

In order to access to the available services description, the logged user clicks the button named “services” on the left bar of the home page. A new page is loaded into the main frame of the home page as shown in Figure 7.

The new page contains a table with the list of services: the available services are mainly divided into the following categories of services:

§ Standard products: Catalogue

§ High Level Products: Catalogue

§ Standard products: New Acquisitions

§ High Level Products: New Acquisitions

For each service of the list, a brief description and the estimated delivery time are indicated.

The services displayed are only available to the user profile

By clicking on the name of any Standard or High Level Product Catalogue service a new page containing the link to define a new order for the service and a short description is loaded.

Figure 8: Service main page

The name of the selected service is provided on the left of the middle bar as shown in Figure 9.

Figure 9: Service name identification

One button is presented on the central frame

“Acquisition Catalog”

Clicking such button the user can create a new order for the selected service.

By clicking on the name of any Standard or High Level products New Acquisition service the loaded page contains the button “Assisted Mode” and a brief description of the service, as shown in the following figure:

Figure 10: Standard Products New Acquisitions service main page

Back to Index

1.7 Service Request definition for Standard Products (New Acquisitions)

In order to define a new service order for standard products, that foresees a new acquisition, the logged user selects the “services” menu item shown on the left frame as defined in the previous section and then selects the requested standard product among the ones available in the “Standard Products New Acquisition” list.

The description of the service is shown on the main central frame; the user can now start the service definition by clicking on the button “Assisted Mode”.

This operation opens a popup window, starting the wizard application that will guide the user in defining the main parameters, by means of a progression of panels.

The current step of service definition operation is shown on top of wizard application together the number of the used request identifier to identify it into user own basket and the name of the selected service.

See also section 2.0 for service request constraints.

Back to Index

1.7.1 Geographical area info

This step allows the definition of the area of interest of the service request. Such definition is not required in case of the requested services are CAL_TR and CAL_IF. To this aim a cartographic representation is provided together with tools aimed to facilitate the identification of such area.

Figure 11: Service Definition wizard: Geographical area definition

The world map provides at first, on the top a map toolbar allows manipulation of the graphical representation. The “MAP Tool bar”: contains the following tools:

“Zoom In”: allows zooming in on a particular position
“Zoom Out”: allows zooming out on a particular position or particular area defined with the mouse by the user
“PAN”: lets you pan on the map by dragging the display in any direction with the mouse
“Select within polygon” to draw a polygonal area
“Select within circle” to draw a circle area
“Select within rectangle” to draw a rectangle area
Target Point: tool allows the draw of target point of the area of interest
Layer control: tool allows changing the Layer(s) Visualization.
Crisis area: button to view on the map the defined crisis area (this button is enable only in crisis operational mode)
“Zoom Value”: shows the actual zoom value. It is also possible to modify directly such value. The map is redrawn accordingly
“Lat” latitude value of the current mouse position in the map
“Long” longitude value of the current mouse position in the map

Note that the layers visualization changes according to the zoom level; in fact when the zoom level is raised some information (e.g. toponyms) change to visible setting.

The button, on the top side near the step counter, allows to access to the next step of service definition.

1.7.1.1 Polygonal area

The user can specify a polygon as area of interest by selecting the polygon selection tool contained in the map tool bar described in section 1.7.1 and drawing a polygon on the map (Figure 12). The table contained in the “Polygon points” panel is updated anytime a new vertex is added providing the corresponding coordinates.

Figure 12: Polygonal area selection

In order to close a defined area the user can

either select a point in the near neighbourhood of the first identified vertex
or double-click on a point on the map corresponding to the last vertex to be added.

In both cases the polygon is automatically closed.

To define a polygon, the user can also manually insert vertex coordinates into the table contained in the panel “Polygon points”. Once the user has inserted all the vertexes record in the table, he/she can draw the corresponding polygon on the map by clicking the button on top of the table “Polygon points”.

The panel “Polygon points”. contains a toolbar to manage the coordinate values, with the following tools:

Remove: Removes the selected record from the coordinates list
Append after: Appends a record after the selected one
Insert before: Inserts a record before the selected one
Add at the top: Adds a record at the top of the list
Add at the end: Adds a record at the end of the list
Remove all: Removes all records of the list
Show on map: Draws the polygon on the map

1.7.1.2 Circular area

The user can specify a circle as area of interest by selecting the circle selection tool contained in the map tool bar described in section 1.7.1 and drawing a circle on the map.

Figure 13: Circular area selection

Circle selection occurs selecting the centre on the map and dragging until the desired radius is reached. While dragging the radius value (expressed in Km) is shown in the field “Radius” in the panel “Circle” on the right of the page. Once the circle has been defined the centre coordinates are shown in the panel “Circle”.

The user can also specify the circle parameters (centre coordinates and radius) in the panel “Circle” manually. Such panel contains also a tool bar holding the following items:

· Clear values: Clears all the values contained in the “Circle” panel fields

· Show on map: Draws on map the circle corresponding to the centre and radius specified by the user in the panel “Circle” fields.

1.7.1.3 Rectangular area

The user can specify a rectangle as area of interest by selecting the rectangle selection tool contained in the map tool bar described in section 1.7.1 and drawing a rectangle on the map.

Figure 14: Rectangular area selection

Rectangle selection occurs selecting a vertex on the map and dragging until the desired rectangle is reached. Once the rectangle has been defined upper left and the lower right corner coordinates are shown in the panel “Rectangle”.

The user can also specify the rectangle upper left and lower right corner coordinates in the panel “Rectangle”. Such panel contains also a tool bar holding the following items:

· Clear values: Clears all the values contained in the “Rectangle” panel fields

· Show on map: Draws on map the rectangle corresponding t upper left and lower right corner specified by the user in the panel “Rectangle” fields.

1.7.1.4 Target centered point

Once the user has selected the area of interest, he/she can specify the “Target centered point” by clicking on the corresponding button of the main tool bar described in section 1.7.1. On the right of the map the panel “Target centered point” appears and the user can specify such a point by:

either manually inserting the coordinates in the panel fields and clicking on the button “Show on map” of the panel toolbar;
or clicking on the map.

In both cases an asterisk corresponding to the selected point appears on the map.

The “Target centered point” panel toolbar contains also a tool to clear the point coordinates.

Back to Index

1.7.2 Observation time constraints

In this step the user defines the temporal constraints of the acquisition used to create the required product/service.

The user can select the type of the acquisition by means of the combo box named “Acquisition Type”. The valid values are:

“single” (for requests that foresees single acquisitions),
“periodical” (for requests that foresees regular time spaced acquisitions),
“repetitive” (for requests that foresees regular time spaced groups of regular time spaced acquisitions).

The user can fill start and stop date/time of the service time with the requested values. Spin buttons and combo boxes helps user for an easier insertion.

Figure 15: Service Definition wizard: Observation time constraint

User can also define:

Granularity: the number of days between two consecutive service requests (for periodical and repetitive service only)
Iterations: the number of service requests (for periodical and repetitive service only)
Repetitive Granularity: the number of days between two consecutive groups (for repetitive requests only)
Repetitive Iterations: the number of groups of service requests (for repetitive requests only)

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.3 Satellite parameters

In this step the user is allowed to define specific COSMO-SkyMed constellation parameters and to select the acquisition station where acquired data shall be downloaded from.

Figure 16: Service Definition wizard: Satellite parameters

The user can select the satellite sensor used for the acquisition and the type of the orbit that the satellite shall have during the acquisition.

Note: The user is allowed not to specify a value for satellite and/or Orbit fields, selecting from the Satellite.Sensor drop-down menu the item named “all” and/or from the Orbit drop-down menu the item named “any direction”.

Further, the user can specify SAR instrument parameters (“instrument” panel).

Specifying incidence angle and delta values, user can force acquisition to have a look angle (Beam Off Nadir) between a minimum and a maximum value. Minimum value is obtained converting specified incidence angle into BON and subtracting and adding delta/2 degrees to get, respectively, minimum and maximum BON.

SensorMode, Polarization and so on are well explained in paragraph 1.8.1.1.2.

Into the Acquisition stations panel, the user can define the acquisition stations where the acquired data shall be downloaded from. In detail, the user selects the list of stations that UGS shall take into account for downloading (“Choice” column). The user can also indicate the mandatory station where the data shall be downloaded (“Mandatory” column) from. Finally, a backup acquisition station can be selected, if none of the chosen stations are available for download (“backup station” combo box).

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.4 Delivery Type Choice

Through the delivery type options form the user is allowed to insert the parameters related to data delivery. User can select the preferred kind of delivery:

Figure 17: Service Definition wizard: Delivery type choice

“electronic delivery” (FTP delivery, next panel is “Ftp Delivery” panel),
“media delivery” (Mail delivery, next panel is “Mail Delivery” panel).

The “Mode” of the delivery can also be selected. This field can hold the following values:

· “single” - the user requires a single delivery of the product.The delivery mode single (single delivery for the all products) is appropriate only for request that involves few standard products;

· “in batch”- the user requires a multiple delivery of the product.The delivery mode in batch means that each product is delivered one by one.

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.5 Delivery options

1.7.5.1 FTP Delivery

Through the FTP delivery panel the user is allowed to insert the parameters related to data delivery by mean electronic link using FTP protocol. The opportunity to select between FTP GET and FTP PUT as transfer type is provided to the user.

The following parameters can be inserted by user:

· Date (if possible) for delivery wished by the user (the estimated processing time for selected service is shown)

· the product format by means of the related combo box. Valid values for product format are for instance (valid values list depends on the service):

o HDF5,

o HTML,

o JPEG,

o GEOTIFF

Figure 18: Service Definition wizard: choice of product format

· the FTP transfer type by means of the last combo box

Figure 19: Service Definition wizard: choice of FTP GET/PUT delivery

In case the user selects an FTP GET mode, the user will download the generated product locally via the FTP GET protocol (see section 1.9.7 for details).

In case the user selects the FTP PUT mode, the following parameters shall be inserted by user:

IP Address of the destination server
user
Password
Confirmation of the password, for security reasons.

Please note that more than one IP address can be provided together with their related parameters for multiple destination delivery by pressing the “Add” button.

The inserted address(es) can be removed by checking the box on the left of the inserted record and clicking the “Remove selected” button.

Clicking “Select All” button, all the check boxes at the left of inserted ftp accounts will be selected allowing removing the accounts all at once.

Figure 20: Service Definition wizard: Insertion of PUT parameters

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

1.7.5.2 Media Delivery

In case the user selects the media delivery option the following parameters shall be filled:

Date (if possible) for delivery wished by the user (the estimated processing time for selected service is shown)
Via: the carrier of the data (DHL)
the product format by mean of the related combo box. Valid values for product format are for instance (valid values list depends on the service):

HDF5
HTML
JPEG
GEOTIFF

Medium required (CDROM, DVDROM, EXABYTE, and TAPE). The kind of media is correlated to the selected product format so that for example is not possible to select an EXABYTE support in case of HTML product format

To add a new mail address, the user shall click on “ADD” button. A form will be displayed on the screen, that shall be filled by the user (fields with ‘*’ are mandatory).

After filling the mail address fields, the user clicks on “OK” button to confirm the form data or “close” to abort the operation.

Figure 21: Service Definition wizard: Insertion of mail parameters

After inserting mail addresses where products shall be delivered, the screen will appear as following figure:

Figure 22: Service Definition wizard: list of inserted mail addresses

The “Remove” tool on the right of the form allows removing the related mail address from the list, while the “Edit” tool allows modifying mail address in the list.

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.6 Specific Parameters insertion

Note: this page will be visualized if needed to define a service request on the selected service.

This page allows the insertion of specific parameters defined in according to the kind of service. The page provides the several sections each of them containing the parameter name, a parameter description and the control used to submit the value.

Note that when a request is saved, its parameters are stored into database but the request is not yet submitted. The user can thus still modify, estimate, delete and submit it as described in the next sections.

Figure 23: Service Definition wizard: Specific parameters options

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.7 Payment Methods

Note: this page is not foreseen for all users.

Figure 24: Service Definition wizard: Payment methods

Commercial users can specify the payment method for the defined service, selecting a value from the combo box of this form. Payment methods can assume one of these three values:

Bank transfer
Credit Card
Cash on delivery

The button allows accessing the next step of service definition; the button allows coming back to the previous step.

Back to Index

1.7.8 Order details

Figure 25: Service Definition wizard: General info definition

The last page allows the user the insertion of Priority information, delivery notification, and a comment related to the order that is going to be submitted. In details:

· Mode: the operative mode. It can assume the following values (depending on the user profile):

- “routine”,

- “crisis”,

- “very urgent”.

The values of this field are in accord with the system operative mode.

· Type: type of the request. It can take on the following valid values (depending of user profile):

- “routine”,

- “privileged”.

· Level: A priority level value that defines the relative importance of the request.

· Notify Delivery: The request notification state via e-mail, telephone or fax according to its preference.

· Comment: A short description to be saved together with the request. This description shall be useful to remind the main characteristics of the request itself.

The button allows saving the current service request; the button allows coming back to the previous step.

When the user clicks on the button, a confirmation message is shown. The only button provided allows closing the main window.

Figure 26: Confirmation window

Note when a request is saved, its parameters are stored into database but the request is not yet submitted in the system. The user can thus still modify, estimate, delete and submit it as described in the next sections.

Back to Index

1.8 Service Request definition for Standard Products (Catalogue)

In order to define a new service order for catalog standard products, the logged user selects the “services” menu item shown on the upper frame as defined in the previous section and then selects the requested high level product on the left frame.

The description of the service is shown on the main central frame; the user can now start the service definition by clicking on the button “Acquisition Catalog”.

This operation changes the content of the central frame starting the wizard application that will guide the user in defining the main parameters.

See also section 2.0 for service request constraints.

Back to Index

1.8.1 Catalogue Browser

In order to define a new service order for catalogue products, the logged user selects the “services” menu item shown on the upper frame as defined in the previous section and then selects the requested high level product on the left frame.

Figure 27: Catalogue service list

Note that copy service allows to retrieve an already processed and catalogued product (raw or higher level) among the available collections .

The description of a generic service is shown on the main central frame; the user can now start the service definition by clicking on the button “Acquisition Catalog” as showed in the following figure:

Figure 28: Acquisition Catalog Button

This operation changes the content of the central frame starting the application that will guide the user in defining the main parameters.

1.8.1.1 The Catalogue Browser

The operator can do the Historical Acquisitions research on the Catalogue by the Catalogue Browser window.

Figure 29: Catalogue Browser window

Five parts compose this window:

Map Viewer
Search panel
Inventory Results table
Information panel
Buttons tool bar

1.8.1.1.1 Map Viewer

For the map tool description see the paragraph 1.7.1.

1.8.1.1.2 Search panel

The Search panel provides sections to compose a complex catalogue query.

Figure 30: Search panel

To compose a query:

· select one collection from the list named Collections. The allowed collections for the logged user listed in the panel are loaded at run time. Possible collections are the following:

o R.SARn.SAR: collection of raw data, where n identifies the order number of satellite belonging to the constellation

o P.RAW_B: collection of raw data product s(L0)

o P.SCS_B and P.SCS_U: collection of single look complex products (L1A)

o P.DGM_B: collection of detected, multilooked and ground projected products (L1B)

o P.GEC_B: collection of ground projected and ellipsoid corrected products (L1C)

o P.GTC_B: collection of ground projected and terrain corrected products (L1D)

o P.MOS_B: collection of mosaicked products (from L1B)

o P.MOS_C: collection of mosaicked products (from L1C)

o P.MOS_D: collection of mosaicked products (from L1D)

o P.MOS_H: collection of mosaicked products (from auxiliary DEM or DEM produced via L1A)

o P.CRG_A: collection of coregistered products (from L1A)

o P.CRG_B: collection of coregistered products (from L1B)

o P.PBR_B: collection of band reduction product

o P.SPF_B: collection of speckle filtered products (from L1B)

The collections displayed in the search panel depend on the service request chosen.

P is for product, R for raw.

· click on the Show below button to obtain the searchable collection query attributes

· set the parameters in the different enabled panels (panels enabled depend on the choice of collection):

§ Temporal Coverage: this panel allows the user to set the start and stop date and time only if the Time Range check button is enabled. All times are expressed in UTC time.

Figure 32: Temporal Coverage panel

By default Time Range check button is enabled and temporal coverage is null.

§ Acquisition Characteristics: this panel allows the user to define the name, the operator and the value for the returned attributes. Below there is an example.

Figure 33: Acquisition Characteristics panel

The Acquisition Characteristics are the following attributes and those displayed to user depend on choice of the collection (R (raw) or P (product)). Together with Catalogue parameters, they are common in several steps of CAM ordering. Anyway not all of them are available for COSMO data, but they have to be taken in account when using Cosmo-Skymed Interoperability.

*Attribute*	*Description*	*Operation*	*On Collections*
SatelliteId	Satellite Identifier	= like	R & P
SensorId	Sensor Identifier	= like	R & P
ProductType	Product Typology	= like	P
RecordNumber	Numeric unique identifier for a product	= => <= > < range	R & P
ProviderId	Unique identifier of the Provider		R & P
OriginatorCollection	List of Collection Identifiers from which product has been processed [ CollectionName_1 ; … ; CollectionName_x ] CollectionName STRING(30)		R & P
ProductFilename	File name	= like	R & P
*Spatial* *Coverage*	Spatial Coverage of a single item of the Collection		R & P
- Box	Upper left corner, Lower Right Corner of the rectangular shape in term of Longitude and Latitude coordinates. Longitude and Latitude are expressed in degree with a precision of hundredth of degree [ UpperLeftCorner ; LowerRightCorner ] UpperLeftCorner POINT LowerRightCorner POINT	=	R & P
- Polygon	List of vertex (last point coinciding with the first point) of the polygonal shape in term of Longitude and Latitude coordinates. The vertex must be specified in a counterclockwise direction. Longitude and Latitude are expressed in degree with a precision of hundredth of degree [ Point_1 ; Point_2 ; ………. Point_x ] Point_x POINT	=	R & P
- Circle	Centre in term of Longitude and Latitude coordinates and Radius of the circular shape Longitude and Latitude are expressed in degree with a precision of hundredth of degree while radius is expressed in km [ CenterPoint ; Radius ] CenterPoint POINT Radius UINT(5)	=	R & P
*Temporal* *Coverage*	Temporal Coverage (Start&End Time) of a single item of the Collection		R & P
- StartOfCoverage	Start Date/Time of the item in µSec	= => <= > < range	R & P
- EndOfCoverage	End Date/Time of the item in µSec	= => <= > < range	R & P
SceneCentre	Scene Centre Coordinates. Scene Centre Coordinates (defined as couple Lon, Lat that is FLOAT(5,2) : FLOAT(4,2) with ranges -180:180 and –90 : 90 respectively. For example, 16.60:40.67.)	=	R & P
PassEquatorXLongitude	Nadir Equator Crossing Longitude for this Pass		R
PassDirection	Flight direction of the Satellite (ascending/descending) A Ascending D Descending B Both	=	R & P
*VerticalCoverage*	Vertical coverage (min and max height)		R & P
- MinimumHeight	Minimum satellite heigh over earth reference surface [units: km]		R & P
- MaximumHeight	Maximum satellite heigh over earth reference surface [units: km]		R & P
OrbitNumber	Absolute Orbit Number	= => <= > < range	R & P
Track	WRS Track Number (Not used for COSMO missions)		R
Frame	WRS Frame Number (Not used for COSMO mission)		R
MissionPhaseId	Indication of the mission phase		R & P
Band	Identifier of a Sensor Band [ Band_1 ; Band_2 ; ….. ; Band_x ] where Band UINT(5)		R & P
ViewAngle	View (opening) angle of the sensor. Units: millidegrees When this parameter is used as search key, the following operation has to be applied: return all the items whose view look angle is the nearest w.r.t. the value set in the inventory search	= => <= > < range	P
Polarization	Polarization (Transmitted – Received) VV Vertical Vertical HH Horizontal Horizontal VH Vertical Horizontal HV Horizontal Vertical CO Co-Polar (Vertical Vertical, Horizontal Horizontal) CH Cross-Polar H (Horizontal Vertical, Horizontal Horizontal) CV Cross-Polar V (Vertical Vertical, Horizontal Horizontal)	= like	R & P
SensorModeId	Specific sensor mode SP_SMART Spotlight SMART (SPOTLIGHT 1) SP_ENHANCED Enhanced Spotlight (SPOTLIGHT 2) SP_300 SPOTLIGHT 300 STR_HIMAGE Stripmap HIMAGE STR_PINGPONG Stripmap PINGPONG SCN_WIDE ScanSAR Wideregion SCN_HUGE ScanSAR Hugeregion CAL_EXT CAL Mode – External Calibration CAL_TR CAL Mode – T/R Calibration CAL_IF CAL Mode – IF Calibration …… other possible sensor modes for FUGS constellations	= like	R & P
SensorModeDescription	Descriptive text of specific sensor mode		R & P
Gain	Gain Value [Units: mdB (milli-dB)]		R
*Illumination*	Sun azimut and elevation		R
- SunAzimut	Sun Azimut [Units: millidegrees]		R
- Sun Elevation	Sun Elevation [Units: millidegrees]		R
CloudCoverage	Percentage of coverage: clouds	= => <= > < range	R & P
AcquisitionStationId	Acquisition Station code where product has been acquired	= like	R & P
*CorrectionParameters*	Delta (errors) angles to nominal sensor pointing direction		R & P
- DeltaSideWardLookingAngle	Nominal look angle of the full observed swath (unsigned angle between nominal reference direction of the multi-beam and satellite nadir) [Units: mdeg (milli-degree)] When this parameter is used as search key, the following operation has to be applied: return all the items whose look angle is the nearest w.r.t. the value set in the inventory search	= => <= > < range	R & P
"- DeltaForwardLookingAngle"	Delta with the nominal forward pointing angle of the related sensor [Units: mdeg (milli-degree)]		R & P
- DeltaRoll	Delta rotation to nominal satellite position around flight axis [Units: mdeg (milli-degree)]		R & P
- DeltaPitch	Delta rotation to nominal satellite position around side axis (‘side’ is orthogonal to flight and nadir direction [Units: mdeg (milli-degree)]		R & P
DeltaYaw	Delta rotation to nominal satellite position around nadir axis [Units: mdeg (milli-degree)]		R & P
*AtmosphericConditions*	Atmospheric parameters useful for special applications		R
- LocalPrecipitationAverage	local precipitation average [Units: millimetres]		R & P
- MeanWaterVapour	mean water vapour [Units: 10(-2) g/cm**2]		R & P
- IonosphereTotalElectronCount	Ionospheric Total Electron Content [Units:10**(-1) TECU]		R & P
*IncidenceAngle*	Near and Far incidence angle		R & P
- NearRangeIncidenceAngle	Near incidence angle [Units: mdeg (milli-degree)]	= => <= > < range	R & P
- FarRangeIncidenceAngle	Far incidence angle [Units: mdeg (milli-degree)]	= => <= > < range	R & P
*ProcessingInformation*	Processing algorithm, centre, date, type		P
- ProcessingAlgorithm&Version	Processing algorithm and version		P
- ProcessingCentre	Processing centre		P
- ProcessingDate&Time	Processing date-time		P
- ProcessingType	Processing type		P
AncillaryData	Short description about ancillary data used in processing algorithm		P
AuxiliaryData	Short description about auxiliary data used in processing algorithm		P
OtherSpecificData	Specific Data different from collection to collection or for future use; they are dynamically defined into the Database in the form TAG – Value. [ Tag_1 = Value_1 ; Tag_2 = Value_2 ; ….. Tag_n = Value_n ]		R & P
Thumbnail	Thumbnail of the raw data		R & P
QuickLookId	Quick Look identifier of the raw data		R & P
BandReductionFlag	Band Reduction flag. If True indicates that the datum is acquired in SPOT300 sub-mode. Possible values: T (True), F (False)	=	R & P
LookSide	Look side. Allowed values: L (LEFT) R (RIGHT) Empty if the look side is not applicable to the collection (in case of nadir pointing or in case of mosaicked products)	=	R & P
DeliveryMode	Identification of the processing mode used to meet the delivery time constraints. It is strictly related to the accuracy level of the support data (in particular of the orbital data) used to originate the product Allowed values: F (Fast delivery) S (Standard delivery)	=	P
MissingLinesPercentage	Missing Lines percentage	= => <= > < range	R
NumberOfGaps	Number of Gaps		R
Resolution	Spatial resolution value [Units: centimeters]	= => <= > < range	R & P
LinkedCoregisteredData	Lists of record numbers of data coregistered with previously selected data. This attribute can be evaluated only in conjunction with an inventory (brief/full), i.e. the records where the query is applied is restricted to the set obtained from a previous query (e.g. a time/spatial query). The returned values are of this type: [RecordNumber_1_1; RecordNumber_1_2; ...; RecordNumber_1_n1; RecordNumber_2_1; RecordNumber_2_2; ...; RecordNumber_2_n2; ... RecordNumber_m_1; RecordNumber_m_2; ...; RecordNumber_2_nm] where RecordNumber UINT(10) This attribute is applicable only to some products collections (coregistered products). REMARK: no further operation (e.g. <, > =) can be performed after that the attribute was used after having queried using it	N.A.	P
TandemInterfCouple	List of record numbers of couple of data that are in CSK tandem interferometric configuration. This attribute can be evaluated only in conjunction with an inventory (brief/full), i.e. the records where the query is applied is restricted to the set obtained from a previous query (e.g. a time/spatial query). CSK interferometric couples are identified according to these criteria: 1) if the collection is of type "P" (product) the data are relative to the same collection 2) if the collection is of type "R" (raw) the data have to be relative to the same sensor but to different satellite IDs 3) the data have to be almost geographically overlapped (within a configurable tolerance, expressed as a percentage) 4) the sensor mode of the 2 products/raw data has to be the same 5) the data must have the same look angle 6) the satellite ID of the two products/raw data has to be different 7) the difference between the sensing start time of the 2 products/raw data has to be less than a configurable threshold (to be se to about 25 seconds) 8) data must have the same look side 9) data must have the same pass direction (data have to be flagged all ascending or all descending; “both” is not an allowed value) It would be also suggestable to identify the master in the couple (info needed for interferometric processing). The master is the one whose sensing start time is before The returned values are of this type: [RecordNumber_1_1; RecordNumber_1_2; RecordNumber_2_1; RecordNumber_2_2; ... RecordNumber_m_1; RecordNumber_m_1] where RecordNumber UINT(10) REMARK: no further operation (e.g. <, > =) can be performed after that the attribute was used after having queried using it	N.A.	R & P
MasterRecordNumber	List of record numbers of the master image among the linked coregistered data or between the inferometric couple (see above). This attribute can be evaluated only in conjunction with an inventory (brief/full), i.e. the records where the query is applied is restricted to the set obtained from a previous query (e.g. a time/spatial query). This attribute is meaningful only together with the attribute "LinkedCoregisterData" The returned values are of this type: [MasterRecord_1; ... MasterRecord_1_m] where MasterRecord UINT(10) This attribute is applicable only to some products collections (coregistered products). REMARK: no further operation (e.g. <, > =) can be performed after that the attribute was used after having queried using it	N.A.	P
LinkedRepeatedTrackInterf	List of record numbers of data that could be used for interferometry purposes (repeated tracks) with a previously selected data This attribute can be evaluated only in conjunction with an inventory (brief/full), i.e. the records where the query is applied is restricted to the set obtained from a previous query (e.g. a time/spatial query). The data linked with a selected datum are searched according to the following criteria: 1) if the collection is of type "P" (product) the data are relative to the same collection 2) if the collection is of type "R" (raw) the data have to be relative to the same sensor (there is no constraint on the satellite ID) 3) the data have to be almost geographically overlapped (within a configurable tolerance, expressed as a percentage) 4) the sensor mode of the 2 products/raw data has to be the same 5) the data must have the same look angle 6) the time difference between the sensing start times has to be a multiple of 1 day, taking into account also a configurable time tolerance 7) data must have the same look side 8) data must have the same pass direction (data have to be flagged all ascending or all descending; “both” is not an allowed value) The returned values are of this type: [RecordNumber_1_1; ...; RecordNumber_1_n1; RecordNumber_2_1; ...; RecordNumber_2_n2; ... RecordNumber_m_1; ...; RecordNumber_m_n2] where RecordNumber UINT(10) REMARK: no further operation (e.g. <, > =) can be performed after that the attribute was used after having queried using it	N.A.	R & P

Table 1: Acquisition Characteristics and Catalogue parameters

Please, remind that most controls have tool-tips explaining the meaning of data shown inside..

§ Spatial Coverage: this panel allows the user:

o to define the rectangle coordinates for catalogue data searching (see rectangle map tool)

o to visualize the coordinates of the geographical area of interest for:

§ bounding box (see Auto map tool)

§ vertexes polygon (see Polygon map tool)

§ circle (see Radius map tool)

Figure 34: Spatial Coverage panel (e. g. bounding box coverage)

§ Coregistr-Interfer: this panel (enabled only for R collections) allows the user to define how interferometric image couple shall be acquired:

Figure 35: Coregistr-Interfer panel

§ The Search button: to submit the query

§ The Clear button: to clear all the parameters text fields.

1.8.1.1.3 Inventory Results

The Inventory Results panel displays the acquisitions that mach the query made by the user.

Figure 36: Inventory Results panel

Each record is also represented on the map.

Selecting a row, is possible to display information simply selecting the folder tab “Info” on the right side of the screen.

Figure 37: Service Definition wizard: Info panel

The following parameters will be displayed:

Collection Type
Product Type
Record Number
Start of coverage
End of coverage
Scene centre
Pass equator cross longitude
Pass direction
Quality classification
Acquisition Station

The meaning of them is explained in the previous paragraph.

The table columns are sortable: one click on the column header to obtain ascending sort, second click to obtain descending sort and another click to come to the beginning situation.

The CAM draws on the map the geographical areas corresponding to retrieve:

· in a bold colour the areas selected;

· in a semitransparent colour the area not selected;

· all the remaining areas are not displayed.

In order to select the product retrieved, click on the check column. One or more products can be selected.

1.8.1.1.4 Information Panel

The Information panel provides information for the specified Historical Acquisitions selected by the user from Historical Acquisitions table.

The Information panel is enabled only when the user selects an Historical Acquisition from the table.

Figure 38: Information panel

Below there are some of the most general returned for the two different catalogue type:

CollectionType: type of the collection;

ProductType: product typology;

RecordNumber: numeric unique identifier;

StartOfCoverage: start date/time of the item;

EndOfCoverage: end date/time of the item;

SceneCentre: scene centre coordinates;

PassEquatorCrossLongitude: Nadir Equator crossing Longitude for this pass;

Passdirection: flight direction of the satellite (ascending/descending);

QualityClassification: quality classification information.

Acquisition Station: identifier of Acquisition Station;

Other Button:

Thumbnail: the thumbnail image returned

Quicklook button: the button opens the quick look image in a different dialog (see below). If the current Historical Acquisition has not quick look the button is disabled.

Figure 39: Quicklook dialog

1.8.1.2 Compose and submit catalogue research query

As described in Search panel section, the user could create a complex query.

In order to compose a complex query:

· click on Search panel, if not selected;

· choose the collection type from the Collection list;

· click on the Show Below button

· fill the enabled parameters text fields;

· define the spatial coverage;

· click on the Search button in the bottom panel.

1.8.1.3 Choose Inventory Catalogue from the result set

Warning: If the selected product is not a standard frame and the AOI is smaller than product area covered, the System doesn t provide the product basing on the AOI but it provides the full product coverage as standard product size. In this case the delivery mode single is not appropriate.

After the CAM has submitted the query, the application filled the Inventory Catalogue table with the catalogue research results.

As described before, the CAM clicks on the Inventory Catalogue table rows in order to view on the map the specific acquisition geographical area in which he is interesting. Furthermore, on the right of the Map Viewer the data information of the selected acquisition are showed (see Information panel).

Figure 40: Catalogue Browser dialog

To complete the order, the user clicks on the check box in order to select the record desired and clicks on the button “Next” placed at the top right of the wizard.

Back to Index

1.9 Service Orders management

The “Orders” link allows the user to browse the orders saved into the order basket.

Note: The user can manage only his service requests.

Figure 41: Orders list

The table showed in the main frame, provide the order list with the following columns:

“ACTION”: clicking with the right button of the mouse on the “action” button into the order table raw, a pop-up menu is shown. Its entries depend on the order status. Details about each entry are given into the next paragraphs.
“REQUEST ID”: the unique identifier of the request into the order basket
“SERVICE NAME”: the name of the service relative the order
“INS DATE”: date of the order
“COMMENT”: description of the order
“STATUS”: order status
“CHANGE DATE”: date of the change order status
”ORDER ID”: unique identifier of the order into the UGS system

Clicking on “REQUEST ID”, “SERVICE NAME” and “INS DATE” table titles, the sort direction of the order list changes.

Clicking on (action button) a pop-up menu will be displayed.

In the following, a description of each pop-up menu entry will be given.

Back to Index

1.9.1 Delete

The “Delete” entry allows the user to permanently delete a previously saved request. A confirmation is required to perform such operation. In case such confirmation is provided the order is no more visible on the list.

This action is allowed in the following service request status: New, Cancelled.

Back to Index

1.9.2 View Details

The “View details” entry is accessible in every request status and allows visualizing the full set of parameters of the introduced request.

Details are provided shown on a scrollable tabular representation.

Figure 42: View Details Window

Back to Index

1.9.3 Modify

The “Modify” entry allows modifying some parameters of a previously saved request. The wizard used to create the service request is presented again but some fields are already filled with the previously inserted value.

Such field, together with the geographical representation, can be modified according to the actual needs. Note that the original geographical area is not represented on the map.

The steps are followed as in case of new request insertion. For details see section 1.7.

This action is allowed in the following service request status: New, Cancelled.

Back to Index

1.9.4 Cancel

The “Cancel” entry allows to cancel the previous estimation and to move to the “cancelled” status so that the request can be modified and sent for estimation again or can be definitively deleted. A confirmation is required.

This action is allowed in the following service request status: New, Cancelled.

Back to Index

1.9.5 Estimate / Estimation Info

The “Estimate” and “Estimation Info” allows to show a window with the estimation parameters such as cost, estimated delivery date and confidence index.

Note that a request needs to be always estimated at least one time before it is submitted after the first estimation the request passes from a state of “New” to the “Estimated” status.

It is possible to recall the estimation info every time that the order window is loaded through the “estimation info” menu entry (see Figure 39).

Figure 43: Order Estimation

The Estimate action is allowed in the following service request status: New.

The Estimate Info action is allow in the following service request status: Estimated, Submitted, Running, Completed, Available, Rejected.

Back to Index

1.9.6 Submit

The “Submit” entry allows submitting a saved request to the system. A confirmation is required.

This action is allowed in the following service request status: Estimated.

Back to Index

1.9.7 Download

The “Download” entry allows downloading the product from the UGS site when the final product is available and the user has required an electronic delivery via FTP GET.

This action is allowed in the following service request status: Available.

Back to Index

2.0 Service List and constraints

As described in the section 1.6 Cosmo-SkyMed makes available catalogue service and new acquisition service for two typology of products: standard and high level.

In the following we provide some remarks and constraints for the generation of SAR standard and high level products. Another service not available for commercial user is the Calibration service.

2.0.1 Services for the generation of SAR standard products

REMARK 1: When the sensor mode is set to SP_ENHANCED, it could happen that the Band Reduction flag is raised (i.e. the sub mode Spotlight 300 is on), even if no explicit setting of this flag was required from the user. This occurrence, in terms of the corresponding services to be provided, has the following impacts:

· If the user requires by CAM the SCS_U (Level-1A) service the PBR_B product (Level-1A band reduced) will be provided. In fact when the Band Reduction flag is raised the SCS_U product cannot be generated.

· If the user requires by CAM the SCS_B (Level-1A) service the PBR_B product (Level-1A band reduced) will be provided. In fact when the Band Reduction flag is raised the SCS_B product cannot be generated.

· If the user requires by CAM the DGM_B, GEC_B, GTC_B service, the corresponding product obtained after Band Reduction processing will be provided

Service name	Remark on the delivered service	Constraints on sensor mode	Constraints on beam ID (i.e. look angle)	Constraints on polarization
RAW_B (L0)	None	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH •VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed: • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)
SCS_B (L1A)	If the sensor mode is SP_ENHANCED and the Band Reduction flag is raised the delivered product is not the end point: it is the PBR_B (Band reduced Level-1A product).	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH • VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed: : • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)
SCS_U (L1A)	If the sensor mode is SP_ENHANCED and the Band Reduction flag is raised the delivered product is not the end point: it is the PBR_B (Band reduced Level-1A product).	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH •VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed : • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)
DGM_B (L1B)	None	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH •VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed: • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)
GEC_B (L1C)	None	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH •VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed : • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)
GTC_B (L1D)	None	For new acquisitions: Only imaging sensor modes are allowed, i.e: • SP_ENHANCED (Spotlight Enhanced) • STR_HIMAGE (Himage - Stripmap) • STR_PINGPONG (Himage - PingPong) • SCN_HUGE (ScanSAR - HugeRegion) • SCN_WIDE (ScanSAR - WideRegion)). The sensor mode is a mandatory parameter	For new acquisitions: According to the selected sensor mode, the choice of the incidence angle is constrained.	For new acquisitions: According to the selected sensor mode, the choice of the polarization is limited. If sensor mode is HI, HR,WR the following polarizations are allowed: •HH •HV •VH •VV If sensor mode is SP_ENHANCED the following polarizations are allowed: •HH •HV If sensor mode is STR_PINGPONG the following polarizations are allowed : • HH-VV (referred as CO, that is Co-polar) • HH-HV (referred as CH, that is Cross-polar H) • VV-VH (referred as CV, that is Cross-polar V)

Table 3: SAR standard products services and related constraints

2.0.2 Services for the generation of SAR high level and speckle filtered products

For what concerns the sensor mode, apart from most of the calibration service requests (last 4 rows of the following table), only imaging sensor modes can be selected.

REMARK 1: if the sensor mode of products to be generated is STR_PINGPONG and there is any constraint, in order to perform a service, on the sensor mode or on the polarization, this constraint has to be considered applicable only to one layer of the PingPong product.

REMARK 2: All the services that deal with pure coregistration, i.e.

· CRG_A from Level-1A (SCS_B product)

· CRG_A from Level-1A (SCS_U product)

· CRG_B

· MOS_B from CRG

cannot start from new acquisitions, i.e. they can start only from data already contained in the catalogue (raising up their processing level or copying coregistered products). This is due to the fact that the external user has to set the master image, that can be detected only by visual inspection of product content (which cannot be performed if data have to be still acquired).

As a consequence, if the user wants to get coregistered products from data to be acquired, he/she has to perform the following service requests:

1) services where the new acquisitions are required (ordering Level-0, Level-1A or Level-1B products)

2) service where coregistration is required (at least L0F data relative to the previous orders are in the catalogue and their Quick Look images are available).

REMARK 3: for what concerns the PBR_B service, it will consist only in the copy (and delivery) of the products present in the catalogue. In other words, PBR_B cannot be generated from new acquisitions by an explicit user request; moreover it cannot be generated by raising the product level (e.g. from catalogued raw data (L0F), or RAW_B (L0 product)) by an explicit user request. These two services are indirectly performed if the users asks for a SCS_U/SCS_B with sensor mode S1 or S2 and if the Band Reduction is on. See also REMARK 1 of section 2.0.1

Service name	Constraints on cardinality and geographical overlap of input data	Constraints on sensor mode	Constraints on beam ID/look side	Constraints on polarization	Other constraints
MOS_B	Minimum number: 2 (not necessarily spatially overlapped)	• If sensor mode is STR_PINGPONG (PingPong), only products with the same sensor mode can be processed • If sensor mode is not PP: there is no constraint on sensor mode (also products with different sensor modes can be processed)	None	All input products must have the same polarization	• All the input data must be relative to the same UTM zone • In order to avoid the generation of too large mosaicked products, the ensemble of the input data cannot exceed a maximum geographical coverage. These limits depend of the sensor mode of input data and on their spacing. The following table describes some specific cases of these constraints; therefore the table is not exhaustive in terms of size/geographical constraints • If the format of the final product is GEOTIFF it has to be taken into account that the maximum allowed output product size is 2 GigaBytes
MOS_C	Minimum number: 2 (not necessarily spatially overlapped)	• If sensor mode is STR_PINGPONG (PingPong), only products with the same sensor mode can be processed • If sensor mode is not PP: there is no constraint on sensor mode (also products with different sensor modes can be processed)	None	All input products must have the same polarization	• All the input data must be relative to the same UTM zone • In order to avoid the generation of too large mosaicked products, the ensemble of the input data cannot exceed a maximum geographical coverage. These limits depend of the sensor mode of input data and on their spacing. The following table describes some specific cases of these constraints; therefore the table is not exhaustive in terms of size/geographical constraints • If the format of the final product is GEOTIFF it has to be taken into account that the maximum allowed output product size is 2 GigaBytes
MOS_D	Minimum number: 2 (not necessarily spatially overlapped)	• If sensor mode is STR_PINGPONG (PingPong), only products with the same sensor mode can be processed • If sensor mode is not PP: there is no constraint on sensor mode (also products with different sensor modes can be processed)	None	All input products must have the same polarization	• All the input data must be relative to the same UTM zone • In order to avoid the generation of too large mosaicked products, the ensemble of the input data cannot exceed a maximum geographical coverage. These limits depend of the sensor mode of input data and on their spacing. The following table describes some specific cases of these constraints; therefore the table is not exhaustive in terms of size/geographical constraints • If the format of the final product is GEOTIFF it has to be taken into account that the maximum allowed output product size is 2 GigaBytes
CRG_A from Level-1A SCS_B	Minimum number: 2 Partially overlapped in the geographical area.	• Only products with the same sensor mode can be processed • Products with sensor mode set to STR_PINGPONG (PingPong) cannot be processed • If sensor mode is Spot: data with band reduction activated cannot be processed	• If sensor mode SP_ENHANCED, STR_HIMAGE, STR_PINGPONG: only products with the same beam ID (i.e. look angle) and with the same look side can be processed. • If sensor mode SCN_WIDE or SCN_HUGE: input products must have the same combination of beam IDs (multibeam ID) and the same look side.	All input products must have the same polarization	• Inputs can be extracted only from the catalogue (i.e. the service cannot be started from new acquisitions) • Among the products to be processed, the master image has to be set (mandatory parameter) • Only products with the same orbit direction (all ascending or all descending; no other choices are allowed) can be processed • Please, note that it is not possible to order .a CGR_A service, choosing SAR1, SAR2, SAR3 or SAR4 collections (Rawdata). If you want to get a CRG_A product, you need to execute the following steps: 1. Choose SCS_U (SCS_B) service from Catalogue 2. Using filter options, find the first Raw datum you need to co-register and submit the request 3. Repeat the previous step for the second Raw datum. 4. The system will generate some SCS_U (SCS_B) products using the first datum and the same number of products using the second raw datum 5. Wait until the previous SCS_U (SCS_B) requests have been completed. 6. Choose CRG_A service from catalogue you need, choose P.SCS_U (P.SCS_B) collection and find the products generated in the step 4 7. Submit a request for each couple of products to co-register, generated from the previous choosen Raw data
CRG_A from Level-1A SCS_U	Minimum number: 2 Partially overlapped in the geographical area.	• Only products with the same sensor mode can be processed • Products with sensor mode set to STR_PINGPONG (PingPong) cannot be processed • If sensor mode is Spot: data with band reduction activated cannot be processed	• If sensor mode SP_ENHANCED, STR_HIMAGE, STR_PINGPONG: only products with the same beam ID (i.e. look angle) and with the same look side can be processed. • If sensor mode SCN_WIDE or SCN_HUGE: input products must have the same combination of beam IDs (multibeam ID) and the same look side.	All input products must have the same polarization	• Inputs can be extracted only from the catalogue (i.e. the service cannot be started from new acquisitions) • Among the products to be processed, the master image has to be set (mandatory parameter) • Only products with the same orbit direction (all ascending or all descending; no other choices are allowed) can be processed • Please, note that it is not possible to order .a CGR_A service, choosing SAR1, SAR2, SAR3 or SAR4 collections (Rawdata). If you want to get a CRG_A product, you need to execute the following steps: 1. Choose SCS_U (SCS_B) service from Catalogue 2. Using filter options, find the first Raw datum you need to co-register and submit the request 3. Repeat the previous step for the second Raw datum. 4. The system will generate some SCS_U (SCS_B) products using the first datum and the same number of products using the second raw datum 5. Wait until the previous SCS_U (SCS_B) requests have been completed. 6. Choose CRG_A service from catalogue you need, choose P.SCS_U (P.SCS_B) collection and find the products generated in the step 4 7. Submit a request for each couple of products to co-register, generated from the previous choosen Raw data
CRG_B	Minimum number: 2 Partially overlapped in the geographical area.	Only products with the same sensor mode can be processed	None	All input products must have the same polarization	• Inputs can be extracted only from the catalogue (i.e. the service cannot be started from new acquisitions) • Among the products to be processed, the master image has to be set (mandatory parameter)
MOS_B from CRG	Minimum number: 2 Partially overlapped in the geographical area.	Only products with the same sensor mode can be processed	None	All input products must have the same polarization	• Inputs can be extracted from the catalogue (i.e. the service cannot be started from new acquisitions) • Among the products to be processed, the master image has to be set (mandatory parameter) • Only products with the same orbit direction (all ascending or all descending; no other choices are allowed) can be processed • All the input data must be relative to the same UTM zone • In order to avoid the generation of too large mosaicked products, the ensemble of the input data cannot exceed a maximum geographical coverage. These limits depend of the sensor mode of input data and on their spacing. The following table describes some specific cases of these constraints; therefore the table is not exhaustive in terms of size/geographical constraints • If the format of the final product is GEOTIFF it has to be taken into account that the maximum allowed product size is 2 GigaBytes
MOS_H	Minimum number: 2 (not necessarily spatially overlapped)	None	None	None	• The only allowed input collection (from catalogue) is DEM_H • All the input data must be relative to the same UTM zone • In order to avoid the generation of too large mosaicked products, the ensemble of the input data cannot exceed a maximum geographical coverage. These limits depend of the sensor mode of input data and on their spacing. The following table describes some specific cases of these constraints; therefore the table is not exhaustive in terms of size/geographical constraints • If the format of the final product is GEOTIFF it has to be taken into account that the maximum allowed product size is 2 GigaBytes
SPF_B	None	None	None	None	None

Table 4: SAR high level and speckle filtered services and related constraints

In the following tables are described the geographical and size contraints:

Acquisition mode	Scene coverage (Km²)	File size (Mbytes)
*Enhanced* *Spotlight*	20 x 20	» 3200
*Himage*	300 x 300	» 28800
*PingPong*	300 x 300	» 3600
*WideRegion*	300 x 300	» 800
*HugeRegion*	400 x 400	» 128

Table 5: MOS_B, MOS_C, MOS_D geographical and size constraints (special case)

Acquisition mode	Scene coverage (Km²)	File size (Mbytes)
*Enhanced* *Spotlight*	20 x 20	» 355
*Himage*	300 x 300	» 6200
*WideRegion*	300 x 300	» 800
*HugeRegion*	400 x 400	» 128

Table 6: MOS_H geographical and size constraints (special case)