1. INTRODUCTION

The overall system architecture for the Copernicus Space Component (CSC) and its evolution are being defined on the basis of user requirements coordinated by the European Commission. The Long Term Scenario (LTS) describes the main elements of this architecture and is being generated in an iterative process in close interaction with the European Commission (COM), EUMETSAT and the EU Member States and Copernicus Participating States.

ESA needs to guarantee the continuity of the on-going operations with the maximum level of performances for the flying Copernicus Sentinels, while facing the technical and financial challenges to adapt to the foreseen future CSC architecture.

The EOF encompasses all the activities necessary to successfully deliver the expected level of CSC GS operations entrusted to ESA (i.e. establishment and maintenance of the new baseline, procurement actions, operations management, reporting, etc.).

The EOF is documented throughout a complete package describing and specifying the applicable operational concepts as well as the architecture and operations procurement approach adopted for establishing and evolving the CSC operations baseline (in particular with respects to the future Expansion Missions, associated with the necessary cost information to size the proposed approach and potential trade-offs).

The EOF implementation is based on a service architecture with well-identified components that exchange data through Internet respecting defined interfaces. A service presents a simple interface to its consumer that abstracts away the underlying complexity. Combined with deployments on public cloud infrastructure, the service approach offers large adaptability to evolution of the operational scenarios in particular for what regards scalability.

Since the transformation process which started in 2019, the EOF-CSC operations have been transferred to cloud based environments (in anticipation of the enlargement of the Copernicus Sentinel missions and in response to the ever-increasing demand for Copernicus data) and the service-oriented approach for each component of the EOF-CSC operations has been strengthened to enhance industrial competitiveness, prevent industrial and technical lock-in and introduce the necessary operational flexibility and transparency to allow the adaptation of the EOF-CSC to future challenges.

Within this context, this document outlines the system budget of the large flow of data being acquired, processed, and distributed within the EOF.

1.1. Scope

This document is part of the ESA EO Observations Framework (EOF) Copernicus Space Component (CSC) documentation package. The system budget scope is to provide an estimate of the expected operations load and the sizing of the general operations. The budget provides an end-to-end global view on the operational data flows within the period 2024 – Q1 2034. These estimations are made on the basis of current operation volumes. The budget should support the sizing of the critical elements.

1.1. EOF CSC High-Level Architecture

The functions composing the EOF-CSC architecture are implemented in the form of operational services, complying to a set of applicable input and output interfaces and to the corresponding operational performance requirements.

For the purpose of architecture and design definition, the interfaces between functions are classified as:

  • Data flow interfaces, for interfaces carrying Sentinel data or auxiliary information required for processing activities

  • Monitoring and control interfaces, for interfaces carrying reporting information (necessary for the performance monitoring at element level or end to end) or operations control information

  • Scheduling interfaces, for interfaces related to mission planning, including ground stations planning, satellite scheduling, etc.

Data flow interfaces, for systematic data transfer between services, are based on the concept of small data cache areas, referred to as data “interface delivery points” (IP) hereafter. Each function or service, generating a systematic or routine data flow to be further managed by one or more services, is making the output data available in an interface delivery point located on a cloud-based environment, which is logically considered as part of, and under the responsibility of, the data source service.

The architecture is presented in [RD-EOF-ARC], and Figure 1 introduces the main elements relevant for the system budget.

img-3.jpeg

Figure 1 High level decomposition of the ESA EO Operations Framework (EOF) Copernicus Space Component (CSC) architecture

The number of instances for each service may vary, it is therefore important for the system budget to consider worst-case scenarios. The system budget does not intend to provide exact figures per mission, but rather to provide an order of magnitude sufficient for the verification of the different service sizing.

1.2. Applicable documents

The following documents are applicable to the System Technical Budget to the extent specified in this document:

Id Title Reference
AD-EOF-DASP Copernicus Space Component Sentinel Data Portfolio ESA-EOPG-EOPGC-TN-12

1.3. Reference documents

The following documents can be consulted as they contain relevant information:

Id Title Reference
RD-EOF-ARC CSC Operations – ESA Framework – Ground Segment Architecture ESA-EOPG-EOPGC-TN-12
RD-EOF-LTS The next phase of Copernicus” Updated Copernicus Space Component (CSC) Long Term Scenario [ESA_PB-EO_2024_10_EN] LTS 2024
RD-EOF-MICD CSC Operations – ESA Framework – Master ICD ESA-EOPG-EOPGC-IF-06
RD-EOF-GLO CSC Sentinel Ground Segment Operations Glossary ESA-EOPG-EOPGC-TN-13
RD-EOF-MSOC- EOF CSC- Mission Specific Operations Configuration – CRISTAL Mission ESA-EOPG-EOPGC-TN-2024-73
EOF CSC- Mission Specific Operations Configuration – LSTM Mission ESA-EOPG-EOPGC-TN-2024-83
EOF CSC- Mission Specific Operations Configuration – ROSE-L Mission ESA-EOPG-EOPGC-TN-2024-74
EOF CSC- Mission Specific Operations Configuration – CHIME Mission ESA-EOPG-EOPGC-TN-2024-70
EOF CSC- Mission Specific Operations Configuration – CIMR Mission ESA-EOPG-EOPGC-TN-2024-71

1.2. Acronimous

1.3. Definitions

Archive Exploitation Ratio

The Users’ interest in Sentinel products can most accurately be monitored by looking at the ‘Archive Exploitation Ratio’ (AER). The AER is defined as the total number of users’ downloads (made from the hub), divided by the total number of products, (which had been published on the hubs since the start of operations). For example a ratio of 1:X indicates that, for each of the published products, there was an average number of X downloads.

Data take

The data take corresponds to the continuous sensing of a given area. The data take is downlinked from the satellite to the ground station according to the mission downlink capabilities. Data take can be downlinked in several portions in different locations.

img-4.jpeg

Sentinel-1 Segments and Assembled Segments

Sentinel-1 Segments of the same data take partially downlinked in different stations are assembled before processing.

Sentinel-1 Slices

Sentinel-1 Slicing is a process applied throughout the processing Production. It consists in cutting a complete L0 segment into parts (“slices”) of configurable size, allowing to distribute and parallelize the processing over several processing nodes

img-5.jpeg

Sentinel 2 Datastrip

Within a given data take, a portion of image downlinked during a pass to a given station is referred to as a “datastrip”. It is expected that the maximum length of a datastrip downlinked to a ground station is approximately 5,000 km.

Sentinel 2 Granules/Tiles

A granule is the minimum indivisible partition of a product (containing all possible spectral bands).

☐ For Level-0, Level-1A and Level-1B, granules are sub-images of a detector with a given number of lines along track. A granule covers approximately 25 km across-track and 23 km along-track.

☐ For Level-1C and Level-2A, the granules, also called tiles, are 100 km² ortho-images in UTM/WGS84 projection

Near Real Time (NRT) and Non Time Critical (NTC)

Products are categorized as either Near Real Time (NRT) or Non-Time Critical (NTC). NRT products are intended to be made available to the users less than 3 hours after acquisition of the data by the sensor. The expectation for NTC products is that they will be published within 24 hours from sensing.

TiB - a unit of information equal to 1024 gibibytes or 2^40 (1,099,511,627,776) bytes.

2. OPERATIONS SIZING

2.1. Copernicus Operations Assumptions

The operations sizing for the first generation of Sentinels are based on the measured and monitored dataflows according to their actual operations. The operations sizing for the Copernicus Expansion and Sentinel Next Generation missions are derived from the best assumptions available within the reference documentation [RD-EOF-MSOC].

In addition to the observational priorities provided by the EC, the following assumptions have been taken for the elements impacting the operations framework:

  • The operational lifetime of the Sentinel -1, -2 and -3 satellites and of the Copernicus Expansion satellites is assumed to be 10 years.

  • A maximum of 2 satellites of the same mission will be simultaneously in routine operations. Operating simultaneously more than 2 satellites of the same mission should be avoided, apart from hand-over and cross-calibration periods or if requested by the EC based on strong user needs.

2.2. Total operational time estimation

Table 1 is an overview of the overall timeline of operations of the different Copernicus missions, considering:

  • The above assumptions,

  • The projection of the operational Copernicus satellites for the period 2024-2034 according to LTS [RD-EOF-LTS]. This timeline does not include the Copernicus Expansion missions or NG Missions. For that reason in 2034 there is the impression of having 1,5 flying satellites. Howevere those are expected to be complemented by the NG missions.

The LTS considers a launch window for each mission. Here, for convenience, the beginning of the launch window is considered as the launch date.

Satellite 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034
S1-A
S1-B
S1-C
S1-D
S2-A
S2-B
S2-C
S2-D
S3-A
S3-B
S3-C
S3-D
SSP

Table 1: Timeline of Copernicus satellites

Grey color: commissioning phase Blue color: routine operations phase

img-6.jpeg

Figure 2 Yearly number of Copernicus satellites

2.3. EOF-CSC architecture elements

For the data budget, the following major EOF-CSC elements are considered:

  • Data Acquisition

    • Critical elements: Stations required bandwidth

  • Systematic Production, On-demand Production and Reprocessing

    • Critical elements: Overall bandwidth to LTA and to the Data Access

  • Data Access – data distribution and user scenario characterization

    • Critical elements: Overall bandwidth towards end users

  • Data Preservation (LTA)

    • Critical elements: Overall archiving volume evolution

2.4. Global Guidelines

Generally, the data total volume has been calculated in accordance with the following guidelines:

  • the average of the two satellites in routine operations (e.g. A and B) is considered for the calculations

  • the data volume provided from current satellites (Example S1A) is similar for future satellites for the same mission (Example S1C).

3. ACQUISITION

3.1. Definition

