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 194 of 350 ○ Systematic inventory and archiving of all data with the configured retention; ○ Systematic and data-driven internal data circulation among the distributed CGSs and PACs according to the configuration; ○ Systematic generation of operation reports at all elaboration steps for performance monitoring and assessment; ○ Systematic distribution of the output data and reports towards external interfaces or local publishing through the data-access network. The generation of the Level-2A prototype product will be performed as triggered interactively by authorised users via the hosted processing functionality. Contingency operations will be triggered on malfunctions in the nominal data flow covering: ○ Recovery of malfunctions in the Level-0 processing chain; ○ Recovery of higher-level productions; ○ Recovery of problems throughout the data archiving and circulation network. All malfunctions will be centrally reported to the Reference Platform for investigation. 4.10.3.4 Long-Term Data Preservation Service This background service aims at globally responding to the long-term accessibility of Sentinel- 2 data. It features in particular the parallel operation of redundant long-term archive centres via well-defined service level agreements ensuring the LTDP objectives described in section 4.5.1.6. Bulk reprocessing operations will be performed as driven by the required evolutions of the Sentinel-2 Level-1 and Level-2 datasets in the long term. 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.
5 PDGS DESIGN GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 195 of 350 This chapter defines the internal design of the PDGS in answering to the operation baseline described in the previous chapter. It consists in a breakdown description of the system into building-block components with reduced perimeter which consistently extend as a whole to the PDGS system perimeter through inter-component interactions. After an outline description of the overall design logic, this chapter details the design of the PDGS from the functional and physical viewpoints. A last section describes the operation layout of the PDGS in each of its different operational configurations as corresponding to the three mission operation scenarios preliminarily introduced in section 4.9 - PDGS Operation Layouts. 5.1 Overall Design Logic The system breakdown will be described at two levels: ○ At functional level (cf. section 5.2), providing a logical split of the required PDGS functionality into functional blocks, each one regrouping a consistent set of low-level functions and operating interfaces with other functions. The breakdown components will be referred to as “Functions” related via “Functional Interfaces”; ○ At physical level (cf. section 5.3), providing an actual split of the defined functionality into generic centres geographically distributed, each one having a well-defined operational role characterised by the logical grouping of the previously defined functional blocks (i.e. Functions), and interacting one with another via physical interfaces within the overall layout. The breakdown components will be referred to as “Centres” related via physical interfaces, exposing some of them externally to the PDGS and corresponding to the external interfaces defined in section 4.2.2. The comprehensive design will derive from this logical-to-physical aggregation of primary Functions into physical Centres, mapping the leading and complementary role of each centre by a simple collocation of primary Functions. The PDGS operation layout will be described (cf. section 5.4) according to the baseline operation scenario defined in section 4.9. The PDGS high-level design does not intend to provide an engineered decomposition of the PDGS into physical components beyond distributed Centres. Some Functions in parts or as a whole will aim at a near direct translation into hardware and software systems (reused or explicitly developed or both). Others will either refer to: ○ a functional service that will not lead to any explicit development and that is intended to be procured through the direct reuse of services that can answer to the demand with little required customisation; ○ a specific functionality that cannot be provided through automated and computer means as requiring specific interactivity and expertise; 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 147 and 148: ESA UNCLASSIFIED - For Official Use
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 189: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 207 and 208: ○ Effective processing resources
Page 231 and 232: o preserving integrity of exchanged
Page 241 and 242:
Page 243 and 244:
6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246:
o Report generation frequency and c
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
○ MSI L1A, L1B, L1C and TCI produ
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
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?