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 118 of 350 This includes in particular the recurrent assessment of the image quality and triggering as needed of the required configuration changes on-board the MSI and/or on-ground in the dataprocessing chain to meet the baseline product quality requirements defined in section 4.4.4. To meet this objective, specific processes referred to as Cal/Val operations will be carried-out regularly. They are described as core mission operations in section 4.5.4.10 as involving coordinated on-board and on-ground operations. As resulting from Cal/Val activities, on-board configuration management of the MSI with coordinated configuration on-ground of the PDGS processing chains will be described in section 4.5.3.3.2 as requiring accurate configuration control and FOS commanding. 4.5.3.3 Mission Configuration Control Operations 4.5.3.3.1 General Principles The PDGS will perform systematic configuration control over all mission reference data applicable to the PDGS in every operation scenario. All critical configuration parameters, either derived from the HLOP or fined-tuned and retrofit after mission performance assessment operations, will be centrally managed in the PDGS over time. The management of mission configuration data strictly applicable to the FOS will however not be duplicated in the PDGS as already taken care of by the FOS. Hence, the scope of mission configuration control operations performed by PDGS will include the management of configurable items such as: ○ The reference orbit of each spacecraft; ○ Satellite operation constraints definition impacting the PDGS-generated planning ○ The database of X-Band stations and their characterisation (for CGS and LGS); ○ The sensor data-acquisition and downlink scenario definitions; ○ On-ground configuration data (GIPP for Level-0/1 processing) ○ Payload parameters (e.g. MSI NUC tables, thermal control tables, etc) ○ PDGS data management rules (e.g. for data circulation, archiving, etc) Some of this critical configuration will be managed independently per spacecraft whilst other will have global relevance to the constellation and will be dealt with accordingly. Mission configuration control operations will include: ○ Housekeeping operations and maintenance over time of all reference data in a central repository, associating applicable dates and operation scenario; ○ The delivery of the applicable reference data to their intended functional targets in a coordinated and controlled way. This coordinated configuration functionality will be used in particular to support the changes of mission scenarios as required via HLOP upgrades (e.g. for the phase-in of EDRS and switch to the operation scenario with EDRS); ○ On-demand reporting over the mission configuration over time. 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 119 of 350 4.5.3.3.2 Coordinated MSI Configuration Control As taking part to the overall operability of the instrument as well as driving its performance inflight, the configuration of some MSI parameter tables loaded on-board will be managed by the PDGS under strict configuration control. The MSI tables managed by the PDGS are: ○ The Non Uniformity Coefficients (NUC) table ○ The Front-End Electronics (FEE) table ○ The set of seven Image Processing Parameter Sets (IPS) tables ○ The Thermal Control Module (TCM) tables, TCM-SBY and TCM-NOM Other tables such as the WICOM microcode and the Global Parameter table will be managed directly by the FOS. The uplink and activation operations of these tables will be performed by the FOS (cf. section 4.3.7.2) and will be coordinated via the Special Operation Request (SOR) interface of the FOS. This interface associates a desired activation time to the table data deposited separately on the FOS server. The FOS will reply to every SOR by an SOR acknowledge providing the planned activation time. The PDGS will feed every new parameter table to the FOS with sufficient time in advance allowing for uplink and on-board activation operations (e.g. following uplink, a new NUC table activation on-board will need preliminary transfer from the OBC to the MSI requiring about 15 minutes to be executed in the eclipse phase of the instrument). In counterpart, It is assumed the acknowledged time will not exceed 24 hours after the desired timing expressed in the SOR. 4.5.4 CORE MISSION OPERATIONS The core mission operation concepts are based to a large extent on the MRD [AD-01] and on the mission simulations reported in [RD-19], while justifying the needed extrapolations when relevant. 4.5.4.1 On-Board Sensor Acquisition 4.5.4.1.1 MSI Acquisition According to the MRD [AD-01], the Sentinel-2 mission nominal acquisition scenario is targeting the systematic and continuous acquisition with the MSI of all land surfaces between 56 South latitude (Cape horn in South America) and 84 North latitude (up to northern Greenland) including major islands (greater than 100 km2 size), EU islands and all the other small islands located at less than 20km from the coastline. In addition it is required to acquire the whole Mediterranean Sea, all inland water bodies and all closed seas. 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 67 and 68: ESA UNCLASSIFIED - For Official Use
Page 97 and 98: Table 4-5 Radiometric image quality
Page 99 and 100: Product- Type On-Line retention Off
Page 103 and 104: 4.5.1.5 Scalability and Flexibility
Page 113: ESA UNCLASSIFIED - For Official Use
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
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:
ESA UNCLASSIFIED - For Official Use
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:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
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?