GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 216 of 350 ○ Files circulation towards EDRS ground link gateway; ○ Relevant M&C information; 5.2.3.9 Precise Orbit Determination (POD) Function 5.2.3.9.1 Function Objectives and High-Level Description The POD function is responsible to generate predicted/restituted orbit products to support MSI science data processing activities in case the Navigation Solution (PVT) presents a degraded error-budget. As such, it is in charge of: ○ Providing Sentinel-2 predicted POD products every orbit for each spacecraft (S2A and S2B) for science data processing in 3h-NRT; ○ Providing Sentinel-2 restituted POD products for each provided L0 satellite ancillary product (for both S2A and S2B spacecrafts) for nominal 24h science data processing; ○ Analysing the on-board navigation solution accuracy and associated reporting activities (delegated to the Off-line POD service interfaced by the MPA function as an Expert Team; cf. section 6.16.3.6); ○ Analysing the own generated POD products accuracy with respect to their related timeliness and accuracy thresholds (delegated to the Off-line POD service interfaced by the MPA function as an Expert Team; cf. section 6.16.3.6); Predicted POD product will be generated by the POD function using as input the GNSS L0 products (obtained from satellite ancillary packet store), auxiliary files from external data providers (GPS clocks & orbits ephemeris, environmental data, etc) and information on the Sentinel-2 spacecraft (manoeuvres, attitude, etc.). The accuracy ensured for POD predicted products is 10m on the 2D position. Restituted POD product will be generated by the POD function using as input the GNSS L0 products, auxiliary files from external data providers (GPS clocks & orbits ephemeris, environmental data, etc) and information on the Sentinel-2 spacecraft (manoeuvres, attitude, etc.). The accuracy ensured for POD restituted products is 3m (TBC). 5.2.3.9.2 Design Drivers and Constraints The following drivers and constraints are identified: ○ Reuse of common multi-sentinels equipment. POD function is designed to offer POD products to different sentinels missions; ○ POD products generation timeliness according to coverage and accuracy needs for science processing. 3h-NRT and 24h nominal processing timeliness for MSI science data imposes timeliness constraints on the POD products generation. 5.2.3.9.3 Function Interfaces The following function interfaces are identified for the POD function: ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 217 of 350 ○ Input satellite L0 ancillary data provided by DPC function through DC function; ○ Input auxiliary data autonomously gathered by POD function from external auxiliary providers (e.g. GPS orbits & clocks data from IGS) making use of DC function; ○ Input FOS orbit files (i.e. predicted & restituted orbit files) provided through the MCC and DC functions ○ FOS manoeuvre and resulting satellite mass property files provided through the MCC and DC functions; ○ Output POD predicted and restituted products autonomously delivered to all centres with MSI data processing capabilities; ○ M&C interface; 5.2.3.10 Auxiliary Data Supply (ADS) function 5.2.3.10.1 Function Objectives and High-Level Description The ADS function is in charge of the generation and supply of all the PDGS required auxiliary data from external sources (cf. [RD-06]). 5.2.3.10.2 Design Drivers and Constraints The ADS function aims for a direct mapping to the external data-sources identified in [RD-06]. Accordingly it will fully mimic the applicable interface mechanisms for every external data source; in such manner ensuring the complete operability of the PDGS without any interaction with the real external data sources. 5.2.3.10.3 Function Interfaces A unique interface to the DC function is identified, either centralised at PDGS level or distributed in every processing centre. 5.2.3.11 Data-Access Index (DAX) Function 5.2.3.11.1 Function Objectives and High-Level Description Because of the distributed PDGS context, Product Data Items (PDIs) may be scattered and possibly mirrored in several PDGS centres. The DAX function aims at providing a single centralised point for maintaining data location indexes of all product data amongst PDGS federated archive centres. Their physical location and relevant metadata is indexed to support their discovery for download as part of the User-Product generation process. In addition, it is in charge of consolidating the global PDGS data catalogue and mirroring it to downstream functions and to external interfaces to allow for catalogue browsing by the users. As such, it is in charge of: ○ Creating and maintaining indexes of all PDGS archived Product Data Items; ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
Page 1 and 2:
document title/ titre du document P
Page 3 and 4:
GSC Sentinel-2 PDGS OCD issue 1 rev
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
[RD-33] Sentinel-2 MSI - Level 2A A
Page 35 and 36:
Page 37 and 38:
LES LGS Land Equipped Sites Local G
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
ESA UNCLASSIFIED - For Official Use
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Table 4-5 Radiometric image quality
Page 99 and 100:
Product- Type On-Line retention Off
Page 101 and 102:
Page 103 and 104:
4.5.1.5 Scalability and Flexibility
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
4.6.3 OPERATIONAL TRANSFER BASELINE
Page 161 and 162: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 163 and 164: ESA UNCLASSIFIED - For Official Use
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 191 and 192: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 207 and 208: ○ Effective processing resources
Page 211: ESA UNCLASSIFIED - For Official Use
Page 231 and 232: o preserving integrity of exchanged
Page 243 and 244: 6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246: o Report generation frequency and c
Page 251 and 252: ○ MSI L1A, L1B, L1C and TCI produ
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Some relevant use cases are present
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Two main mapping services have been
Page 327 and 328:
The requirement on the cloud covera
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?