The overall data is estimated by considering the current volume of downlinked data. The data load has been calculated in accordance with the following assumptions:

  • The downlink data rate for Sentinels 1, 2, 3 is 560 Mbps and 310 Mbps for Sentinels 5P,

  • Sentinel 1, 2, 3 have 2 downlinks channels per satellite and 1 downlink channel for Sentinel 5P,

  • There is an average of 14,58 orbits per day for Sentinel-1, of 14,3 orbits per day for Sentinel- 2 and Sentinel-3 satellites and of 14,2 orbits per day for Sentinel-5P satellite,

  • For each mission, the satellites are spaced equidistant along the orbit (this assumption is applicable for two, three or four satellites of the same mission flying),

  • For Sentinel-1 and Sentinel-2, data is downlinked over all stations available in order to optimize the data delivery timeliness,

  • For Sentinel-1, pass-through RT happens only over X-Band Stations,

  • For Sentinel-3 and Sentinel-5P, data is ddownlinked only once per orbit.

3.2. Data volume

Based on the above and the average downlink times currently measured for each flying satellite, the following yearly average downlinked data is expected:

One Satellite Downlink Rate (Mbps) X-Band Downlink time (nb minutes / orbit) GdG Downlink time (nb minutes / orbit) Total GiB orbit Orbits daily TiB per day Total TiB yearly
S156011,8711,5691,6514,581,30476
S25609,4512,4585,6414,301,20437
S35607,67-29,9914,300,42153
S5P3109,45-20,4614,200,28104

Table 2 Yearly average downlinked data volume for one Satellite

According to the current assumption on launch dates and lifetime, the following profile is expected for the yearly data volume (TiB) for each mission.

img-7.jpeg

Figure 3 Downlinked volume per year (TiB)

The acquisition scenario and associated budget have to consider the variability of the scenario. The Acquisition service shall adapt the capacity to the required load, taking in consideration potential shifts.

3.3. Bandwidth

The above volume is to be circulated between the station physical location and the interface delivery point.

In average the required transfer rate is below 1 Gb/s and should not create a technological risk. Still, the downlink patterns may create peaks of activities that need to be sized.

A scenario in which 4 satellites would downlink for 10 minutes in parallel, with 15 minutes to get the data out of the station would lead to a bandwidth of about 2 Gb/s.

The Acquisition Service shall pay attention to such situations that may become critical through time.

Even if this scenario is unlikely, exceptional circumstances like contingencies and the need to disseminate several orbits in parallel may create similar situations. The Acquisition services shall take in consideration some margins to accommodate this need.

4. OVERALL DATA FLOWS

The system budget is mainly driven by the systematic production. The following sections present the overall production frame, the Long-Term Archiving and the data dissemination.

4.1. Data flow scenarios

The following table represents the circulation between the architectural elements of the CGS EOF-CSC

Mission Timeliness L0 L1 L2
S1NRTDD, LTADDDD
NTCDD, LTADDDD
S2NTCLTADDDD
S3NRT + STCLTADDDD
NTCXXDDDD
S5PNRTXDDDD
NTC (OFFL)LTADDDD

Table 3 Synthesis data flow

X This type does not exist

XX Not circulated Product types

5. DATA PRODUCTION

All the volumes and number mission specificities are reported in chapter 8 DATA FLOW PROCESS CHART, taking into account the mission rules available in chapter 10 ANNEX.

The production allows to generate:

  • Level-0 from CADUs chunks

  • Level-1 and Level-2 products from Level-0.

5.1. Data Volume

The following tables provides the estimated Sentinel-1, Sentinel-3 and Sentinel-5P average volumes per mission product level for one satellite:

Volume
Per Day
(TiB per One satellite per day) L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 0,242 0,685 0,700 2,016 0,001 0,004 3,649
S3 0,289 0,000 0,528 0,466 0,108 0,148 1,539
S5P X 0,245 0,622 0,573 0,061 0,069 1,570
Per Week
(TiB per One satellite per week) L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 1,696 4,797 4,903 14,113 0,009 0,025 25,543
S3 2,026 0,000 3,698 3,260 0,754 1,038 10,776
S5P X 1,712 4,355 4,010 0,425 0,486 10,987
Per Month
(TiB per One satellite per month) L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 7,377 20,859 21,319 61,365 0,000 0,109 111,029
S3 8,805 0,000 16,069 14,165 3,277 4,508 46,824
S5P X 7,437 18,922 17,424 1,845 2,113 47,740
Per Year
(TiB per One satellite year) L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 88,520 250,306 255,831 736,385 0,461 1,309 1332,813
S3 105,657 0,000 192,832 169,980 39,322 54,102 561,893
S5P X 89,245 227,058 209,089 22,136 25,357 572,885

Table 4 Sentinel-1, Sentinel-3 and Sentinel-5P Production Volumes (TiB) per product level for one satellite

The following table provides the estimated Sentinel-1 average volumes per product type for one satellite:

Volume
Per Day
S1 (TiB per One satellite per day) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
0,242 0,685 0,126 0,353 0,604 1,763 0,001 0,003
Total 0,928 0,479 2,368 0,004
Per Week
S1 (TiB per One satellite week) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
1,70 4,797 0,882 2,471 4,230 12,342 0,007 0,021
Total 6,494 3,353 16,573 0,028
Per Month
S1 (TiB per One satellite month) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
7,377 20,859 3,835 10,744 18,395 53,667 0,030 0,091
Total 28,236 14,580 72,061 0,122
Per Year
S1 (TiB per One satellite year) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
88,520 250,306 46,022 128,933 220,734 644,000 0,365 1,096
Total 338,826 174,955 864,734 1,461

Table 5 Sentinel-1 Production Volumes (TiB) per product type for one satellite

The following table provides the estimated Sentinel-3 average volumes per instrument and level for one satellite:

Per Day
S3 [TIB per One satellite per day] OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,107 0,000 0,055 0,000 0,000 0,000 0,127 0,000
L1 0,178 0,178 0,172 0,171 0,050 0,050 0,128 0,066
L2 0,022 0,022 0,026 0,055 0,0548 0,0689 0,00544 0,00243
Total 0,307 0,200 0,253 0,227 0,105 0,119 0,261 0,068
Total 0,507 0,479 0,224 0,329
Per Week
S3 [TIB per One satellite per week] OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,750 0,000 0,384 0,000 0,000 0,000 0,891 0,000
L1 1,247 1,249 1,202 1,200 0,350 0,350 0,898 0,460
L2 0,151 0,151 0,182 0,387 0,384 0,482 6,286 3,220
Total 2,147 1,401 1,768 1,587 0,734 0,833 8,075 3,680
Total 3,548 3,355 1,566 11,756
Per Month
S3 [TIB per One satellite per month] OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 3,259 0,000 1,669 0,000 0,000 0,000 3,876 0,000
L1 5,421 5,433 5,229 5,217 1,523 1,523 3,905 2,000
L2 0,655 0,659 0,791 1,682 1,668 2,097 0,166 0,074
Total 9,336 6,091 7,689 6,899 3,191 3,620 7,946 2,074
Total 15,427 14,588 6,811 10,020
Per Year
S3 [TIB per One satellite per year] OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 39,112 0,000 20,030 0,000 0,000 0,000 46,510 0,000
L1 65,055 65,192 62,743 62,606 18,278 18,278 46,856 24,004
L2 7,862 7,905 9,489 20,183 20,011 25,166 1,986 0,886
Total 112,030 73,097 92,262 82,789 38,290 43,444 95,353 24,890
Total 185,127 175,051 81,733 120,243

Table 6 Sentinel-3 Production Volumes (TiB) per instrument and level for one satellite

The following table provides the estimated Sentinel-2 average volumes per product type and for one satellite. There aren’t different production timeliness for Sentinel-2.

Per Day
0,9800,0001,1042,5623,6618,308

Per Week

S2 (TiB per One satellite week) L0 L1A L1B L1C L2A Total
6,8620,0037,73117,93525,62758,158

Per Month

S2 (TiB per One satellite month) L0 L1A L1B L1C L2A Total
29,8170,01133,59577,932111,356252,711

Per Year

S2 (TiB per One satellite year) L0 L1A L1B L1C L2A Total
357,8090,132403,139935,1861336,2683032,533

Table 7 Sentinel 2 Production Volumes (TiB) per product type for one satellite

According to the current assumption on launch dates and lifetime (RD-EOF-LTS), the following profile is expected for the overall yearly NTC data volume (PiB). As Sentinel-2 does not have NRT production, relevant data volume is included only in NTC graph:

img-8.jpeg

Figure 4 NTC Yearly Production Data Volume (PiB)

Sentinel-1, Sentinel-3 and Sentinel-5P NRT Production is presented here below:

img-9.jpeg

Figure 5 Sentinel-1, Sentinel-35 and Sentinel-S5P NRT Yearly Production Data Volume (PiB)

The total average bandwidth for circulating the production is equivalent to 4 Gb/s, which is within a range of common on-the-shelf service for cloud providers. The variability through time already mentioned for the acquisition is to be considered as well (i.e. network scalability on the cloud provider side would deserve some attention as the service offer may differ from one provider to another).

5.2. Number of Products

The following tables provide the estimated Sentinel-1, Sentinel-3 and Sentinel-5P average number of products per mission-product level for one satellite:

Number of Products in production
Daily:
Num Products per One satellite per day L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 283 781 654 1764 246 470 4196.55
S3 986 0 1.143 786 1.286 1.515 5.716
S5P X 756 1.720 162 1.791 204 4.633
Weekly:
Products per One satellite per week L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 1.980 5.466 4.576 12.347 1.719 3.289 29.376
S3 6.903 0 8.003 5.502 9.003 10.603 40.014
S5P X 5292 12.040 1.131 12.537 1.428 32.428
Monthly:
Products per One satellite per month L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 8.609 23.767 19.896 53.688 7.473 14.300 127.732
S3 29.994 0 34.775 23.907 39.120 46.075 173.870
S5P X 22.995 52.317 4.912 54.476 6.205 140.905
Yearly:
Products per One satellite per year L0 L1 L2 Total
NRT NTC NRT NTC NRT NTC all Levels and timeliness types
S1 103.305 285.210 238.752 644.250 89.673 171.599 1.532.789
S3 359.927 0 417.297 286.883 469.437 552.895 2.086.439
S5P X 275.940 627.800 58.948 653.715 74.460 1.690.863

Table 8 Sentinel-1, Sentinel-3 and Sentinel-5P produced number of products per product level for one satellite

Number of products
Daily:
S2 Num Products per One
satellite per day. (After
Transformation)		L0L1AL1BL1CL2ATotal
58.5522656.38211.92211.778138.660

Weekly:

S2 Products per satellite per One week (After Transformation) L0 L1A L1B L1C L2A Total
409.863183394.67183.45682.447970.619

Monthly:

S2 Products per One satellite per month (After Transformation) L0 L1A L1B L1C L2A Total
1.780.9527931.714.941362.636358.2514.217.572

Yearly:

S2 Products per One satellite per year (After Transformation) L0 L1A L1B L1C L2A Total
21.371.4259.52020.579.2874.351.6304.299.00650.610.868

Table 9 Sentinel-2 produced number of products for one satellite

For the number of products of Sentinel-2 see explanation in Chapter 9.3.

According to the current assumption on launch dates and lifetime (RD-EOF-LTS), the following profiles are expected for the yearly number of products(PiB) produced for each mission. As Sentinel-2 does not have NRT production, number of data volume are presented only as NTC.

S1, S3 and S5P NTC number of products per year

img-10.jpeg

Figure 6 Yearly S1, S3, S5P NTC Number of products

img-11.jpeg

Figure 7 Yearly S2 NTC Number of products

img-12.jpeg

Figure 8 Yearly S1, S3, S5P NRT Number of products

6. DATA PRESERVATION

6.1. Definition

The long-term archiving function pursues two main objectives:

  • Preserve the L0 and auxiliary mission data for the long term,

  • Offer efficient access to past data for the operations services (e.g. data distribution, reprocessing, on-demand production, …)

6.2. Guidelines

  • The budget is provided considering a unique equivalent LTA regrouping all missions,

  • L0 products of all missions are archived. The list of L0 for each mission is given in the tables in chapter 10 ANNEX.

  • Auxiliary data of all missions are archived. For S5P auxiliary data has started to be archived in one of the LTA since March 2024, including the historical ones. The list of auxiliary for each mission is given in the tables in chapter 10 ANNEX.

6.3. Auxiliary Data Volume

Auxiliary data are generated from by external data providers or from production services (such as Sentinel-1 ETAD atmospheric auxiliary data) and used in the processing.

The following tables provide the Auxiliary average data volumes per mission to be archived in the LTAs, according to the current operational scenario.

Since March 2024 Sentinel-5P auxiliary data, both historical and new generated, are also archived by one of the four LTAs.

Only systematic auxiliary data are considered in this estimation, as volume of asynchronous auxiliary data (e.g. configuration files) can be considered negligible.

Auxiliary Volume
Per Day
(TiB per per day) AUX
S1 0,057
S2 0,007
S3 0,015
S5P 0,157
Per Week
(TiB per per week) AUX
S1 0,397
S2 0,051
S3 0,106
S5P 1,102
Per Month
(TiB per month) AUX
S1 1,728
S2 0,221
S3 0,461
S5P 4,790
Per Year
(TiB per year) AUX
S1 20,735
S2 2,655
S3 5,532
S5P 57,478

Table 10 Auxiliary Data Volumes (TiB) for each mission

6.4. Level 0 Data Volume

The LTA average volume of new acquired L0 data per year for one satellite is estimated for each mission, according to the current operational scenario, and given in the following table:

One Satellite TiB per day TiB per Month TiB per Year
S1 0,93 28,24 338,83
S2 0,98 29,84 358,05
S3 0,32 9,78 117,30
S5P 0,24 7,44 89,31
Total 2,47 75 903,49

Table 11 Yearly LTA volume of newly acquired L0 data (TiB)

6.5. Cumulative Auxiliary and Level 0 Data Volume

The cumulative Auxiliary and Level 0 volume is reported in the table below. It is based on the last “Long Term Scenario” (RD-EOF-LTS).

Volume [PiB]
S1 L0S1 AUXS2 L0S2 AUXS3 L0S3 AUXS5P L0S5P AUXAll L0All AUX
Historical
data@Dec2024		4,480,0335,360,0191,660,0440,590,04412,080,14
20255,300,0846,230,0261,870,0540,680,05414,080,22
20265,970,1246,930,0312,090,0660,760,06615,750,29
20276,630,1657,630,0362,300,0770,850,07717,410,35
20287,290,2058,500,0432,510,0880,850,08819,150,42
20297,950,2469,200,0482,750,1000,850,10020,750,49
20308,610,2869,900,0532,950,1110,850,11122,320,56
20319,270,32710,600,0583,160,1220,850,12223,880,63
20329,940,36711,300,0633,360,1330,850,13325,450,70
203310,600,40812,000,0693,570,1430,850,14327,020,76
203411,090,43812,520,0723,730,1520,850,15228,190,81

Table 12 Yearly AUX and L0 Cumulative Volume (PiB) one copy per mission

img-13.jpeg

Figure 9 Yearly L0 Cumulative volume (PiB) one copy per mission

img-14.jpeg

Figure 10 YearlyAUX Cumulative volume (PiB) one copy per mission

6.6. Auxiliary Number of products

The following tables provide the average numbers of Auxiliary data per mission to be archived in the LTAs, according to the current operational scenario.

To be consistent with the volume estimation, only systematic auxiliary data are taken into account:

Auxiliary Number of products
Per Day
(Num per day) AUX
S1 889,30
S2 259,28
S3 92,56
S5P 4567,84
Per Week
(Num per week) AUX
S1 6225,10
S2 1814,97
S3 647,92
S5P 31974,89
Per Month
(Num per month) AUX
S1 27068,07
S2 7891,89
S3 2817,30
S5P 139033,66
Per Year
(Num per year) AUX
S1 324816,83
S2 94702,66
S3 33807,54
S5P 1668403,96

Table 13 Number of Auxiliary data for each mission

6.7. Level 0 Number of products

The total amount of L0 products in LTA since the launch of the missions satellites until end of December 2024 is given in the table below:

Satellite L0
S1A+S1B 5.372.698
S2A+S2B 327.397.730
S3A+S3B 5.177.646
S5P 2.052.217
Total 340.000.291

Table 14 Total Number of Products archived until December 2024 (Historical data)

The estimated average numbers of L0 products, according to the current operational scenario, archived in LTA for one satellite per year is given in the table below.

One Satellite Num Per Day Num Per Month Num Per Year
S1 1.064 32.376 388.515
S2 58.523 1.781.289 21.375.471
S3 986 30.014 360.173
S5P 756 23.011 276.129
Total 61.329 1.866.691 22.400.288

Table 15 Yearly Total Number of Products archived (newly acquired data)

7. DATA DISTRIBUTION

The volumes and the number of products presented in this section are representative for the Data Access system.

Data Access system has been provided by the Copernicus Open Access Hub (Open Access Hub (copernicus.eu)) until 01/11/2023 and since then from the Copernicus Data Space Ecosystem (CDSE - Copernicus Data Space Ecosystem | Europe’s eyes on Earth).

The CDSE started its ramp-up operations at the end of January 2023 and operated together with the Open Access Hub for most of 2023, gradually increasing its functionalities throughout the year. Since the Open Access Hub decommissioning, the CDSE has been the ESA’s sole data access service for Copernicus Sentinel data.

In addition to the User level data CDSE has started publishing also the engineering data for each mission, consisting in L0 products and auxiliary data. Such data has a 14-days rolling policy and are restricted to expert users.

7.1. Published Data volumes

The current average user level data volumes published at the Data Access system, for one satellite, is summarized in the table below divided per product level and mission:

Published Data Volumes

L0

One Satellite TiB per day TiB per Month TiB per Year
S1 0,93 28,24 338,83
S2 0,00 0,00 0,00
S3 0,00 0,00 0,00
S5P 0,00 0,00 0,00
Total 0,93 28,24 338,83

L1

One Satellite TiB per day TiB per Month TiB per Year
S1 4,62 140,56 1686,77
S2 (L1C) 2,40 73,19 878,26
S3 0,89 27,11 325,32
S5P 1,19 36,37 436,45
Total 9,11 277,23 3326,80

L2

One Satellite TiB per day TiB per Month TiB per Year
S1 0,01 0,25 3,01
S2 (L2A) 3,18 96,63 1159,61
S3 0,26 7,79 93,42
S5P 0,00 0,13 1,52
Total 3,45 104,80 1257,56

Total

One Satellite TiB per day TiB per Month TiB per Year
S1 5,55 169,05 2028,60
S2 5,58 169,82 2037,87
S3 1,15 34,90 418,75
S5P 1,20 36,50 437,96
Total 13,48 410,27 4923,18

Table 16: Yearly average published data volumes per product level and mission (TiB)

The following tables report instead, separately for Sentinel-1, Sentinel-2 and Sentinel-3, the user level data volumes published at the Data Access system, for one satellite, divided per product type:

