GSC Sentinel-2 PDGS OCD - Emits - ESA
GSC Sentinel-2 PDGS OCD - Emits - ESA
GSC Sentinel-2 PDGS OCD - Emits - ESA
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 90 of 350<br />
Over oceans or open seas, the WGS84 geoid altitude is considered. Presently WGS 84 uses<br />
the 1996 Earth Gravitational Model (EGM96) geoid, revised in 2004. Over land and inland<br />
waters, the altitude information is given with respect to the geoid altitude reference EGM96.<br />
4.3.9.3 Data Compression versus Data Quality Trade-Off Constraints<br />
An average acquisition of 6640 km along the <strong>Sentinel</strong>-2 orbit will amount to about 60GBytes<br />
of on-board compressed raw instrument data. Therefore the daily amount of compressed data<br />
received on-ground will result to about 887GB per satellite. Besides issues related to data<br />
processing and storage, these large volumes raise a non-negligible constraint for the efficient<br />
dissemination of final products to end users. Indeed, it was computed that a <strong>Sentinel</strong>-2<br />
square image of 290km x 290km comprehensive of all spectral bands will weight around 7.4<br />
GBytes without any compression.<br />
Hence, a data-compression step is provisioned for at the term of the MSI processing cycle.<br />
Nevertheless, data-compression shall be controlled such as to avoid jeopardizing image<br />
quality. To this end, a preliminary trade-off analysis based on the standard JPEG2000<br />
compression algorithm is reported in [RD-30] to support the optimal selection of this<br />
compression step.<br />
4.3.10 CONSTRAINTS AND DEPENDENCIES DRIVEN BY THE CGS<br />
NETWORK<br />
As a matter of fact, the CGS network that will support the <strong>PDGS</strong> operations is at this stage<br />
not settled. This section reviews the constraints and dependencies associated.<br />
4.3.10.1 Near-Real-Time Data Timeliness<br />
The large MSI mission data-rate and global acquisition plan coupled with the available CGS<br />
network selected to recover the payload data on-ground will constrain the amount and data<br />
that can be provided with NRT timeliness, while ensuring that all data can be provided within<br />
a day.<br />
Based on [AD-03], it is assumed that about 25% of the globally acquired data by one<br />
spacecraft can be downlinked with NRT-compatible timeliness when using a suitable CGS<br />
network of 4 stations. It was also calculated that a payload data recovery plan leading to<br />
100% of NRT-compatible timeliness can be obtained using a network of about 6<br />
complementary ground-stations.<br />
Figure 4-6 extracted from [RD-19] depicts the distribution of the age of the data at the time it<br />
is acquired on-ground, without zone prioritization for NRT playback, and considering a CGS<br />
network composed of the Kiruna, Svalbard, Maslapomas, and Prince-Albert stations. In this<br />
simulation, the globally averaged timeliness amounts to 6.298 hours at data-reception time.<br />
When using the NRT priority downlink functionality outlined in section 4.5.4.2.2 ensuring that<br />
specific zones are acquired with NRT-compatible latencies, the remaining global timeliness<br />
distribution may be altered significantly; Figure 4-7 shows that in the same 4 stations<br />
scenario, prioritizing Europe for NRT timeliness makes the geographical distribution of data<br />
age vary meaningfully with respect to the routine scenario.<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>.