SLSTR data will be distributed as Product Dissemination Units (2 minutes acquisition products). There would be a need to be able to take two L1B SLTSR PDUs and generate a single SLSTR L1B (i.e., with a single manifest and concatenated datasets)
TDS: 2 L1b SLSLTR PDUs (from ESTEC) and as a backup if not available the PDGS L1B SLSTR delivered with the S3TBX (with the limitation that this product would first need to be cut into two individual files before being re-assembled into a single one).
You say, the tool shall take two PDUs. This requires repeatedly applying it to multiple PDUs if you want to reconstruct full orbit products. Might be better to handle any number of subsequent PDUs.
Is there already a reliable product specification for the PDU format? For SLSTR, we have "Product Data Format Specification - SLSTR, Level 1 & Level 2 Instrument Products", S3IPF.PDS.005, issue 1.6, date 15 May 2014. But it seems not to mention PDUs at all.
TDS: Could you please provide two (or more) PDUs as they will be generated by the PDGS, so that we can account for any peculiarities in the metadata and scan line ordering or possible overlaps.
SLSTR data will be distributed as Product Dissemination Units (2 minutes acquisition products). There would be a need to be able to take two L1B SLTSR PDUs and generate a single SLSTR L1B (i.e., with a single manifest and concatenated datasets)
TDS: 2 L1b SLSLTR PDUs (from ESTEC) and as a backup if not available the PDGS L1B SLSTR delivered with the S3TBX (with the limitation that this product would first need to be cut into two individual files before being re-assembled into a single one).