Interface Control Document : IDP & OLQC

Transcription

1 PAGE : 1 / 63 Control Document : IDP Written by Company Responsibility Date Signature C.Samson Thales Services IPF Technical Manager for TS 06/04/12 P.Branet Verified by R.Joyeux Thales Services Thales Services TS Design Authority 06/04/12 Project Manager for TS 06/04/12 S. Bonnot TAS Technical Manager 06/04/12 Approved by A. Le Ber TAS Project Manager 06/04/12 Approval evidence is kept within the documentation management system. Documentation Information Submitted to ESA for Filename: Information Review Approval S2_PDGS_TAS_DI_BPDP_ICD_IPF_03 C ontrol_document_idp_olqc.doc

2 PAGE : 2 / 63 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR 01 Draft 08/12/2012 First draft version for ESA review C. SAMSON 01 13/01/2012 First official version for PDR C. SAMSON 02 15/03/2012 Implementation of PDR-RID-286/EC-17: first version of OLQC-GIPP XSD scheme defined (including new test configuration management). Implementation of PDR-RID-287/EC-18: details on OLQC interface, first version of OLQC-GIPP and OLQC Report XSD files. Implementation of PDR-RID-308/EC-23: I/F per IDP-SC or OLQC-SC are detailed. I/F IPU to OLQC has been set to "mixed", a link to ENVI format description is given. Implementation of PDR-RID-316/EC-24: PVI format is set to GML jpeg2000. C. SAMSON A. FIROBEN R. AURIEMMA N. BENECH 03 06/04/2012 Modifications after pre-teb meeting Jpeg 2000 for TCI List of Reference Documents modified References clean-up Typos File Naming Convention: Implementation of RIDS PDR-RID-40/FM-12 Implementation of RIDS PDR-RID-37/FM-09 C. SAMSON A. FIROBEN R. AURIEMMA N. BENECH

3 PAGE : 3 / 63 TABLE OF CONTENTS 1. INTRODUCTION PURPOSE OF THE DOCUMENT DOCUMENT STRUCTURE DOCUMENTATIONS AND GLOSSARY INSTRUMENT PROCESSING FACILITY CONTEXT EXTERNAL INTERFACES DPC IDP INTERFACE DPC / IDP-SC or OLQC-SC common interfaces DPC / IDP-SC interfaces for L0c processing DPC / IDP-SC interfaces for L1A/B radiometric processing and L1A formatting DPC / IDP-SC interfaces for L1B geometric processing and formatting DPC / IDP-SC interfaces for L1C processing DPC / OLQC-SC interface INTERNAL INTERFACES INTERNAL INTERFACES LIST IDP-ORCHESTRATOR / IDP-SC -SC INTERFACES IDP-ORCHESTRATOR / IPF TASK TABLE INTERFACE DECOMPRESSION CFI INTERFACES OLQC-SC/AMALFI INTERFACES IDP-SC/JP2K INTERFACE INTERFACES DEFINITION EXTERNAL INTERFACES DEFINITION Name: DEM to IDP Name: DPC - IPF control Name: DPC - IPF monitoring Name: ECMWF AuxData to IDP Name: GIPP to IDP Name: GIPP to OLQC Name: GRI to IDP Name: IERS AuxData to IDP Name: IPU to IDP Name: IPU to OLQC Name: OLQC Report to DPC Name: POD Product to IDP (Contingency) Name: Processed IPU from IDP Name: Quality Annotated IPU from OLQC FILE NAMING CONVENTIONS STANDARDS... 61

4 PAGE : 4 / 63 Table of Figures FIGURE 1: IPF IN THE FRAMEWORK OF PRODUCTION SERVICES... 9 FIGURE 2: IDP-SC AND OLQC-SC INTERFACE WITH DPC FIGURE 3: IPF INTERFACES FOR THE STAND-ALONE CONFIGURATION Table of Tables ERREUR! AUCUNE ENTREE DE TABLE D'ILLUSTRATION N'A ETE TROUVEE.

5 PAGE : 5 / 63

6 PAGE : 6 / INTRODUCTION 1.1 Purpose of the document This document provides the interfaces description of the Instrument Processing Facility (IPF). 1.2 Document Structure This document is structured as follows: Chapter 1: Chapter 2: Chapter 3: Chapter 4: Chapter 5: Provides the current introduction, describing the scope and the structure of the document, and the list of applicable and reference documents; Describes the environment of Instrument Processing Facility. Provides the Instrument Processing Facility external interfaces. Provides the Instrument Processing Facility internal interfaces. Details the definition of interfaces. 1.3 Documentations and Glossary Acronyms used in the documentation are defined in S2 PDGS Glossary & definitions Document [S2-PDGS-TAS-DI-CMS-GLODEF] The list of Applicable and Reference documents is defined in the following tables: Applicable Documents Reflabel Reference Version Date Title CORE-BPDP- SOW-IPF S2-PDGS-TAS-DI-BP- SOW /04/2012 Statement of Work for S2 PDGS IPF Project PSD S2-PDGS-TAS-DI- PSD /04/2012 Product Specification Document Reference Documents Reflabel Reference Version Date Title CCTS-IPF S2-PDGS-TAS-DI-BPDP- CCTS-IPF /04/2012 Instrument Processing Facility Requirement Specifications