Published Data Volumes
Per Day
S1 (TiB per one satellite per day) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
0,242 0,685 0,126 0,353 0,604 1,763 0,001 0,003
Total 0,928 0,479 2,368 0,004
Per Week
S1 (TiB per one satellite per week) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
1,70 4,797 0,882 2,471 4,230 12,342 0,007 0,021
Total 6,494 3,353 16,573 0,028
Per Month
S1 (TiB per one satellite per month) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
7,377 20,859 3,835 10,744 18,395 53,667 0,030 0,091
Total 28,236 14,580 72,061 0,122
Per Year
S1 (TiB per one satellite per year) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
88,520 250,306 46,022 128,933 220,734 644,000 0,365 1,096
Total 338,826 174,955 864,734 1,461

Table 17: Sentinel-1 published data volumes per product type (TiB)

Published Data Volumes
Per Day
S2 (TiB per one satellite per day) L0 L1A L1B L1C L2A
0,00 0,00 0,00 2,40 3,18
Per Week
S2 (TiB per one satellite per week) L0 L1A L1B L1C L2A
0,00 0,00 0,00 16,83 22,24
Per Month
S2 (TiB per one satellite per month) L0 L1A L1B L1C L2A
0,00 0,00 0,00 73,14 96,63
Per Year
S2 (TiB per one satellite per year) L0 L1A L1B L1C L2A
0,00 0,00 0,00 877,66 1159,61

Table 18: Sentinel-2 published data volumes per product type (TiB)

Published Data Volumes
Per Day
S3 (TIB per one satellite per day) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,000 0,000 0,000 0,000 0,000 0,000 0,000 0,000
L1 0,178 0,178 0,172 0,000 0,000 0,000 0,126 0,065
L2 0,022 0,022 0,026 0,000 0,0538 0,068 0,005 0,002
Total 0,200 0,200 0,198 0,000 0,054 0,068 0,132 0,067
Total 0,400 0,198 0,122 0,199
Per Week
S3 (TIB per one satellite per week) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,000 0,000 0,000 0,000 0,000 0,000 0,000 0,000
L1 1,247 1,249 1,202 0,000 0,000 0,000 0,884 0,453
L2 0,151 0,151 0,182 0,000 0,377 0,478 6,185 3,169
Total 1,397 1,401 1,384 0,000 0,377 0,478 7,068 3,622
Total 2,798 1,384 0,855 10,690
Per Month
S3 (TIB per One satellite per month) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,000 0,000 0,000 0,000 0,000 0,000 0,000 0,000
L1 5,421 5,433 5,229 0,000 0,000 0,000 3,842 1,969
L2 0,655 0,659 0,791 0,000 1,638 2,081 0,166 0,074
Total 6,076 6,091 6,019 0,000 1,638 2,081 4,007 2,042
Total 12,168 6,019 3,718 6,050
Per Year
S3 (TIB per One satellite per year) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0,000 0,000 0,000 0,000 0,000 0,000 0,000 0,000
L1 65,055 65,192 62,743 0,000 0,000 0,000 46,102 23,622
L2 7,862 7,905 9,489 0,000 19,651 24,966 1,986 0,886
Total 72,917 73,097 72,233 0,000 19,651 24,966 48,089 24,508
Total 146,014 72,233 44,618 72,597

Table 19: Sentinel-3 published data volumes per instrument and level (TiB)

According to the current assumption on the launch dates and the lifetime (RD-EOF-LTS), the following profile is expected for the yearly published data volume (PiB) for each mission:

img-15.jpeg

Figure 11 Yearly average published data volume (PiB)

7.2. Published number of products

The assumption for the representations of the overall number of published products yearly per year is that the number of users and the average data volume per year is maintained. The table below reports the number of products published at the Data Access system, for one satellite, divided per product level and mission:

Number of published products
L0
One Satellite Num per day Num per Month Num per Year
S1 1063,70 32376,25 388515,02
S2 0 0 0
S3 0 0 0
S5P 0 0 0
Total 1.064 32.376 388.515
L1
One Satellite Num per day Num per Month Num per Year
S1 2417,53 73583,48 883001,78
S2 (L1C) 5.877 178.759 2.145.105
S3 1.601 48.682 584.183
S5P 1.882 56.445 677.340
Total 11.777 357.469 4.289.629
L2
One Satellite Num per day Num per Month Num per Year
S1 715,32 21772,67 261272,06
S2 (L2A) 5.382 163.703 1.964.430
S3 2.772 84.324 1.011.893
S5P 1.995 59.850 718.200
Total 10.865 329.650 3.955.795
Total
One Satellite Num per day Num per Month Num per Year
S1 4196,55 127732,41 1532788,86
S2 11.259 342.461 4.109.535
S3 4.373 133.006 1.596.076
S5P 3.877 116.295 1.395.540
Total 23.705 719.495 8.633.940

Table 20 Average yearly number of published products per product level and mission (TiB)

The following tables report instead, separately for Sentinel-1, Sentinel-2 and Sentinel-3, the number of products published at the Data Access system, for one satellite, divided per product type:

Number of Published Products
Per Day
S1 (TiB per One satellite per day) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
283 781 332 839 300 832 236 432
Total 1064 1172 1132 668
Per Week
S1 (TiB per One satellite week) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
1980 5466 2326 5876 2101 5822 1650 3025
Total 7446 8203 7923 4675
Per Month
S1 (TiB per One satellite month) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
8609 23767 10115 25552 9136 25314 7175 13155
Total 32376 35667 34449 20330
Per Year
S1 (TiB per One satellite year) L0 GRD SLC OCN
NRT NTC NRT NTC NRT NTC NRT NTC
103305 285210 121380 306620 109626 303764 86097 157861
Total 388515 428000 413390 243958

Table 21 Sentinel-1 number of published products per product type (TiB)

Number of Published Products
Per Day
S2 (TiB per One satellite per day) L0 L1A L1B L1C L2A
0 0 0 5877 5382
Per Week
S2 (TiB per One satellite week) L0 L1A L1B L1C L2A
0 0 0 41139 37674
Per Month
S2 (TiB per One satellite month) L0 L1A L1B L1C L2A
0 0 0 178759 163703
Per Year
S2 (TiB per One satellite year) L0 L1A L1B L1C L2A
0 0 0 2145105 1964430

Table 22 Sentinel-2 number of published products per product type (TiB)

