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 288 of 350 6.13.3.2 Archived Data Retrieval This scenario accounts for the archived data retrieval from the LTA service function according to the offered interface. The following steps are identified for this operation scenario: 1) The AI function requests the retrieval of some archived data by the LTA service function; 2) The LTA service function retrieves the requested data and supplies it to the AI function according to the settled interface. On the PACs (Processing & Archive Centres) with the long-term data preservation role assigned, the AI function instance locally deployed requests for (old) data archived in the associated LTA service function according to its needs (e.g. for data-access). The AI function archives the data supplied by the LTA service function (the retrieved data is now available online through the AI function). 6.13.3.3 Bulk Data Re-processing This scenario accounts for the operator-driven MSI bulk data re-processing according to the HLOP (e.g. one year data-reprocessing with the most recent version of the IPF). 1) The operator defines data-reprocessing campaign parameters (i.e. affected MSI data inputs time coverage, desired products type, execution priorities, etc.); 2) The operator triggers the data-reprocessing campaign execution according to configuration definition; 3) The LTA service function autonomously performs required processing actions according to the definition of the data re-processing campaign. This operation scenario will be used for the bulk data-reprocessing campaigns (i.e. one year of production data or more) triggered by the availability of a new IPF version and / or a new set of on-ground parameters effectively characterised and adjusted. 6.14 Mission Configuration Control (MCC) Operations 6.14.1 PRINCIPLES 6.14.1.1 Mission Configuration Control Concepts The PDGS MCC function is responsible for keeping under a controlled environment all the mission reference files. The MCC function will control critical configuration and essential operations information with a multiple objective: Keep under a controlled environment all critical configuration parameters and essential operation reports into a central repository. This objective aims at a centralised and 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 289 of 350 comprehensive management of all essential configuration and operations data over time; Provide the functionality to activate a specific system configuration throughout the distributed PDGS from a single point, and to collect all derived operation reports. This objective aims at an accurate management of the PDGS configuration covering their preparation, activation and monitoring; Provide query capabilities to the operator for the full understanding on the active mission reference files at any moment along the mission life-time. 6.14.1.2 Function Managed Data The MCC function will manage all the critical configuration and essential data that have an impact on the operations and performance as mission reference files. All the configuration parameters with an impact on the PDGS performance will be globally managed under POM supervision. One example of critical mission reference files is the MSI on-board configuration generated by the PDGS Mission Performance Assessment (MPA) function and used on-board to control the imagery acquisition. Such on-board configuration may change and evolve in time under the requests and approval of the POM. Essential mission reference information reporting upon mission performance measures and indicators will be as well managed and mainly used for overall mission performance assessment (used by the PDGS Mission Performance Assessment function). For instance ground stations acquisition, data circulation, data archive reports, mission plans, FOS schedule plans, etc will be managed as part of the mission reference files as providing indicators on the PDGS and overall system performance. The MCC function will manage mission reference files that are either common to both S2A and S2B spacecrafts or specific to a specific unit (e.g. orbital changes scenario will be addressed for each spacecraft while ground station characterisation is applicable to the mission). 6.14.1.2.1 Configuration Files The MCC function regroups all the PDGS critical configuration files having a direct impact on the PDGS functioning and performance. Some of this critical configuration will be managed independently per spacecraft whilst other will have global relevance. Some of these files will be generated either internally by the MCC function or gathered from other functional systems. As Mission Reference Files, these files will be kept under controlled configuration and will be when required released to their intended functional targets in controlled way. Typical examples of configuration reference files are enumerated hereafter: Reference orbit (S2A, S2B) Ground stations database Ground stations characterisation Downlink scenario definition (S2A, S2B) Spacecraft Safety Constraints File (S2A, S2B) Downlink Constraints (X-Band Banned Segments, Station Banned Segments) 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:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
o preserving integrity of exchanged
Page 233 and 234: GSC Sentinel-2 PDGS OCD Issue 1 Rev
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 261 and 262: ESA UNCLASSIFIED - For Official Use
Page 283: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 289 and 290: Some relevant use cases are present
Page 325 and 326: Two main mapping services have been
Page 327 and 328: The requirement on the cloud covera
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?