7 PAGE : 7 / 63 Reflabel Reference Version Date Title SMICD NRTPOD- ICD S2-PDGS-TAS-DI-ICD- MICD GMES-GSEG-EOPG-IC /03/2012 Master Control Document (MICD) 0.1 draft 25/03/2011 Sentinel-2 Core PDGS NRT POD ICD GRI-TN POD-FFS GMES-GSEG-EOPG-TN GMES-GSEG-EOPG-FS draft 03/12/2010 Sentinel-2 Global Reference Images Generation GMES Sentinel Precise Orbit Determination (POD) /02/2011 Service: OFL POD Service and NRT POD Facility File Format Specifications System DEM (GLOBE, filtered SRTM) GPP-DEM GS2-IF-GSGP-70-CNES /03/2010 content and format EOFFS- PDGS GMES-GSEG-EOPG-TN Earth Observation GS File Format Standard Tailoring /02/2011 for the Sentinel Missions PDGS GML Application schema for Earth Observation HMA-GML OGC r /06/2007 products SAFE-TN GMESPH-ACS-TEC- TNO24-E GMES Products Harmonisation SAFE Implementation : /12/2010 Sentinel2 Support SAFE-SPEC GAEL-P264-DOC /07/2011 Sentinel Standard Archive Format for Europe GEN- PDGSIPF GMES-GSEG-EOPG-TN /09/2009 GMES Generic PDGS-IPF Specifications AMALFI- SUM GAEL-P264-SUM /2011 Amalfi User Manual DRB-SUM GAEL-P243-DOC /09/2008 Data Request Broker DRB API Handbook TDS-TN GPP-TN-DLR-S /09/11 Test Data Specifications MDS- SUM- MRCPBG MAG-MRCPBG-MIMU- 01-LAN /11/11 MRCPBG v9.0 installation instructions and user manual

8 PAGE : 8 / INSTRUMENT PROCESSING FACILITY CONTEXT The Level-0 and Level-1 Instrument Processing Facility (IPF) corresponds to a set of data processing software elements fulfilling the requirements of the Instrument Data Processing (IDP) function of the PDGS associated to MSI level-0 and Level-1 data processing. The IPF also contains a set of essential quality checks performed on each product generated by the IDP thanks to the implementation of the On Line Quality Control (OLQC) function. In the operational configuration (hereafter referred to as DPC-driven mode), the PDGS Data Processing Control (DPC) component is in charge of performing the IDP function by orchestrating a set of Instrument Data Processing Software Components (IDP-SC) in workflow in order to generate the Level-0c up to Level-1C products. The DPC is also responsible of product quality checks by calling the OLQC Software Component OLQC-SC in the production workflows. The main goal of the IPF developments is to implement the IDP and OLQC functions. These developments will be integrated by the PDGS Prime Contractor within the DPC environment. In order to test the complete workflow, the IPF also includes the development of a specific software, the "IDP-Orchestrator", that allows to test the end-to-end processing in isolation from the DPC. The IDP-Orchestrator software component will implement an end-to-end processing in a simplified (e.g. not fully optimized in term of processing timeline compared to the DPC environment configuration) workflow triggering all IDP-SC and OLQC-SC in a logical sequence. The detailed description of IPF software components can be found in [CCTS-IPF], the following sections are focusing on detailing the set of IPF external and internal interfaces.

9 PAGE : 9 / 63 Production Services <DPC> DPC orchestrator Instrument Processing Functionality <IPF> IDP Orchestrator manage manage manage manage <DPC> Data Exchange Manager <IDP> Hosted Processing <IDP> Telemetry Processing <IDP> Image Processing execute execute launch launch <IPF> IPF Hosted Processing <IAS> <IAS> HP-SC HP-IAS <IAS> HP-IAS use use <IPF <IDP> Best IDP-SC Practice> PDGS-IAS use use <OLQC> OLQC-SC use <CFI> DFEP <CFI> S2_WICOM DECOMPRESSION <COTS> JP2K COMPRESSOR <CFI> AMALFI <CFI> S2_WICOM DECOMPRESSION <IPF> Figure 1: IPF in the framework of Production Services

10 PAGE : 10 / EXTERNAL INTERFACES As shown on Figure 1, IPF external interfaces are limited to IDP-SC and OLQC-SC interfaces with the DPC for use in the DPC-driven mode. These interfaces are the one that shall be used by the DPC to directly run the IDP-SC or OLQC- SC in the nominal configuration (DPC-driven automatic configuration). Note that before their integration into the Production Service (DPC interfacing), the IDP-SC and OLQC-SC shall be run by the IDP-Orchestrator on a similar way, but in this configuration such interfaces are considered as internal. All other interfaces are therefore considered as IPF internal interfaces. 3.1 DPC IDP The table hereafter lists these interfaces: I/F Name From To Job Order DPC IDP-SC / OLQC-SC Processing Configuration DPC IDP-SC / OLQC-SC Start/Stop DPC IDP-SC / OLQC-SC Auxiliary data DPC IDP-SC / OLQC-SC Ancillary data DPC IDP-SC Input Processing Unit DPC IDP-SC / OLQC-SC Output Processing Unit IDP-SC / OLQC-SC DPC Logging IDP-SC / OLQC-SC DPC Product Report IDP-SC / OLQC-SC DPC Exit Code IDP-SC / OLQC-SC DPC Data exchange repository all all Table 1: List of interfaces between DPC and IDP-SC / OLQC-SC These interfaces with DPC may be represented in the following way:

11 PAGE : 11 / 63 L0 data L0c (reprocessing) DPC Job Order Processing Configuration Start/Stop Logging Product Report Exit Code Ancillary data Auxiliary data Input PU IDP-SC IDP-SC IDP-SC or OLQC-SC Ouptut PU L0c/L1A/L1B/L1C Products (inspected by OLQC) Aux/Anc data IPF Workflow PDIs Figure 2: IDP-SC and OLQC-SC interface with DPC

