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>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 283 of 350<br />

‣ Navigation through the authorised datasets;<br />

‣ Search of products according to the user-driven filtering requests;<br />

‣ Specific <strong>Sentinel</strong>-2 filtering capabilities based on the products cloud-coverage;<br />

‣ Product pre-visualisation capabilities based on the archived browse images;<br />

‣ Geo-reference of the browse image and display through Web Map Servers;<br />

‣ Visual inspection of the associated product metadata;<br />

‣ Product selection and ordering based on the previous product discovery activities.<br />

This operation scenario allows the user to discover the available production according to the<br />

authorised access leverage. Subsequently, the user will be able to request the desired<br />

production for download at the user-base.<br />

6.11.3.6 Product Download<br />

This operation scenario stands for the user-driven activities for product download at the userbase.<br />

Once the user has identified the desired production (cf. previous scenario), it requests it<br />

for product download.<br />

The MMUS function relies on the DAG function for the product-component (granules/tiles)<br />

download activities from the archive centres and subsequent end-product reconstruction<br />

activities (cf. section 6.10.3.1).<br />

The following steps are identified for this operation scenario:<br />

1) The user via MMUS client-side (i.e. web browser) request for download the desired<br />

production as identified by the product discovery activities;<br />

2) The MMUS function verifies the user access-leverage and authorises the request;<br />

3) The MMUS function conforms a request according to the defined interface and passes<br />

it to the DAG function client side (i.e. a plug-in to the web browser) that performs the<br />

products components download;<br />

4) The DAG function client side, once all the product components have been<br />

downloaded at the user base, reconstructs the user-product as requested.<br />

In this manner, the (registered) users can download the authorised <strong>Sentinel</strong>-2 products.<br />

6.11.3.7 Subscriptions for Automatic Product Download<br />

This operation scenario stands for the automatic product download at the user-base. By<br />

usage of the MMUS function (ngEO Download Manager), the user is able to automatically<br />

receive the desired <strong>Sentinel</strong>-2 products.<br />

The following steps are identified for this operation scenario:<br />

1) The user subscribes to the desired and authorised datasets (i.e. shopcart<br />

management);<br />

<strong>ESA</strong> UNCLASSIFIED – For Official Use<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!