29.11.2014 Views

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ESA</strong> UNCLASSIFIED – For Official Use<br />

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>OCD</strong><br />

Issue 1 Revision 2 (draft) - 25.07.2010<br />

GMES-GSEG-EOPG-TN-09-0008<br />

page 281 of 350<br />

‣ Gateway towards the CDS/DAIL in support of the HMA cataloguing and ordering<br />

service.<br />

6.11.1.2 Role Split with the DAG Function<br />

The MMUS function catalogues the <strong>Sentinel</strong>-2 production in order to support the product<br />

queries performed by the users and subsequently offer an on-line download interface.<br />

As explained in section 6.10.1.3, the MMUS function will make use of the DAG function to<br />

perform the actual downloads.<br />

6.11.2 OPERATION CONSTRAINTS<br />

The MMUS function, although it has a multi-mission nature, it must cope with some mission<br />

specific design drivers in order to be able to perform the related product presentation and<br />

subsequent management of the product download activities. More concretely, the MMUS<br />

function will manage the <strong>Sentinel</strong>-2 product breakdown strategy (i.e. product decomposition<br />

into granules and tiles, cf. [RD-07]) as part of the catalogue activities and subsequent product<br />

discovery and download activities triggered by the user.<br />

6.11.3 OPERATION SCENARIOS<br />

6.11.3.1 <strong>Sentinel</strong>-2 Users Management<br />

This operation scenario stands for the operator-driven (administrator level) management of<br />

the <strong>Sentinel</strong>-2 users including definition of profiles, users pre-registration activities, accessleverage<br />

definition, etc.<br />

Accordingly the MMUS function operation will administrate the access to the users, and their<br />

related authentication and authorisation activities.<br />

6.11.3.2 <strong>Sentinel</strong>-2 Datasets Management<br />

This operation scenario stands for the operator-driven (administrator level) management of<br />

the <strong>Sentinel</strong>-2 production datasets (i.e. product collections) offered to the users. As part of<br />

this scenario, it is comprised the definition, publishing, update and removal of the different<br />

<strong>Sentinel</strong>-2 datasets.<br />

This scenario includes the appropriate definition of the access leverage to such datasets<br />

according to the different user profiles.<br />

The MMUS function operator will define the <strong>Sentinel</strong>-2 datasets and the access leverage<br />

according to the HLOP covering typically:<br />

‣ Datasets definition based on time-window and geographic coverage;<br />

‣ Datasets definition based on the cloud-cover percentage;<br />

‣ Datasets definition based on the product-type;<br />

‣ Datasets envisaged for the expert and cal/val users.<br />

© <strong>ESA</strong><br />

The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied or<br />

communicated to any third party without written permission from <strong>ESA</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!