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 260 of 350 2) The OLQC function according to its configuration and provided product-type to be checked, verifies autonomously whether product relevant parameter-values and metadata are within threshold ranges; 3) New generated Quality Indicators are autonomously stored as QI PDIs that might be included as product metadata according to configuration; 4) The OLQC function autonomously generates a quality report on the verified products that summarises performed activities such as the quality checks, appended QI metadata, etc. 6.5 Data Circulation (DC) Operations 6.5.1 PRINCIPLES 6.5.1.1 Data Circulation Concepts The PDGS DC function is responsible for performing file exchange operations between subsystem interfaces within and external to a PDGS centre. The DC function will support interface electronic and media data circulation according to the PDGS needs. PDGS DC function supports different “media” as any physical storage device pluggable to a computer (e.g. external USB HDDs, LTO equipment, etc). In addition it will be able to interface with the on-ground EDRS equipment for data multicasting. Data circulation operations performed either via electronic means or physical media will be identified and managed according to their nature. Electronic data circulation interfaces will be characterized by means of typical connectivity parameters such as hostname, protocol used, username, etc, while physical media interfaces will be identified from the physical media hardware devices to be circulated. The DC function allows defining data circulation rules for different type of files to be performed between two interfaces (source and target interface). It systematically performs data circulation required operations based on the new data available and the configured data circulation rules in a systematic manner and data-driven manner. Circulation activities are systematic and will limit operator intervention to the sole management of media volumes when required (e.g. load new media for data input, unload when complete, change media when full, etc). The DC activities will be triggered either: ○ Automatically on availability of new files at an electronic input interface; ○ Manually by the operator on reception of new media (e.g. by post mail) 6.5.1.2 Horizontal Support to other PDGS functions The DC function supports all other PDGS functions when require circulating files (file retrieval and delivery operations) to and from other function interfaces internal or external hosted in other 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.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 261 of 350 6.5.2 OPERATION CONSTRAINTS The following operation constraints are identified: ○ Data circulation involving media will rely on mail courier services and therefore will not be used for critical timeliness data exchange operations; ○ Data circulation operations via media will be automated to the maximum feasible extent, limiting operator intervention to the sole loading/unloading and labelling of tape media. 6.5.3 OPERATION SCENARIOS 6.5.3.1 Data Circulation Configuration The scenario accounts for the operator-driven configuration of the different instances of the Data-Circulation function. The DC function supports other PDGS functions allocated in the different PDGS federative centres and therefore may require a complete view for every single data circulation configuration according to the PDGS overall system. Therefore, in case the DC configuration requires coherency amongst the different PDGS centres, the configuration definition will be coordinated by the MCC function and as such, modelled as Mission Reference Files (cf. section 6.14). The operator will configure the DC according to the different ICDs for external interfaces data circulation and according data-flow needs for internal ones. The following steps are identified for this operation scenario: 1) Define and configure the different interfaces (media and electronic ones) according to applicable ICDs; 2) Define the data circulation rules accordingly, associating the previously defined source and target interfaces (media or electronic), and identification of the type of data to be circulated; 3) Depending on the scope of the DC configuration (i.e. PDGS global), the DC function configuration will be managed as Mission Reference Files by the MCC function (cf. sections 6.14.3.2 and 6.14.3.3). Some use cases are presented according to this operation scenario: PDGS deployment in a new centre - DC function will be configured accordingly (interfaces configuration + circulation rules definition); Implementation of an ICD change - DC function will be re-configured to adapt to new interface definition baseline; New product-type available - DC function will configure a new circulation rule for such new product. 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: ESA UNCLASSIFIED - For Official Use
Page 207 and 208: ○ Effective processing resources
Page 209 and 210: GSC Sentinel-2 PDGS OCD Issue 1 Rev
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 255: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 289 and 290: Some relevant use cases are present
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?