12 PAGE : 12 / DPC / IDP-SC or OLQC-SC common interfaces Job Order This interface is used by the DPC to launch an IDP-SC or the OLQC-SC, referred to as SC. The Job Order file is generated by the DPC. A job order XML file is associated to each SC. The naming convention is Job Order_<order_id>.xml where order_id is a unique integer ID associated to this production order. The Job Order contains: The SC name and version The list of input files and pathname which is a sub-set of (depending on the SC): Auxiliary data Ancillary data Input Processing Unit files (Image data, Metadata, Masks) Processing Configuration (TBD) The list of output files and pathname which is a sub-set of (depending on the SC): Output Processing Unit files (Image data, Metadata, Masks) Product Report file The settings for a trace mode through (Breakpoints): Breakpoint enabling List of breakpoint files A complete XSD schema of the Job Order file is provided as a separate file. Note: in DPC driven mode, Task Tables are never used. Only the Job Order interface is used. A naming convention will be provided by the PDGS Prime Contractor to identify the various input and output data in Job order interface.

13 PAGE : 13 / Processing Configuration This interface is an XML file used by the DPC to configure an IDP-SC or the OQLC-SC. The set of configurations is made of any processing options and/or algorithmic performance for each SC that is not already in the Auxiliary GIPP file. Typical examples of these switches are: performance options (e.g. maximum RAM size to be used by a given IDP-SC) Start/Stop This interface is used by the DPC to start/stop the execution of an IDP-SC or OQLC-SC (hereafter referred to as Job). The Start interface consists in executing a Job through a command line with the related Job Order as an argument. The Job Order is the only argument of the command line used to launch each IPD-SC or OLQC-SC. The Stop interface allows to stop the execution of a Job with a killing signal (kill -2). In this case, the IDP-SC shall: send a log message notifying the end on kill, terminate the execution of the report in a clean way and exits with a particular return code Auxiliary Data Input All auxiliary input data that shall be ingested by an IDP-SC or OLQC-SC are listed in its Job Order. The set of Auxiliary data is: The Ground Image Processing Parameters (GIPP) corresponding to a set of XML files associated to a processing component (i.e. IDP/OLQC-SC) to define a set of parameters and their values. A GIPP file is associated to a validity period since the parameters can be tuned during the PDGS lifetime. The Digital Elevation Model (DEM) is made of binary files, tiles, covering the Earth Globe (up to certain latitudes). For Shuttle Radar Topography Mission (SRTM) DEM, the files are in dted format. The Global Reference Image (GRI) [GRI-TN] is a set of Sentinel-2 mono-spectral Level-1B products (granules, metadata) covering all land regions within the acquisition plan. The GRI is used during geometric processing to improve the geo-location accuracy and to reach the absolute geo-location accuracy and multi-temporal co registration requirements. Ozone, surface pressure and water vapour data are required for Level-1C processing. These data are published by the European Centre for Medium-Range Weather Forecasts (ECMWF). The data are GRIdded Binary format GRIB described at

