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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

single access point to all the <strong>PDGS</strong> archived content keeping the necessary references to the<br />

archive sources.<br />

6.9.1.2 Data Index Composition<br />

The DAX function will host all the required information needed to support the data-location<br />

requests and assemble the <strong>Sentinel</strong>-2 products. Such information is the hereafter called “data<br />

indexes” and it is generated from the distributed archives inventoried metadata.<br />

The data indexes encapsulate the <strong>PDGS</strong> federated nature and manage the potential<br />

redundancy of the archived data available in different archives:<br />

The DAX function consolidates the metadata, identifying potential redundancies (same<br />

product data available on different archive centres), and normalizes it as part of the<br />

data indexes generation activities;<br />

The DAX function keeps trace to all the sources (i.e. the different archives) available to<br />

support the data retrieval operation of every component of the product data.<br />

The data indexes will make use of different product components metadata and will typically<br />

include:<br />

Product-type<br />

Sensing-time coverage<br />

Archive sources (data-sinks location)<br />

The supported data discovery requests based on the data indexes can be classified in:<br />

Data availability request. A view on the available data according to the request criteria<br />

is provided hiding data redundancies if any;<br />

Data location request. References to the data physical location within the archives are<br />

provided to support data retrieval activities.<br />

Therefore the data indexes will replicate as required the metadata inventoried in the<br />

distributed archives to support queries on the location of the product components archived on<br />

the different centres.<br />

6.9.2 OPERATION CONSTRAINTS<br />

The following operation constraints have been identified:<br />

The DAX function will be able to operate in hot-redundancy between remote centres<br />

(with a DAX function backup instance);<br />

As a federation function, the DAX function will systematically interface to newly<br />

deployed archives centres and in consequence assume additional indexing load;<br />

The DAX function will be able to support a growing number of simultaneous request in<br />

result of a potential increase of data-access requests;<br />

The DAX function will be centrally deployed in a <strong>PDGS</strong> single access point that will be<br />

mirrored for redundancy.<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!