|Paper title||Introduction to the EarthCARE Payload Data Ground Segment|
|Form of presentation||Poster|
The EarthCARE (Earth Clouds, Aerosol and Radiation Explorer) mission will be equipped with four co-located instruments (three from ESA and one provided by JAXA) to derived information related to aerosols/clouds/radiation and their interaction through the processing of single instrument data as well as synergistic products.
The Payload Data Ground Segment (PDGS) is the component of the overall EarthCARE Ground Segment in charge of receiving the housekeeping telemetry and instrument source packets via X-Band from the satellite, processing the packets in order to generate different product levels and disseminating them to users in few hours from sensing. The main products include level 0 (corrected and time sorted packets), level 1B (instrument science data calibrated and geolocated), level 2A (geophysical parameters derived from a single instrument) and level 2B or synergistic products (geophysical parameters derived by merging information of several EarthCARE instruments). The PDGS is also in charge of the routine calibration and monitoring of the three ESA instruments, of products quality control as well as planning of payload operations The EarthCARE PDGS consist of several components called facilities. Although the general architecture is similar to other PDGS developed by ESA for Earth Observation Missions, some evolutions were required to take into account some EarthCARE specific aspects.. In particular, the synergistic nature of the mission results in a complex processing model which involves about 30 different processors. In order to streamline the integration of this large number of processors and in anticipation of initially frequent updates, a formal modelling of the processing chain has been introduced to support automatic configuration of the processing facility. In addition, a new facility called the Level 2 TestBed has been included in the PDGS in order to allow processor developers to test their code in quasi operational conditions and in an autonomous way including the possibility to upload new processor versions without assistance from PDGS operators. The presence of a Japanese Instrument on-board also imposes tight dependencies between the ESA and JAXA components in terms of processing as well as in terms of payload planning.
This poster presents the functional and architectural breakdown of the PDGS, external interfaces including FOS (Flight Operation Segment), ECMWF and JAXA. It details the main design drivers including data latency, production model, data volumes, network bandwidth as well as interfaces with end users. The current integration status of the PDGS and its underlying facility is also presented.