Number of Published Products
Per Day
S3 (TIB per One satellite per day) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0 0 0 0 0 0 0 0
L1 229 229 472 472 0 0 171 29
L2 229 229 472 943 229 243 343 86
Total 457 457 943 1415 229 243 514 114
Total 915 2358 472 629
Per Week
S3 (TIB per One satellite per week) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0 0 0 0 0 0 0 0
L1 1601 1601 3301 3301 0 0 1200 200
L2 1601 1601 3301 6602 1601 1701 8403 1400
Total 3201 3201 6602 9903 1601 1701 9603 1600
Total 6402 16505 3301 11203
Per Month
S3 (TIB per One satellite per OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0 0 0 0 0 0 0 0
L1 6960 6960 14353 14353 0 0 5219 870
L2 6960 6960 14353 28707 6960 7395 10439 2610
Total 13919 13919 28707 43060 6960 7395 15658 3480
Total 27838 71767 14354 19138
Per Year
S3 (TIB per One satellite per year) OLCI SLSTR SYNERGY SRAL
NRT NTC NRT NTC NRT NTC NRT NTC
L0 0 0 0 0 0 0 0 0
L1 83514 83514 172241 172241 0 0 62633 10439
L2 83514 83514 172241 344482 83514 88737 125266 31317
Total 167029 167029 344482 516723 83514 88737 187899 41755
Total 334058 861205 172252 229655

Table 23 Sentinel-3 number of published products per instrument and level (TiB)

According to the current assumption on launch dates and lifetime (RD-EOF-LTS of March 2024), the following profile is expected for the yearly number of products published for each mission:

img-16.jpeg

Figure 12 Yearly number of published products

7.3. Downloaded Data volume

According to what reported by the Copernicus Open Access Hub the ‘Archive Exploitation Ratio’ (AER) for 2023 and for each mission are:

Mission AER
S1 1:15
S2 1:13
S3 1:13
S5P 1:26

Table 24 Archive Exploitation Ratio per mission at the end of 2023

Then, based on downloaded data volume provided by the Copernicus Data Space Ecosystem until December 2024 the average yearly downloaded data volume for each mission has been estimated.

The assumption for the representations of the overall downloaded data volume yearly is that the number of users and the average data volume per year is maintained.

Downloaded Volumes

One Satellite TiB per Day TiB per Month TiB per Year
S1 108,76 3.262,78 39.724,33
S2 138,34 4.150,25 50.529,35
S3 18,49 554,67 6.753,14
S5P 12,62 378,48 4.608,02
Total 278,21 8.346,19 101.614,84

Table 25 Average yearly downloaded data volume

According to the current assumption on launch dates and lifetime, the following profile is expected for the yearly downloaded data volume (PiB) for each mission:

img-17.jpeg

Figure 13 Yearly average downloaded data volume (PiB)

7.4. Downloaded number of products

Based on downloaded number of products provided by the Copernicus Data Space Ecosystem from November 2023 until September 2024 the average yearly downloaded number of products for each mission has been estimated.

The assumption for the representations of the overall downloaded number of products yearly is that the number of users and the average data volume per year is maintained.

Downloaded number of products

One Satellite Num per day Num per Month Num per Year
S1 1.185.960 35.578.803 433.171.927
S2 12.430.291 372.908.735 4.540.163.849
S3 1.365.700 40.970.994 498.821.852
S5P 310.018 9.300.554 113.234.245
Total 1.185.960 458.759.086 5.585.391.872

Table 26 Average yearly number of products downloaded

According to the current assumption on launch dates and lifetime, the following profile is expected for the yearly number of products downloaded for each mission:

img-18.jpeg

Figure 14 Yearly number of downloaded products

7.5. User scenario

Since the lunch of Sentinel-1A, the Copernicus Sentinels Data Access was provided by the Copernicus Open Access Hub (Open Access Hub (copernicus.eu)), operated until 01/11/2023. This has subsequently been superceeded by the Copernicus Data Space Ecosystem (CDSE).

In both cases the Sentinels Data Access is open worldwide to anyone who wishes to register an account.

During the nine years of operations from 2014 until the closing of the registration in 31 October 2023 the total number of registered users for the Copernicus Open Access Hub reached 759.494. A detailed analysis of the user access scenarios are available here:

https://sentinels.copernicus.eu/web/sentinel/-/ninth-copernicus-sentinel-data-access-annual-report

The Copernicus Data Space Ecosystem (CDSE) has been developed with a strategy to evolve towards an open data space ecosystem that further increases the ease with which users can exploit Copernicus Sentinel data, also without download, thanks to enhanced data access, applications and services.

The number of registered users on the CDSE since the start of its operations until end of 2024 is 309.103. The first data access report for the CDSE is available here:

https://dataspace.copernicus.eu/news/2024-11-5-copernicus-data-space-ecosystem-cdse-releases-annual-report-2023

8. REPROCESSING

8.1. General assumptions

Reprocessing campaigns are performed to take into account processing evolution (e.g. quality improvement) and to provide full consistent dataset since the beginning of the related mission.

Reprocessing activities do not impact operational data production as they are either done by external provider and/or using processing facilities different from the operational ones.

Input data, L0 products and auxiliary data, are retrieved from LTA, while reprocessed output products are disseminated to the data access system in order to be available for the final users. As L0 are the inputs of production and are not part of the reprocessing activities, LTA archives are not impacted, while, concerning the data access system, after the completion of the ingestion of the entire reprocessed data set, old data overlapping in sensing are deleted from it.

8.2. Reprocessing campaigns

The table below reports the main completed data reprocessing campaigns for each mission.

Publication date indicates the date of the availability of the full reprocessed dataset on Data Access system.

For Sentinel-3, reprocessing always refers to NTC products.

Mission Product Type Product Level Reprocessed Sensing time Reprocessed Data Volume [GB] Publication date PB
S2A/BMSI_L1B_GR
MSI_L1B_DS
MSI_L1C_TL
MSI_L1C_TC
MSI_L1C_DS		L1S2A:07/2015 – 31/12/2021
S2B: 03/2017 – 31/12/2021		13.678.452Sep-245.0
MSI_L2A_DS
MSI_L2A_TL		L2S2A:07/2015 – 31/12/2021
S2B: 03/2017 – 31/12/2021		12.735.489
S3AOL_1_ERR
OL_1_EFR		L125/04/2016 – 29/11/201782.600Sep-182.23
OL_2_LRR
OL_2_LFR		L201/03/2016 – 01/02/201881.000
SR_1_SRA___
SR_1_SRA_A_
SR_1_SRA_BS		L101/03/2016 – 15/02/2018238.000Nov-182.33
SR_2_LAN___L201/03/2016 – 15/02/2018
S3BOL_1_ERR
OL_1_EFR		L114/05/2018 - 30/10/2019786.902.880Jul-201.34
OL_2_LRR
OL_2_LFR		L214/05/2018 - 30/10/2019132.347.115
SL_1_RBTL109/05/2018-16/02/202012.095.727Jan-211.40
SL_2_LSTL209/05/2018-16/02/202017.539.409
S3A/BSR_2_LAN_SI
SR_2_LAN_HY
SR_2_LAN_LI		L201/03/2016 – 01/04/2023
08/05/2018 – 01/04/2023		10.500Nov-233.20
S5PL2__CO___
L2_O3___
L2_CLOUD_
L2__AER_AI		L230/04/2018 – 31/03/202238.190Dec-222.4
L1B productsL130/04/2018 – 25/07/20221.491.860Mar-232.4
L2_CH4__
L2_NO2__
L2__AER_LH		L230/04/2018 – 25/07/2022
L2__CO___
L2_O3___
L2_CLOUD_
L2__AER_AI		L201/04/2022 - 25/07/2022
L2__SO2___
L2__HCHO___		L207/05/2018 – 03/08/202272.620Apr-232.4
L2__O3_TCL
L2__O3_PR		L230/04/2018 - 03/08/2022

Table 27 Completed reprocessing campaigns

9. DATA FLOW PROCESS CHART

9.1. Sentinel 1 Data flow

Based on the values presented in the previous chapters, an overall view of the data flow of Sentinel-1 is presented here:

img-19.jpeg

Figure 15 Sentinel 1 Overall Data Flow

9.1.1. Sentinel-1 Particularities

The Sentinel-1 production operation concept is strongly driven by the satellites capabilities and constraints. It shall be noticed that additional data types generated as part of the S1 production (such as the segments for L0) and not intended for preservation or dissemination are outside the scope of this System Technical Budget.

9.1.2. Sentinel-1 On board Data Compression

The Sentinel-1 on-board data compression is based on the Flexible Dynamic Block Adaptive Quantisation (FDBAQ), which provides a variable bit rate coding, resulting in a non deterministic SAR instrument data compression rate [RD-5]. The number of bits allocated to compress the instrument data before memory storage (or before direct downlink in the case of pass-through mode operations) is variable, depending on the surface reflectivity and increasing for bright scatterers.

The allocated number of bits on board varies between 3 and 5, with non-integer intermediate steps. It is defined to reduce the average data rate, ensuring a IW data rate close to the downlink data rate of 260 Mbps.

The direct result of this approach is that the on board memory volume occupied by a given data take will depend on the allocated number of bits during the on board compression process. This number of bits (or resulting data volume) is not fixed for a given area, but is expected to vary for different polarisation and incidence angles and eventually, over time, according to the surface reflectivity changes.

This approach leads to a not fully predictable on-board compression rate and therefore, to a not fully predictable on board memory volume occupied for each data take and to a not fully predictable time required for downlinking each data take. This results in the impossibility to manage data downlink through sensing start and stop times.

Prediction of the occupied memory volume by each acquisition segment (and the required downlink time) and real-time ground monitoring of the memory evolution can be performed using the predicted average downlink rate and complemented by modelling the FDBAQ compression on ground using an accurate global backscattering map.

9.1.3. Sentinel-1 Data Rates

The Sentinel-1 satellite is able to transmit SAR data on ground over two X-band channels at a net rate of 260 Mbps (ISP level) per channel

Estimated average SAR data rates after on-board FDBAQ compression are shown in Figure 16. The SAR instrument data rate may be higher than the data downlink rate (only for Stripmap Swath-1 according to the table below). In such case, data acquired in pass-through mode over

an X-Band Receiving Ground Station might not be completely down-linked over the same ground station if passthrough operations are maintained until the end of the contact time.

SAR Instrument Mode Data rate per mode [Mbps]
Single polarization Dual polarization
Stripmap 1 279.132 558.264
Stripmap 2 232.501 465.002
Stripmap 3 235.507 471.014
Stripmap 4 194.839 289.678
Stripmap 5-N 207.477 414.954
Stripmap 5-S 206.142 412.284
Stripmap 6 183.835 367.670
Extra Wide 63.573 127.146
Interferometric Wide 206.629 413.258
Wave 15.281 Not Applicable

Figure 16 Sentinel-1 SAR FDBAQ Estimated Average Data Rates

9.1.4. Compression

The produced data L1 and L2 are compressed for achieving and publishing. The compression rate is 40% less volume archived and published.

9.1.5. L0 Slices

In production, the L0 Assembly/Slicing Processor assembles partial segments of Level 0 Data Takes acquired by different Acquisition to generate a Complete Level 0 Product. The assembled Level 0 Product is also cut into Level 0 Slices used to feed the higher level productions.

The volumes and the number of products presented here are considering only the number of slices for L0 NRT+NTC (300TiB/year).

The volume of L0 NRT data includes only the L0 slices, without considering the segments.

9.2. Sentinel-2 Data flow

Based on the values presented in the previous chapters an overall view of the data flow of Sentinel-2 is presented here:

img-20.jpeg

Figure 17 Sentinel 2 Overall Data flow

9.3. Sentinel-2 Number of packages

In the past all granules and the Data strips were archived in a single package. Currently the granules are archived individually. All existing packages in LTA are modified according the new need. This would not impact the overall data volume.

9.4. Sentinel-2 acquisition changes during one year

Sentinel-2 acquisition principle is to acquire data from the land surfaces under specific sun illumination conditions (during the descending portion of the orbit). Hence, the data volume is object of seasonal variations along the year of about 20%.

9.5. Sentinel-2A and Sentinel-2B acquisition differences

Differences in acquisition between Sentinel-2A and Sentinel-2B are not constant over the years but depend on the campaigns of acquisition Mission Planning has to implement.

9.5.1. Levels volume/number of products calculations using proportions relationship

The relation between the levels (L0, L1, L2) volumes or numbers of products can be estimated.

  • Number of products

The L1B is similar to L0.

The L2A is similar to L1C.

  • Volumes

The L1C is 2,1 times more than L1B. The level L2A is 30% more than L1C.

9.6. Sentinel-3 Data flow

Based on the values presented in the previous chapters an overall view of the data flow of Sentinel-3 is presented here:

img-21.jpeg

Figure 18 Sentinel 3 Overall Data flow

9.7. Sentinel-3 Particularities

The Sentinel-3 CSC operation concept is strongly driven by the instruments on board, more precisely the OLCI (Ocean and Land Colour Instrument), SLSTR (Sea and Land Surface Temperature Radiometer) and the SRAL (Sentinel-3 Ku/C Radar Altimeter).

The volumes and the numbers of products by product are represented in chapter 10 ANNEX.

9.8. Sentinel-5P Data flow

Based on the values presented in the previous chapters an overall view of the data flow of Sentinel-5P is presented here:

img-22.jpeg

Figure 19 Sentinel-5P Overall Data flow

9.8.1. Sentinel – S5P Particularities

The L1CAL and L1 ENG in NTC are not published via CDSE. They are in any case considered as negligible in overall dataflow.

There is one L0 flow that feeds both NRT and NTC processing chains.

The L1 NTC is compressed: the published data volume is 60 % of the produced data volume.

For Sentinel-5P not only L0 is archived, but also exceptionally there is one copy of L1, L2.

9.8.2. Auxiliary Data

The auxiliary data volume of Sentinel-5P represents 3% of the archived data volume.

10. ANNEX

10.1. Mission Rules

The following tables refers to the estimations for 1 satellite.

The columns ‘P’, ‘A’, ‘D’ indicate the service where the specific Product Type is ‘Produced’, ‘Archived’ and ‘Disseminated’, respectively.

10.2. Sentinel -1

TYPE Instrument Level Timeliness #Number products / orbit/unit #Num/ day P A D Volume per Orbit [GB] Volume per day [GB]
S(1.2.3.4.5.6)_RAW__0S(SH/SV/
DH/DV)		SM0NTC0,1562,280PSLTADA0,2293,299
S(1.2.3.4.5.6)_RAW__0C(SH/SV/
DH/DV)		SM0NTC0,1452,120PSLTADA-
S(1.2.3.4.5.6)_RAW__0N(SH/SV/
DH/DV)		SM0NTC0,1452,120PSLTADA--
S(1.2.3.4.5.6)_RAW__0A(SH/SV/
DH/DV)		SM0NTC0,1452,120PSLTADA--
RF_RAWRFC0NTC0,89213,000PSLTADA0,0761,100
IW_RAW__0S(SH/SV/DH/DV)IW0NRT9,570139,53
0		PSLTADA16,798241,892
IW_RAW__0C(SH/SV/DH/DV)IW0NRT0,70310,250PSLTADA0,1532,199
IW_RAW__0N(SH/SV/DH/DV)IW0NRT0,70210,240PSLTADA0,0761,100
IW_RAW__0A(SH/SV/DH/DV)IW0NRT0,70310,250PSLTADA0,0000,000
EW_RAW__0S(SH/SV/DH/DV)EW0NRT1,78926,090PSLTADA2,06229,687
EW_RAW__0C(SH/SV/DH/DV)EW0NRT0,4967,230PSLTADA0,0761,100
EW_RAW__0N(SH/SV/DH/DV)EW0NRT0,4967,230PSLTADA0,0000,000
EW_RAW__0A(SH/SV/DH/DV)EW0NRT0,4967,230PSLTADA0,0000,000
IW_RAW__0S(SH/SV/DH/DV)IW0NTC25,988378,90
0		PSLTADA45,049648,711
IW_RAW__0C(SH/SV/DH/DV)IW0NTC3,01743,990PSLTADA0,4586,597
IW_RAW__0N(SH/SV/DH/DV)IW0NTC3,01743,990PSLTADA0,2293,299
IW_RAW__0A(SH/SV/DH/DV)IW0NTC3,01743,990PSLTADA0,0761,100
EW_RAW__0S(SH/SV/DH/DV)EW0NTC2,49636,390PSLTADA2,13830,786
EW_RAW__0C(SH/SV/DH/DV)EW0NTC0,92413,470PSLTADA0,0761,100
EW_RAW__0N(SH/SV/DH/DV)EW0NTC0,92413,470PSLTADA0,0000,000
EW_RAW__0A(SH/SV/DH/DV)EW0NTC0,92413,470PSLTADA--
WV_RAW__0S(SH/SV)WV0NTC1,92628,080PSLTADA5,11673,667
WV_RAW__0C(SH/SV)WV0NTC1,91427,900PSLTADA0,1532,199
WV_RAW__0N(SH/SV)WV0NTC1,91427,900PSLTADA--
WV_RAW__0A(SH/SV)WV0NTC1,91427,900PSLTADA0,0000,000
GP_RAW__0_GPSR0_1,92428,050PSLTA0,0000,000
HK_RAW__0_HKTM0_1,92428,050PSLTA0,0000,000
OBS_SS__Orbit and
Burst
Synchronis
ation		_1,00014,580PSLTADA0,0000,000
S(1.2.3.4.5.6)_SLC__1S(SH/SV/D
H/DV)		SM1NTC0,1572,290PSDA0,4586,597
S(1.2.3.4.5.6)_SLC__1A(SH/SV/D
H/DV)		SM1NTC0,1572,290PSDA--
S(1.2.3.4.5.6)_GRDH_1S(SH/SV/
DH/DV)		SM1NTC0,1562,280PSDA--
S(1.2.3.4.5.6)_GRDH_1A(SH/SV/
DH/DV)		SM1NTC0,1562,280PSDA--
IW_SLC__1S(SH/SV/DH/DV)IW1NRT9,607140,07
0		PSDA43,293623,422
IW_SLC__1A(SH/SV/DH/DV)IW1NRT9,607140,07
0		PSDA0,0761,100
IW_GRDH_1S(SH/SV/DH/DV)IW1NRT9,608140,08
0		PSDA9,163131,941
IW_GRDH_1A(SH/SV/DH/DV)IW1NRT9,608140,08
0		PSDA0,0000,000
EW_SLC__1S(SH/SV/DH/DV)EW1NRT0,5437,910PSDA2,67238,483
EW_SLC__1A(SH/SV/DH/DV)EW1NRT0,5437,910PSDA0,0000,000
EW_GRDM_1S(SH/SV/DH/DV)EW1NRT1,78926,080PSDA0,4586,597
EW_GRDM_1A(SH/SV/DH/DV)EW1NRT1,78926,080PSDA--
IW_SLC__1S(SH/SV/DH/DV)IW1NTC26,132381,01
0		PSDA122,16
8		1759,216
IW_SLC__1A(SH/SV/DH/DV)IW1NTC26,132381,01
0		PSDA0,2293,299
IW_GRDH_1S(SH/SV/DH/DV)IW1NTC26,136381,06
0		PSDA26,342379,331
IW_GRDH_1A(SH/SV/DH/DV)IW1NTC26,136381,06
0		PSDA0,0761,100
EW_SLC__1S(SH/SV/DH/DV)EW1NTC0,1151,680PSDA0,6118,796
EW_SLC__1A(SH/SV/DH/DV)EW1NTC0,1151,680PSDA--
EW_GRDM_1S(SH/SV/DH/DV)EW1NTC2,49736,400PSDA0,5347,697
EW_GRDM_1A(SH/SV/DH/DV)EW1NTC2,49736,400PSDA--
WV_SLC__1S(SH/SV)WV1NTC1,93628,230PSDA10,995158,329
WV_SLC__1A(SH/SV)WV1NTC1,93628,230PSDA0,0000,000
SM_OCN__2S(SH/SV/DH/DV)SM2NTC0,1281,870PSDA--
SM_OCN__2A(SH/SV/DH/DV)SM2NTC0,1281,870PSDA--
IW_OCN__2S(SH/SV/DH/DV)IW2NRT6,38393,060PSDA0,0761,100
IW_OCN__2A(SH/SV/DH/DV)IW2NRT6,38393,060PSDA0,0000,000
EW_OCN__2S(SH/SV/DH/DV)EW2NRT1,70124,800PSDA0,0000,000
EW_OCN__2A(SH/SV/DH/DV)EW2NRT1,70124,800PSDA--
IW_OCN__2S(SH/SV/DH/DV)IW2NTC10,365151,12
0		PSDA0,0761,100
IW_OCN__2A(SH/SV/DH/DV)IW2NTC10,365151,12
0		PSDA0,0000,000
EW_OCN__2S(SH/SV/DH/DV)EW2NTC2,39034,850PSDA0,0761,100
EW_OCN__2A(SH/SV/DH/DV)EW2NTC2,39034,850PSDA--
WV_OCN__2S(SH/SV/DH/DV)WV2NTC1,93828,260PSDA0,0761,100
WV_OCN__2A(SH/SV/DH/DV)WV2NTC1,93828,260PSDA0,0000,000

Auxiliary:

TYPE Asynchronous/Systematic Level #Num/day P A D Volume per day [GB] Volume [GB]
AUX_PREORBSystematicAUX14PODLTADA0,0002
AUX_RESORBSystematicAUX14PODLTADA0,0011
AUX_POEORBSystematicAUX1PODLTADA0,0006
AUX_WNDSystematicAUX180ADGSLTADA4,6179
AUX_WAVSystematicAUX100ADGSLTADA0,0387
AUX_ICESystematicAUX1ADGSLTADA0,0011
AUX_TECSystematicAUX0,8ADGSLTADA0,0003
AUX_TROSystematicAUX4ADGSLTADA6,4424
AUX_GNSSRDSystematicAUXPOD-DA0,0299
AUX_PROQUASystematicAUXPOD-DA0,0100
S[1..6]_ETA__AXSystematicAUX2,50PS0,0365
IW_ETA__AXSystematicAUX557,00PS47,2446
EW_ETA__AXSystematicAUX13,00PS3,9943
AUX_ML2AsynchronousAUXMPC0,4992
AUX_PP1AsynchronousAUXMPCLTADA0,0003
AUX_CALAsynchronousAUXMPCLTADA0,0010
AUX_INSAsynchronousAUXMPCLTADA0,0010
AUX_PP2AsynchronousAUXMPCLTADA0,0010
AUX_SCSAsynchronousAUXMPCLTADA2,7488
AUX_ITCAsynchronousAUXMPCLTADA0,0000
AUX_SCFAsynchronousAUXMPCLTADA0,0000

10.3. Sentinel-2

  • the L1B, L1C and L2A production is systematic.

  • The L1A is produced in relation to the calibration observations only, and it is not distributed to the final user . The results of L1A are negligible in numbers and volumes, with respect to other product levels. They have hence not been reflected in the document.

TYPE Instrument Level Timeliness #Num per products/orbit/unit #Num/day P A D Volume per Orbit [GB] Volume per day [GB]
MSI_L0__DSMSI0NTC5,81783,190PSLTADA0,1752,5068
MSI_L0__GRMSI0NTC4086,69058439,660PSLTADA75,1991075,3409
MSI_L1A_DSMSI1NTC0,0150,211PSDA0,0000,0009
MSI_L1A_GRMSI1NTC1,80925,871PSDA0,0280,3959
MSI_L1B_DSMSI1NTC5,42777,608PSDA0,0490,7014
MSI_L1B_GRMSI1NTC3937,34356304,000PSDA84,8741213,6968
MSI_L1C_DSMSI1NTC5,43677,735PSDA0,0480,6795
MSI_L1C_TLMSI1NTC414,1265922,000PSDA172,909172,909 2472,5991
MSI_L1C_TCMSI1NTC414,1645922,539PSDA24,044343,8351
MSIL1C.SAFEMSI1NTC410,9795877,000PSDA184,883184,883 2643,8317
MSI_L2A_DSMSI2NTC5,27375,400PSDA0,0460,6630
MSI_L2A_TLMSI2NTC409,1855851,350PSDA259,603259,603 3712,3233
MSI_L2A_TCMSI2NTC409,1855851,349PSDA21,841312,3283
MSIL2A.SAFEMSI2NTC376,3645382,000PSDA244,276244,276 3493,1455
AUX_SADATAMSIAUXNTC4,000268,880PSLTADA0,1017,2733
PRD_HKTMNTC29,000PSLTA0,0361,1138

Auxiliary:

TYPE Asynchronous/Systematic Level #Num/day P A D Volume per day [GB] Volume [GB]
AUX_CAMSFOSystematicAUX2ADGSLTADA1,074
AUX_ECMWFDSystematicAUX2ADGSLTADA0,468
AUX_UT1UTCSystematicAUX0,140ADGSLTADA0,000
GIP_R2ABCA (*)SystematicAUX0,075ADGSLTADA0,0000
GIP_R2EQOG (*)SystematicAUX0,978ADGSLTADA0,0006
AUX_GNSSRDSystematicAUX1PODDA0,0240
AUX_PROQUASystematicAUX1PODDA0,0159
AUX_POEORB
AUX_CAMSAN
AUX_CAMSRE		Systematic
Asynchronous
Asynchronous		AUX
AUX
AUX		1POD
ADGS
ADGS		LTA
LTA		DA
DA
DA		1,074
1,074

(*) updated once a month

10.4. Sentinel-3

  • The L1 and L2 STC budgets are added to the corresponding L1 and L2 NRT budgets.

TYPE Instrument Level Timeliness #Num/orbit/unit #Num/day P A D Volume per Orbit [GB] Volume per day [GB]
DO_0_DOP__GDORISISPNRT114,3ACQ0,0010,015
DO_0_NAV__GDORISISPNRT114,3ACQ0,0010,015
GN_0_GNS__GGNSSISPNRT114,3ACQ0,0090,123
MW_0_MWR__GMWRISPNRT114,3ACQ0,0030,046
OL_0_CR___GOLCIISPNRT114,3ACQ0,0080,107
OL_0_EFR__GOLCIISPNRT22314,4ACQ9,884141,138
SL_0_SLT__GSLSTRISPNRT20285,8ACQ5,29775,636
SR_0_CAL__GSRALISPNRT114,3ACQ0,0080,107
SR_0_SRA__GSRALISPNRT10142,9ACQ7,695109,877
TM_0_HKM__GTMISPNRT114,3ACQ0,0080,107
TM_0_HKM2_GTMISPNRT114,3ACQ0,0010,015
TM_0_NAT__GTMISPNRT228,6ACQ0,0010,015
DO_0_DOP___DORISL0NRT114,3PSLTADA0,0010,007
DO_0_NAV___DORISL0NRT114,3PSLTADA0,0000,002
GN_0_GNS___GNSSL0NRT685,7PSLTADA0,0040,055
MW_0_MWR___MWRL0NRT114,3PSLTADA0,0010,020
OL_0_CR0___OLCIL0NRT114,3PSLTADA0,0030,036
OL_0_CR1___OLCIL0NRT114,3PSLTADA2,44634,931
OL_0_EFR___OLCIL0NRT22314,4PSLTADA8,237117,624
SL_0_SLT___SLSTRL0NRT20285,8PSLTADA4,22260,295
SR_0_CAL___SRALL0NRT114,3PSLTADA0,0050,065
SR_0_SRA___SRALL0NRT10142,9PSLTADA9,799139,932
TM_0_HKM___TML0NRT114,3PSLTA0,0070,096
TM_0_HKM2__TML0NRT114,3PSLTA0,0010,008
TM_0_NAT___TML0NRT228,6PSLTA0,0030,043
MW_1_CAL___MWRL1NRT114,3PSLTADA0,0000,000
MW_1_MWR___MWRL1NRT114,3PSDA0,0030,047
OL_1_EFR___OLCIL1NRT15214,4PSDA12,756182,153
OL_1_ERR___OLCIL1NRT114,3PSDA0,95813,682
OL_1_RAC___OLCIL1NRT114,3PSLTADA0,0000,000
OL_1_SPC___OLCIL1NRT114,3PSLTADA0,0000,000
SL_1_RBT___SLSTRL1NRT34471,6PSDA13,227188,876
SR_1_CAL___SRALL1NRT114,3PSLTADA0,0000,000
SR_1_SRA_A_SRALL1NRT10142,9PSDA4,86369,391
SR_1_LAN_RDSRALL1NRT10142,9PSDA0,0801,140
OL_2_LFR___OLCIL2NRT15214,4PSDA1,48321,183
OL_2_LRR___OLCIL2NRT114,3PSDA0,1742,485
SL_2_LST___SLSTRL2NRT34471,6PSDA2,00028,566
SR_2_LAN_SISRALL2NRT685,7PSDA0,0731,044
SR_2_LAN_HYSRALL2NRT685,7PSDA0,0851,218
SR_2_LAN_LISRALL2NRT685,7PSDA0,0711,009
OL_0_EFR___OLCIL0NTC114,3PS9,134130,436
SL_0_SLT___SLSTRL0NTC114,3PS4,63766,209
MW_1_MWR___MWRL1NTC114,3PSDA0,0030,046
OL_1_EFR___OLCIL1NTC15214,4PSDA12,785182,565
SL_1_RBT___SLSTRL1NTC34471,6PSDA13,198188,463
SR_1_SRA_A_SRALL1NTC228,6PSDA4,63471,110
SR_1_LAN_RDSRALL1NTC228,6PSDA0,0811,150
SY_1_MISR__SYNL1NTC114,3PSDA3,85355,023
OL_1_ERR___OLCIL1NTC114,3PSDA0,95813,682
OL_2_LFR___OLCIL2NTC15214,4PSDA1,49221,306
OL_2_LRR___OLCIL2NTC114,3PSDA0,1742,489
SL_2_FRP___SLSTRL2NTC34471,6PSDA2,33033,277
SL_2_LST___SLSTRL2NTC34471,6PSDA1,92427,479
SR_2_LAN_SISRALL2NTC228,6PSDA0,0630,907
SR_2_LAN_HYSRALL2NTC228,6PSDA0,0801,137
SR_2_LAN_LISRALL2NTC228,6PSDA0,0440,622
SY_2_AOD___SYNL2NTC114,3PSDA0,0340,481
SY_2_SYN___SYNL2NTC15214,4PSDA5,12273,145
SY_2_V10___SYNL2NTC00,0PSDA0,0200,292
SY_2_VG1___SYNL2NTC00,0PSDA0,0580,830
SY_2_VGK___SYNL2NTC114,3PSDA0,0420,600
SY_2_VGP___SYNL2NTC114,3PSDA0,0290,409
SR_0_SRA___SRALL0STC114,3PS4,61565,896
MW_1_MWR___MWRL1STC114,3PSDA0,0030,047
SR_1_SRA_A_SRALL1STC228,6PSDA4,52269,391
SR_1_LAN_RDSRALL1STC228,6PSDA0,0791,129
SY_1_MISR__SYNL1STC114,3PSDA3,85355,023
SR_2_LAN_SISRALL2STC228,6PSDA0,0640,916
SR_2_LAN_HYSRALL2STC228,6PSDA0,0791,133
SR_2_LAN_LISRALL2STC228,6PSDA0,0460,659
SY_2_SYN___SYNL2STC15214,4PSDA4,03857,659
SY_2_V10___SYNL2STC00,0PSDA0,0180,261
SY_2_VG1___SYNL2STC00,0PSDA0,0580,827
SY_2_VGK___SYNL2STC114,3PSDA0,0761,084
SY_2_VGP___SYNL2STC114,3PSDA0,0290,409
HK_RAW__TMRAWNRT114,30,0050,077

Auxiliary:

TYPE Asynchronous/Systematic Level #Num/day P A D Volume per day [GB] Volume [GB]
AUX_MOEORBSystematicAUX1POD-DA
AUX_POEORBSystematicAUX1POD-DA
AUX_PRCPTFSystematicAUX1POD-DA
AUX_GNSSRDSystematicAUX2PODLTADA0,0600
AUX_PROQUASystematicAUX1POD-DA0,0159
AUX_COMBSystematicAUX1PODDA0,0020
SR___POE_AXSystematicAUX9POD-DA
AX___MF1_AXSystematicAUX8ADGSLTADA1,3800
AX___MFA_AXSystematicAUX4ADGSLTADA0,0500
AX___MA1_AXSystematicAUX4ADGSLTADA0,6300
AX___MF2_AXSystematicAUX8ADGSLTADA5,4800
AX___MA2_AXSystematicAUX4ADGSLTADA2,7800
AX___FPO_AXSystematicAUX1ADGSLTADA0,0000
AX___FRO_AXSystematicAUX1ADGSLTADA0,0018
SR_1_CA{1L,1S,2K,2C}AXSystematicAUX6PSLTADA0,0678
MW_1_{NIR,DNB,MON}_AXSystematicAUX14,28PSLTADA3,0702
SL_1_VSC_AXSystematicAUX14,28PSLTADA0,0002
SR___MGNPAXSystematicAUX1ADGSLTADA0,0006
SR___POEPAXSystematicAUX1ADGSLTADA0,0006
SR_2_PMPPAXSystematicAUX1ADGSLTA-0,0004
SR_2_PCPPAXSystematicAUX1ADGSLTADA0,0004
SR___MDO_AXSystematic1ADGSLTADA0,0001
SR___POESAXSystematic1ADGSLTADA0,0001
SR_2_PMPSAXSystematic1ADGSLTADA0,0000
SR_2_RMO_AXSystematic4ADGSLTADA0,0061
SR_2_PMO_AXSystematic4ADGSLTADA0,0061
SR_2_POL_AXSystematic1ADGSLTADA0,0003
SR_2_PGI_AXSystematic1ADGSLTADA0,0002
SR_2_RGI_AXSystematic1ADGSLTADA0,0002
SR_1_USO_AXSystematic1ADGSLTADA0,0007
SR___MGNSAXSystematic1ADGSLTADA0,0001
SR_2_SIC{N,S}AXSystematic1ADGSLTADA0,0021
SR_2_SIF{N,S}AXSystematic1ADGSLTADA0,0021
SR_2_ICTNAXSystematic1ADGSLTADA0,0060
SR_2_ICTSAXSystematic1ADGSLTADA0,0042
SL_2_SSTAAXSystematic1ADGSLTADA0,0160
SL_2_DIMSAXSystematic1ADGSLTADA0,0024
AX___OSF_AXAsynchronousAUXADGSLTADA

10.4.1. Sentinel 5P

  • NTC is equivalent to the OFFL.

  • There is one L0 flow that feeds both NRT and NTC chains.

TYPE Instrument Level Timeliness #Num/orbit/unit #Num/day P A D Volume per Orbit GB Volume per day GB
OPER_L0__ENG_A_TROPOMIL0NTC5,512,7LTADA0,0140,199
OPER_L0__ODB_1_TROPOMIL0NTC5,512,7LTADA0,95513,561
OPER_L0__ODB_2_TROPOMIL0NTC5,512,7LTADA2,98542,387
OPER_L0__ODB_3_TROPOMIL0NTC5,512,7LTADA2,98542,387
OPER_L0__ODB_4_TROPOMIL0NTC5,512,7LTADA2,98542,387
OPER_L0__ODB_5_TROPOMIL0NTC5,512,7LTADA2,98542,387
OPER_L0__ODB_6_TROPOMIL0NTC5,512,7LTADA2,98542,387
OPER_L0__ODB_7_TROPOMIL0NTC5,512,7LTADA1,65723,529
OPER_L0__ODB_8_TROPOMIL0NTC5,512,7LTADA1,65723,529
OPER_L0__SAT_A_TROPOMIL0NTC5,512,7LTADA0,0020,028
OFFL_L1B_CA_SIRTROPOMIL1BNTC114,5PSLTADA3,5550,410
OFFL_L1B_CA_UVNTROPOMIL1BNTC114,5PSLTADA16,857239,369
OFFL_L1B_ENG_DBTROPOMIL1BNTC114,5PSLTADA0,060,852
OFFL_L1B_IR_SIRTROPOMIL1BNTC11PSLTADA0,0040,057
OFFL_L1B_IR_UVNTROPOMINTC11PSLTADA0,0120,170
OFFL_L1B_RA_BD1TROPOMIL1BNTC114,5PSLTADA0,6819,670
OFFL_L1B_RA_BD2TROPOMIL1BNTC114,5PSLTADA3,57150,708
OFFL_L1B_RA_BD3TROPOMIL1BNTC114,5PSLTADA3,57150,708
OFFL_L1B_RA_BD4TROPOMIL1BNTC114,5PSLTADA3,57150,708
OFFL_L1B_RA_BD5TROPOMIL1BNTC114,5PSLTADA3,57150,708
OFFL_L1B_RA_BD6TROPOMIL1BNTC114,5PSLTADA3,57150,708
OFFL_L1B_RA_BD7TROPOMIL1BNTC114,5PSLTADA2,14330,431
OFFL_L1B_RA_BD8TROPOMIL1BNTC114,5PSLTADA2,14330,431
OFFL_L2__AER_AITROPOMIL2NTC114,5PSLTADA0,2193,110
OFFL_L2__AER_LHTROPOMIL2NTC114,5PSLTADA0,0861,221
OFFL_L2__CH4_TROPOMIL2NTC114,5PSLTADA0,0610,866
OFFL_L2__CLOUD_TROPOMIL2NTC114,5PSLTADA0,5127,270
OFFL_L2__CO____TROPOMIL2NTC114,5PSLTADA0,2092,968
OFFL_L2__FRESCOTROPOMIL2NTC114,5PSLTADA0,2062,925
OFFL_L2__HCHO_TROPOMIL2NTC114,5PSLTADA0,75710,749
OFFL_L2__NO2___TROPOMIL2NTC114,5PSLTADA0,6068,605
OFFL_L2__NP_BD3TROPOMIL2NTC114,5PSLTADA0,4356,177
OFFL_L2__NP_BD6TROPOMIL2NTC114,5PSLTADA0,4336,149
OFFL_L2__NP_BD7TROPOMIL2NTC114,5PSLTADA0,2092,968
OFFL_L2__03_TCLTROPOMIL2NTC11PSLTADA0,0010,014
OFFL_L2__O3__PRTROPOMIL2NTC114,5PSLTADA0,3915,552
OFFL_L2__O3____TROPOMIL2NTC114,5PSLTADA0,3354,757
OFFL_L2__SO2___TROPOMIL2NTC114,5PSLTADA1,06415,109
NRTI_L1B_ENG_DBTROPOMIL1BNRT20,5288PS0,1091,548
NRTI_L1B_RA_BD1TROPOMIL1BNRT12179PS1,3640719,370
NRTI_L1B_RA_BD2TROPOMIL1BNRT12179PS7,87189111,781
NRTI_L1B_RA_BD3TROPOMIL1BNRT12179PS7,87189111,781
NRTI_L1B_RA_BD4TROPOMIL1BNRT12179PS7,87189111,781
NRTI_L1B_RA_BD5TROPOMIL1BNRT12179PS7,87189111,781
NRTI_L1B_RA_BD6TROPOMIL1BNRT12179PS7,87189111,781
NRTI_L1B_RA_BD7TROPOMIL1BNRT12179PS3,6658352,055
NRTI_L1B_RA_BD8TROPOMIL1BNRT12179PS3,6658352,055
NRTI_L2__AER_AITROPOMIL2NRT12179PSDA0,231533,288
NRTI_L2__AER_LHTROPOMIL2NRT12179PSDA0,087791,247
NRTI_L2__CLOUD_TROPOMIL2NRT12179PSDA0,520937,397
NRTI_L2__CO____TROPOMIL2NRT12179PSDA0,229603,260
NRTI_L2__FRESCOTROPOMIL2NRT12179PSDA0,218023,096
NRTI_L2__HCHO_TROPOMIL2NRT12179PSDA0,8585812,192
NRTI_L2__NO2___TROPOMIL2NRT12179PSDA0,612688,700
NRTI_L2__03_TCLTROPOMIL2NRT0,071PSDA0,000080,001
NRTI_L2__O3__PRTROPOMIL2NRT12179PSDA0,415495,900
NRTI_L2__O3____TROPOMIL2NRT12179PSDA0,373245,300
NRTI_L2__SO2___TROPOMIL2NRT12179PSDA1,1478916,300

Auxiliary:

TYPE Asynchronous/ Systematic Level #Num/day P A D Volume per day [GB] Volume [GB]
AUX_MET_2DSystematicAUX2PSLTADA0,100
AUX_MET_QPSystematicAUX2PSLTADA1,423
AUX_MET_TPSystematicAUX2PSLTADA1,236
AUX_CTMCH4 (*)SystematicAUX0,003MPCLTADA0,001
AUX_CTM_CO (*)SystematicAUX0,003MPCLTADA0,000
AUX_CTMANASystematicAUX1PSLTADA1,527
AUX_CTMFCTSystematicAUX1PSLTADA7,799
AUX_NISESystematicAUX1EXTLTADA0,002
AUX_IERS_B (**)SystematicAUX0,033EXTLTA0,000
(*)AUX_IERS_CSystematicAUX0,003EXTLTA0,000
VIIRS_CMSystematicAUX149,7PSLTA31,875
VIIRS_L1B_GEOSystematicAUX990PSLTA24,438
VIIRS_L1B_RRSystematicAUX2970PSLTA14,375
VIIRS_CPSystematicAUX149,7PSLTA7,906
VIIRS_DCOMPSystematicAUX149,7PSLTA23,906
VIIRS_CTHSystematicAUX149,7PSLTA58,438

(*) updated once a year (**) updated once a month