4 Final Report - Emits - ESA

4 Final
Report
management functions, e.g. provisions of access rights, granting of user privileges, etc. By defining
the access rights, a user may have the privilege only to browse the request/mission catalogue, to
subscribe to request to currently scheduled acquisitions products, up to requesting new acquisitions.
In this context, the User Portal is also responsible of providing prioritized access for users requesting
new acquisitions in the frame of emergency applications. This is in particular necessary to guarantee
the high reactivity of the overall system for emergency situations.
The UACC (User Access, Coordination and Control) domain is currently responsible of the interface
with the end-user and for all the services pertaining to the user interfaces including the ordering
function, the mission planning, the master catalogue and the help desk (with the exception of the
dissemination). The UACC domain is composed of a number of heterogeneous elements, some of
them being natively multi-mission (e.g.: MUIS, MMMC, EOLI), some other elements, which were notnatively
multi-mission, have been adapted. The UACC domain is located at ESRIN.
For Geo-Oculus, the evolvement of the current UACC towards multi-mission planning can be
considered as a preliminary baseline for defining the realisation of user accesses and all related
functionalities.
4.6.2.6 Payload Data Reception, Processing and Dissemination
As already stated earlier, the reception of Payload data can make use of:
• A nominal Payload Receiving Station collocated with the main Processing and Archiving
Facility
• A set of smaller user dedicated Payload Receiving Stations, with smaller size dishes.
At time of ingestion, the Payload data will be decrypted first. After that, the Payload data have to be
screened and the metadata attached to this Payload data are extracted in order to feed the catalogue.
A Moving Window Display function may be included to provide the capability to display the raw data
before it is processed.
Within the Payload Data Ground Segment, the processing should proceed up to Level 1B or even
further, depending on the availability of auxiliary and ancillary data required for processing. These
include auxiliary data resulting from calibration (generated inside the PDGS), predicted or restituted
orbit data (generated by the FOS) and other auxiliary / ancillary data for instance for more precise
geo-localisation or ortho-rectification.
Dissemination should occur mainly towards the service segment, the latter being in charge of further
processing and delivery of value added services in compliance with the GMES Service provision
model.
The above-mentioned processing chain for the image product has to be fully automatic in order to
minimise the processing delays in the context of emergency observation missions. The assignment of
different priority levels for each self-contained image product may be suitable to additionally accelerate
the processing and transmission of urgent data.
Regarding the required processing performance, it is suitable to analyse a worst-case scenario. For
oil-slick detection, an image size of approx. 6E+09 Bits can be assumed. A product consists of 15
image parts, giving in total 9E10 Bits to be processed. As a reference for a first approximation we can
assume that the required floating point operations (FLOPS) per bit are comparable to the processing
of a Spot 5 image. For a Spot 5 image, 2000 FLOPS per bit are required, which results in a total of
Page 4-84 Doc. No: GOC-ASG-RP-002
Issue: 2
Astrium GmbH Date: 13.05.2009