12.07.2015 Views

GSC Sentinel-2 PDGS STBD - emits - ESA

GSC Sentinel-2 PDGS STBD - emits - ESA

GSC Sentinel-2 PDGS STBD - 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>STBD</strong>Issue 1 Revision 2 (draft) - 25.07.2010GMES-GSEG-EOPG-TN-09-0031page 54 of 606 CONCLUSIONThis document has described the <strong>Sentinel</strong>-2 <strong>PDGS</strong> technical budget offering a preliminarydimensioning that, even if it needs to be refined by the <strong>PDGS</strong> prime contractor, allowshighlighting the bottlenecks and the greatest difficulties but also showing the feasibility of thesystem.The Nominal and NRT timeliness constraints are finally less problematic than it seemed atthe beginning of the analysis.The main difficulties are linked to the huge data volume to manage for processing,circulation, dissemination and archive.Considered the instrument complex architecture, complicated algorithms shall be applied forthe corrections on ground and they shall foresee a high level of parallelisation to meet thetimeliness requirements. Nowadays solutions exist to solve this point thus, under this aspect,the <strong>PDGS</strong> team is confident about system feasibility.The federative configuration is the main bottleneck of <strong>Sentinel</strong>-2 <strong>PDGS</strong> development.The amount of data to circulate, distribute and archive has no precedents and it constitutes atechnological challenge that is without any doubts solvable with nowadays resources andthat in the future will be for sure even easier to cope with.<strong>ESA</strong> UNCLASSIFIED – For Official Use© <strong>ESA</strong>The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied orcommunicated 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!