14 PAGE : 14 / 63 The International Earth Rotation & Reference Systems service (IERS) is publishing daily ASCII TXT data bulletins about Earth orientation and Terrestrial reference system (Earth Pole position, UT1-UTC,). These data are required for the computation of the geometrical model The OLQC-SC does not need any Ancillary Data as an input. All Ancillary input data that shall be ingested by an IDP-SC are listed in the relevant Job Order. The Ancillary data are made of a set of files for System Ancillary Data (observation mode...) Instrument Ancillary Data (compression ratio, acquisition datation...) Satellite Ancillary Data (orbit, position) Input Precise Orbit Determination POD data (optional: if the attitude information is not matching the expected accuracy) The Ancillary data is contained in a XML file: directly issued from the Front-End-Processing or contained in the metadata XML file Input Processing Units All the input PU files that shall be ingested by an IDP-SC or OLQC-SC are listed in the relevant Job Order. The input PU is made of the following files (or sub-set of files, depending on IDP-SC): A set of image files which can be: o On-board compressed binary files (up to L0c) o ENVI format images (a "flat binary file" and a small associated ASCII (text) header file, see o JP2K compressed images (QuickLook images in case of reprocessing) A set of XML Metadata files A set of GML Mask files A naming convention will be provided by the PDGS Prime Contractor to identify the various input and output data files.

15 PAGE : 15 / Output Processing Units All the output PU files that shall be issued by an IDP-SC or OLQC-SC are listed in the relevant Job Order. The output PU is made of the following files (or sub-set of files, depending on IDP-SC): A set of image files which can be: o ENVI format images (a "flat binary file" and a small associated ASCII (text) header file, see o JP2K compressed images A set of XML Metadata files A set of GML Mask files A naming convention will be provided by the PDGS Prime Contractor to identify the various input and output data files Logging The Logging interface allows to monitor the status of the running IDP-SC/OLQC-SC through a set of messages sent to the DPC. The DPC is able to analyze the messages and possibly route them to the S2-PDGS M&C, depending on severity. Logging messages are syslog style ASCII strings, variable length, NL terminated. The messages shall allow monitoring the events (DEBUG, INFO), warnings (WARNING) and health status (STATUS) and are sent on stdout, except errors (ALARM) and progress messages (PROGRESS) that are sent to stderr. The message format consists of sub-strings fields separated by a blank character. The full description is given in the next table: Field Format Date and Time 26 characters, in the format yyyy-mm-ddthh:mm:ss.nnnnnn where the dash,colon, period and T characters are sub-field separators, and the sub-field meaning is as follows yyyy year : 4 digits MM month : 2 digits, left padded with zeros dd day : 2 digits, left padded with zeros hh hours : 2 digits, left padded with zeros mm minutes : 2 digits, left padded with zeros ss seconds : 2 digits, left padded with zeros nnnnnn microseconds : 6 digits, right padded with Node Name variable length alphanumeric string (no whitespace characters allowed) zeros The node name to be put in the message shall be the

16 PAGE : 16 / 63 Field Format string retrieved through the gethostname system call IDP-SC/OLQC-SC Name variable length alphanumeric string This field identifies the IDP- (no whitespace characters allowed) SC or OLQC-SC IDP-SC/OLQC-SC Version 5 characters, in the format nn.nn The embedded period is included in the count, and must be present) PID 12 characters (including square brackets) in the format [nnnnnnnnnn] This field specifies the system level process id of the processor, obtained through the getpid system call Header Separator 1 colon character : No space shall be inserted between the PID and the separator; Message Type [<type>] (square brackets are mandatory) This field identifies the type of message being issued which can be one of the following: ALARM: critical failure WARNING: some failure but not critical INFO: simple information DEBUG: simple information for developers, available only for debug when this logging mode is activated PROGRESS: particular information messages indicating processing completion progress, with % indication (0% at IDP-SC or OLQC-SC start, 100% at IDP-SC or OLQC-SC successful completion) STATUS: working status notification (periodically every n minutes with n configurable) Other TBD Message Text (for ALARM, variable length string, no restriction, This field contains the WARNING, INFO, NL-terminated (unix-style) descriptive free text of the DEBUG, PROGRESS) message itself Status Text (for STATUS) <status_string> This field contains the component status, which can be one of the following: ON: working properly OFF: shut down (if relevant) FAILURE: some critical failure (reasons shall be notified to operator through proper ALARM messages)

17 PAGE : 17 / 63 Field Format DEGRADED: some failure, and is working in degraded way Other TBD Table 2: Logging format A typical example of log entry is shown below (ASCII String) T14:02: IPFS2 RESAMPLE [ ]:[INFO] Processor starting. Config file is /home/resamples2/config.xml Product Report This interface is used to generate an XML report file at the end of each IDP-SC or OLQC-SC execution. The path and filename of the Product Report are defined in the Job Order file. The full content of the Product Report file has to be tailored for each IDP-SC or OLQC-SC but it shall at least contain: The name and version of the IDP/OLQC-SC The messages of the Logging (optional, configurable according to log severity) Self-explanatory information that can help identifying the status of the main processing steps, to be defined later for every IDP-SC according to image quality mission performance assessment needs The Job Order file An XSD schema of a Report file is provided as a separate file Exit Code All the IDP-SC or OLQC-SC shall return an exit code through a return statement at the end of the main function for instance, or through a call to the exit system call. The exit code values are listed in the table below: Code Definition 0 OK The IDP-SC/ or OLQC-SC has been succefully completed 1-10 WARNING Reserved exit codes to be defined later in coordination with PDGS Prime Contractor INCOMPLETE Recoverable errors have been encountered

18 PAGE : 18 / 63 Code Definition 128 FAILURE Any other unrecoverable errors Table 3: Exit codes If a child process is launched by the main process started by DPC, the exit code of the child process shall be propagated to the main process Data exchange repository All the files exchanged between DPC and every IDP-SC or OLQC-SC (job order files, configuration files, input processing files, output processing files, reports, etc), are available in a direct access file tree shared between DPC and IPF components. This tree is created by DPC before IDP-SC and OLQC-SC launch, for files and subdirectories read, write and delete. IPF components temporary files will be stored in a dedicated subdirectory created by DPC before launch. After IDP-SC and OLQC-SC completion, the deletion or further use of files and working directories is managed by DPC DPC / IDP-SC interfaces for L0c processing The following paragraphs present the interfaces of each IDP-SC in charge of L0c processing INIT_LOC_L0 interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The XML GIPP files : o GS2_DATATION_PARAMETERS.xml o GS2_INIT_LOC_INV_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml GLOBE DEM files The IERS data bulletin at the date of ISP acquisition. Either SAD data or read from Metadata at datastrip level (ephemeris, attitudes, datation model, ) datastrip xml file for each granule of the processed datastrip, a granule xml file Output Processing Units Metadata : datastrip xml files (input updating) granule xml files (input updating) Logging Cf

19 PAGE : 19 / 63 Product Report Cf Exit Code Cf QL_GEO interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The XML GIPP files : o GS2_LR_EXTRACTION_PARAMETERS.xml o GS2_INIT_LOC_INV_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml GLOBE DEM. The IERS data bulletin at the date of ISP acquisition. Read from Metadata at datastrip level (ephemeris, attitudes, datation model, ) datastrip xml file for each granule of the processed datastrip, a granule xml file ATF (decompressed LR images; one by band and detector for each datablock) Output Processing Units Metadata : granule xml files (input update) Logging Cf Product Report Cf Exit Code Cf quicklook images (one by band and detector for each datablock) QL_CLOUD_MASK interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input In the NOMINAL scenario, the set of required Auxiliary data is: The XML GIPP files : o GS2_INIT_LOC_INV_PARAMETERS.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2_CLOUD_INV_PARAMETERS.xml

20 PAGE : 20 / 63 o GS2_INTER_DETECTOR_PARAMETERS.XML In the REPROCESSING scenario, the set of required Auxiliary data is: The XML GIPP files : o GS2_INIT_LOC_INV_PARAMETERS.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2_CLOUD_INV_PARAMETERS.xml Read from Metadata at datastrip level (ephemeris, attitudes, datation model, ) datastrip xml file In the NOMINAL scenario, the set of required Data input PU is: quicklook images (one by band and detector for each datablock) In the REPROCESSING scenario, the set of required Data input PU is: quicklook images (one by band for each datablock) Output Processing Units Metadata : datastrip xml file (input update) In the NOMINAL scenario, the set of required Data input PU is: concatenated QuickLook images (one file by band and ATF) cloud mask vector (one file by ATF) In the REPROCESSING scenario, the set of required Data input PU is: cloud mask vector Logging Cf Product Report Cf Exit Code Cf FORMAT_IMG(QL JP2000) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP: o GS2_JP2K_PARAM.xml: specific processing parameters (e.g. compression parameters) None datastrip xml file Output Processing Units Logging Cf Product Report Cf Exit Code Cf concatenated QuickLook images (one file by band and input datablock) concatenated QuickLook images (one JPEG2000 file by band and by input datablock)

21 PAGE : 21 / FORMAT_ISP interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None (TBC) None datastrip xml file granule (for each granule) xml files Image Source Packets (gathered by band and detector for each datablock) Output Processing Units Metadata : granule xml file (input update) SAFE packaged ISP (generated for each granule) Logging Cf Product Report Cf Exit Code Cf FORMAT_METADATA(GR-L0c) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None (TBC) Taken from Input DS metadata (TBC) datastrip xml file granule (for each granule) xml files cloud mask vector (for the whole datastrip, by ATF) SAFE packaged ISP for each granule Output Processing Units Metadata : L0c Metadata at granule level in SAFE format (input update) SAFE formatted granule Logging Cf Product Report Cf Exit Code Cf

22 PAGE : 22 / FORMAT_METADATA(DS-L0c) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The XML GIPP files : GS2_ABSOLUTE_CALIBRATION.xml GS2_ CLOUD_INV _PARAMETERS.xml GS2_DATATION_PARAMETERS.xml GS2_INIT_LOC_INV_PARAMETERS.xml GS2_LR_EXTRACTION_PARAMETERS.xml GS2_SPACECRAFT_MODEL_PARAMETERS.xml GS2_VIEWING_DIRECTIONS.xml IERS bulletin DEM: reference to coarse DEM (Globe) used in L0 processing ASP : Ancillary Source Packet datastrip xml file quicklook images Output Processing Units Metadata : datastrip xml file (input update) SAFE formatted datastrip Logging Cf Product Report Cf Exit Code Cf DPC / IDP-SC interfaces for L1A/B radiometric processing and L1A formatting The following paragraphs present the interfaces of each IDP-SC in charge of L1A/B radiometric processing and L1A formatting UNFORMAT_SAFE(GR) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None (TBC) None Input Processing Units SAFE formatted granule Output Processing Units SAFE unformatted granule (IPF internal format)

23 PAGE : 23 / 63 Set of ISP (for all available bands) for each processed granule Metadata : granule xml file (IPF internal format) Logging Cf Product Report Cf Exit Code Cf UNFORMAT_SAFE(DS) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None (TBC) Ancillary Source Packet (ASP) Input Processing Units SAFE formatted datastrip Output Processing Units Metadata : datastrip xml files Quicklook JPEG2000 images Logging Cf Product Report Cf Exit Code Cf UPDATE_LOC interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: IERS bulletin Coarse DEM (GLOBE) GIPP : o GS2_DATATION_PARAMETERS.xml o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_SPACECRAFT_MODEL.xml o GS2_VIEWING_DIRECTIONS.xml POD data (degraded case only) Exogenous Datation model (degraded case only) Datation information at ISP level (degraded case only) SAD data (reprocessing only) Otherwise read from Metadata at datastrip level (ephemeris, attitudes, datation model, )

24 PAGE : 24 / 63 datastrip xml file for each granule of the processed datastrip, a granule xml file Output Processing Units Metadata : datastrip xml file (update) for each granule of the processed datastrip, a granule xml file (update) Logging Cf Product Report Cf Exit Code Cf QL_DECOMP interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP: o GS2_DECOMP_PARAM.xml : DECOMP specific processing parameters None Input Processing Units Full swath JPEG2000 compressed QuickLook images (one file by band and by datablock) Output Processing Units Metadata : Logging Cf Product Report Cf Exit Code Cf datastrip xml file Full swath concatenated QuickLook images (one file by band and datablock) QL_CLOUD_MASK interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: The XML GIPP files : o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2_CLOUD_INV_PARAMETERS.xml Read from Metadata at datastrip level (ephemeris, attitudes, datation model, )

25 PAGE : 25 / 63 datastrip xml files quicklook images (one by band and detector for each datablock) Output Processing Units Metadata : datastrip xml files (input update) concatenated QuickLook images (one file by band and ATF) cloud mask vector (one file by ATF) Logging Cf Product Report Cf Exit Code Cf INIT_LOC_L1 interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP : o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2-CLOUD_INV_PARAMETERS.xml Coarse DEM (GLOBE) Read from Metadata at datastrip level datastrip xml files granule xml files for each granule of the processed detectors Coarse Cloud Mask in QuickLook geometry Output Processing Units Metadata : granule xml files (update) ATF, for each band of each processed detector : o Detector footprint o Cloud mask in Focal plan geometry o Technical masks (ancillary data) Logging Cf Product Report Cf Exit Code Cf

26 PAGE : 26 / DECOMP interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP: o GS2_DECOMP_PARAM.xml : DECOMP specific processing parameters None datastrip xml files granule files for each granule of the processed ATF Image Source Packets (gathered by band for each granule) Output Processing Units Metadata : datastrip xml files (update) granule files for each granule of the processed ATF (update) Decompressed images (one file by band) Mission Data Quality Masks (degraded and lost) Logging Cf Product Report Cf Exit Code Cf RADIO_AB interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP : o GS2_RADIO2_PARAMETERS.xml o GS2_RADIO2_REARRANGEMENT.xml o GS2_RADIO2_EQUALIZATION_ONBOARD.xml o GS2_RADIO2_EQUALIZATION_ONGROUND.xml o GS2_BLIND_PIXELS.xml o GS2_RADIO2_SWIR_ARRANGEMENT.xml o GS2_RADIO2_CROSSTALK_CORRECTION.xml o GS2_RADIO2_DEFECTIVE_PIXELS.xml o GS2_RADIO2_DECONVOLUTION_FILTER.xml o GS2_RADIO2_INSTRUMENT_NOISE_MODEL.xml o GS2_RADIO2_WAVELET_FILTERS.xml o GS2_RADIO2_L2_NORM_COEFFICIENTS.xml o GS2_RADIO2_DENOISING_THRESHOLDs.xml o GS2_RADIO2_BINNING.xml Read from Metadata at datastrip level

27 PAGE : 27 / 63 datastrip xml files On-board decompressed images (all available bands) Output Processing Units Metadata : datastrip xml files (update) Images without deconvolution and denoising scenario : ATF images files (one file by band) Or a set of granule images files (one file by band and by granule) Logging Cf Product Report Cf Exit Code Cf RADIO_FINALIZE interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: GIPP : o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_RADIO2_INSTRUMENT_NOISE_MODEL.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2_MASK2_PARAMETERS.xml A list of ancillary data by ATF datastrip xml files for each detector : for each ATF for each band : o A list of Detector footprint by ATF o A list of Cloud mask in Focal plan geometry by ATF o A list of Technical masks (ancillary data) by ATF o A list of Technical masks (mission data) by ATF o A list of Radiometric masks by ATF Output Processing Units Metadata : datastrip xml files (update) Logging Cf Product Report Cf for each band of each processed detector) o Detector footprint o Cloud mask in Focal plan geometry o Technical masks o Radiometric masks

