GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

The following steps are identified for this operation scenario: 1) Refer to the Mission Reference Files registration section; GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 294 of 350 2) After the configured mission reference files gathering and ingestion activities, the configured files to be delivered as MR-U are autonomously circulated to the applicable interfaces. Some relevant use cases, more concretely for the mission operations data, are presented according to this operation scenario: The different PDGS functions activity reports are autonomously circulated to the PDGS/MPA function for monitoring and assessment activities; The mission plan, once based on already well proven configuration is gathered from MPL function and autonomously circulated to FOS; Ground stations acquisition reports are gathered and autonomously delivered to the PDGS/MPA function. 6.14.3.5 Configuration Reporting & Query Capabilities The scenario is activated on-request by the operator for reporting on the managed mission reference files changes. In addition, the MCC will be able to provide traceability between mission reference files flagged as configuration and the ones flagged as operations. This scenario is based on the interactive visualisation and reporting capabilities of the MCC. The following use cases are identified following this operation scenario: The MCC operator presents a report with including the description mission reference files (flagged as configuration) updated to the POM for assessment and approval before release; In response to a POM request, the MCC function supplies the appropriate reporting information about a specific mission reference configuration parameter, its current value and its evolution along mission lifetime. The operator will display or generate a report with the requested information; On anomalies management, the MCC operator will present a report with the irregular mission reference file and the configuration that was applicable during its generation; The MCC operator queries the function on the applicable set of mission reference files for a given time-period. 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 295 of 350 6.15 Mission Planning (MPL) Operations 6.15.1 PRINCIPLES 6.15.1.1 Global Mission & Systematic Planning The Sentinel-2 mission aims for the global and sustained monitoring of land and coastal areas (cf. section 3.1). According to the mission objectives, continuous acquisitions over well defined and predictable areas of interests are performed. The Sentinel-2 near-polar sun-synchronous orbit characteristics with a 10 days repeat cycle (cf. section 3.4) ensures a high revisit time with same illumination conditions over the mission area of interest which will be doubled with a second spacecraft unit (cf. section 3.3). The Sentinel-2 MSI payload provides a large spatial coverage on every acquisition (i.e. single wide swath coverage 290 km) with a single observation mode to be scheduled on the mission area of interest at every opportunity (cf. section 3.1). As such, Sentinel-2 requested sensing will be highly predictable with little changes as derived from special acquisition campaigns, special calibrations, etc (cf. section 4.5.4.1.1). 6.15.1.2 PDGS Planning Scope In this section it is explained the perimeter of the PDGS planning. The PDGS provides the mission plan to the FOS for its scheduling and uplink to the satellite (cf. 4.5.3.1.1). The PDGS planning perimeter will include the scheduling of ground stations reception activities derived from the mission plan (cf. 4.5.3.1.3). The PDGS generates the mission plan and commands the required satellite elements including: o Generation and maintenance of the mission reference orbit file o Management and use of the Spacecraft Safety Constraints File for operations o Generation of the Coarse Downlink Budget ‣ Characterisation of the CGS and LGS network resources ‣ Management of the Multi-Sentinels restriction for X-Band operations ‣ Management of the EDRS Availability Segments assigned for the Sentinel-2 Mission ‣ Ground stations and EDRS GEO contact time generation ‣ Contact times restriction and optional manual update o Generation of the Image-Acquisition-Plan ‣ MSI commanding for imagery acquisition ‣ Memory recording of MSI acquired data synchronised with MSI acquisition activities 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: 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: 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 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?