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 268 of 350 6.8 Archive & Inventory (AI) Operations 6.8.1 PRINCIPLES 6.8.1.1 PDGS Archive Concept The Sentinel-2 PDGS will archive all the MSI data during the mission operations phases (E1 and E2 phases) plus 25 years after EOM. The PDGS will cope with different archive needs on data access timeliness, size storage needs, data availability, consumers requiring such data (end users, other PDGS elements, etc.). Accordingly, the PDGS archive concept is implemented through PDGS AI function and the LTA service function. More concretely the AI function will interface with the LTA service for data supply and retrieval of the long-term archived data. Thus the AI function will encapsulate the LTA service function to the other PDGS functions by direct interface. 6.8.1.2 PDGS Archive Federated & Collaborative Concept 6.8.1.2.1 Core PDGS Archive The Sentinel-2 PDGS Products Data Access and Long Term Data Preservation (LTDP) services will be ensured by the PDGS archive deployed in the different core centres. The PDGS archives will be deployed into the different centres following the PDGS federative concept whereby all individual archives contribute to the global PDGS archive. 6.8.1.2.2 Collaborative Centre Archive In addition to the PDGS archive deployed into the different core centres, the collaborative centres will be able to mirror the archived data totally or partially. Such collaborative centres will enhance the global PDGS capabilities for data preservation (data mirrored in different centres) and data access (data available closer to the users based on regional use). Collaborative centres will be able to make use of media data circulation capabilities (import different media like tapes, external USB HDDs, etc) to ingest the data circulated from the core archives as a trade-off complement to digital network based circulation. 6.8.1.3 Archived Elements The AI function will support the archive of data of different nature; this is the MSI data, satellite ancillary data, orbit data, auxiliary data for the MSI processing, HKTM, etc. Therefore the AI function will manage such different data in a homogeneous manner coping with every one specific characteristic. For instance, the MSI data will be archived on meaningful pieces, supporting effective retrieval and subsequent data processing strategies during their generation (e.g. parallelisation), used to compose the mission final products. The AI function minimum archive unit is defined as one or more product data items (PDIs) plus its associated metadata. 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 269 of 350 6.8.2 OPERATION CONSTRAINTS The AI function will be distributed amongst different PDGS centres supporting the data generation and products dissemination activities. The related archive configuration activities such as data retention rules on every centre will require synchronisation and coordination amongst the federated centres where deployed and therefore managed from the Payload Data Management Centre (PDMC). The PDGS/MCC function (cf. section 6.14) copes with the following aspects of the Archive distributed nature: Coupling between the AI function and the DPC function to support effective data processing strategies; Independence of each centre; Distributed responsibility; Central function of the Data Management Processes; 6.8.3 OPERATION SCENARIOS 6.8.3.1 Archive & Inventory Configuration This scenario accounts for the operator-driven configuration of the Archive & Inventory function. The AI function configuration is managed by the PDGS/MCC function (see Mission Configuration Control Operations section). As the AI function is deployed in several centres, the data retention policies may not be the same for all of them (e.g. core and collaborative centres may differ on the managed products, archive retention timeliness, etc.). Accordingly the MCC function releases the official archive configuration for every centre hosting the AI function. The POM will provide the full data retention picture for the overall PDGS then decomposed into individual data retention rules for every archive centre. The AI function archive rules configuration for each centre includes among others the following items: Archived mission, ancillary, auxiliary, HKTM, products type; Metadata inventoried for each archived product type; Retention rules based on products ageing or / and metadata parameters like geographic parameters; Clean-up rules such as deletion or circulation to long term archive service based on rules as for retention; Circulation rules based on metadata (e.g. geo-location coverage, cloud cover percentage, etc.). The following steps are identified for this operation scenario: 1) The MCC function produces a new AI function configuration; 2) The AI function configuration is circulated to the archive centres; 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:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Product- Type Identifier S2MSI0 S2M
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
○ Effective processing resources
Page 209 and 210:
Page 211 and 212:
Page 213 and 214: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 223 and 224: 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 289 and 290: Some relevant use cases are present
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?