28 PAGE : 28 / 63 Exit Code Cf FORMAT_METADATA (GR-L1A) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None Read from Metadata at datastrip level datastrip xml files granule xml file for each granule ATF : o List of L1A radiometric masks (defective pixels, saturated pixels, No_Data pixels) o List of Technical masks (mission data quality masks, ancillary data quality masks) o List of Cloud masks Output Processing Units Metadata : granule xml file for each granule (update) Logging Cf Product Report Cf Exit Code Cf Pixel level Quality indicators (masks at granule level) o L1A radiometric masks, o Coarse cloud masks, o Technical masks FORMAT_METADATA (DS-L1A) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_ABSOLUTE_CALIBRATION.xml o GS2_BLIND_PIXELS.xml o GS2_CLOUD_INV _PARAMETERS.xml o GS2_DATATION_PARAMETERS.xml o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_MASK2_PARAMETERS.xml o GS2_RADIO2_BINNING.xml o GS2_RADIO2_CROSSTALK_CORRECTION.xml o GS2_RADIO2_DECONVOLUTION_FILTER.xml

29 PAGE : 29 / 63 o GS2_RADIO2_DEFECTIVE_PIXELS.xml o GS2_RADIO2_DENOISING_THRESHOLDs.xml o GS2_RADIO2_EQUALIZATION_ONBOARD.xml o GS2_RADIO2_EQUALIZATION_ONGROUND.xml o GS2_RADIO2_INSTRUMENT_NOISE_MODEL.xml o GS2_RADIO2_L2_NORM_COEFFICIENTS.xml o GS2_RADIO2_PARAMETERS.xml o GS2_RADIO2_REARRANGEMENT.xml o GS2_RADIO2_SWIR_ARRANGEMENT.xml o GS2_RADIO2_WAVELET_FILTERS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml IERS bulletin DEM: reference to coarse DEM (Globe) used in L1A processing None datastrip xml files Output Processing Units Metadata : datastrip xml files (update) Formatted L1A datastrip Logging Cf Product Report Cf Exit Code Cf FORMAT_IMG (L1A_JP2000) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP: o GS2_JP2K_PARAM.xml : specific processing parameters (e.g. compression parameters) None datastrip xml file Output Processing Units Logging Cf Product Report Cf Exit Code Cf L1A images for each band of processed ATF L1A images for each band of each granule of processed ATF for each granule, L1A JPEG2000 compressed image (one file by available band)

