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 30 of 350 1 INTRODUCTION 1.1 Purpose The purpose of this document is to describe the Sentinel-2 Payload Data Ground Segment Operations Concept, satisfying the data and services requirements from the GMES Services, the projection of these requirements for the GSC operations phase from 2013 onwards and the expected National and scientific requirements. 1.2 Background The Global Monitoring for Environment and Security programme (GMES) is a European initiative for the implementation of information services dealing with environment and security. It is based on observation data received from Earth Observation satellites and ground based information. Within the GMES programme, the GMES Service Segment (GSS) composed over several GMES Service Projects (GSPs) is in charge of providing value-added data and services to the GMES final users, while the GMES Space Component (GSC) is responsible for providing to the GMES Service Segment the necessary Earth-Observation (EO) data and services. As part of the GMES Space Component Programme, ESA is responsible for developing a fully operational space-based capability to feed the GSS with satellite data. This capability will be achieved with the implementation of GMES dedicated Earth Observation Missions, the Sentinels missions, under development by ESA. The Sentinel-2 mission is one of this series of GMES EO missions, scheduled for launch by 2013. Access to EO data and services by the GSS shall however be ensured already before the Sentinel era. This is being achieved by relying on a set of EO missions capable of satisfying the data requirements from the GSS. These missions contributing to the GSC are generically referred to as GSC (or GMES) Contributing Missions (GCMs). The GSC Coordinated Data Access System (CDS) is the pre-operational infrastructure being developed by ESA for providing access to GSC data and services to the GSS before the GMES Sentinels are launched. Although the CDS is initially implemented for the GMES preoperations phase, it is however designed to support the successive operational phase with the Sentinels. The Sentinels PDGS shall therefore be conceived as being part of the GSC Data Access system (GSCDA) as a fully integrated GMES mission. The GSCDA data and services are accessible through a portfolio of Data Sets (DSs). These DSs are derived from the GMES Services requirements captured in the DAP-R [RD-11], which after trade-off with the system available capacity are propagated in the GSC DAP, where GMES Services updated requirements and evolving space systems capacity are taken into account. The DAP Data Sets are pre-defined collections of coherent multi-mission products responding to specific different users needs and therefore with different characteristics. 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 31 of 350 The CDS interfaces with the GMES Service Component for gathering data requests and providing coordinated data access and services, and with the Ground Segments of the GCM’s and the Sentinel missions for coordinating the data provision from the GCM’s in response to the requests. Figure 1-1 sketches the GSC Data Access System context, the role of the Coordinated Data Access System (CDS) and its interface with the GMES Service Segment (for gathering data requests and providing coordinated data access and services), and with the Ground Segment of the GCM’s and the Sentinel missions (for coordinating the data provision in response to the requests). The GSCDA data and services provision from the GMES Contributing Missions (GCMs) is regulated through specific agreements with ESA through the DAP Management function. Being dedicated GMES missions, the latter interface is not strictly necessary for the Sentinel missions. Long-term EO Data Requirements Agreements DAP Management GMES Service GMES GMES Projects Service Services Projects • Registrations • Data Requests • Subscription Registrations GSC Data Sets GSC Products • Data Requests • Subscription Requests Coordinated Data Access System (CDS) •Products •Reports • Data Requests • Subscription Requests •GCM Products •Reports GSC GSC Contributing GSC Contributing Missions Contributing Missions Missions GSC GSC Sentinel Sentinel Missions GSC Sentinel Missions Missions GCM & Sentinel Products GSC Data Access Figure 1-1 GMES Space Component Data Access System Overview The Sentinel missions, as dedicated GSC missions, will be integrated with the CDS to contribute to the overall data provision to the GSC. The Sentinel missions will interface with the CDS through the Sentinel Ground Segment (GS) and particularly though the Payload Data Ground Segment (PDGS), as illustrated in Figure 1-2. 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 25: GSC Sentinel-2 PDGS OCD issue 1 rev
Page 29 and 30: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 33 and 34: [RD-33] Sentinel-2 MSI - Level 2A A
Page 37 and 38: LES LGS Land Equipped Sites Local G
Page 47 and 48: 3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 67 and 68: ESA UNCLASSIFIED - For Official Use
Page 71 and 72: ESA UNCLASSIFIED - For Official Use
Page 77 and 78:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 79 and 80:
Page 81 and 82:
ESA UNCLASSIFIED - For Official Use
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:
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?