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

the on-ground POD products generated (i.e. Predicted and Restituted POD products), which<br />

are relevant to the MSI processing activities according to the mission requirements in terms of<br />

geometric accuracy.<br />

6.7.2 OPERATION CONSTRAINTS<br />

The following operation constraints are identified:<br />

○ POD function operations rely on adequate GNSS measurements and cannot be<br />

intended to generate orbit products in case of unavailability of the on-board GNSS<br />

receiver.<br />

○ POD activities result from an estimation process of an adequate GNSS measurements<br />

datasets that determine the position and the velocity of the <strong>Sentinel</strong>-2 satellite centre of<br />

mass. Depending on the parameterization needed for the required accuracy of the<br />

orbit determination, potential data gaps in the GNSS data may degrade the<br />

performance (typically when duration achieves a quarter of an orbit). Therefore<br />

significant GNSS data gaps due will result in the generation of degraded POD products<br />

or not generation at all depending on the gaps length.<br />

6.7.3 OPERATION SCENARIOS<br />

6.7.3.1 POD Configuration<br />

This scenario accounts for the operator-driven configuration of the Precise Orbit<br />

Determination function. The POD configuration includes amongst others required input files<br />

definition, auxiliary data provider interfaces definition, processing rules definition, etc.<br />

The following configuration steps can be performed in support of the other operation<br />

scenarios:<br />

1) Define and configure the different interfaces for inputs management (e.g. definition of<br />

the interfaces for the GPS clocks & orbits data gathering);<br />

2) Define the POD products generation rules by configuration of used input file-types,<br />

generation method (scheduled / data-driven), GNSS data gaps management, etc;<br />

3) Configure the analysis and reporting of the<br />

The use case of this operation scenario is the configuration of the different tasks performed<br />

by the POD function such as:<br />

Auxiliary inputs management. This is the definition of the interfaces plus applicable<br />

products gathered.<br />

<strong>Sentinel</strong>-2 predicted POD product generation configuration performed by definition of<br />

the triggering mode (scheduled or data-driven), inputs type, coverage, timeliness, etc.<br />

<strong>Sentinel</strong>-2 restituted POD product generation configuration performed by definition of<br />

the triggering mode (scheduled or data-driven), inputs type, coverage, timeliness, etc.<br />

Configuration of the on-board navigation and POD products reports by definition of the<br />

generation frequency, definition of the contents, delivery method, etc.<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!