GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

o Generation of the Downlink-Plan associated to the Image-Acquisition-Plan ‣ Memory playback of MSI data ‣ Memory playback of satellite ancillary data ‣ Memory playback of satellite HKTM data ‣ X-band downlink synchronised wrt. playback activities ‣ OCP downlink synchronised wrt. playback activities GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 296 of 350 o Notify in advance to every ground station the list of required downlink passes according to the Mission-Plan o Generation of the ground stations Acquisition-Schedule-Plan o Generation of the EDRS Booking-Plan All planning activities will be referenced in OPS mode. Very specific activities might make use of the MTL scheduling mechanism. 6.15.1.3 Multi-spacecraft Management Load balancing between the constellation spacecrafts will be implemented at mission planning level. This will be performed at various levels: ○ In the MSI Image-Acquisition-Plan such that the relative planning of the two satellites can slightly diverge to accommodate special acquisitions; ○ Downlink-Plan generation according to different ground resources assigned (i.e. possibility to downlink the data to different ground-stations); ○ In the mission data recovery plan such that different zone coverage priorities impacting timeliness can be managed independently. 6.15.1.4 SPF-PIF Protocol The PDGS together with the FOS will implement the mission planning loop (cf. section 4.3.7.1). The exchange of planning information between PDGS and FOS will follow the SPF-PIF protocol. The Skeleton Plan File (SPF) is generated by the PDGS and delivered to the FOS. The SPF mainly contains requests to schedule an instrument task or command sequences according to the mission database. Sentinel-2 mission supports MTL and OPS requests. In response to the PDGS provided SPF, the FOS generates the Plan Increment File (PIF) when checking and verifying PDGS requests suitability. 6.15.2 OPERATION CONSTRAINTS The following operation constraints have been identified: 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 297 of 350 Staff involved in the mission-planning activities on both FOS and PDGS sides are available during nominal working hours only (operations performed on weekly days); S/band opportunities assigned to Sentinel-2 mission for the mission uplink plan (cf. 4.3.7.1); X-Band ground stations scheduling duty cycle for the downlink-passes booking beforehand according to the planned activities; Additional operation constraints derived from the EDRS exploitation. 6.15.3 OPERATION SCENARIOS 6.15.3.1 Planning Configuration This scenario accounts for the operator-driven MPL function configuration covering all preparatory activities prior to the mission plan generation. The following activities are considered part of the configuration scope: Ingestion and handling of the applicable Mission Reference Files released by the MCC function (i.e. mainly the FOS files required for planning acknowledge and ground station scheduling activities); Planning templates rules generation and their activation to span the Image-Acquisition- Plan; Characterisation of the Downlink capabilities assigned to the Sentinel-2 (Coarse Downlink Budget); Management of the FOS released Spacecraft Safety Constraints File with impact on the PDGS mission planning activities; Internal configuration parameters such as planning mode (automatic or manual, generation frequency, default plan coverage, etc.); The PDGS/MPL function configuration comprises activities that are performed automatically and others attached to operator handling. The operator defines and introduces the mission planning configuration parameters for the latter mission planning generation activities. See below a proposed example of some parameters that can be defined and used to characterise the CGS/LGS usage by the two spacecrafts units. 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:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242: 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 289 and 290: Some relevant use cases are present
Page 291: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 325 and 326: Two main mapping services have been
Page 327 and 328: The requirement on the cloud covera
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?