30 PAGE : 30 / DPC / IDP-SC interfaces for L1B geometric processing and formatting The following paragraphs present the interfaces of each IDP-SC in charge of L1A/B radiometric processing and L1B geometric processing and formatting GET_GRI interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None None GRI Metadata at datastrip level GRI Metadata at datastrip level Metadata at datastrip level Detector footprint for band used by IMAGE-GRI registration Output Processing Units Metadata : GRI metadata at datastrip level, for each GRI that intercept the datastrip (update) list of GRI that intercept the datastrip Logging Cf Product Report Cf Exit Code Cf UNFORMAT_GRI interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None None Input Processing Units In decompression only scenario : Metadata := o GRI Metadata at datastrip level o JPEG2000 compressed GRI images (one by granule of the processed ATF) In mask aggregate only scenario :

31 PAGE : 31 / 63 Metadata : o GRI Metadata at datastrip level o masks (by granule of the processed detector) Output Processing Units In decompression only scenario : decompressed GRI images (one by granule of the processed ATF) In mask aggregate only scenario : masks Aggregated by detectors Logging Cf Product Report Cf Exit Code Cf INIT_VS_GEO interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input The set of required Auxiliary data is: DEM (SRTM class) GIPP : o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_GEOS2_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REDEFINED.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml Read from metadata at datastrip level Metadata at datastrip level GRI metadata at datastrip level (for Image-GRI registration only) Output Processing Units Virtual Sensor Viewing model Logging Cf Product Report Cf Exit Code Cf RESAMPLE_TO_VS interfaces Job Order Cf

