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 140 of 350 4.5.4.5.2 Level-1 Processing Context and Datastrip Processing The terminology “Datastrip” refers to all MSI data acquired during a given orbit and received at a given CGS during a given satellite pass. In the PDGS distributed context, to ensure the timeliness requirements and as driven by the downlink scenario scattering MSI Datastrips amongst several ground-stations, the Level-1 processing will be carried out per Datastrip as opposed to being applied on the complete MSI orbit. Datastrips will stem from RT or NRT priority downlinks or from on-board playback interruptions explicitly commanded at LOS to let subsequent ones recover the remains of the on-board store. Considering the average imaging duration of 16 minutes per orbit relatively to the average downlink budget available at every ground-station pass (about 8 minutes), every MSI imaging orbit received on ground will hence produce at least two Datastrips, even without any RT or NRT commanding within the orbit. Figure 4-24 depicts this general case where the MSI orbit imaging pass is systematically fragmented after downlink into two sub-orbit Datastrips acquired at remote stations. Datastrip 1 dowlinked at station A Datastrip 2 dowlinked at station B Figure 4-24 Sub-Orbit Datastrips This happening creates a major constraint to the Level-1 processing as it imposes that the processing is performed on Datastrip portions of a non deterministic sub-orbit size. The MSI processing constraints described in sections 4.3.9.1, 4.3.9.2.2 and 4.3.9.2.3 require continuity of the input flow. Such continuity is ensured by the MMFU on-board memory management as described in 4.5.4.2.2.2 section. MSI scenes are duplicated on the MSI segments boundaries allocated in the memory to avoid sensing discontinuities on-ground produced by the on-board recording operations switch to different priorities (i.e. transitions amongst RT/NRT/nominal recording priorities) and the downlink operations as explained in 3.5.4.3 section. 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 141 of 350 The update of the MSI Packet-Store Management strategy, which is presented in section 4.5.4.2.2, ensures the required margins in the input data-flow to the level 1 processing (3 MSI scenes preceding each time-continuous segment) are embedded in the space-to-ground downlinks to produce a continuous level 1 timeline along all the Datastrips. Figure 4-25 MSI level 1 continuous processing timeline 4.5.4.5.3 Level-1A and Level-1B Processing 4.5.4.5.3.1 Ancillary-Data Handling As highlighted previously, the on-board recorded Ancillary-Data is required for MSI Level-1 processing and is recovered by playback separately to the MSI data. Nevertheless, the downlink strategy defined in 4.5.4.2.3 will ensure that the Ancillary-Data coinciding in time with every MSI Datastrip will be available on-ground contemporaneously at the term of every downlink. Hence, whilst the Level-0 initial processing will be performed in real-time in parallel to datareception operations, Level-0 consolidation and Level-1 processing activities will be delayed as triggered after the recovery on-ground of the Ancillary-Data at the end of every satellite pass. Ancillary-Data will be ingested together with the MSI raw-data at the beginning of the Level-0 consolidation processing sequence and used seamlessly through the algorithmic steps by time-correlation with the MSI data. 4.5.4.5.3.2 Datation Refinement The datation refinement will not be nominally performed as justified in section 4.3.9.2.1. Nevertheless, to provision for a possible contingency on the on-board datation process, Level-1 processing will optionally support the generation and handling of a refined datation model. The generation of this ancillary data by the PDGS is currently not foreseen but will be accommodated if required as a change to solve this eventual contingency. In addition, datation accuracy will be monitored in the PDGS as part of nominal and recurrent quality control procedures (e.g. on a monthly basis). 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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 97 and 98: Table 4-5 Radiometric image quality
Page 99 and 100: Product- Type On-Line retention Off
Page 101 and 102: ESA UNCLASSIFIED - For Official Use
Page 103 and 104: 4.5.1.5 Scalability and Flexibility
Page 135: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
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?