GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

ESA UNCLASSIFIED – For Official Use GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 276 of 350 1) On schedule basis (e.g. every 15 minutes), the DAX function consolidates the indexes by sorting on sensing-time, identification of duplications, relocation of the older data, etc; 2) The DAX function detects the new indexed product components (not previously archived in any other centre) and extracts the relevant metadata and the associated browse image; 3) The DAX function notifies to the PDGS Front-End Services (i.e. the MMUS and OLIB functions) the availability of the new product components. Some relevant use cases are presented according to this operation scenario: The DAX function feeds the MMUS function with the metadata and browse images of the new product components available. The MMUS function catalogues the Sentinel-2 production in support of the product discovery activities performed by the user; The DAX function feeds the OLIB function with the TCI metadata and associated browse images. 6.9.3.4 Coverage Reports Supply to the CDS/SCI This operation scenario stands for the autonomous generation of the coverage reports according to the CDS/SCI ICD [RD-11]. This scenario can be seen as a specialisation of the previous one in which, the DAX function autonomously notifies to the CDS/SCI the new product components available at the PDGS data-sinks. The DAX function supplies the information and generates a unique timeline that is formatted according to the SCI coverage report ICD to notify on the new production available. 6.9.3.5 Product Data Location Requests This scenario accounts for the autonomous management and response to product data location requests based on the PDGS data indexes. This scenario is always initiated by other PDGS functions when searching for the location of the PDGS archived data according to some criteria. The DAX function returns the physical location of the product data present in the different archives in support of the data-access activities (as requested by the DAG function). The DAG function, when used by the Front-End Services (i.e. the MMUS and OLIB functions) for the data-access activities, will request to the DAX function the location of the desired product data items. The MMUS and OLIB functions catalogue the Sentinel-2 production but rely on the DAG function for the product location requests to the DAX and subsequent dataaccess activities. 6.9.3.6 Bulk Metadata Harvesting and Indexes Re-Generation This scenario accounts for the operator-driven metadata harvesting from the archive centres. The operator collects manually the archive contents metadata (i.e. via network or specific media delivery) from the AI function and manually triggers the ingestion and processing into the DAX function. © 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 277 of 350 As such, the DAX function processes the metadata and re-generates / updates the data indexes accordingly (as explained in population scenario). The main use case for this scenario is in case of contingency to re-populate and / or regenerate the data indexes. 6.9.3.7 Maintenance This scenario accounts for the required maintenance activities in support of the function nominal operations. This is a mixed automatic and operator-driven scenario to ensure the correct performances when supporting the data-location requests. The PDGS/DAX function manages important volumes of data as part of its nominal operations (metadata ingestion, indexing, querying, etc). Therefore the required function capacities enhancement (mainly on data storage and query access timeliness) along the mission life-time is considered. The following activities have been identified for maintenance: Data relocation operations (e.g. due to a disk failure) Storage enhancements to cope with increasing data along mission life Data indexes sorting and recreation Data backup activities Data restore activities 6.10 Data-Access Gateway (DAG) Operations 6.10.1 PRINCIPLES 6.10.1.1 Single Data-Access Point towards the Users The Data-Access Gateway (DAG) function is in charge of providing a single data-access point towards the PDGS distributed data-sinks. As such, the DAG function, supported by the DAX function, encapsulates the distributed archiving topology towards the Front-End Services such as the MMUS and the OLIB functions acting as central hubs for user data-access activities. Accordingly, the DAG function performs the download of the product-components spread through the archive centres and the subsequent user-product reconstruction at the user base. 6.10.1.2 Client/Server Approach In order to achieve the single data-access point towards the users, it is envisaged a client/server approach with the following responsibility assignation: ‣ DAG function server side, coupled with the PDGS data-sinks; 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:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222: 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 271: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 289 and 290: Some relevant use cases are present
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?