32 PAGE : 32 / 63 Processing Configuration None Start/Stop Cf Auxiliary Data Input DEM (SRTM class) GIPP : o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_GEOS2_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REDEFINED.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml Read from metadata at datastrip level (TBC) Metadata at datastrip level Output Processing Units Logging Cf Product Report Cf Exit Code Cf GRI metadata at datastrip level (for Image-GRI registration only) Radiocorrected Images Images resampled in Virtual Sensor geometry (either Image and GRI or VNIR and SWIR images) Masked area (not to be used area mask) TP_COLLECT interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_GEOS2_PARAMETERS.xml None (TBC) Input Processing Units In Densification of input collection scenario : Images resampled in Virtual Sensor geometry (either Image and GRI or VNIR and SWIR images) List of filtered homologous point (could be empty) Masked area (not to be used area mask) In Automatic scenario : Images resampled in Virtual Sensor geometry (either Image and GRI or VNIR and SWIR images)

33 PAGE : 33 / 63 Masked area (not to be used area mask) Output Processing Units List of homologous tie-points Logging Cf Product Report Cf Exit Code Cf TP_FILTER interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_GEOS2_PARAMETERS.xml None (TBC) Metadata at datastrip level Lists of collected Tie-Points/GCP (one list by input ATF, input ATF combination represent all the detector) Output Processing Units Lists of filtered Tie-Points/GCP (one list by input ATF) Logging Cf Product Report Cf Exit Code Cf SPATIO interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input Precise DEM (SRTM class) GIPP o GS2_GEOS2_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REFINED.xml None (TBC) at datastrip level, xml file Filtered set of Tie-Points Filtered set of Ground Control Points Output Processing Units Metadata : at datastrip level, xml file (update)

34 PAGE : 34 / 63 Logging Cf Product Report Cf Exit Code Cf GEO1B_FINALIZE interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input Precise DEM (SRTM class) GIPP : o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REDEFINED.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml Read from Metadata at datastrip level at datastrip level, xml file Output Processing Units densificated Detector footprint, for each band of each processed detector Logging Cf Product Report Cf Exit Code Cf FORMAT_METADATA (GR-L1B) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input Precise DEM (SRTM class) GIPP : o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REDEFINED.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml Read from Metadata at datastrip level Metadata at datastrip level L1B Metadata at granule level

35 PAGE : 35 / 63 L1A checked metadata at granule level for each granule Technical masks for each granule Cloud masks for each granule Output Processing Units Metadata : Updated L1B Metadata at granule level Logging Cf Product Report Cf Exit Code Cf Pixel level Quality indicators (masks at granule level) o L1B radiometric masks, o Coarse cloud masks, o Technical masks FORMAT_METADATA (DS-L1B) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_ABSOLUTE_CALIBRATION.xml o GS2_BLIND_PIXELS.xml o GS2_CLOUD_INV _PARAMETERS.xml o GS2_DATATION_PARAMETERS.xml o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_GEOS2_PARAMETERS.xml o GS2_INIT_LOC_PROD_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_MASK2_PARAMETERS.xml o GS2_PARAMETERS_TO_BE_REFINED.xml o GS2_RADIO_DATA.xml o GS2_RADIO2_BINNING.xml o GS2_RADIO2_CROSSTALK_CORRECTION.xml o GS2_RADIO2_DECONVOLUTION_FILTER.xml o GS2_RADIO2_DEFECTIVE_PIXELS.xml o GS2_RADIO2_DENOISING_THRESHOLDs.xml o GS2_RADIO2_EQUALIZATION_ONBOARD.xml o GS2_RADIO2_EQUALIZATION_ONGROUND.xml o GS2_RADIO2_INSTRUMENT_NOISE_MODEL.xml o GS2_RADIO2_L2_NORM_COEFFICIENTS.xml o GS2_RADIO2_PARAMETERS.xml o GS2_RADIO2_REARRANGEMENT.xml o GS2_RADIO2_SWIR_ARRANGEMENT.xml o GS2_RADIO2_WAVELET_FILTERS.xml

36 PAGE : 36 / 63 o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml IERS bulletin DEM: reference to coarse DEM (Globe) used in L1A processing DEM: reference to precise DEM (SRTM class) used in L1B processing list of GRI that intercept the datastrip (to be referenced) None (TBC) L1B Metadata at datastrip level L1A checked Metadata at datastrip level Data Densificated Detector footprint Output Processing Units Metadata : Updated L1B Metadata at datastrip level Datastrip footprint Formatted L1B datastrip Logging Cf Product Report Cf Exit Code Cf FORMAT_IMG (L1B_JP2000) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP: o GS2_JP2K_PARAM.xml : specific processing parameters (e.g. compression parameters) None at datastrip level, xml file L1B images (all available bands) Output Processing Units L1B JPEG2000 compressed image (one file by available band) Logging Cf Product Report Cf Exit Code Cf

37 PAGE : 37 / DPC / IDP-SC interfaces for L1C processing The following paragraphs present the interfaces of each IDP-SC in charge of L1C processing GET_TILE_LIST interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_TILINGS2_PARAMETERS.xml None datastrip xml file datastrip footprint Output Processing Units Metadata : datastrip xml file (update) Logging Cf Product Report Cf Exit Code Cf TILE_INIT interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input DEM (DEM quality mask) ECMWF raw data GIPP : o GS2_TILINGS2_PARAMETERS.xml o GS2_RESAMPLES2_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_ABSOLUTE_CALIBRATION.xml o GS2_ECMWF_IMPORT_PARAM.xml : ECMWF processing parameters (ECMWF resampled grid definition) None (TBC) datastrip xml file Output Processing Units Metadata : Creation and updating of metadata at tile level, xml file

38 PAGE : 38 / 63 DEM quality mask ECMWF L1C tile Logging Cf Product Report Cf Exit Code Cf GEN_ORTHO_TOA interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input Precise DEM (SRTM class) GIPP : o GS2_RESAMPLES2_PARAMETERS.xml o GS2_VIEWING_DIRECTIONS.xml o GS2_EARTH_MODEL_PARAMETERS.xml o GS2_GEOMETRICAL_PARAMETERS.xml o GS2_INTER_DETECTOR_PARAMETERS.xml o GS2_SPACECRAFT_MODEL_PARAMETERS.xml o GS2_ABSOLUTE_CALIBRATION.xml Read from metadata at datastrip level datastrip xml file metadata at tile level, xml file Detector footprint (for processed bands) L1B masks (for processed bands) L1B Radiocorrected images (for processed bands) Output Processing Units Detector Masks (for processed bands) L1B projected masks (for processed bands) Satellite incidence angles grid (for processed bands) LookUp Table for reflectance conversion (for processed bands) TOA reflectance images (for processed bands) Logging Cf Product Report Cf Exit Code Cf TILE_FINALIZE interfaces Job Order Cf Processing Configuration None

39 PAGE : 39 / 63 Start/Stop Cf Auxiliary Data Input None None datastrip xml file metadata at tile level, xml files Satellite incidence angles grid (for all available bands) LookUp Table used for reflectance conversion (for all available bands) MSI and ancillary data quality masks in L1C geometry (for all available bands) Output Processing Units Metadata : metadata at tile level, xml files (update) Logging Cf Product Report Cf Exit Code Cf MASK_S2 interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : o GS2_MASK2_PARAMETERS.xml Read from Metadata at datastrip level (ephemeris, attitudes, datation model, ) (TBC) datastrip xml file at tile level, xml files Images in TOA reflectance for 5 bands, for processed tile Output Processing Units Metadata : metadata at tile level, xml files (update) Cloud masks Land/Water masks Logging Cf Product Report Cf Exit Code Cf

40 PAGE : 40 / FORMAT_IMG (L1C_JP2000) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP: o GS2_JP2K_PARAM.xml : specific processing parameters (e.g. compression parameters) Read from Metadata at tile level (footprint, ) at datastrip level, xml file at tile level (for geographic information to be embedded in GML-JP2000), xml files L1C images (all available bands) Output Processing Units Logging Cf Product Report Cf Exit Code Cf For each tile, L1C GML-JPEG2000 compressed image (one file by available band) FORMAT_IMG (PVI & TCI) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP: o GS2_JP2K_PARAM.xml : specific processing parameters (e.g. compression parameters) None at datastrip level, xml file at tile level (for geographic information to be embedded in GML-JP2000), xml files Images in TOA reflectance for 3 bands Output Processing Units Metadata : at tile level, xml files (update) TCI GML-Jpeg2000 file PVI GML-Jpeg2000 file Logging Cf Product Report Cf Exit Code Cf

41 PAGE : 41 / FORMAT_METADATA (TILE - L1C) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input None (TBC) None at datastrip level, xml file at tile level, xml files all files relevant to processed tile (metadata, masks, ) Output Processing Units Metadata : at tile level, xml files (update) Logging Cf Product Report Cf Exit Code Cf FORMAT_METADATA (DS - L1C) interfaces Job Order Cf Processing Configuration None Start/Stop Cf Auxiliary Data Input GIPP : all GIPP used in L1A, L1B and L1C processing IERS bulletin DEM: reference to coarse DEM (Globe) used in L1A processing DEM: reference to precise DEM (SRTM class) used in L1B and L1C processing Reference to the list of GRI used for L1B refining None at datastrip level, xml file Output Processing Units Metadata : at datastrip level, xml file (update) Logging Cf Product Report Cf Exit Code Cf DPC / OLQC-SC interface Job Order Cf

42 PAGE : 42 / 63 Processing Configuration None Start/Stop Cf Auxiliary Data Input An OLQC-GIPP is defined through the XSD file referred to as "olqcgipp.xsd" (provided as a separate file) None Input Processing Units The input PU can be one of the following: A Data Granule (or set of) L0, L1A, L1B,L1C A Data Strip L0, L1A, L1B, L1C A L1B image data An Auxiliary data file (ECMWF data) A TCI or PVI image file Output Processing Units Depending on the number of checklist to be performed per Input processing Unit, several XML reports can be generated (maximum being one for each checklist) Logging Cf and in case of failed status, a log message shall summarize the reason of the failed status and the log message text shall start with the OLQC_RESULT keyword in order to allow the DPC identifying those messages. Product Report Cf Exit Code Cf

43 PAGE : 43 / INTERNAL INTERFACES 4.1 Internal s list IPF internal interfaces the interfaces between IPF components or interfaces with items provided as CFIs for IPF. The internal interfaces are: IDP-Orchestrator interface with IDP-SC and OLQC-SC IDP-SC interface with Decompression CFI software IDP-SC interface with JP2K COTS software OLQC-SC interface with Amalfi CFI software 4.2 IDP-orchestrator / IDP-SC -SC s These interfaces are the one used by IDP-Orchestrator to directly run the every IDP-SC or OLQC- SC individually or a set of chained IDP-SC and OLQC-SC. The Figure 3 presents these interfaces for the stand-alone configuration mode (when IDP-SC and OLQC-SC are not interfaced with the DPC but with the IDP-Orchestrator). In both the stand-alone or DPC-driven mode, these interfaces are partially compliant with GMES Generic PDGS-IPF s defined in [GEN-PDGSIPF].