doc.: td-gs-ps-3028 · the following documents are fully applicable together with this document....

Doc.: TD-GS-PS-3028 Issue: 1.2 Date: 27.01.2012 Page: 2 of 192

Remote Sensing Technology Institute

TanDEM-X Ground Segment

- TanDEM-X Experimental Product Description - - public -

DOCUMENT PREPARATION

The document on hand was prepared with contributions from the personnel listed below:

N. Name Organizational Unit Remote Sensing Technology Institute (DLR-IMF)

T. Fritz IMF SV

S. Duque IMF SV

Microwaves and Radar Institute (DLR-HR) B. Bräutigam HR

J. L. Bueso Bello HR

DISTRIBUTION

This document is publically available.

Custodian of this document is: T. Fritz





DOCUMENT CHANGE CONTROL

This document is under configuration control.

Issue Date Chapter Changes 1.0 Draft 05.03.2008 All First issue – Draft only

1.1 Draft 07.12.2010 All In-Comissioning Phase Version. Product format and ITP output consolidated.

1.2 27.01.2012 All First public release. Several editorials and adaptations. Product portfolio extended; “additional” modes included. Performance parameters and beam tables added.

Note: Verify that this is the correct revision before use. Check the document server for the latest version. Hardcopies of distributed documents are not updated automatically.

.





TABLE OF CONTENTS

1 Introduction................................................................................................................... 6 1.1 Purpose ...................................................................................................................... 6 1.2 Scope......................................................................................................................... 6

2 References ..................................................................................................................... 7 2.1 Applicable references.................................................................................................. 7 2.2 Informative references ................................................................................................ 7

3 TanDEM-X Operational Modes and Products Overview............................................. 8 3.1 Overview.................................................................................................................... 8 3.2 Operational Modes..................................................................................................... 8 3.3 Operational Product Generation ............................................................................... 11

4 Product Characteristics................................................................................................ 15 4.1 General Characteristics ............................................................................................. 15 4.2 Coverage and Product Location ................................................................................ 15 4.3 Radiometric Quality .................................................................................................. 16 4.4 Geometric Quality .................................................................................................... 16

5 Experimental Product Modes and Acquisition Performance.................................... 18 5.1 Polarization Channel Combinations........................................................................... 18 5.2 Elevation Beams Definition........................................................................................ 20 5.3 Performance Parameters ........................................................................................... 21

5.3.1 Range Bandwidth in Stripmap Modes ............................................................................. 21 5.3.2 PRF Range and Values..................................................................................................... 23 5.3.3 Processing Bandwidth ..................................................................................................... 23

5.4 Special TanDEM-X Features....................................................................................... 24 5.4.1 Bistatic Calibration of Interferometer............................................................................... 24 5.4.2 Synchronization Link ....................................................................................................... 24 5.4.3 Exclusion Zones............................................................................................................... 24

5.5 Image Characterization of TanDEM-X Experimental Products..................................... 25 5.5.1 PSLR and ISLR ................................................................................................................. 25 5.5.2 Azimuth Resolution......................................................................................................... 25 5.5.3 Range Resolution ............................................................................................................ 26 5.5.4 Ground Swath Width...................................................................................................... 27 5.5.5 Noise Equivalent Sigma Zero ........................................................................................... 27

6 CoSSC Product Structure and Format......................................................................... 28 6.1 Structure .................................................................................................................. 28 6.2 CoSSC Annotation ................................................................................................... 31

6.2.1 Base Parameter Classes ................................................................................................... 32 6.3 CoSSC Components ................................................................................................. 35

6.3.1 Additional Annotation Files ............................................................................................. 35 6.3.2 Auxiliary Raster Files........................................................................................................ 35 6.3.3 Preview Files ................................................................................................................... 35 6.3.4 Common Image Data...................................................................................................... 37





6.3.5 Data Components........................................................................................................... 37 6.4 Binary Image Data Format......................................................................................... 37

6.4.1 CoSAR Files..................................................................................................................... 37 6.4.2 Image Raster files............................................................................................................ 38

7 CoSSC XML Schema Definition................................................................................... 39

A. Annex......................................................................................................................... 185 A.1 Experimental Product Beam Definition Parameters .................................................. 185 A.2 SM single polarization elevation beams................................................................... 185 A.3 SM dual polarization elevation beams ..................................................................... 186 A.4 tanDEM elevation beams ........................................................................................ 188 A.5 SL/HS elevation beams (single and dual polarization) ............................................... 189





1 Introduction

1.1 Purpose

This document gives an overview of the variety of experimental products generated from TanDEM-X acquisitions. Experimental TanDEM-X products are generated from acquisitions in a mode which belongs to a subset of the possible instrument and acquisition mode combinations. This subset defines the operational modes of TanDEM-X. A further reduced set of possible TanDEM-X acquisition modes is used for DEM product generation which are the basic products of the TanDEM-X mission specified in the DEM Product Specification document.

Data from acquisition modes beyond the variety of operational modes are not routinely processed to higher level products by the TanDEM-X ground segment. The respective modes are called experimental modes.

The document provides a description of the basic characteristics, the structure, the basics of the format and the design rationale for the operationally available experimental products. It also includes some products of modes which were not part of the initial product portfolio and are not operationally released as experimental products. Some of them are however commanded and generated pre-operationally using the operational processes. These variants might become available to the users on best effort basis and/or in later mission phases.

The performance parameters of experimental products are not specified. Unlike for TerraSAR-X basic products or the TanDEM-X DEM acquisitions, the product performance of each individual TanDEM-X experimental product may vary (e.g. in terms of swath coverage, geometric and radiometric resolution), depending on the actual acquisition conditions and processor settings adapted to the encountered acquisition performance (bistatic SNR, sync pulse performance, …). Hence the product parameters are characterized only in this document.

1.2 Scope

This document will be made available to the user community which has access to experimental products generated by the TanDEM-X ground segment.

It thus addresses SAR experts and does hence not further introduce basic SAR / InSAR principles or instrument and mission characteristics besides those relevant for the classification of product types.

It is out of scope of this document to detail product ordering, user access to archives, availability of specific types of data products and delivery mechanisms. With respect to these issues, please refer to [I3] & [I4] and contact the science coordination team.





2 References

2.1 Applicable references

The following documents are fully applicable together with this document. Document ID Document Title Issue

[A1] TD-GS-DD-0018

TanDEM-X GS Design Document 2.3

2.2 Informative references

The following documents, though not formally part of this document, amplify or clarify its content. Document ID Document Title Issue

[I1] TX-GS-DD-3302

TerraSAR-X Basic Product Specification Document 1.7

[I2] TX-GS-DD-3307

TerraSAR-X Level 1b Product Format Specification 1.3

[I3] TD-GS-UM0115

TanDEM-X Science Service System Manual 1.0

[I4] TD-GS-PL-0069

TanDEM-X Science Plan 1.0





3 TanDEM-X Operational Modes and Products Overview

3.1 Overview

Experimental TanDEM-X products are generated from acquisitions in a mode which belongs to a subset of the possible combinations of imaging mode, polarization mode, cooperative mode and formation geometry. This subset defines the operational modes of TanDEM-X. A further reduced set of possible TanDEM-X acquisition modes is used for DEM product generation which are the basic products of the TanDEM-X mission specified in the DEM Product Specification document.

Data from acquisition modes beyond the variety of operational modes are not routinely processed to higher level products by the TanDEM-X ground segment. The respective modes are called experimental modes and those data are archived as raw data only.

Experimental products are the result of special scientific SAR experiments based on new techniques which are possible due to the innovative configuration given by the TanDEM-X mission. The ordering of such kind of products is coordinated and executed by a SAR expert team. Due to the nature of the TanDEM-X mission which is based on a systematic global acquisition strategy, these experiments are to be placed in specific phases with appropriate formation geometries. As a consequence, the data takes are systematically and data driven processed by one unified operational processing system to archive products. This ensures a uniform product quality and performance. The generated products are then available to the users as delivery products from the established product catalogue (i.e. via EOWEB catalogue orders).

Additionally to the experimental products, the CoSSC products from DEM acquisitions which are intended as processing chain internal, intermediate products which shall support the InSAR processing in later mission phases, are also archived and formatted the same way. They are thus identical in terms of product handling (not in performance) for those users which have access to the archive.

3.2 Operational Modes

A TanDEM-X acquisition is a coordinated SAR instrument data take by both satellites of the TanDEM-X mission (the TerraSAR-X satellite TSX and the TanDEM-X satellite TDX). During such an acquisition, each satellite is operated in instrument modes similar to those for the TerraSAR-X mission.

A further dimension is defined by the degree of cooperation of both SAR instruments – acting as one coordinated & synchronized SAR instrument or just two separate ones. TanDEM-X product characteristics like focussing quality (resolution, …) and radiometry are thus ruled by the effectiveness of this cooperation.

The complexity is increased by the influence of the formation geometry of the two satellites at the time of acquisition (along- and across track separation / effective baselines) which turns TanDEM-X into one interferometric SAR instrument with different sensitivities to observables on ground as e.g. height, movements, de-correlation.

The Fig. 3-1 sketches the 4 determining factors for operational modes and product classification.





Fig. 3-1: Determining factors for operational modes and product classification.

The currently possible modes are thus combinations of the

• Imaging Mode of each instrument: stripmap (SM), spotlight (SL), high-resolution spotlight (HS), ScanSAR (SC) and experimental Dual Receive Antenna (DRA) – ATI and aperture switching

• Polarization Mode of each instrument: Single / Dual and experimental Twin & Quad

• Cooperative Mode of the two Instruments: bistatic, alternating bistatic, pursuit monostatic, none (TS-X mission) & other experimental commandings

• Formation Geometry: small or large along & across track separation / effective baseline

The TanDEM-X mission offers the possibility to operate both satellites in an along-track interferometric configuration where they are ~20 km apart. This configuration allows for pursuit mono-static imaging which is - from a satellites point of view - the same as running a TerraSAR-X mission with both satellites just a few seconds apart taking the same images. This is nevertheless a coordinated TanDEM-X acquisition and a defined cooperative mode different from the not-cooperative TerraSAR-X mission acquisitions (which are in their sense also coordinated in order to prevent interference).

Classified as operational are acquisitions in which both satellites acquire in the same imaging and polarization mode. Additional restrictions e.g. for polarization channel combinations apply. Operational across-track separations are below 4 km. The operational along track separation is below 1 km for bistatic cooperative modes but not restricted for the pursuit monostatic mode. The operational modes are given in the table below:

IM

coop

geo

pol

DEMs

Exp. Product

Exp. Mode





Operational Modes

TanDEM-X Cooperative Mode

Instrument Imaging Modes

Instrument Polarization Modes

SM SL HS SC Single (S)

Dual (D) not SC

Quad (Q) *DRA SM only

bistatic x (x) (x) x x x*

alternating bistatic x (x) (x) x (x)

pursuit monostatic x x x x** x x x*

*: quad polarization for TanDEM-X requires successful implementation, testing, characterization and release of the TerraSAR-X experimental DRA mode for both satellites and additionally the implementation in the joint mission. As of now, DRA has not been used on TanDEM-X in orbit. **: ScanSAR from pursuit-monostatic data will be only provided as TerraSAR-X-like products and in single polarization only. (x): indicates, that this mode is not an “operational mode” but an additional mode which is processed and provided by the processor on best effort basis using the operational commanding, production and distribution chains.

Operationally available polarization channel combinations for TerraSAR-X mission dual pol products are currently

• HH/VV, HH/HV, VV/VH in stripmap mode and

• HH/VV for the two spotlight modes.

Full “quad” polarisation (HH/HV/VH/VV) is available for stripmap only in campaigns for specific experimental acquisitions. ScanSAR is only available in single polarisation mode. Deviating combinations may be processable on best effort basis.

In the TanDEM-X case, the variety of possible polarization combinations in commanding the two instruments is huge. Many of them yield combinations which can not be directly combined without additional information to interferometric pairs. Only matching polarizations can be used for signal based coherent cross correlation yielding the required high precision coregistration in the fully automatic processing. This is required for all single polarization data takes.

Both instruments may toggle the [ Tx Rx ] polarization according to the same commanding sequence or independently (or not toggle at all). If the commanded sequence match, the data take is called an Interferometric Dual Pol (e.g. active sat1: HH VV – passive sat2: HH VV, or VV VH – VV VH, …)

If the polarization channels are generated by different commanding, it is a Double Pol data take:

• Double Single Pol: HH - HV, VV - VH or a

• Double Dual Pol (HH VV – HV VH, …)

Only interferometric Dual (and Quad) Pols are processed by the operational processor to nominal user products. For alternating bistatic data, the polarization toggling is linked to the toggling between active transmitter and passive receiver of the others instrument signal. The alternating bistatic “dual” polarization data takes are hence processed to a set of single polarization products with different master instruments and different polarization channels.





3.3 Operational Product Generation

The systematic processing of the TanDEM-X acquisition to the operational products is performed by the Integrated TanDEM Processor (ITP). The ITP functionalities comprise:

A. screening of TDX/TSX data takes at the receiving stations (as “TanDEM-X Screener”), B. a quality check of a joint TanDEM-X acquisition, C. (bi-static) SAR focusing to co-registered single look slant range complex products (CoSSCs) as

intermediate products required for further multi baseline InSAR processing, D. InSAR processing with single and multi baseline phase unwrapping and E. generation of Raw DEMs as input for the subsequent mosaicking and calibration processor (MCP)

which generates mosaicked and edited DEM products out of them.

Additional functionalities are:

F. the experimental product generation for some operational modes and G. the generation of specific (e.g. high-resolution) Raw DEMs for regional (and / or temporal)

customized DEMs.

The ITP is thus the heart of the operational processing chain, generating all operational products which use data from both satellites.

While only a subset of the operational mode variants (bi-static, alternating bi-static and pursuit mono-static) is suited for DEM generation, a greater variety of instrument configurations and formations is intended for experimental product generation. The ITP is able to generate the required product variants which are similar to the CoSSCs generated for internal use in the DEM processing chain. ITP processing of acquisitions for experimental products thus follows the nominal processing chain and mainly provides as output the intermediate SSC files generated after focusing and coregistration to CoSSCs. This is finalized by common product formatting steps.

The main “container” for all TanDEM-X specific products besides DEMs is thus one CoSSC which nominally contains two SSCs – one of each satellite of which the passive (secondary) channel is co-registered to the active (master) channel. These two SSCs are formatted very similar to a TerraSAR-X mission L1b product completed with some common annotation, product components and quicklooks.

However, for generation of the additional experimental products which shall comprise all TerraSAR-X modes (including ScanSAR) and Level 1b product variants, the slightly modified TerraSAR-X Multi-Mode SAR Processor (TMSP) is provided for monostatic processing of single acquisition channels. This chain will provide also the full variety of TerraSAR-X mission basic products from an active channel(s) of bistatic and pursuit monostatic TanDEM-X acquisitions generated upon request as catalogue order via the nominal TerraSAR-X mission user interface (e.g. EOWEB) based on TanDEM-X L0 archive products (without catalogue browse images however). Note that the TerraSAR-X basic product specification (and the TerraSAR-X experimental product description) generally do not apply to products generated from TanDEM-X acquisitions. The product performance may be reduced due to different instrument settings optimized for DEM generation but product structure and format will be kept. All relevant information on those products is given in [I1] and [I2] and is not further dealt with in this document.

Experimental mode acquisitions (system data takes with undefined imaging modes or experimental settings) may be fitted with very basic annotation parameters and are available inside the ground segment as raw data only. The figures below illustrate the operational product generation and the Table summarizes the available modes and products.

Aiming for global coverage, the TanDEM-X DEM acquisitions are generally long data takes in SM mode. As for the DEM processing chain, the experimental data takes (in SM mode) are split into slightly overlapping “scenes” and processed separately to several experimental products. A (longer) acquisition





is thus available as 1-n CoSSC-scenes with scene extents that correspond more or less to TS-X L1b products (50km x 30km). The same mechanism is applied for experimental acquisitions. The framing is based on geographic rasters and may thus split even short data takes if crossing such geographic raster line. An overlap between these scenes is however guaranteed and the relevant parameters used in processing (e.g. phase synchronization etc.) are based on the entire data take. Therefore the continuity of the products is fulfilled.

Fig. 3-2: Products from the operational DEM processing chain.





Fig. 3-3: Experimental TanDEM-X products from the operational TanDEM-X processing chain.

Fig. 3-4: Experimental TanDEM-X product generation from the TerraSAR-X processing chain and archive access as intended for later mission phases.





TanDEM-X Acquisition Modes and Products Operational Modes

(plus additional modes for product generation) Experimental Modes

Commanding nominal TanDEM-X commanding System order

TanDEM-X Cooperative Mode

Bistatic Alternating Bistatic

Pursuit Monostatic

Any

Instrument Imaging Modes

Stripmap (SM) additional: SL,HS

Stripmap (SM) additional: SL,HS

All basic modes (SM, SL, HS, SC)

Any

Instrument Polarization Modes

All basic modes for SM (incl. DRA for Quad**)

Single additional: Dual

All basic modes (incl. DRA for Quad**)

Any

Formation Geometry

Cross-track baselines

< 4 km < 4 km < 4 km Any

Along-track baselines

< 1 km < 1 km Any Any

Processing and Products

TanDEM-X Screening (SCR) to L0 products with annotation

Only DEM acquisitions

No - basic annotation only

Only DEM acquisitions

No - basic annotation only

oper

atio

nal p

rodu

cts

Acquisition variants suitable for ITP Raw DEM and CoSSC generation

SM single pol SRA mode

(in close formation)

- SM single pol SRA mode

(fallback solution)

-

Experimental products generated by ITP (1…n = number of geographic frames)

(1…n) CoSSCs for all SM (+ SL, HS single & dual pol) acquisitions

3 x (1…n) CoSSCs for all acquisitions (2 x bistatic + 1 x monostatic pairs)

(1…n) CoSSCs for all SM (+ SL, HS single & dual pol) acquisitions

Operational mode variants on best effort basis

expe

rimen

tal p

rodu

cts

Experimental products generated by TerraSAR-X TMSP

(1…n) TerraSAR-X like level 1b products* (incl. geocoding) of the monostatic active channel for all acquisitions

- 2 x (1…n) TerraSAR-X like level 1b products* (incl. geocoding) for all acquisitions

“Imaging” DTs on best effort basis

*: The TerraSAR-X basic product spec may not apply in terms of performance**: The DRA mode is not yet operationally available for the TanDEM-X mission





4 Product Characteristics

4.1 General Characteristics

The SAR and InSAR performance of an experimental acquisition with TanDEM-X will strongly depend on the actual acquisition conditions. It is to be estimated individually from the acquisition parameters. Generally a range of typical performance parameters for selected mode combinations is indicated in this document. These will be however always only estimates based on evaluation of a restricted number of products.

Operational TanDEM-X acquisitions are joint acquisitions by two satellites with the main purpose of interferometric data acquisition. Thus the operational products (CoSSCs) generated out of such acquisitions are optimally prepared for this use by the processing systems.

The CoSSCs are the basic products for further (polarimetric / interferometric, ATI-MTI, …) processing and evaluation. The ITP processor is adapting many of its processing parameters dynamically to the characteristics of the data take. For example the spectral shift filtering is not always applied for more extreme geometric conditions. However, the experimental nature of some mode combinations may require to restrict processing to the nominal settings in the automatic processing chain. Hence this may lead to stronger sidelobe responses, ambiguities and so forth.

Coregistration is however limited to the individual SSC pair; the 3 CoSSCs from one geographic scene of an alternating bistatic mode (which yields 2 pairs of bistatic SSCs and one monostatic pair) for example are not coregistered to one master but in each bistatic pair to its active channel and the monostatic one is coregistered to one of the two active channels (the interferometric master).

4.2 Coverage and Product Location

The data access incidence angle range of all products is based on the incidence angle range of TerraSAR basic products and the one of the TanDEM-X beams. The valid coverage of a CoSSC is the common swath of a joint acquisition. It is thus reduced to that what is contained in both channels after application of synchronization and echo window position correction. Despite using wider beams and a more extended echo window (for the passive satellite) - at least for DEM acquisitions - it is likely that the common swath will be reduced with respect to a single satellite data take.

Spotlight modes additionally yield a reduced common azimuth scene extent (e.g. from the Doppler centroid and start time deviations), nominally below the one specified for single satellite products.

Not relevant for TanDEM-X products is the 3dB beam width for radiometric accuracy and the geometric resolution. It is thus implemented to process beyond the limits corresponding to 100% chirp correlation (e.g. at echo window position (EWP) shifts). This may in turn even widen the common swath. However, low SNR leads to low interferometric coherence and thus restricts the usability of this extension.

Generally, the orbit, timing and synchronized use of both instruments is crucial in the TanDEM-X mission. The synchronized start of the instruments refers however to time only – not to the location in orbit. The matching of the product coverage area with the ordered one and the common swath extent are thus expected not to be as good as for TerraSAR-X and are ruled by the combined errors of both data take executions.





4.3 Radiometric Quality

TanDEM-X experimental (bistatic) products are not radiometrically calibrated. However, the effects of the combination of the projected one way pattern and e.g. effects of instrument temperatures are corrected for in the operational processing. The radiometric performance / SNR depend on how accurately the two instruments match in terms of pointing / Doppler centroid course during one acquisition. For nominal conditions the extremely stable radiometric performance and accurate knowledge and correction of antenna pattern and beam pointing found in the TerraSAR-X mission products does also apply to a certain extent to TanDEM-X data. Calibration constants on best effort basis are be provided.

Noise level estimates for (bistatic) TanDEM-X products are very limited in their accuracy and provided on best effort basis only.

Generally, the active / monostatic channels of TanDEM-X products may be very close in radiometric performance to TerraSAR-X products, depending on the use and calibration information available on specific TanDEM-X beams. One limiting factor is that part of a bistatic acquisition is covered by the exchange of sync pulses at a rate of about 3-10Hz. This implies that several imaging pulses at each interleaved sync pulse exchange sequence are not recorded (compared to a monostatic data take) and hence the radiometric sensitivity is lowered.

Additionally, aiming for increased coverage, TanDEM-X DEM acquisition raw data are stored more compressed on board of the instruments. Thus they are more affected by effects like weak target suppression and quantization errors. These compression settings may however not apply to all operational modes and are partly optimized for individual acquisition types (e.g. spotlight modes).

4.4 Geometric Quality

In terms of resolution, the bandwidth reduction by common spectral filtering always widens the point target response 3dB width with respect to a TerraSAR-X product of same geometry and instrument settings. Also focussing below the 100% correlation limit reduces the resolution further beyond the swath limits. A minor reduction in focussing quality may result from bistatic processing approximations when applied for extreme baselines / Doppler centroid variations. Unlike for TerraSAR-X products, the azimuth processing bandwidth for example is dynamically adapted to the commanded instrument settings. This implies a variable azimuth resolution for different acquistions of otherwise similar parameters.

Since precise knowledge of positions, delays and baselines is the base for the success of the TanDEM-X DEM generation, the experimental products will benefit from this high accuracy in terms of pixel localization accuracy.

The need for high priority experimental TanDEM-X products and the respective fast processing that is required, will obviously not yield this precision. Generation of experimental products with coarse baselines and rapid orbit accuracy allows to process within hours or days (provided that the raw data arrives fast at the processing facility) but results in a product quality reduction that goes beyond pure location errors since the interferometric (pre-)processing taking place in the CoSSC generation sequence crucially depends on the baseline accuracy and the operational chain is set up for nominal parameter ranges. However, focussing will not be affected significantly by the quality reduction as long as the bistatic angles are small.

As the CoSSCs for DEM generation, the experimental CoSSCs are precisely coregistered far below the sub-pixel range to preserve coherence. The experimental product coregistration either uses the signal based (coherent) cross-correlation derived on patches of 32x32 pixels separated by about 64 samples or





the reference DEM based terrain adaptive correction as fallback for some patches, depending on the coherence of the data. The resampling manipulation on the secondary channel is partly revertible with the knowledge of the applied shifts, which are provided as a file in the common aux raster directory. Especially for extreme geometric configurations beyond the range intended for DEM acquisitions or experimental polarisation combinations, such processing may however introduce errors.

Nevertheless, any reversion of the resampling of bistatic channels does not yield an SSC with timing and geometry described by the second’s channel annotation. The bistatic acquisition implies that each and every pixel is described with its timing by a virtual point in space which can not be derived by simple geometric shifts but only by iterative approaches taking the entire formation geometry and signal delays into account.





5 Experimental Product Modes and Acquisition Performance

5.1 Polarization Channel Combinations

The following table shows the possible polarization channel combinations. The letters A – I can be H or V polarization. Each letter represents the unique combination of satellite (master or slave), channel type (TX or RX) and polarization (H or V).

Interferometric Mode

Pol. Mode TX

Pol. Mode RX

Pol. TX Master Sat

Pol. TX Slave Sat

Pol. RX Master Sat

Pol RX Slave Sat

Bistatic Single Single A B C

Bistatic Dual Dual AB CD EF

Alt. Bist. Single Single A B C D

Alt. Bist. Single Dual A B CD EF

Pursuit Mono. Single Single A B C D

Pursuit Mono. Dual Dual AB CD EF GI

For the interferometric modes bistatic and pursuit monostatic, 1 CoSSC product is obtained after processing. In the case of alternating bistatic, 3 different CoSSC products are obtained after processing. The combinations of the polarizations and resulting data pairs which can be commanded are summarized in the following table, related with the polarization combinations indicated in the previous one. BTX1 represents the monostatic/active channel, BRX2 represents the bistatic/passive channel.

Pair No. 1 2 3

Interf. mode BTX1 BRX2 BTX1 BRX2 MON1 MON2

Bistatic single AB AC

Bistatic dual AC BD AE BF

Alt. Bistatic single AC AD BD BC AC BD

Alt. Bistatic dual AC AE BF BD AC BF

Interf. mode MON1 MON2

Pursuit mon. single AC BD

Pursuit mon. dual AE BF CG DI

There is a huge variety of possible polarization combinations. However, only those combinations which can be exploited interferometrically are considered as operational products. As example for an experimental mode, an alternating bistatic multi polarization product set is realized from two interleaved bistatic single polarization instrument settings. Here the following polarization channel





combinations are commanded and the following CoSSC products polarizations would be obtained after processing:

Pair No. 1 2 3

Pol. TX

Sat 1

Pol. TX

Sat 2

Pol. RX

Sat 1

Pol. RX

Sat 2 BTX1 BRX2 BTX1 BRX2 MON1 MON2

A B C D AC AD BD BC AC BD

H TSX

V TDX

H TSX

V TDX

HH TSX TSX

HV TSX TDX

VV TDX

TDX

VH TDX

TSX

HH TSX TSX

VV TDX TDX

Since neither of the two channels of each CoSSC match, this is not considered an operational product. This restriction is necessary since the precise coregistration is based on the coherent signal cross correlation of the two channels of one CoSSC. If there is no coherence, a geometric fallback solution has to be applied which is based on reference DEM information, yielding badly coregistered data specifically outside of the SRTM coverage. Hence operational CoSSC generation is limited to such polarization combinations where the two SSCs in one CoSSC have the same polarization channel. These are called “fully interferometric processable” and are listed in the following table. Combinations where limitations apply are marked in green.

Product No.

CoSSC-1 CoSSC-2 CoSSC-3

Interf. mode BTX1 BRX2 BTX1 BRX2 MON1 MON2

Bistatic single AB AB

Bistatic dual AC BD AC BF*

Alt.Bistatic single AC AC AC AC AC AC

Alt. Bistatic dual AC AC BF BF AC** BF**

Interf. mode MON1 MON2

Pursuit mono. single

AC AC

Pursuit mono. dual

AE BF AE DI*

*: Second polarization channel does not necessarily match. The coregistration information is taken from the matching polarization channel combination.

**: If the polarization channels do not match, the coregistration is based on (unreliable) reference DEM information only. The user may want to perform ”monostatic” coregistration of the two master channels (CoSSC-ALT1_BTX1 with CoSSC-ALT2_BTX1) by himself in that case for improving coherence and accuracy of the alternating bistatics monostatic interferometric pair.





5.2 Elevation Beams Definition

The following table shows a summary of the elevation beams definition used for the experimental modes of the TanDEM-X Mission.

Interferometric mode

Beam ID Min. look

angle [deg]

Max. look

angle [deg]

Ground swath width [km]

Ground swath

overlap to next swath [km]

Number of

beams

strip 13.25 41.34 31.7 7.6 14

strip 40.94 45.11 30.1 6.0 3

strip 44.81 53.49 27.1 5.4 10

strip 53.40 55.50 20.7 3.0 4

tanDEM 26.1 41.34 30.9 4.0 14

tanDEM 40.12 43.88 25.7 4.0 4

Bistatic SM Single Polarization and Pursuit Monostatic SM Single Polarization

tanDEM 53.44 55.14 24.8 3.3 4

stripNear/Far 13.41 41.25 16.6 4.6 28

stripNear/Far 41.03 45.03 15.0 3.0 6

Bistatic SM Dual Polarization and Alternating Bistatic SM Single (and Dual) Polarization

stripNear/Far 44.88 53.45 13.5 2.7 6

Bistatic SL and HS Single and Dual Polarization

spot 13.57 53.35 17.7 12.7 122

The Annex provides a detailed list of the beam definitions for TanDEM-X products.





5.3 Performance Parameters

5.3.1 Range Bandwidth in Stripmap Modes

Due to the hardware design of the SAR instrument, a 150 MHz receive bandwidth is not possible for all SM modes. Depending on the PRF and the incidence angle, the bandwidth is usually set to 100 MHz for far range beams.

The commanding is optimized to always use 150 MHz when possible to achieve optimum radiometric resolution. The probability of 100 MHz data taking in full performance range beams was estimated based on a set of representative bistatic single polarization SM data takes (DT). The result is shown in the table below, but deviations for special acquisition geometries may exist.

Beam ID Number of DT with 100

MHz Total number of DT DT with 100 MHz [%]

strip_003 0 39 0.0

strip_004 1 35 2.9

strip_005 0 46 0.0

strip_006 0 62 0.0

strip_007 12 30 40.0

strip_008 45 46 97.8

strip_009 104 110 94.5

strip_010 59 92 64.1

strip_011 26 26 100.0

strip_012 71 71 100.0

strip_013 75 75 100.0

strip_014 74 74 100.0

tanDEM_a1_010 13 92 14.1%

tanDEM_a1_020 22 92 23.9%

tanDEM_a1_030 80 93 86.0%

tanDEM_a1_040 61 69 88.4%

tanDEM_a1_050 91 91 100.0%

tanDEM_a1_060 64 81 79.0%

tanDEM_a1_070 30 30 100.0%

tanDEM_a1_080 68 68 100.0%

tanDEM_a1_090 26 26 100.0%

tanDEM_a2_005 0 16 0.0%

tanDEM_a2_015 15 23 65.2%

tanDEM_a2_025 6 13 46.2%

tanDEM_a2_035 3 8 37.5%

tanDEM_a2_045 42 42 100.0%





tanDEM_a2_055 11 12 91.7%

tanDEM_a2_065 29 29 100.0%

tanDEM_a2_075 23 23 100.0%

tanDEM_a2_085 11 11 100.0%





5.3.2 PRF Range and Values

The flexibility of the SAR instrument allows commanding PRF values from about 2000 Hz up to around 6700 Hz. Depending on the target area, the employed beam and on the interferometric imaging mode, a different range of PRFs is usually used. The following table gives an overview of the typical effective PRF. In the case of dual polarization and alternating bistatic SM, SL, HS modes the table depicts the effective PRF (PRF per channel), which corresponds to half the total instrument PRF.

The minimum and maximum PRF show the limits of the possible PRF range inside each group of beams. Depending on the interferometric mode, an average PRF value has been calculated from a representative set of bistatic data takes.

Beam ID Min. PRF

[Hz] Max. PRF

[Hz] Typical effective PRF

[Hz]

strip 001-014 3100 – 3300 4500 – 5500 3750

strip 015-027 2300 – 3100 4000 –4300 3500

tanDEM 3000 5600 3800

stripNear/Far (dual pol & alt. bistatic)

1800 – 2250 3125 2770

spot 001-070

(single pol.) 3400 5000 – 6500 3800

spot 071-100

(single pol.) 3000 – 3300 3400 – 3800 3580

spot 101-122

(single pol.) 2800 – 3000 6500 2885

spot

(dual pol & alt. bistatic)

2100 – 2750 3250 3055

5.3.3 Processing Bandwidth

In order to reduce the azimuth ambiguities an azimuth instantaneous processing bandwidth has been defined depending on the effective PRF. The following plot shows their relation. The azimuth processing bandwidth varies from 1000 to 2765 Hz. Hamming windowing is applied in TanDEM-X with a factor of 0.6 for azimuth and range. In range the full transmitted bandwidth is processed.





500

1000

1500

2000

2500

3000

2000

2100

2200

2300

2400

2500

2600

2700

2800

2900

3000

3100

3200

3300

3400

3500

3600

3700

3800

3900

4000

PRF [Hz]

Proc

esse

d B

andw

idth

[Hz]

5.4 Special TanDEM-X Features

5.4.1 Bistatic Calibration of Interferometer

The interferometric calibration of the bistatic TanDEM-X system is required to derive absolute heights of the acquired global DEM. Experimental modes have not been optimized with respect to phase and timing calibration, thus residual phase and timing offsets may exist between the interferometric channels.

5.4.2 Synchronization Link

In bistatic acquisitions it is necessary to correct the frequency difference and drift of the independent oszillators at the two satellites. Therefore a synchronization link between both satellites is implemented. Special synchronization pulses are exchanged between both satellites during bistatic data taking. The interchange of sync pulses introduces a loss of pulses in the order of 5 Hz.

5.4.3 Exclusion Zones

For the TanDEM-X mission the two satellites fly in a close helix formation to enable single-pass interferometry for optimized acquisition geometries. The helix configuration implies that, during certain segments of one orbit, one satellite might be illuminated by the radar beam of the other satellite. The satellite that is “behind” the other one (seen from the ground) must not transmit radar signals. In order to avoid critical values of mutual inter-satellite irradiation by the SAR antennas, exclusion zones are defined for the two satellites flying in close formation. Inside an exclusion zone simultaneous transmission or alternating bistatic acquisitions are thus not possible.





5.5 Image Characterization of TanDEM-X Experimental Products

The following summary describes the initial characterization of TanDEM-X experimental products. As only a sub-set of mode variants or acquisition geometries have been investigated, the average image quality parameters make no claim to be complete or representative for all possible experimental products.

5.5.1 PSLR and ISLR

The following table shows a stable performance of the peak-to-side lobe ratio (PSLR) and integrated side lobe ratio (ISLR) values for the different channels in the bistatic acquisitions. BTX1 represents the monostatic/active channel, BRX2 represents the bistatic/passive channel.

BTX1 BTX1 BRX2 BRX2

Average Std. Dev. Average Std. Dev.

PSLR [dB] -28.36 1.11 -29.54 2.46 Range

ISLR [dB] -19.62 0.22 -19.70 0.37

PSLR [dB] -28.93 1.39 -29.43 1.55 Azimuth

ISLR [dB] -19.20 0.45 -19.31 0.64

In bistatic Spotlight images, point target responses are slightly degraded as their azimuth spectral behavior is distorted due to the interleave sync pulse sequences.

5.5.2 Azimuth Resolution

As already explained, the azimuth resolution depends on the processed azimuth target bandwidth. In spotlight modes, the total processed azimuth target bandwidth is the integrated spectral combination of the instantaneous processing bandwidth for the individual azimuth beams. It thus depends on the azimuth beam steering (aperture length) applied and is hence higher than the instantaneous bandwidths given in the sections above. The following figure shows the azimuth resolution for the analyzed operational and additional experimental modes.





5.5.3 Range Resolution

The slant range resolution is relatively constant for all experimental modes. The major influence comes from the selected range bandwidth and the spectral shift filtering applied. The probability of 100 MHz data taking in full performance range beams has been presented above. A detailed representation of the variation, depending on the channel is depicted in the following figure. The secondary channel (BRX2) presents a slightly worse range resolution with respect to the primary channel (BTX1), which is observed for both transmit bandwidths.





5.5.4 Ground Swath Width

The obtained ground range swath widths for the different analyzed images provide the expected values described in the beam definition tables, including the considered margins. Also the minimum ground swath width in azimuth for SL/HS acquisitions have been measured to be of the expected size.

5.5.5 Noise Equivalent Sigma Zero

An analysis of the Noise Equivalent Sigma Zero (NESZ) several COSSC products has been performed. Only stripmap imaging modes have been investigated. The mode information and the obtained mean NESZ over the complete scene are shown in the following table.

Interferometric mode

Beam ID Transmitted Bandwidth

[MHz] Channel

Mean NESZ [dB]

Bistatic tanDEM_a1_030 150 BTX1 -18.97 Bistatic tanDEM_a1_030 150 BRX2 -19.28 Bistatic tanDEM_a1_080 100 BTX1 -21.19 Bistatic tanDEM_a1_080 100 BRX2 -21.54

Alt. Bistatic stripFar_003 150 ALT1-BTX1 -20.40 Alt. Bistatic stripFar_003 150 ALT1-BRX2 -20.49 Alt. Bistatic stripFar_003 150 ALT2-BTX1 -20.23 Alt. Bistatic stripFar_003 150 ALT2-BRX2 -20.86 Alt. Bistatic stripFar_003 150 MON1 -19.96 Alt. Bistatic stripFar_003 150 MON2 -20.23 Alt. Bistatic stripFar_008 150 ALT1-BTX1 -22.63 Alt. Bistatic stripFar_008 150 ALT1-BRX2 -22.67 Alt. Bistatic stripFar_008 150 ALT2-BTX1 -22.28 Alt. Bistatic stripFar_008 150 ALT2-BRX2 -22.63 Alt. Bistatic stripFar_008 150 MON1 -22.33 Alt. Bistatic stripFar_008 150 MON2 -22.81





6 CoSSC Product Structure and Format

6.1 Structure

The TerraSAR-X mission heritage is adhered to by choosing a structure and format for the CoSSCs that follows the basics of the level 1b format specification. In fact, the CoSSCs are very close to two TerraSAR-X level 1b products supplemented by the common data. The individual SSCs are however different from the TerraSAR-X level 1b products since some parameter sets are optional only and omitted for the passive instrument in a bistaic mode product (i.e. antenna pattern and replica chirp analysis). However, for the sake of compatibility and to ease access to the data, some basic information is doubled. Also some enumeration types will be altered to accommodate TanDEM-X specific parameter values yielding annotation files which may not fully validate with TerraSAR-X schema files since the parameters originate from different auxiliary data sources.

Internal CoSSCs for DEM generation and experimental products are generated by the same software and formatted in a similiar way. Nevertheless, their characteristics are not identical due to differing processing parameters. These differences are annotated in the products. The main annotation file which comprises the common aspects of a CoSSC also serves as ITP output file for archival purposes and as a main source for an interferometric quality check product derived from the archived products. As such, it follows a generic ITP output product xml scheme.

In the Figure, the blue colour represents the common files and structures. The yellow color indicates the sub components of the product. The objects in these (marked in green) are the TerraSAR-X level 1b SSC like product components close to the ones specified in [I1] and [I2]. Optional or supplemental components are marked with dashed lines. Additional image layers (e.g. polarimetric channels) are colored magenta. The optional subdirectories in the common directories holding the common files of the different polarization channels are numbered 2,3,4 for multi-polarization CoSSC products.

The main annotation file in the (sub-component) directory carries the product name with the extension “.xml”. The file naming scheme is outlined here using constituents (e.g. AAA) which are separated by underscores (“_”). Note again that only the main annotation file / product naming follows the specified convention and that the components may be named and located differently as referenced in the relevant “productComponents” annotation section (indicated by the red arrows in the figure).

For archival, quality assurance and processor internal reuse for Raw DEM (re-)processing, additional components (i.e. logging and parameter pool files) are archived along with the CoSSCs described here but not delivered to the user.





...

SAT#_SAR__AAA_BBBB_CC_D_EEE_xxxxxxxxTxxxxxx_yyyyyyyyTyyyyyy

SAT#_SAR__AAA_BBBB_CC_D_EEE_xxxxxxxxTxxxxxx_yyyyyyyyTyyyyyy.xml

ANNOTATION GEOREF.xml ...

IMAGEDATA IMAGE_FF_GGG_[beam ID].cos

... PREVIEW QL_FF_GGG_[beam ID].tif

COMPOSITE_QL.tif

BROWSE.tif

MAP_PLOT.pngSUPPORT

SAT#_SAR__AAA_BBBB_CC_D_EEE_xxxxxxxxTxxxxxx_yyyyyyyyTyyyyyy

TDM#_SAR__III_HHHH_CC_D_EEE_xxxxxxxxTxxxxxx_yyyyyyyyTyyyyyy

TDM#_SAR__III_HHHH_CC_D_EEE_xxxxxxxxTxxxxxx_yyyyyyyyTyyyyyy.xml

COMMON_ANNOTATION

COMMON_AUXRASTER

COMMON_PREVIEW

COMMON_IMAGEDATA INTERFEROGRAM.ras ...

...

...

spectral_filter_frequencies.xml … .xml

QL_SLT_phase.tif

slave_shift_[az|rg][_geo].flt

n

n

n

n

AUXRASTER, ...

Fig. 6-1: Directory structure and files of the CoSSC product.





Constituent ID Constituent Name Value Range Remark

TDM# mission ID TDM1, TDM2, … TanDEM-X mission

e.g. TDM1 with satellites TSX-1 & TDX-1

- sensor SAR_ fixed

III product type & variant COS COS CoSSC standard product

HHHH cooperative mode MONO,

BIST,

ALT1, ALT2

NONE

pursuit monostatic, bistatic, alternating bistatic and “none” for TerraSAR-X mission repeat pass product (for tests)

CoSSC product sub-component names:

SAT# satellite ID TSX1, TDX1, …

- sensor SAR_ fixed string

AAA product variant SSC product class (fixed)

BBBB transmit / receive (interferometric) channel from cooperative mode

MON1,

MON2,

BTX1,

BRX2

CoSSC product sub-component type: MON1 monostatic master MON2 monostatic secondary BTX1 active bistatic BRX2 passive bistatic

common product sub-component names (identical for all):

CC imaging mode SM, SL, HS example: HS for High-Resolution SpotLight

D polarisation mode S, D, Q example: D for DUAL polarization mode

EEE antenna receive configuration

SRA, DRA SRA for single-receive antenna DRA for dual-receive antenna

xxxxxxxxTxxxxxx UTC start time - master times. Format: YYYYMMDDThhmmss

yyyyyyyyTyyyyyy UTC stop time -

variable parts of the product component file names:

FF polarization channel image layer

HH, HV, VH, VV TxRx polarization

GGG geometric (antenna receive channel) image layer

SRA,

FWD, AFT

geometric layers for DRA/ATI mode (forward and after). QuadPol data is processed with the “SRA” geometric





phase center offset (thus 0).

[beam ID] elevation beam (configuration) ID

e.g. strip_007, … Identifying the different image layers for each (sub)swath of the product

Table 6-1: File name constituents.

The file name extensions used are:

• “.xml” for the annotation files following the schema definitions in this document • “.tif” for TIFF / GeoTIFF images with different depths and representations • “.cos” for the COSAR image format specified herein • “.ras” for the SUN raster format • “.png, .txt” for standard PNG and text files.

The cooperative mode indicator is used for grouping and distinguishing the three CoSSCs of an alternating bistatic data take that belong to one geographic scene:

• ALT1 and ALT2 are the two bistatic products with the two different instruments as the respective active masters. In terms of processing and format (not in performance), the ALT* products are otherwise identical to BIST products.

• The MONO indicates the product generated from the two active channels. It is indeed identical in its generation process to a “nominal” pursuit monostatic product – just with a very short along track distance (where their signals would interfere if not toggling the transmit/receive sequence).

The alternating bistatic monostatic pair is provided for consistency and for the users convenience; it can be also be generated by the user from the two active SSCs of the two bistatic products with nominal “monostatic” InSAR tools (e.g. for switching the master/slave roles).

6.2 CoSSC Annotation

The main product directory contains the CoSSC main annotation file. It contains in a comprehensive way the information common to the product from the joint TanDEM-X acquisition. Like the TerraSAR-X L1b geo grid annotation file, detailed parameters on specific topics (i.e the spectral processing information) are sourced out to files in the common annotation directory.

For the main product components, a pointer to the file or directory and a unique name to identify the component is delivered. The element type is used to specify the data type. This is a generic structure used for every ITP output product. The high level parameters provide information on the basic properties of the product itself like joint geographic coverage and e.g. (data take) IDs and are also intended for cataloguing (similar - but not necessarily identical - to product archive meta data).

For CoSSCs, the specific parameter sections contain parameters which describe the joint bistatic (& interferometric) processing parameters, geometric and timing corrections and baselines information of the configuration. It also describes the characteristics of a CoSSC common to both SSCs (e.g. shadow layover statistics). The detailed parameters like instrument settings, geo-grids or processing steps is to be found in the individual annotation of each SSC as for the TerraSAR-X L1b products. The content of the parameters related to interferometric processing varies with the type of the product (i.e. there is information on DEM generation in the nominal CoSSCs but not in the experimental ones).





6.2.1 Base Parameter Classes

The following table sketches the kind of available information in the XML file. It is neither complete nor binding in terms of parameter names or structure and servs as an orientation guide to the content of the parameters only.

Parameter Classes

Parameter group Content / examples

#

Remark

product type CoSSC

product variant standard standard for nominally generated CoSSCs

product generation info ITP version, date, time, creation site, …

TanDEM-X common acquisition info

1

data take IDs TAP_0101.211_G_AF_ETH_tanDEM_a1_090R_000602

1009818

TAPTake ID (string which codes the mission phase, area, beam, …)

acquisition Item ID (to identify the data take)

acquisition class appliedToID experimental data (notUsedForDEM), DEM data (usedForGlobalDEM),…

data take operations mode

OPERATIONAL, TEST,…

of both instruments

cooperative mode bistatic of the TanDEM configuration

antenna look direction Right, Left of both instruments

orbit direction Ascending / Descending

at scene start

along / across track separation min, mean, max

geometric distances (bistatic) distances and baselines for the mid-scene

effective baseline projected BL vector components, h_ambig

at mid scene, resulting height of ambiguity

Acquisition mode info for each instrument

2

sat ID TSX-1

instrument mode active, passive





elevation beam configuration

strip_007

imaging mode SM, SL, … of both instruments has to be identical for processing to CoSSC

polarization mode S, D, Q, …

antenna receive configuration

SRA, DRA

range bandwidth class 150MHz nominal instrument BW (not filtered) of both instruments

polarization channels HH, VV, … Transmit/Receive configuration(s)

commanded start / stop time

UTC CCSDS (exact product coverage times are given in master SSC product annotation)

Scene & processing info 1

total number of scenes geographic frames of entire DT

scene sequence number number of this CoSSC scene in the sequence of scenes generated from the DT

processing flags / steps co-registration, interferogram generated, raw DEM generated

indicating e.g. if fine signal cross correlation co-registration was applied. Note that even for experimental CoSSCs a DEM is internally generated (from simulated phases of reference DEMs) for consistency and geocoding of quicklooks. Its quality is not related to the interferometric quality of the CoSSC itself

spatial coverage center and corner coordinates

coordinates of valid scene coverage (geographic)

incidence angle range near, mid, far of valid scene

auxiliary products orbit//baseline/Interferometric Aux product used for common processing

product files/versions, coarse or precise baseline product used, rapid or science orbits, …





baseline product quality orbit/baseline (availability)

state vectors counted as gaps since flagged for manoeuvres, …

DEM generation info 1 (Only for CoSSCs for DEM processing)

raw DEM ID and geographic frame

name and geographic frame corner coordinates in MCP notation

provided only if a raw DEM is generated

scene geometry complexity indicators

total shadow area (%), total layover area (%), water coverage (%)

this information is based partly on acquisition geometry and reference DEM and land cover information. ITP generates this information along with a flag mask specifically for future (re-) acquisition planning for DEM acquisitions.

interferometric processing quality statistics

coherence statistics, suspected phase unwrapping error indicator, PU statistics.

for standard CoSSCs derived during phase unwrapping & DEM generation and from scene geometry / reference DEM.

Quality info 1

interferometric acquisition quality indicators

indicators for e.g. swath degradation, Doppler deviation indicator(s), synchronization loss indicator, swath illumination indicator

combinations of individual data take quality assessment and common parameter evaluation (e.g. average Doppler centroid for each satellite within TZDS limits, relative difference of the two Doppler centroids within limits, …)

interferometric quality indicators

e.g. sync pulse signal quality limit violation

limit checks of quality indicators against interferometric IOCS aux product limits

processing quality approval

quality warning encountered during processing

automatic ITP internal quality check result





6.3 CoSSC Components

The common files are found in the COMMON_* product components. For Dual or Quad-Pol products, there are additional indexed sub-directories included which hold the common interferometric files of the respective polarization channels. The “master” polarization data (on which the coregistration is based) remain at the upper level of the directories.

6.3.1 Additional Annotation Files

Besides the main annotation file, the CoSSC may contain further, very specific product parameters in dedicated XML files in the common annotation file directory. This may include (depending on the application of spectral shift filtering) the optional files

• spectral_filter_frequencies.xml which provides the applied and resulting Doppler centroids, bandwidths, frequency shifts, etc. for each range and azimuth block of the filtered slave scene.

• image_layer_info.txt ASCII file which lists the basic characteristics related to the polarization, beam and antenna mode of the specific image layer in the current (sub-)directory. Especially relevant for multi-polarization products where it is required to identify the polarization channels.

6.3.2 Auxiliary Raster Files

The following image raster files mainly originate from nominal DEM processing and may be hence only available for standard CoSSCs which were generated along with Raw DEMs. They are thus optional.

• slave_shift_[az/rg][_geo].flt 4byte floating point SUN raster file of the shifts applied to the slave in resampling and the geometric estimates used – accompanied by quality control raster files (qc_*.ras).

• coreg_type.ras coding if coherent, incoherent signal correlation or the geometric fallback information was used for the coregistration at each patch. Additional processor internal files for quality control are also provided.

6.3.3 Preview Files

The quicklook files which are already embedded in the individual two SSC product sub-components, provide a preview of the images prior to co-registration and cropping – they do not represent the modified CoSSC-SSC-Images! The common preview directory contains the interferometric and other preview files which are obviously optional and only provided for CoSSCs which also undergo InSAR/DEM processing. The quicklook files are neither in the same geometry nor commonly sampled. These files are however not only preview/quicklook images but also serve for quality control, acquisition quality assessment and future planning.

• QL_SLT_QM.tif low resolution Flag-File which is coded as the RawDEM Flag Mask and includes the minimum cost flow phase unwrapping quality control map in slant range geometry packed in an 8-Bit TIFF with bit-coded information on unwrapping phase residuals (0/+/-), and branch cuts between them (0/1). The remaining bits represent the shadow and layover regions, and the Globecover water flag. Obviously, there may be different combinations of bits set:





Bit value

Resulting value

Meaning

0 1 2 3 4 5 6 7

1 2 4 8 16 32 64 128

1 0 0 0 0 0 0 0 1 Shadow

0 1 0 0 0 0 0 0 2 Layover

0 0 1 0 0 0 0 0 4 Globecover Water

0 0 0 1 0 0 0 0 8 PU-Indicator 1

0 0 0 0 1 0 0 0 16 PU-Indicator 2

0 0 0 0 0 1 0 0 32 PU-Indicator 3

0 0 0 0 0 0 1 0 64 PU-Indicator 4

0 0 0 0 0 0 0 1 128 phase modification

• QL_SLT_dinsar_[phase/radargr].tif low resolution phase unwrapping quality map as 8-Bit TIFF file in slant range geometry. It provides coarse information on possible problematic error regions by indicating discrepancies of the unwrapped phase w.r.t. the reference DEM (“phase”) and radargrametric estimate (“radargr”) provided for processing. Again, this is only relevant if the phase has been unwrapped for DEM generation.

For those experimental products (and DEM generation CoSSCs) which are processed to interferograms the following raster files are provided

• QL_SLT_coher.tif low resolution coherence estimate in slant range geometry and 8-Bit TIFF format. The pixel value range may be scaled with a gamma curve in order to enhance representation of highly coherent data.

• QL_SLT_ampl_composite.tif low resolution RGB 24-bit TIFF image in slant range geometry indicating the amplitude differences of the two acquisitions.

• QL_SLT_phase.tif low resolution RGB TIFF image in slant range geometry indicating the phase. Note that it is downsampled using a median filter in order not to smooth the phase wrapping and is thus rather noisy.

All the following optional low resolution raster files are gecoded and from Raw DEM generation steps. They provided in GeoTIFF format and accompanied by kml files but the coordinate annotation embedded is only a very coarse location indicator. The sampling and dimension are as close to each other as possible.

• QL_GTC_DEM.tif 24-Bit GeoTIFF browse image of shaded and coloured geocoded Raw DEM that was initially generated from this standard CoSSC or from a simulated phase in the experimental cases.





• QL_GTC_DEM_16bit.tif 16-Bit GeoTIFF image of the geocoded Raw DEM values that was initially generated from this standard CoSSC or from a simulated phase in the experimental cases.

• QL_GTC_amplitude.tif scaled 24-Bit GeoTIFF browse image of the multi-looked, detected and geocoded amplitude image provided along with the Raw DEM.

• QL_GTC_coherence.tif scaled 8-Bit GeoTIFF browse image of the geocoded coherence used for the height error map (HEM) of a RawDEM.

6.3.4 Common Image Data

For those experimental CoSSCs which are interferometrically processed, the optional common image data directory (of each layer if applicable) hosts the interferograms.

• INTERFEROGRAM.ras & .flt color coded 8bit (“.ras”) and single-precision floating point (4 byte, “.flt”) binary SUN raster file of each interferometric pair. It has the same geometry / extent as the valid data of the two SSCs but the sampling is set adaptive to the number of looks used in interferogram generation. The 8bit raster file is provided for a quick full resolution visualization.

• GTC_AMPLITUDE.ras optional 16bit SUN raster file of the master amplitude geocoded with the reference DEM for some experimental products.

6.3.5 Data Components

As already detailed, the two SSCs of which the passive / secondary is co-registered to the master channel are provided as two level 1b product like SSCs, formatted according to [I2] with minor exceptions in enumeration types and more some elements (i.e. antenna pattern for the passive instrument and chirp annotation) which are only given for consistency purposes in the bistatic passive case.

Note again that most of the annotation of a co-registered SSCs slave channel is obsolete and only kept for informative purposes. It is resampled and shifted to the master geometry (hence their name) and thus the parameters of the master are applicable. An exception is the orbit (=baseline) information which is relevant for the InSAR processing. The only annotation section updated in both files is the sceneInfo segment with new coordinates/extents.

Also note again that for an experimental product from an alternating bistatic acquisition, the three different CoSSC products of one geographic scene are not matching each other w.r.t. to master / secondary geometric configuration (the interferometric coregistration masters of the two bistatic CoSSCs are the respective active transmitting instruments).

6.4 Binary Image Data Format

6.4.1 CoSAR Files

The SSC image data files are contained in the TerraSAR-X Level 1b product like structure of the two channels. They are packed using the same CoSAR file format using the same structure, same byte order (MSB) and using the same bytes per sample as specified in [I2]. However, in order to preserve the high phase accuracy of the TanDEM-X data over a wider dynamic range without significant quantization





losses, there is an important difference in the format: The complex samples are represented using a floating point data format instead of integer values. However, to maintain the size (bytes per sample), the TanDEM-X CoSSCs are formatted using the so called "Half Precision Floating Point" format for each of the complex values which differs from the"Single Precision Floating Point" format by using only 2 bytes instead of 4. Details can be found in the IEEE norm 754-2008 (e.g. in http://en.wikipedia.org/wiki/IEEE_754-2008).

The CoSAR files can be distinguished by the version identifier in the binary “burst” annotation, where 1 refers to the nominal integer complex value and 2 identifies the new extended CoSAR variant. The following samples (starting with 1) in the burst header annotation are relevant for the interpretation:

Sample# Parameter Old CoSAR Version New CoSAR Version

9 version 1 2

13 (new) SB = number of sign bits 1 (fixed if set) 1 (exemplary)

14 (new) EB = number of exponent bits 0 (fixed if set) 5 (exemplary)

15 (new) MB = number of mantissa bits 15 (fixed if set) 10 (exemplary)

6.4.2 Image Raster files

The optional COMMON_IMAGEDATA and the AUXRASTER files are in the SUNRASTER format, consisting of

► A 32-byte header of 8 4-byte unsigned integer values. According to the SUNRASTER format the header is always in big-endian byte order.

► Binary single-precision floating point (4 byte) phase values (*.flt) or 1-2 byte integer values (*.ras), e.g. for shifts and amplitude.

The 8 4-byte integers of the header have the meaning shown in the following table.

Header byte Meaning raster file value

1-4 SUNRASTER indicator 1504078485

5-8 Number of grid columns variable

9-12 Number of grid rows variable

13-16 Bit-depth of elevation values e.g. 32

17-20 Length of binary data in bytes 4 * (no. of columns) * (no. of rows)

21-24 Type code of raster file e.g. 200

25-28 Type of color map 0

29-32 Length of color map in bytes 0





7 CoSSC XML Schema Definition Schema cossc_product.xsd

schema location: D:\docs\tdm\cossc_format\cossc_product.xsd

attribute form default: unqualified element form default: qualified Elements Complex types cossc_product componentType

parameterType

schema location: D:\docs\tdm\cossc_format\generalHeader.xsd

attribute form default: unqualified element form default: qualified Elements Simple types generalHeader string1024

string128

string20

string255

string80

element cossc_product





diagram

properties content complex

children generalHeader productComponents productInfo commonAcquisitionInfo commonSceneInfo baselineInfo processingInfo rawDEMInfo productQuality

annotation documentation This XML file contains the common meta data of cossc products. Additional annotation files are the optional spectral_filter_frequencies.xml and the image_layer_info.txt files.

source <xs:element name="cossc_product"> <xs:annotation> <xs:documentation>This XML file contains the common meta data of cossc products. Additional annotation files are the optional spectral_filter_frequencies.xml and the image_layer_info.txt files.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element ref="generalHeader"/> <xs:element name="productComponents"> <xs:annotation> <xs:documentation>Lists and points to the product components.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence>





<xs:element name="component" type="componentType" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="productInfo"> <xs:annotation> <xs:documentation>high level info</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="productType" type="string128"> <xs:annotation> <xs:documentation>CoSSC</xs:documentation> </xs:annotation> </xs:element> <xs:element name="productVariant" type="string128"> <xs:annotation> <xs:documentation>standard or experimental</xs:documentation> </xs:annotation> </xs:element> <xs:element name="processingStepsPerformed"> <xs:annotation> <xs:documentation>processing level</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bistaticCorrections" type="xs:boolean"/> <xs:element name="coregistration" type="xs:boolean"/> <xs:element name="spectralFilteringAzimuth" type="xs:boolean"/> <xs:element name="spectralFilteringRange" type="xs:boolean"/> <xs:element name="interferogramGeneration" type="xs:boolean"/> <xs:element name="phaseUnwrapping" type="xs:boolean"/> <xs:element name="phaseUnwrappingDualBL" type="xs:boolean"/> <xs:element name="phaseUnwrappingMultiBL" type="xs:boolean"/> <xs:element name="rawDEMGeneration" type="xs:boolean"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="commonAcquisitionInfo"> <xs:annotation> <xs:documentation>describing the joint acquisition. Details on the individual acquisitions are found in the level 1b annotation of each SSC component</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="missionID" type="string80"> <xs:annotation> <xs:documentation>TDM-1</xs:documentation> </xs:annotation> </xs:element> <xs:element name="cooperativeMode" type="string80"> <xs:annotation> <xs:documentation>common coop mode bistatic, pursuitMonostatic, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="satelliteIDsat1" type="string80"/> <xs:element name="satelliteIDsat2" type="string80"> <xs:annotation> <xs:documentation>TSX-1, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="inSARmasterID" type="string80"> <xs:annotation> <xs:documentation>logical ID (SAT1, SAT2)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="operationsInfo"> <xs:annotation> <xs:documentation>processing order and data take IDs</xs:documentation>





</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="TAPtakeID" type="string80"/> <xs:element name="acquisitionItemID" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>Unique Acquisition Item ID</xs:documentation> </xs:annotation> </xs:element> <xs:element name="appliedToID" type="string80"> <xs:annotation> <xs:documentation>data takes used for DEM generation or experimental products.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="processingPriority" type="string80"/> <xs:element name="operationsTypeSat1" type="string80"> <xs:annotation> <xs:documentation>OPERATIONAL, TEST, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="operationsTypeSat2" type="string80"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="acquisitionGeometry"> <xs:annotation> <xs:documentation>coarse parameters (of entire data take / scene)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="effectiveBaseline" type="xs:double"/> <xs:element name="heightOfAmbiguity" type="xs:double"/> <xs:element name="distanceActivePos" type="xs:double"/> <xs:element name="distanceTracks" type="xs:double"/> <xs:element name="orbitDirection" type="string80"> <xs:annotation> <xs:documentation>ascending / descending A/D</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lookDirection" type="string80"> <xs:annotation> <xs:documentation>left/right R / L</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="acquisitionMode" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>of each instrument</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="cooperativeInstrumentMode" type="string80"> <xs:annotation> <xs:documentation>bistaticActive, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStartTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStopTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="imagingMode" type="string80"> <xs:annotation> <xs:documentation>SM, SL ...</xs:documentation> </xs:annotation>





</xs:element> <xs:element name="polarizationMode" type="string80"> <xs:annotation> <xs:documentation>S, D ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="polarizationList"> <xs:annotation> <xs:documentation>polarization layer list (HH, VV, HV, VH) </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="polLayer" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="antennaReceiveConfiguration" type="string80"> <xs:annotation> <xs:documentation>SRA, DRA</xs:documentation> </xs:annotation> </xs:element> <xs:element name="elevationBeamConfiguration" type="string80"> <xs:annotation> <xs:documentation>e.g. tanDEM_a1_050</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthClass"> <xs:complexType> <xs:sequence> <xs:element name="rgBW" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"> <xs:annotation> <xs:documentation>SAT1 / SAT2</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="commonSceneInfo"> <xs:complexType> <xs:sequence> <xs:element name="sceneIndex" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>scene index number</xs:documentation> </xs:annotation> </xs:element> <xs:element name="totalScenes" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>geographic frames/scenes of this datatake</xs:documentation> </xs:annotation> </xs:element> <xs:element name="sceneCornerCoord" minOccurs="4" maxOccurs="4"> <xs:annotation> <xs:documentation>geographic corner coords of the common scene. early_az_near...</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude, positive towards east</xs:documentation> </xs:annotation>





</xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="sceneCenterCoord"> <xs:annotation> <xs:documentation>geographic coordinates</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude positive towards east</xs:documentation> </xs:annotation> </xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="headingAngle" type="xs:float"> <xs:annotation> <xs:documentation>rotation of azimuth heading clock wise w.r.t. North at mid-scene in degree</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="baselineInfo"> <xs:annotation> <xs:documentation>info on baseline or master orbit used. Statevectors of baseline products are to be found in the "level 1b" annotation in the platform/orbit section. Baselines are converted to orbit information.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="orbitHeader"> <xs:annotation> <xs:documentation>baseline header is converted into orbitHeader format for convinience</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>of MOS / GFZ</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string255"> <xs:attribute name="version" type="string80"> <xs:annotation> <xs:documentation>Software version number of the generation system</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="sensor" type="string80">





<xs:annotation> <xs:documentation>PROP for predicted orbit GPSS for single GPS GPSD for differential GPS, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="accuracy" type="string80"> <xs:annotation> <xs:documentation>COAR PREC CALB</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVectorRefFrame" type="string80"> <xs:annotation> <xs:documentation>state vector reference frame indicator e.g. WGS84</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coordSystemTransfrom" minOccurs="0"> <xs:annotation> <xs:documentation>applied transform if orbit data source was not in ref frame</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rotMatrixCoeff" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="i" type="string80" use="required"/> <xs:attribute name="j" type="string80" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="shift" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="stateVectorRefTime" type="string80"> <xs:annotation> <xs:documentation>state vector reference time indicator e.g. GPS</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVecFormat" type="string80"> <xs:annotation> <xs:documentation>e.g. units</xs:documentation> </xs:annotation> </xs:element> <xs:element name="numStateVectors" type="xs:int"> <xs:annotation> <xs:documentation>total number of state vectors</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTime"> <xs:complexType> <xs:sequence> <xs:element name="firstStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of first state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence>





</xs:complexType> </xs:element> <xs:element name="lastStateTime"> <xs:complexType> <xs:sequence> <xs:element name="lastStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of last state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="stateVectorTimeSpacing" type="xs:double"> <xs:annotation> <xs:documentation>[sec] state vector time spacing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="positionAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element> <xs:element name="velocityAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element> <xs:element name="recProcessingTechnique" type="string80"> <xs:annotation> <xs:documentation>recommended orbit interpolation or approximation technique</xs:documentation> </xs:annotation> </xs:element> <xs:element name="recPolDegree" type="xs:int"> <xs:annotation> <xs:documentation>recommended interpolation polynomial degree</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dataGapIndicator" type="xs:int"> <xs:annotation> <xs:documentation>number of state vectors with qualInd=0</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="processingInfo"> <xs:complexType> <xs:sequence> <xs:element name="inputData"> <xs:complexType> <xs:sequence> <xs:element name="orderType" type="string80"> <xs:annotation> <xs:documentation>TDM-PRCSCR->RDEMGEN</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMajorVersion" type="string80">





<xs:annotation> <xs:documentation>Interferometric Aux product (for the common combined instrument information used for (biststic) processing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMinorVersion" type="string80"/> <xs:element name="ifAuxGenerationTime" type="string80"/> <xs:element name="baselineProductUsed" type="xs:boolean"> <xs:annotation> <xs:documentation>was a baseline (of sufficient quality) used for processing</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="bistaticProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>Is also given for monostatic data since the correctrions (of zero drifts for monostatic data) are always applied.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="syncPulseEvaluation" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>characteristics of the sync pulses</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="driftHighPRF" type="xs:double"/> <xs:element name="driftLowPRF" type="xs:double"/> <xs:element name="missingQuality" type="xs:double"/> <xs:element name="blockQuality" type="xs:double"/> <xs:element name="powerQuality" type="xs:double"/> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"/> </xs:complexType> </xs:element> <xs:element name="averageFastTimeCorrection" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>calculated from sat 1/ 2 sync analysis</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="satID" type="string20" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coregistration" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR coregistration step result. Input/output rasters. Start times of master/slave min max shifts in pixe applied on the slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="masterFirstAzTime" type="xs:double"/> <xs:element name="masterFirstRgTime" type="xs:double"/> <xs:element name="slaveFirstAzTime" type="xs:double"/> <xs:element name="slaveFirstRgTime" type="xs:double"/> <xs:element name="slaveShiftAzMin" type="xs:double" minOccurs="0"> <xs:annotation> <xs:documentation>[samples/lines]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="slaveShiftAzMax" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMin" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMax" type="xs:double" minOccurs="0"/> <xs:element name="coregRaster">





<xs:annotation> <xs:documentation>output size</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputMasterRaster"> <xs:annotation> <xs:documentation>input size master</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputSlaveRaster"> <xs:annotation> <xs:documentation>input size slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="spectralFiltering" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR processing common bandwidth filtering</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="azimuthBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="azimuthHammingCoef" type="xs:double"/> <xs:element name="rangeHammingCoef" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inSARProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>main parameters for InSAR processing</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="observationMode" type="string80"> <xs:annotation> <xs:documentation>InSAR mode: dual_pass=monostatic, single_pass = bistatic</xs:documentation> </xs:annotation> </xs:element> <xs:element name="looks"> <xs:complexType> <xs:sequence> <xs:element name="range" type="xs:int"/> <xs:element name="azimuth" type="xs:int"/>





<xs:element name="eqNumLooks" type="xs:double"/> <xs:element name="ifResolution" type="xs:double"> <xs:annotation> <xs:documentation>mean</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ifRaster"> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="averageCoherence" type="xs:double"> <xs:annotation> <xs:documentation>of total scene</xs:documentation> </xs:annotation> </xs:element> <xs:element name="localHeight" type="xs:double"> <xs:annotation> <xs:documentation>mean heigt (reference)</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="rawDEMInfo" minOccurs="0"> <xs:annotation> <xs:documentation>mostly from DEM geocoding step. Not given for experimental products</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rawDEMname" type="string80"> <xs:annotation> <xs:documentation>associated RawDEM product (raster file)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="postingClass" type="xs:double"> <xs:annotation> <xs:documentation>ordered DEM posting</xs:documentation> </xs:annotation> </xs:element> <xs:element name="absPhaseOffset" type="xs:double"> <xs:annotation> <xs:documentation>unwrapped phase vs. true phase difference. applied for geocoding (absolute height calibration)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coordsDEMFrame"> <xs:annotation> <xs:documentation>geographic coords of frame </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="upN" type="xs:double"/> <xs:element name="lowN" type="xs:double"/> <xs:element name="rightE" type="xs:double"/> <xs:element name="leftE" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coordsDEMScene"> <xs:annotation> <xs:documentation>DEM scene coords (early azimuth near range (eanr), etc. ...)</xs:documentation> </xs:annotation>





<xs:complexType> <xs:sequence> <xs:element name="eanrLat" type="xs:float"/> <xs:element name="eanrLon" type="xs:float"/> <xs:element name="eafrLat" type="xs:float"/> <xs:element name="eafrLon" type="xs:float"/> <xs:element name="lanrLat" type="xs:float"/> <xs:element name="lanrLon" type="xs:float"/> <xs:element name="lafrLat" type="xs:float"/> <xs:element name="lafrLon" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="demRaster"> <xs:annotation> <xs:documentation>in degree and lines/samples</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="spacingLat" type="xs:double"/> <xs:element name="spacingLon" type="xs:double"/> <xs:element name="nNorth" type="xs:int"/> <xs:element name="nEast" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="statisticsDEMScene"> <xs:annotation> <xs:documentation>refers to geocoded DEM scene, its Flag Mask and HEM</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="pointsTotal" type="xs:int"/> <xs:element name="pointsShadow" type="xs:int"/> <xs:element name="pointsLayover" type="xs:int"/> <xs:element name="pointsWater" type="xs:int"/> <xs:element name="pointsMCFResPos" type="xs:int"/> <xs:element name="pointsMCFResNeg" type="xs:int"/> <xs:element name="pointsMCFSingleCut" type="xs:int"/> <xs:element name="pointsMCFMultiCut" type="xs:int"/> <xs:element name="heightMin" type="xs:float"/> <xs:element name="heightMax" type="xs:float"/> <xs:element name="heightMean" type="xs:float"/> <xs:element name="heightStdDev" type="xs:float"/> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/> <xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="percentageWater" type="xs:double"> <xs:annotation> <xs:documentation>coarse estimate from from GLOBECOVER data used for flagging</xs:documentation> </xs:annotation> </xs:element> <xs:element name="statisticsDEMLand"> <xs:annotation> <xs:documentation>statistics over GLOBE_COVER land classes</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/>





<xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> <xs:element name="pointsMCFResPos" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFResNeg" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFSingleCut" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFMultiCut" type="xs:float" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="statisticsSlantRange"> <xs:annotation> <xs:documentation>affected pixel in interferogram</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="percentageLayover" type="xs:float"/> <xs:element name="percentageShadow" type="xs:float"/> <xs:element name="percentageMCFResPos" type="xs:float"/> <xs:element name="percentageMCFResNeg" type="xs:float"/> <xs:element name="percentageMCFSingleCuts" type="xs:float"/> <xs:element name="percentageMCFMultiCuts" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="statisticsDEMUnwrapping" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="ratioRadargramRegions" type="xs:float"/> <xs:element name="phaseAdjustPercentageLowCoh" type="xs:float"/> <xs:element name="phaseAdjustLowCoh" type="xs:float"/> <xs:element name="phaseAdjustHighCoh" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChanged" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedDEM" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedLand" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coherenceHistogram"> <xs:annotation> <xs:documentation>coherence distribution. currently 50 bins for 0.0 to 1.0</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:int"> <xs:attribute name="num" use="required"> <xs:annotation> <xs:documentation>running number starting with zero</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:unsignedShort"> <xs:minInclusive value="0"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coherenceToHeightErrorLUT"> <xs:annotation> <xs:documentation>coherence to height calculation for HEM values</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" maxOccurs="unbounded"> <xs:complexType>





<xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="coh" type="xs:double" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="productQuality"> <xs:complexType> <xs:sequence> <xs:element name="datatakeQuality"> <xs:annotation> <xs:documentation>for entire datatake (screening results during DEM generation)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap (azimuth)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeCoverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap range</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedCoverage" type="xs:double"> <xs:annotation> <xs:documentation>3dB illumination of echo window</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedRangeCoverage" type="xs:double"/> <xs:element name="commonDoppler"> <xs:complexType> <xs:sequence> <xs:element name="dopplerQuality" type="xs:double"> <xs:annotation> <xs:documentation>fractional</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dopplerBandwidthQuality" type="xs:double"> <xs:annotation> <xs:documentation>fraction of spectral overlap (coarse)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMin" type="xs:double"> <xs:annotation> <xs:documentation>difference between (bistatic) Doppler centroids</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMax" type="xs:double"/> <xs:element name="midRangeRelDopplerShiftMean" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SyncPulseEvaluation"> <xs:annotation> <xs:documentation>also included for monostatic data (quality is then 1.0)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="evaluationQuality" type="xs:double"/> <xs:element name="useDriftGapQuality" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>





</xs:sequence> </xs:complexType> </xs:element> <xs:element name="qualityWarningFlag" type="xs:boolean"> <xs:annotation> <xs:documentation>Were QA-Warnings encountered during processing (not all are considered)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolutionSat1" type="xs:double"> <xs:annotation> <xs:documentation>SSC ground resolution</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolutionSat2" type="xs:double"> <xs:annotation> <xs:documentation>before filtering and coreg (!)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolution" type="xs:double"> <xs:annotation> <xs:documentation>for CoSSC = min (1,2) for satellite data security regulations</xs:documentation> </xs:annotation> </xs:element> <xs:element name="phaseInformationIncluded" type="xs:boolean"> <xs:annotation> <xs:documentation>always TRUE ( for satellite data security regulations)</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productComponents

diagram

properties isRef 0 content complex

children component

annotation documentation Lists and points to the product components.

source <xs:element name="productComponents"> <xs:annotation> <xs:documentation>Lists and points to the product components.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="component" type="componentType" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productComponents/component





diagram

type componentType


children name type qualityInfo file instrument

attributes Name Type Use Default Fixed Annotation componentClass xs:string required documentation helps to decide

how the component is archived imageData, quicklook, browseComponent, annotation, auxRasterFiles, mapPlot, undef1, ... , undef9

source <xs:element name="component" type="componentType" maxOccurs="unbounded"/>

element cossc_product/productInfo





diagram


children productType productVariant processingStepsPerformed

annotation documentation high level info

source <xs:element name="productInfo"> <xs:annotation> <xs:documentation>high level info</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="productType" type="string128"> <xs:annotation> <xs:documentation>CoSSC</xs:documentation> </xs:annotation> </xs:element> <xs:element name="productVariant" type="string128"> <xs:annotation> <xs:documentation>standard or experimental</xs:documentation> </xs:annotation> </xs:element> <xs:element name="processingStepsPerformed"> <xs:annotation> <xs:documentation>processing level</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bistaticCorrections" type="xs:boolean"/> <xs:element name="coregistration" type="xs:boolean"/> <xs:element name="spectralFilteringAzimuth" type="xs:boolean"/> <xs:element name="spectralFilteringRange" type="xs:boolean"/> <xs:element name="interferogramGeneration" type="xs:boolean"/> <xs:element name="phaseUnwrapping" type="xs:boolean"/> <xs:element name="phaseUnwrappingDualBL" type="xs:boolean"/> <xs:element name="phaseUnwrappingMultiBL" type="xs:boolean"/> <xs:element name="rawDEMGeneration" type="xs:boolean"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productInfo/productType

diagram





type string128

properties isRef 0 content simple

facets maxLength 128

annotation documentation CoSSC

source <xs:element name="productType" type="string128"> <xs:annotation> <xs:documentation>CoSSC</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productInfo/productVariant

diagram

type string128



annotation documentation standard or experimental

source <xs:element name="productVariant" type="string128"> <xs:annotation> <xs:documentation>standard or experimental</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productInfo/processingStepsPerformed





diagram


children bistaticCorrections coregistration spectralFilteringAzimuth spectralFilteringRange interferogramGeneration phaseUnwrapping phaseUnwrappingDualBL phaseUnwrappingMultiBL rawDEMGeneration

annotation documentation processing level

source <xs:element name="processingStepsPerformed"> <xs:annotation> <xs:documentation>processing level</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bistaticCorrections" type="xs:boolean"/> <xs:element name="coregistration" type="xs:boolean"/> <xs:element name="spectralFilteringAzimuth" type="xs:boolean"/> <xs:element name="spectralFilteringRange" type="xs:boolean"/> <xs:element name="interferogramGeneration" type="xs:boolean"/> <xs:element name="phaseUnwrapping" type="xs:boolean"/> <xs:element name="phaseUnwrappingDualBL" type="xs:boolean"/> <xs:element name="phaseUnwrappingMultiBL" type="xs:boolean"/> <xs:element name="rawDEMGeneration" type="xs:boolean"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productInfo/processingStepsPerformed/bistaticCorrections

diagram

type xs:boolean






source <xs:element name="bistaticCorrections" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/coregistration

diagram

type xs:boolean


source <xs:element name="coregistration" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/spectralFilteringAzimuth

diagram

type xs:boolean


source <xs:element name="spectralFilteringAzimuth" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/spectralFilteringRange

diagram

type xs:boolean


source <xs:element name="spectralFilteringRange" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/interferogramGeneration

diagram

type xs:boolean






source <xs:element name="interferogramGeneration" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/phaseUnwrapping

diagram

type xs:boolean


source <xs:element name="phaseUnwrapping" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/phaseUnwrappingDualBL

diagram

type xs:boolean


source <xs:element name="phaseUnwrappingDualBL" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/phaseUnwrappingMultiBL

diagram

type xs:boolean


source <xs:element name="phaseUnwrappingMultiBL" type="xs:boolean"/>

element cossc_product/productInfo/processingStepsPerformed/rawDEMGeneration

diagram

type xs:boolean






source <xs:element name="rawDEMGeneration" type="xs:boolean"/>

element cossc_product/commonAcquisitionInfo

diagram


children missionID cooperativeMode satelliteIDsat1 satelliteIDsat2 inSARmasterID operationsInfo acquisitionGeometry acquisitionMode

annotation documentation describing the joint acquisition. Details on the individual acquisitions are found in the level 1b annotation of each SSC component

source <xs:element name="commonAcquisitionInfo"> <xs:annotation> <xs:documentation>describing the joint acquisition. Details on the individual acquisitions are found in the level 1b annotation of each SSC component</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="missionID" type="string80"> <xs:annotation> <xs:documentation>TDM-1</xs:documentation> </xs:annotation> </xs:element> <xs:element name="cooperativeMode" type="string80"> <xs:annotation> <xs:documentation>common coop mode bistatic, pursuitMonostatic, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="satelliteIDsat1" type="string80"/>





<xs:element name="satelliteIDsat2" type="string80"> <xs:annotation> <xs:documentation>TSX-1, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="inSARmasterID" type="string80"> <xs:annotation> <xs:documentation>logical ID (SAT1, SAT2)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="operationsInfo"> <xs:annotation> <xs:documentation>processing order and data take IDs</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="TAPtakeID" type="string80"/> <xs:element name="acquisitionItemID" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>Unique Acquisition Item ID</xs:documentation> </xs:annotation> </xs:element> <xs:element name="appliedToID" type="string80"> <xs:annotation> <xs:documentation>data takes used for DEM generation or experimental products.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="processingPriority" type="string80"/> <xs:element name="operationsTypeSat1" type="string80"> <xs:annotation> <xs:documentation>OPERATIONAL, TEST, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="operationsTypeSat2" type="string80"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="acquisitionGeometry"> <xs:annotation> <xs:documentation>coarse parameters (of entire data take / scene)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="effectiveBaseline" type="xs:double"/> <xs:element name="heightOfAmbiguity" type="xs:double"/> <xs:element name="distanceActivePos" type="xs:double"/> <xs:element name="distanceTracks" type="xs:double"/> <xs:element name="orbitDirection" type="string80"> <xs:annotation> <xs:documentation>ascending / descending A/D</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lookDirection" type="string80"> <xs:annotation> <xs:documentation>left/right R / L</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="acquisitionMode" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>of each instrument</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="cooperativeInstrumentMode" type="string80"> <xs:annotation> <xs:documentation>bistaticActive, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStartTime" type="string80">





<xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStopTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="imagingMode" type="string80"> <xs:annotation> <xs:documentation>SM, SL ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="polarizationMode" type="string80"> <xs:annotation> <xs:documentation>S, D ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="polarizationList"> <xs:annotation> <xs:documentation>polarization layer list (HH, VV, HV, VH) </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="polLayer" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="antennaReceiveConfiguration" type="string80"> <xs:annotation> <xs:documentation>SRA, DRA</xs:documentation> </xs:annotation> </xs:element> <xs:element name="elevationBeamConfiguration" type="string80"> <xs:annotation> <xs:documentation>e.g. tanDEM_a1_050</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthClass"> <xs:complexType> <xs:sequence> <xs:element name="rgBW" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"> <xs:annotation> <xs:documentation>SAT1 / SAT2</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/missionID

diagram

type string80

properties isRef 0





content simple

facets maxLength 80

annotation documentation TDM-1

source <xs:element name="missionID" type="string80"> <xs:annotation> <xs:documentation>TDM-1</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/cooperativeMode

diagram

type string80


facets maxLength 80

annotation documentation common coop mode bistatic, pursuitMonostatic, ...

source <xs:element name="cooperativeMode" type="string80"> <xs:annotation> <xs:documentation>common coop mode bistatic, pursuitMonostatic, ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/satelliteIDsat1

diagram

type string80


facets maxLength 80

source <xs:element name="satelliteIDsat1" type="string80"/>

element cossc_product/commonAcquisitionInfo/satelliteIDsat2

diagram





type string80


facets maxLength 80

annotation documentation TSX-1, ...

source <xs:element name="satelliteIDsat2" type="string80"> <xs:annotation> <xs:documentation>TSX-1, ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/inSARmasterID

diagram

type string80


facets maxLength 80

annotation documentation logical ID (SAT1, SAT2)

source <xs:element name="inSARmasterID" type="string80"> <xs:annotation> <xs:documentation>logical ID (SAT1, SAT2)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/operationsInfo

diagram






children TAPtakeID acquisitionItemID appliedToID processingPriority operationsTypeSat1 operationsTypeSat2

annotation documentation processing order and data take IDs

source <xs:element name="operationsInfo"> <xs:annotation> <xs:documentation>processing order and data take IDs</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="TAPtakeID" type="string80"/> <xs:element name="acquisitionItemID" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>Unique Acquisition Item ID</xs:documentation> </xs:annotation> </xs:element> <xs:element name="appliedToID" type="string80"> <xs:annotation> <xs:documentation>data takes used for DEM generation or experimental products.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="processingPriority" type="string80"/> <xs:element name="operationsTypeSat1" type="string80"> <xs:annotation> <xs:documentation>OPERATIONAL, TEST, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="operationsTypeSat2" type="string80"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/operationsInfo/TAPtakeID

diagram

type string80


facets maxLength 80

source <xs:element name="TAPtakeID" type="string80"/>

element cossc_product/commonAcquisitionInfo/operationsInfo/acquisitionItemID

diagram

type xs:int

properties isRef 0





content simple

annotation documentation Unique Acquisition Item ID

source <xs:element name="acquisitionItemID" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>Unique Acquisition Item ID</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/operationsInfo/appliedToID

diagram

type string80


facets maxLength 80

annotation documentation data takes used for DEM generation or experimental products.

source <xs:element name="appliedToID" type="string80"> <xs:annotation> <xs:documentation>data takes used for DEM generation or experimental products.</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/operationsInfo/processingPriority

diagram

type string80


facets maxLength 80

source <xs:element name="processingPriority" type="string80"/>

element cossc_product/commonAcquisitionInfo/operationsInfo/operationsTypeSat1

diagram

type string80






facets maxLength 80

annotation documentation OPERATIONAL, TEST, ...

source <xs:element name="operationsTypeSat1" type="string80"> <xs:annotation> <xs:documentation>OPERATIONAL, TEST, ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/operationsInfo/operationsTypeSat2

diagram

type string80


facets maxLength 80

source <xs:element name="operationsTypeSat2" type="string80"/>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry

diagram


children effectiveBaseline heightOfAmbiguity distanceActivePos distanceTracks orbitDirection lookDirection

annotation documentation coarse parameters (of entire data take / scene)

source <xs:element name="acquisitionGeometry"> <xs:annotation>





<xs:documentation>coarse parameters (of entire data take / scene)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="effectiveBaseline" type="xs:double"/> <xs:element name="heightOfAmbiguity" type="xs:double"/> <xs:element name="distanceActivePos" type="xs:double"/> <xs:element name="distanceTracks" type="xs:double"/> <xs:element name="orbitDirection" type="string80"> <xs:annotation> <xs:documentation>ascending / descending A/D</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lookDirection" type="string80"> <xs:annotation> <xs:documentation>left/right R / L</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/effectiveBaseline

diagram

type xs:double


source <xs:element name="effectiveBaseline" type="xs:double"/>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/heightOfAmbiguity

diagram

type xs:double


source <xs:element name="heightOfAmbiguity" type="xs:double"/>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/distanceActivePos

diagram

type xs:double






source <xs:element name="distanceActivePos" type="xs:double"/>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/distanceTracks

diagram

type xs:double


source <xs:element name="distanceTracks" type="xs:double"/>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/orbitDirection

diagram

type string80


facets maxLength 80

annotation documentation ascending / descending A/D

source <xs:element name="orbitDirection" type="string80"> <xs:annotation> <xs:documentation>ascending / descending A/D</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionGeometry/lookDirection

diagram

type string80


facets maxLength 80

annotation documentation left/right R / L

source <xs:element name="lookDirection" type="string80"> <xs:annotation> <xs:documentation>left/right R / L</xs:documentation>





</xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode

diagram


children cooperativeInstrumentMode datatakeStartTime datatakeStopTime imagingMode polarizationMode polarizationList antennaReceiveConfiguration elevationBeamConfiguration rangeBandwidthClass

attributes Name Type Use Default Fixed Annotation satID string20 required documentation SAT1

/ SAT2

annotation documentation of each instrument

source <xs:element name="acquisitionMode" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>of each instrument</xs:documentation> </xs:annotation>





<xs:complexType> <xs:sequence> <xs:element name="cooperativeInstrumentMode" type="string80"> <xs:annotation> <xs:documentation>bistaticActive, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStartTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="datatakeStopTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element> <xs:element name="imagingMode" type="string80"> <xs:annotation> <xs:documentation>SM, SL ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="polarizationMode" type="string80"> <xs:annotation> <xs:documentation>S, D ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="polarizationList"> <xs:annotation> <xs:documentation>polarization layer list (HH, VV, HV, VH) </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="polLayer" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="antennaReceiveConfiguration" type="string80"> <xs:annotation> <xs:documentation>SRA, DRA</xs:documentation> </xs:annotation> </xs:element> <xs:element name="elevationBeamConfiguration" type="string80"> <xs:annotation> <xs:documentation>e.g. tanDEM_a1_050</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthClass"> <xs:complexType> <xs:sequence> <xs:element name="rgBW" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"> <xs:annotation> <xs:documentation>SAT1 / SAT2</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/cooperativeInstrumentMode

diagram





type string80


facets maxLength 80

annotation documentation bistaticActive, ...

source <xs:element name="cooperativeInstrumentMode" type="string80"> <xs:annotation> <xs:documentation>bistaticActive, ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/datatakeStartTime

diagram

type string80


facets maxLength 80

annotation documentation UTC time

source <xs:element name="datatakeStartTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/datatakeStopTime

diagram

type string80


facets maxLength 80

annotation documentation UTC time

source <xs:element name="datatakeStopTime" type="string80"> <xs:annotation> <xs:documentation>UTC time</xs:documentation> </xs:annotation>





</xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/imagingMode

diagram

type string80


facets maxLength 80

annotation documentation SM, SL ...

source <xs:element name="imagingMode" type="string80"> <xs:annotation> <xs:documentation>SM, SL ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/polarizationMode

diagram

type string80


facets maxLength 80

annotation documentation S, D ...

source <xs:element name="polarizationMode" type="string80"> <xs:annotation> <xs:documentation>S, D ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/polarizationList

diagram






children polLayer

annotation documentation polarization layer list (HH, VV, HV, VH)

source <xs:element name="polarizationList"> <xs:annotation> <xs:documentation>polarization layer list (HH, VV, HV, VH) </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="polLayer" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/polarizationList/polLayer

diagram

type string80


facets maxLength 80

source <xs:element name="polLayer" type="string80" maxOccurs="unbounded"/>

element cossc_product/commonAcquisitionInfo/acquisitionMode/antennaReceiveConfiguration

diagram

type string80


facets maxLength 80

annotation documentation SRA, DRA

source <xs:element name="antennaReceiveConfiguration" type="string80"> <xs:annotation> <xs:documentation>SRA, DRA</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/elevationBeamConfiguration





diagram

type string80


facets maxLength 80

annotation documentation e.g. tanDEM_a1_050

source <xs:element name="elevationBeamConfiguration" type="string80"> <xs:annotation> <xs:documentation>e.g. tanDEM_a1_050</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/rangeBandwidthClass

diagram


children rgBW

source <xs:element name="rangeBandwidthClass"> <xs:complexType> <xs:sequence> <xs:element name="rgBW" type="string80" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonAcquisitionInfo/acquisitionMode/rangeBandwidthClass/rgBW

diagram

type string80


facets maxLength 80

source <xs:element name="rgBW" type="string80" maxOccurs="unbounded"/>

element cossc_product/commonSceneInfo





diagram


children sceneIndex totalScenes sceneCornerCoord sceneCenterCoord headingAngle

source <xs:element name="commonSceneInfo"> <xs:complexType> <xs:sequence> <xs:element name="sceneIndex" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>scene index number</xs:documentation> </xs:annotation> </xs:element> <xs:element name="totalScenes" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>geographic frames/scenes of this datatake</xs:documentation> </xs:annotation> </xs:element> <xs:element name="sceneCornerCoord" minOccurs="4" maxOccurs="4"> <xs:annotation> <xs:documentation>geographic corner coords of the common scene. early_az_near...</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude, positive towards east</xs:documentation> </xs:annotation> </xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>





<xs:element name="sceneCenterCoord"> <xs:annotation> <xs:documentation>geographic coordinates</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude positive towards east</xs:documentation> </xs:annotation> </xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="headingAngle" type="xs:float"> <xs:annotation> <xs:documentation>rotation of azimuth heading clock wise w.r.t. North at mid-scene in degree</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonSceneInfo/sceneIndex

diagram

type xs:int


annotation documentation scene index number

source <xs:element name="sceneIndex" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>scene index number</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/totalScenes

diagram

type xs:int

properties isRef 0





content simple

annotation documentation geographic frames/scenes of this datatake

source <xs:element name="totalScenes" type="xs:int" minOccurs="0"> <xs:annotation> <xs:documentation>geographic frames/scenes of this datatake</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/sceneCornerCoord

diagram


children lat lon incidenceAngle

annotation documentation geographic corner coords of the common scene. early_az_near...

source <xs:element name="sceneCornerCoord" minOccurs="4" maxOccurs="4"> <xs:annotation> <xs:documentation>geographic corner coords of the common scene. early_az_near...</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude, positive towards east</xs:documentation> </xs:annotation> </xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonSceneInfo/sceneCornerCoord/lat





diagram

type xs:float


annotation documentation geographical latitude positive towards north

source <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/sceneCornerCoord/lon

diagram

type xs:float


annotation documentation geographical longitude, positive towards east

source <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude, positive towards east</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/sceneCornerCoord/incidenceAngle

diagram

type xs:float


annotation documentation incidence angle

source <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element>





element cossc_product/commonSceneInfo/sceneCenterCoord

diagram


children lat lon incidenceAngle

annotation documentation geographic coordinates

source <xs:element name="sceneCenterCoord"> <xs:annotation> <xs:documentation>geographic coordinates</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude positive towards east</xs:documentation> </xs:annotation> </xs:element> <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/commonSceneInfo/sceneCenterCoord/lat

diagram

type xs:float






annotation documentation geographical latitude positive towards north

source <xs:element name="lat" type="xs:float"> <xs:annotation> <xs:documentation>geographical latitude positive towards north</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/sceneCenterCoord/lon

diagram

type xs:float


annotation documentation geographical longitude positive towards east

source <xs:element name="lon" type="xs:float"> <xs:annotation> <xs:documentation>geographical longitude positive towards east</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/sceneCenterCoord/incidenceAngle

diagram

type xs:float


annotation documentation incidence angle

source <xs:element name="incidenceAngle" type="xs:float"> <xs:annotation> <xs:documentation>incidence angle</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/commonSceneInfo/headingAngle

diagram

type xs:float






annotation documentation rotation of azimuth heading clock wise w.r.t. North at mid-scene in degree

source <xs:element name="headingAngle" type="xs:float"> <xs:annotation> <xs:documentation>rotation of azimuth heading clock wise w.r.t. North at mid-scene in degree</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo

diagram


children orbitHeader

annotation documentation info on baseline or master orbit used. Statevectors of baseline products are to be found in the "level 1b" annotation in the platform/orbit section. Baselines are converted to orbit information.

source <xs:element name="baselineInfo"> <xs:annotation> <xs:documentation>info on baseline or master orbit used. Statevectors of baseline products are to be found in the "level 1b" annotation in the platform/orbit section. Baselines are converted to orbit information.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="orbitHeader"> <xs:annotation> <xs:documentation>baseline header is converted into orbitHeader format for convinience</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>of MOS / GFZ</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string255"> <xs:attribute name="version" type="string80"> <xs:annotation> <xs:documentation>Software version number of the generation system</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="sensor" type="string80"> <xs:annotation> <xs:documentation>PROP for predicted orbit GPSS for single GPS





GPSD for differential GPS, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="accuracy" type="string80"> <xs:annotation> <xs:documentation>COAR PREC CALB</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVectorRefFrame" type="string80"> <xs:annotation> <xs:documentation>state vector reference frame indicator e.g. WGS84</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coordSystemTransfrom" minOccurs="0"> <xs:annotation> <xs:documentation>applied transform if orbit data source was not in ref frame</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rotMatrixCoeff" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="i" type="string80" use="required"/> <xs:attribute name="j" type="string80" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="shift" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="stateVectorRefTime" type="string80"> <xs:annotation> <xs:documentation>state vector reference time indicator e.g. GPS</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVecFormat" type="string80"> <xs:annotation> <xs:documentation>e.g. units</xs:documentation> </xs:annotation> </xs:element> <xs:element name="numStateVectors" type="xs:int"> <xs:annotation> <xs:documentation>total number of state vectors</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTime"> <xs:complexType> <xs:sequence> <xs:element name="firstStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of first state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="lastStateTime">





<xs:complexType> <xs:sequence> <xs:element name="lastStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of last state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="stateVectorTimeSpacing" type="xs:double"> <xs:annotation> <xs:documentation>[sec] state vector time spacing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="positionAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element> <xs:element name="velocityAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element> <xs:element name="recProcessingTechnique" type="string80"> <xs:annotation> <xs:documentation>recommended orbit interpolation or approximation technique</xs:documentation> </xs:annotation> </xs:element> <xs:element name="recPolDegree" type="xs:int"> <xs:annotation> <xs:documentation>recommended interpolation polynomial degree</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dataGapIndicator" type="xs:int"> <xs:annotation> <xs:documentation>number of state vectors with qualInd=0</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader





diagram






children generationSystem sensor accuracy stateVectorRefFrame coordSystemTransfrom stateVectorRefTime stateVecFormat numStateVectors firstStateTime lastStateTime stateVectorTimeSpacing positionAccuracyMargin velocityAccuracyMargin recProcessingTechnique recPolDegree dataGapIndicator

annotation documentation baseline header is converted into orbitHeader format for convinience

source <xs:element name="orbitHeader"> <xs:annotation> <xs:documentation>baseline header is converted into orbitHeader format for convinience</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>of MOS / GFZ</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string255"> <xs:attribute name="version" type="string80"> <xs:annotation> <xs:documentation>Software version number of the generation system</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="sensor" type="string80"> <xs:annotation> <xs:documentation>PROP for predicted orbit GPSS for single GPS GPSD for differential GPS, ...</xs:documentation> </xs:annotation> </xs:element> <xs:element name="accuracy" type="string80"> <xs:annotation> <xs:documentation>COAR PREC CALB</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVectorRefFrame" type="string80"> <xs:annotation> <xs:documentation>state vector reference frame indicator e.g. WGS84</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coordSystemTransfrom" minOccurs="0"> <xs:annotation> <xs:documentation>applied transform if orbit data source was not in ref frame</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rotMatrixCoeff" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="i" type="string80" use="required"/> <xs:attribute name="j" type="string80" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="shift" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>





<xs:element name="stateVectorRefTime" type="string80"> <xs:annotation> <xs:documentation>state vector reference time indicator e.g. GPS</xs:documentation> </xs:annotation> </xs:element> <xs:element name="stateVecFormat" type="string80"> <xs:annotation> <xs:documentation>e.g. units</xs:documentation> </xs:annotation> </xs:element> <xs:element name="numStateVectors" type="xs:int"> <xs:annotation> <xs:documentation>total number of state vectors</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTime"> <xs:complexType> <xs:sequence> <xs:element name="firstStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of first state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="lastStateTime"> <xs:complexType> <xs:sequence> <xs:element name="lastStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of last state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="stateVectorTimeSpacing" type="xs:double"> <xs:annotation> <xs:documentation>[sec] state vector time spacing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="positionAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element> <xs:element name="velocityAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation>





</xs:annotation> </xs:element> <xs:element name="recProcessingTechnique" type="string80"> <xs:annotation> <xs:documentation>recommended orbit interpolation or approximation technique</xs:documentation> </xs:annotation> </xs:element> <xs:element name="recPolDegree" type="xs:int"> <xs:annotation> <xs:documentation>recommended interpolation polynomial degree</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dataGapIndicator" type="xs:int"> <xs:annotation> <xs:documentation>number of state vectors with qualInd=0</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader/generationSystem

diagram

type extension of string255



attributes Name Type Use Default Fixed Annotation version string80 documentation Software

version number of the generation system

annotation documentation of MOS / GFZ

source <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>of MOS / GFZ</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string255"> <xs:attribute name="version" type="string80"> <xs:annotation> <xs:documentation>Software version number of the generation system</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>





element cossc_product/baselineInfo/orbitHeader/sensor

diagram

type string80


facets maxLength 80

annotation documentation PROP for predicted orbit GPSS for single GPS GPSD for differential GPS, ...

source <xs:element name="sensor" type="string80"> <xs:annotation> <xs:documentation>PROP for predicted orbit GPSS for single GPS GPSD for differential GPS, ...</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/accuracy

diagram

type string80


facets maxLength 80

annotation documentation COAR PREC CALB

source <xs:element name="accuracy" type="string80"> <xs:annotation> <xs:documentation>COAR PREC CALB</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/stateVectorRefFrame

diagram





type string80


facets maxLength 80

annotation documentation state vector reference frame indicatore.g. WGS84

source <xs:element name="stateVectorRefFrame" type="string80"> <xs:annotation> <xs:documentation>state vector reference frame indicator e.g. WGS84</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/coordSystemTransfrom

diagram


children rotMatrixCoeff shift

annotation documentation applied transform if orbit data source was not in ref frame

source <xs:element name="coordSystemTransfrom" minOccurs="0"> <xs:annotation> <xs:documentation>applied transform if orbit data source was not in ref frame</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rotMatrixCoeff" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="i" type="string80" use="required"/> <xs:attribute name="j" type="string80" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="shift" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader/coordSystemTransfrom/rotMatrixCoeff





diagram

type extension of xs:double


attributes Name Type Use Default Fixed Annotation

i string80 required j string80 required

source <xs:element name="rotMatrixCoeff" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="i" type="string80" use="required"/> <xs:attribute name="j" type="string80" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader/coordSystemTransfrom/shift

diagram

type xs:double


source <xs:element name="shift" type="xs:double"/>

element cossc_product/baselineInfo/orbitHeader/stateVectorRefTime

diagram

type string80


facets maxLength 80





annotation documentation state vector reference time indicatore.g. GPS

source <xs:element name="stateVectorRefTime" type="string80"> <xs:annotation> <xs:documentation>state vector reference time indicator e.g. GPS</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/stateVecFormat

diagram

type string80


facets maxLength 80

annotation documentation e.g. units

source <xs:element name="stateVecFormat" type="string80"> <xs:annotation> <xs:documentation>e.g. units</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/numStateVectors

diagram

type xs:int


annotation documentation total number of state vectors

source <xs:element name="numStateVectors" type="xs:int"> <xs:annotation> <xs:documentation>total number of state vectors</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/firstStateTime





diagram


children firstStateTimeUTC firstStateTimeGPS firstStateTimeGPSFraction

source <xs:element name="firstStateTime"> <xs:complexType> <xs:sequence> <xs:element name="firstStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of first state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="firstStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader/firstStateTime/firstStateTimeUTC

diagram

type string80


facets maxLength 80

annotation documentation UTC time of first state vector

source <xs:element name="firstStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of first state vector</xs:documentation>






element cossc_product/baselineInfo/orbitHeader/firstStateTime/firstStateTimeGPS

diagram

type xs:long


annotation documentation GPS time of first state vector (integer second counter)

source <xs:element name="firstStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/firstStateTime/firstStateTimeGPSFraction

diagram

type xs:double


annotation documentation fraction GPS time of first state vector as fraction of second

source <xs:element name="firstStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/lastStateTime





diagram


children lastStateTimeUTC lastStateTimeGPS lastStateTimeGPSFraction

source <xs:element name="lastStateTime"> <xs:complexType> <xs:sequence> <xs:element name="lastStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of last state vector</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="lastStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/baselineInfo/orbitHeader/lastStateTime/lastStateTimeUTC

diagram

type string80


facets maxLength 80

annotation documentation UTC time of last state vector

source <xs:element name="lastStateTimeUTC" type="string80"> <xs:annotation> <xs:documentation>UTC time of last state vector</xs:documentation>






element cossc_product/baselineInfo/orbitHeader/lastStateTime/lastStateTimeGPS

diagram

type xs:long


annotation documentation GPS time of first state vector (integer second counter)

source <xs:element name="lastStateTimeGPS" type="xs:long"> <xs:annotation> <xs:documentation>GPS time of first state vector (integer second counter)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/lastStateTime/lastStateTimeGPSFraction

diagram

type xs:double


annotation documentation fraction GPS time of first state vector as fraction of second

source <xs:element name="lastStateTimeGPSFraction" type="xs:double"> <xs:annotation> <xs:documentation>fraction GPS time of first state vector as fraction of second</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/stateVectorTimeSpacing

diagram

type xs:double






annotation documentation [sec] state vector time spacing

source <xs:element name="stateVectorTimeSpacing" type="xs:double"> <xs:annotation> <xs:documentation>[sec] state vector time spacing</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/positionAccuracyMargin

diagram

type xs:double


annotation documentation 3D RMS value

source <xs:element name="positionAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/velocityAccuracyMargin

diagram

type xs:double


annotation documentation 3D RMS value

source <xs:element name="velocityAccuracyMargin" type="xs:double"> <xs:annotation> <xs:documentation>3D RMS value</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/recProcessingTechnique

diagram

type string80






facets maxLength 80

annotation documentation recommended orbit interpolation or approximation technique

source <xs:element name="recProcessingTechnique" type="string80"> <xs:annotation> <xs:documentation>recommended orbit interpolation or approximation technique</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/recPolDegree

diagram

type xs:int


annotation documentation recommended interpolation polynomial degree

source <xs:element name="recPolDegree" type="xs:int"> <xs:annotation> <xs:documentation>recommended interpolation polynomial degree</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/baselineInfo/orbitHeader/dataGapIndicator

diagram

type xs:int


annotation documentation number of state vectors with qualInd=0

source <xs:element name="dataGapIndicator" type="xs:int"> <xs:annotation> <xs:documentation>number of state vectors with qualInd=0</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo





diagram


children inputData bistaticProcessing coregistration spectralFiltering inSARProcessing

source <xs:element name="processingInfo"> <xs:complexType> <xs:sequence> <xs:element name="inputData"> <xs:complexType> <xs:sequence> <xs:element name="orderType" type="string80"> <xs:annotation> <xs:documentation>TDM-PRCSCR->RDEMGEN</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMajorVersion" type="string80"> <xs:annotation> <xs:documentation>Interferometric Aux product (for the common combined instrument information used for (biststic) processing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMinorVersion" type="string80"/> <xs:element name="ifAuxGenerationTime" type="string80"/> <xs:element name="baselineProductUsed" type="xs:boolean"> <xs:annotation> <xs:documentation>was a baseline (of sufficient quality) used for processing</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="bistaticProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>Is also given for monostatic data since the correctrions (of zero drifts for monostatic data) are always applied.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="syncPulseEvaluation" minOccurs="0" maxOccurs="unbounded"> <xs:annotation>





<xs:documentation>characteristics of the sync pulses</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="driftHighPRF" type="xs:double"/> <xs:element name="driftLowPRF" type="xs:double"/> <xs:element name="missingQuality" type="xs:double"/> <xs:element name="blockQuality" type="xs:double"/> <xs:element name="powerQuality" type="xs:double"/> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"/> </xs:complexType> </xs:element> <xs:element name="averageFastTimeCorrection" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>calculated from sat 1/ 2 sync analysis</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="satID" type="string20" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coregistration" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR coregistration step result. Input/output rasters. Start times of master/slave min max shifts in pixe applied on the slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="masterFirstAzTime" type="xs:double"/> <xs:element name="masterFirstRgTime" type="xs:double"/> <xs:element name="slaveFirstAzTime" type="xs:double"/> <xs:element name="slaveFirstRgTime" type="xs:double"/> <xs:element name="slaveShiftAzMin" type="xs:double" minOccurs="0"> <xs:annotation> <xs:documentation>[samples/lines]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="slaveShiftAzMax" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMin" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMax" type="xs:double" minOccurs="0"/> <xs:element name="coregRaster"> <xs:annotation> <xs:documentation>output size</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputMasterRaster"> <xs:annotation> <xs:documentation>input size master</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputSlaveRaster"> <xs:annotation> <xs:documentation>input size slave</xs:documentation>





</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="spectralFiltering" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR processing common bandwidth filtering</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="azimuthBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="azimuthHammingCoef" type="xs:double"/> <xs:element name="rangeHammingCoef" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inSARProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>main parameters for InSAR processing</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="observationMode" type="string80"> <xs:annotation> <xs:documentation>InSAR mode: dual_pass=monostatic, single_pass = bistatic</xs:documentation> </xs:annotation> </xs:element> <xs:element name="looks"> <xs:complexType> <xs:sequence> <xs:element name="range" type="xs:int"/> <xs:element name="azimuth" type="xs:int"/> <xs:element name="eqNumLooks" type="xs:double"/> <xs:element name="ifResolution" type="xs:double"> <xs:annotation> <xs:documentation>mean</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ifRaster"> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="averageCoherence" type="xs:double"> <xs:annotation> <xs:documentation>of total scene</xs:documentation> </xs:annotation> </xs:element> <xs:element name="localHeight" type="xs:double"> <xs:annotation>





<xs:documentation>mean heigt (reference)</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/inputData

diagram


children orderType ifAuxProductMajorVersion ifAuxProductMinorVersion ifAuxGenerationTime baselineProductUsed

source <xs:element name="inputData"> <xs:complexType> <xs:sequence> <xs:element name="orderType" type="string80"> <xs:annotation> <xs:documentation>TDM-PRCSCR->RDEMGEN</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMajorVersion" type="string80"> <xs:annotation> <xs:documentation>Interferometric Aux product (for the common combined instrument information used for (biststic) processing</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ifAuxProductMinorVersion" type="string80"/> <xs:element name="ifAuxGenerationTime" type="string80"/> <xs:element name="baselineProductUsed" type="xs:boolean"> <xs:annotation> <xs:documentation>was a baseline (of sufficient quality) used for processing</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/inputData/orderType





diagram

type string80


facets maxLength 80

annotation documentation TDM-PRCSCR->RDEMGEN

source <xs:element name="orderType" type="string80"> <xs:annotation> <xs:documentation>TDM-PRCSCR->RDEMGEN</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/inputData/ifAuxProductMajorVersion

diagram

type string80


facets maxLength 80

annotation documentation Interferometric Aux product (for the common combined instrument information used for (biststic) processing

source <xs:element name="ifAuxProductMajorVersion" type="string80"> <xs:annotation> <xs:documentation>Interferometric Aux product (for the common combined instrument information used for (biststic) processing</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/inputData/ifAuxProductMinorVersion

diagram

type string80


facets maxLength 80





source <xs:element name="ifAuxProductMinorVersion" type="string80"/>

element cossc_product/processingInfo/inputData/ifAuxGenerationTime

diagram

type string80


facets maxLength 80

source <xs:element name="ifAuxGenerationTime" type="string80"/>

element cossc_product/processingInfo/inputData/baselineProductUsed

diagram

type xs:boolean


annotation documentation was a baseline (of sufficient quality) used for processing

source <xs:element name="baselineProductUsed" type="xs:boolean"> <xs:annotation> <xs:documentation>was a baseline (of sufficient quality) used for processing</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/bistaticProcessing

diagram


children syncPulseEvaluation averageFastTimeCorrection





annotation documentation Is also given for monostatic data since the correctrions (of zero drifts for monostatic data) are always applied.

source <xs:element name="bistaticProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>Is also given for monostatic data since the correctrions (of zero drifts for monostatic data) are always applied.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="syncPulseEvaluation" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>characteristics of the sync pulses</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="driftHighPRF" type="xs:double"/> <xs:element name="driftLowPRF" type="xs:double"/> <xs:element name="missingQuality" type="xs:double"/> <xs:element name="blockQuality" type="xs:double"/> <xs:element name="powerQuality" type="xs:double"/> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"/> </xs:complexType> </xs:element> <xs:element name="averageFastTimeCorrection" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>calculated from sat 1/ 2 sync analysis</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="satID" type="string20" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation

diagram


children driftHighPRF driftLowPRF missingQuality blockQuality powerQuality






satID string20 required

annotation documentation characteristics of the sync pulses

source <xs:element name="syncPulseEvaluation" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>characteristics of the sync pulses</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="driftHighPRF" type="xs:double"/> <xs:element name="driftLowPRF" type="xs:double"/> <xs:element name="missingQuality" type="xs:double"/> <xs:element name="blockQuality" type="xs:double"/> <xs:element name="powerQuality" type="xs:double"/> </xs:sequence> <xs:attribute name="satID" type="string20" use="required"/> </xs:complexType> </xs:element>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/driftHighPRF

diagram

type xs:double


source <xs:element name="driftHighPRF" type="xs:double"/>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/driftLowPRF

diagram

type xs:double


source <xs:element name="driftLowPRF" type="xs:double"/>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/missingQuality

diagram

type xs:double

properties isRef 0





content simple

source <xs:element name="missingQuality" type="xs:double"/>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/blockQuality

diagram

type xs:double


source <xs:element name="blockQuality" type="xs:double"/>

element cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/powerQuality

diagram

type xs:double


source <xs:element name="powerQuality" type="xs:double"/>

element cossc_product/processingInfo/bistaticProcessing/averageFastTimeCorrection

diagram




satID string20 required

annotation documentation calculated from sat 1/ 2 sync analysis

source <xs:element name="averageFastTimeCorrection" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>calculated from sat 1/ 2 sync analysis</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent>





<xs:extension base="xs:double"> <xs:attribute name="satID" type="string20" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>

element cossc_product/processingInfo/coregistration

diagram


children masterFirstAzTime masterFirstRgTime slaveFirstAzTime slaveFirstRgTime slaveShiftAzMin slaveShiftAzMax slaveShiftRgMin slaveShiftRgMax coregRaster inputMasterRaster inputSlaveRaster

annotation documentation InSAR coregistration step result. Input/output rasters. Start times of master/slave min max shifts in pixe applied on the slave

source <xs:element name="coregistration" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR coregistration step result. Input/output rasters. Start times of master/slave min max shifts in pixe applied on the slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="masterFirstAzTime" type="xs:double"/> <xs:element name="masterFirstRgTime" type="xs:double"/> <xs:element name="slaveFirstAzTime" type="xs:double"/> <xs:element name="slaveFirstRgTime" type="xs:double"/> <xs:element name="slaveShiftAzMin" type="xs:double" minOccurs="0"> <xs:annotation>





<xs:documentation>[samples/lines]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="slaveShiftAzMax" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMin" type="xs:double" minOccurs="0"/> <xs:element name="slaveShiftRgMax" type="xs:double" minOccurs="0"/> <xs:element name="coregRaster"> <xs:annotation> <xs:documentation>output size</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputMasterRaster"> <xs:annotation> <xs:documentation>input size master</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="inputSlaveRaster"> <xs:annotation> <xs:documentation>input size slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/coregistration/masterFirstAzTime

diagram

type xs:double


source <xs:element name="masterFirstAzTime" type="xs:double"/>

element cossc_product/processingInfo/coregistration/masterFirstRgTime

diagram

type xs:double






source <xs:element name="masterFirstRgTime" type="xs:double"/>

element cossc_product/processingInfo/coregistration/slaveFirstAzTime

diagram

type xs:double


source <xs:element name="slaveFirstAzTime" type="xs:double"/>

element cossc_product/processingInfo/coregistration/slaveFirstRgTime

diagram

type xs:double


source <xs:element name="slaveFirstRgTime" type="xs:double"/>

element cossc_product/processingInfo/coregistration/slaveShiftAzMin

diagram

type xs:double


annotation documentation [samples/lines]

source <xs:element name="slaveShiftAzMin" type="xs:double" minOccurs="0"> <xs:annotation> <xs:documentation>[samples/lines]</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/coregistration/slaveShiftAzMax





diagram

type xs:double


source <xs:element name="slaveShiftAzMax" type="xs:double" minOccurs="0"/>

element cossc_product/processingInfo/coregistration/slaveShiftRgMin

diagram

type xs:double


source <xs:element name="slaveShiftRgMin" type="xs:double" minOccurs="0"/>

element cossc_product/processingInfo/coregistration/slaveShiftRgMax

diagram

type xs:double


source <xs:element name="slaveShiftRgMax" type="xs:double" minOccurs="0"/>

element cossc_product/processingInfo/coregistration/coregRaster

diagram


children samples lines

annotation documentation output size

source <xs:element name="coregRaster"> <xs:annotation>





<xs:documentation>output size</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/coregistration/coregRaster/samples

diagram

type xs:int


source <xs:element name="samples" type="xs:int"/>

element cossc_product/processingInfo/coregistration/coregRaster/lines

diagram

type xs:int


source <xs:element name="lines" type="xs:int"/>

element cossc_product/processingInfo/coregistration/inputMasterRaster

diagram



annotation documentation input size master

source <xs:element name="inputMasterRaster"> <xs:annotation> <xs:documentation>input size master</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence>





<xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/coregistration/inputMasterRaster/samples

diagram

type xs:int



element cossc_product/processingInfo/coregistration/inputMasterRaster/lines

diagram

type xs:int



element cossc_product/processingInfo/coregistration/inputSlaveRaster

diagram



annotation documentation input size slave

source <xs:element name="inputSlaveRaster"> <xs:annotation> <xs:documentation>input size slave</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType>





</xs:element>

element cossc_product/processingInfo/coregistration/inputSlaveRaster/samples

diagram

type xs:int



element cossc_product/processingInfo/coregistration/inputSlaveRaster/lines

diagram

type xs:int



element cossc_product/processingInfo/spectralFiltering

diagram


children azimuthBandwidthInCenter rangeBandwidthInCenter azimuthHammingCoef rangeHammingCoef

annotation documentation InSAR processing common bandwidth filtering

source <xs:element name="spectralFiltering" minOccurs="0"> <xs:annotation> <xs:documentation>InSAR processing common bandwidth filtering</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence>





<xs:element name="azimuthBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element> <xs:element name="azimuthHammingCoef" type="xs:double"/> <xs:element name="rangeHammingCoef" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/spectralFiltering/azimuthBandwidthInCenter

diagram

type xs:double


annotation documentation [Hz]

source <xs:element name="azimuthBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/spectralFiltering/rangeBandwidthInCenter

diagram

type xs:double


annotation documentation [Hz]

source <xs:element name="rangeBandwidthInCenter" type="xs:double"> <xs:annotation> <xs:documentation>[Hz]</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/spectralFiltering/azimuthHammingCoef





diagram

type xs:double


source <xs:element name="azimuthHammingCoef" type="xs:double"/>

element cossc_product/processingInfo/spectralFiltering/rangeHammingCoef

diagram

type xs:double


source <xs:element name="rangeHammingCoef" type="xs:double"/>

element cossc_product/processingInfo/inSARProcessing

diagram


children observationMode looks ifRaster averageCoherence localHeight

annotation documentation main parameters for InSAR processing

source <xs:element name="inSARProcessing" minOccurs="0"> <xs:annotation> <xs:documentation>main parameters for InSAR processing</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence>





<xs:element name="observationMode" type="string80"> <xs:annotation> <xs:documentation>InSAR mode: dual_pass=monostatic, single_pass = bistatic</xs:documentation> </xs:annotation> </xs:element> <xs:element name="looks"> <xs:complexType> <xs:sequence> <xs:element name="range" type="xs:int"/> <xs:element name="azimuth" type="xs:int"/> <xs:element name="eqNumLooks" type="xs:double"/> <xs:element name="ifResolution" type="xs:double"> <xs:annotation> <xs:documentation>mean</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ifRaster"> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="averageCoherence" type="xs:double"> <xs:annotation> <xs:documentation>of total scene</xs:documentation> </xs:annotation> </xs:element> <xs:element name="localHeight" type="xs:double"> <xs:annotation> <xs:documentation>mean heigt (reference)</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/inSARProcessing/observationMode

diagram

type string80


facets maxLength 80

annotation documentation InSAR mode: dual_pass=monostatic, single_pass = bistatic

source <xs:element name="observationMode" type="string80"> <xs:annotation> <xs:documentation>InSAR mode: dual_pass=monostatic, single_pass = bistatic</xs:documentation> </xs:annotation> </xs:element>





element cossc_product/processingInfo/inSARProcessing/looks

diagram


children range azimuth eqNumLooks ifResolution

source <xs:element name="looks"> <xs:complexType> <xs:sequence> <xs:element name="range" type="xs:int"/> <xs:element name="azimuth" type="xs:int"/> <xs:element name="eqNumLooks" type="xs:double"/> <xs:element name="ifResolution" type="xs:double"> <xs:annotation> <xs:documentation>mean</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/processingInfo/inSARProcessing/looks/range

diagram

type xs:int


source <xs:element name="range" type="xs:int"/>

element cossc_product/processingInfo/inSARProcessing/looks/azimuth

diagram

type xs:int






source <xs:element name="azimuth" type="xs:int"/>

element cossc_product/processingInfo/inSARProcessing/looks/eqNumLooks

diagram

type xs:double


source <xs:element name="eqNumLooks" type="xs:double"/>

element cossc_product/processingInfo/inSARProcessing/looks/ifResolution

diagram

type xs:double


annotation documentation mean

source <xs:element name="ifResolution" type="xs:double"> <xs:annotation> <xs:documentation>mean</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/inSARProcessing/ifRaster

diagram



source <xs:element name="ifRaster"> <xs:complexType> <xs:sequence> <xs:element name="samples" type="xs:int"/> <xs:element name="lines" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element>





element cossc_product/processingInfo/inSARProcessing/ifRaster/samples

diagram

type xs:int



element cossc_product/processingInfo/inSARProcessing/ifRaster/lines

diagram

type xs:int



element cossc_product/processingInfo/inSARProcessing/averageCoherence

diagram

type xs:double


annotation documentation of total scene

source <xs:element name="averageCoherence" type="xs:double"> <xs:annotation> <xs:documentation>of total scene</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/processingInfo/inSARProcessing/localHeight

diagram

type xs:double






annotation documentation mean heigt (reference)

source <xs:element name="localHeight" type="xs:double"> <xs:annotation> <xs:documentation>mean heigt (reference)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/rawDEMInfo





diagram


children rawDEMname postingClass absPhaseOffset coordsDEMFrame coordsDEMScene demRaster statisticsDEMScene





percentageWater statisticsDEMLand statisticsSlantRange statisticsDEMUnwrapping coherenceHistogram coherenceToHeightErrorLUT

annotation documentation mostly from DEM geocoding step. Not given for experimental products

source <xs:element name="rawDEMInfo" minOccurs="0"> <xs:annotation> <xs:documentation>mostly from DEM geocoding step. Not given for experimental products</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="rawDEMname" type="string80"> <xs:annotation> <xs:documentation>associated RawDEM product (raster file)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="postingClass" type="xs:double"> <xs:annotation> <xs:documentation>ordered DEM posting</xs:documentation> </xs:annotation> </xs:element> <xs:element name="absPhaseOffset" type="xs:double"> <xs:annotation> <xs:documentation>unwrapped phase vs. true phase difference. applied for geocoding (absolute height calibration)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coordsDEMFrame"> <xs:annotation> <xs:documentation>geographic coords of frame </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="upN" type="xs:double"/> <xs:element name="lowN" type="xs:double"/> <xs:element name="rightE" type="xs:double"/> <xs:element name="leftE" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coordsDEMScene"> <xs:annotation> <xs:documentation>DEM scene coords (early azimuth near range (eanr), etc. ...)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="eanrLat" type="xs:float"/> <xs:element name="eanrLon" type="xs:float"/> <xs:element name="eafrLat" type="xs:float"/> <xs:element name="eafrLon" type="xs:float"/> <xs:element name="lanrLat" type="xs:float"/> <xs:element name="lanrLon" type="xs:float"/> <xs:element name="lafrLat" type="xs:float"/> <xs:element name="lafrLon" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="demRaster"> <xs:annotation> <xs:documentation>in degree and lines/samples</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="spacingLat" type="xs:double"/> <xs:element name="spacingLon" type="xs:double"/> <xs:element name="nNorth" type="xs:int"/> <xs:element name="nEast" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element>





<xs:element name="statisticsDEMScene"> <xs:annotation> <xs:documentation>refers to geocoded DEM scene, its Flag Mask and HEM</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="pointsTotal" type="xs:int"/> <xs:element name="pointsShadow" type="xs:int"/> <xs:element name="pointsLayover" type="xs:int"/> <xs:element name="pointsWater" type="xs:int"/> <xs:element name="pointsMCFResPos" type="xs:int"/> <xs:element name="pointsMCFResNeg" type="xs:int"/> <xs:element name="pointsMCFSingleCut" type="xs:int"/> <xs:element name="pointsMCFMultiCut" type="xs:int"/> <xs:element name="heightMin" type="xs:float"/> <xs:element name="heightMax" type="xs:float"/> <xs:element name="heightMean" type="xs:float"/> <xs:element name="heightStdDev" type="xs:float"/> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/> <xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="percentageWater" type="xs:double"> <xs:annotation> <xs:documentation>coarse estimate from from GLOBECOVER data used for flagging</xs:documentation> </xs:annotation> </xs:element> <xs:element name="statisticsDEMLand"> <xs:annotation> <xs:documentation>statistics over GLOBE_COVER land classes</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/> <xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> <xs:element name="pointsMCFResPos" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFResNeg" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFSingleCut" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFMultiCut" type="xs:float" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="statisticsSlantRange"> <xs:annotation> <xs:documentation>affected pixel in interferogram</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="percentageLayover" type="xs:float"/> <xs:element name="percentageShadow" type="xs:float"/> <xs:element name="percentageMCFResPos" type="xs:float"/> <xs:element name="percentageMCFResNeg" type="xs:float"/> <xs:element name="percentageMCFSingleCuts" type="xs:float"/> <xs:element name="percentageMCFMultiCuts" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="statisticsDEMUnwrapping" minOccurs="0"> <xs:complexType>





<xs:sequence> <xs:element name="ratioRadargramRegions" type="xs:float"/> <xs:element name="phaseAdjustPercentageLowCoh" type="xs:float"/> <xs:element name="phaseAdjustLowCoh" type="xs:float"/> <xs:element name="phaseAdjustHighCoh" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChanged" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedDEM" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedLand" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coherenceHistogram"> <xs:annotation> <xs:documentation>coherence distribution. currently 50 bins for 0.0 to 1.0</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:int"> <xs:attribute name="num" use="required"> <xs:annotation> <xs:documentation>running number starting with zero</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:unsignedShort"> <xs:minInclusive value="0"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="coherenceToHeightErrorLUT"> <xs:annotation> <xs:documentation>coherence to height calculation for HEM values</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="coh" type="xs:double" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/rawDEMname

diagram

type string80






facets maxLength 80

annotation documentation associated RawDEM product (raster file)

source <xs:element name="rawDEMname" type="string80"> <xs:annotation> <xs:documentation>associated RawDEM product (raster file)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/rawDEMInfo/postingClass

diagram

type xs:double


annotation documentation ordered DEM posting

source <xs:element name="postingClass" type="xs:double"> <xs:annotation> <xs:documentation>ordered DEM posting</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/rawDEMInfo/absPhaseOffset

diagram

type xs:double


annotation documentation unwrapped phase vs. true phase difference. applied for geocoding (absolute height calibration)

source <xs:element name="absPhaseOffset" type="xs:double"> <xs:annotation> <xs:documentation>unwrapped phase vs. true phase difference. applied for geocoding (absolute height calibration)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/rawDEMInfo/coordsDEMFrame





diagram


children upN lowN rightE leftE

annotation documentation geographic coords of frame

source <xs:element name="coordsDEMFrame"> <xs:annotation> <xs:documentation>geographic coords of frame </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="upN" type="xs:double"/> <xs:element name="lowN" type="xs:double"/> <xs:element name="rightE" type="xs:double"/> <xs:element name="leftE" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/coordsDEMFrame/upN

diagram

type xs:double


source <xs:element name="upN" type="xs:double"/>

element cossc_product/rawDEMInfo/coordsDEMFrame/lowN

diagram

type xs:double


source <xs:element name="lowN" type="xs:double"/>





element cossc_product/rawDEMInfo/coordsDEMFrame/rightE

diagram

type xs:double


source <xs:element name="rightE" type="xs:double"/>

element cossc_product/rawDEMInfo/coordsDEMFrame/leftE

diagram

type xs:double


source <xs:element name="leftE" type="xs:double"/>

element cossc_product/rawDEMInfo/coordsDEMScene

diagram


children eanrLat eanrLon eafrLat eafrLon lanrLat lanrLon lafrLat lafrLon

annotation documentation DEM scene coords (early azimuth near range (eanr), etc. ...)





source <xs:element name="coordsDEMScene"> <xs:annotation> <xs:documentation>DEM scene coords (early azimuth near range (eanr), etc. ...)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="eanrLat" type="xs:float"/> <xs:element name="eanrLon" type="xs:float"/> <xs:element name="eafrLat" type="xs:float"/> <xs:element name="eafrLon" type="xs:float"/> <xs:element name="lanrLat" type="xs:float"/> <xs:element name="lanrLon" type="xs:float"/> <xs:element name="lafrLat" type="xs:float"/> <xs:element name="lafrLon" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/coordsDEMScene/eanrLat

diagram

type xs:float


source <xs:element name="eanrLat" type="xs:float"/>

element cossc_product/rawDEMInfo/coordsDEMScene/eanrLon

diagram

type xs:float


source <xs:element name="eanrLon" type="xs:float"/>

element cossc_product/rawDEMInfo/coordsDEMScene/eafrLat

diagram

type xs:float


source <xs:element name="eafrLat" type="xs:float"/>





element cossc_product/rawDEMInfo/coordsDEMScene/eafrLon

diagram

type xs:float


source <xs:element name="eafrLon" type="xs:float"/>

element cossc_product/rawDEMInfo/coordsDEMScene/lanrLat

diagram

type xs:float


source <xs:element name="lanrLat" type="xs:float"/>

element cossc_product/rawDEMInfo/coordsDEMScene/lanrLon

diagram

type xs:float


source <xs:element name="lanrLon" type="xs:float"/>

element cossc_product/rawDEMInfo/coordsDEMScene/lafrLat

diagram

type xs:float


source <xs:element name="lafrLat" type="xs:float"/>





element cossc_product/rawDEMInfo/coordsDEMScene/lafrLon

diagram

type xs:float


source <xs:element name="lafrLon" type="xs:float"/>

element cossc_product/rawDEMInfo/demRaster

diagram


children spacingLat spacingLon nNorth nEast

annotation documentation in degree and lines/samples

source <xs:element name="demRaster"> <xs:annotation> <xs:documentation>in degree and lines/samples</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="spacingLat" type="xs:double"/> <xs:element name="spacingLon" type="xs:double"/> <xs:element name="nNorth" type="xs:int"/> <xs:element name="nEast" type="xs:int"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/demRaster/spacingLat

diagram

type xs:double






source <xs:element name="spacingLat" type="xs:double"/>

element cossc_product/rawDEMInfo/demRaster/spacingLon

diagram

type xs:double


source <xs:element name="spacingLon" type="xs:double"/>

element cossc_product/rawDEMInfo/demRaster/nNorth

diagram

type xs:int


source <xs:element name="nNorth" type="xs:int"/>

element cossc_product/rawDEMInfo/demRaster/nEast

diagram

type xs:int


source <xs:element name="nEast" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene





diagram


children pointsTotal pointsShadow pointsLayover pointsWater pointsMCFResPos pointsMCFResNeg pointsMCFSingleCut pointsMCFMultiCut heightMin heightMax heightMean heightStdDev coherMin coherMax coherMean coherStdDev heightErrorMin heightErrorMax heightErrorMean heightErrorStdDev

annotation documentation refers to geocoded DEM scene, its Flag Mask and HEM

source <xs:element name="statisticsDEMScene"> <xs:annotation> <xs:documentation>refers to geocoded DEM scene, its Flag Mask and HEM</xs:documentation> </xs:annotation>





<xs:complexType> <xs:sequence> <xs:element name="pointsTotal" type="xs:int"/> <xs:element name="pointsShadow" type="xs:int"/> <xs:element name="pointsLayover" type="xs:int"/> <xs:element name="pointsWater" type="xs:int"/> <xs:element name="pointsMCFResPos" type="xs:int"/> <xs:element name="pointsMCFResNeg" type="xs:int"/> <xs:element name="pointsMCFSingleCut" type="xs:int"/> <xs:element name="pointsMCFMultiCut" type="xs:int"/> <xs:element name="heightMin" type="xs:float"/> <xs:element name="heightMax" type="xs:float"/> <xs:element name="heightMean" type="xs:float"/> <xs:element name="heightStdDev" type="xs:float"/> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/> <xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsTotal

diagram

type xs:int


source <xs:element name="pointsTotal" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsShadow

diagram

type xs:int


source <xs:element name="pointsShadow" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsLayover

diagram

type xs:int






source <xs:element name="pointsLayover" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsWater

diagram

type xs:int


source <xs:element name="pointsWater" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsMCFResPos

diagram

type xs:int


source <xs:element name="pointsMCFResPos" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsMCFResNeg

diagram

type xs:int


source <xs:element name="pointsMCFResNeg" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsMCFSingleCut

diagram

type xs:int






source <xs:element name="pointsMCFSingleCut" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/pointsMCFMultiCut

diagram

type xs:int


source <xs:element name="pointsMCFMultiCut" type="xs:int"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightMin

diagram

type xs:float


source <xs:element name="heightMin" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightMax

diagram

type xs:float


source <xs:element name="heightMax" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightMean

diagram

type xs:float






source <xs:element name="heightMean" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightStdDev

diagram

type xs:float


source <xs:element name="heightStdDev" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/coherMin

diagram

type xs:float


source <xs:element name="coherMin" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/coherMax

diagram

type xs:float


source <xs:element name="coherMax" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/coherMean

diagram

type xs:float






source <xs:element name="coherMean" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/coherStdDev

diagram

type xs:float


source <xs:element name="coherStdDev" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightErrorMin

diagram

type xs:float


source <xs:element name="heightErrorMin" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightErrorMax

diagram

type xs:float


source <xs:element name="heightErrorMax" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightErrorMean

diagram

type xs:float






source <xs:element name="heightErrorMean" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMScene/heightErrorStdDev

diagram

type xs:float


source <xs:element name="heightErrorStdDev" type="xs:float"/>

element cossc_product/rawDEMInfo/percentageWater

diagram

type xs:double


annotation documentation coarse estimate from from GLOBECOVER data used for flagging

source <xs:element name="percentageWater" type="xs:double"> <xs:annotation> <xs:documentation>coarse estimate from from GLOBECOVER data used for flagging</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/rawDEMInfo/statisticsDEMLand





diagram


children coherMin coherMax coherMean coherStdDev heightErrorMin heightErrorMax heightErrorMean heightErrorStdDev pointsMCFResPos pointsMCFResNeg pointsMCFSingleCut pointsMCFMultiCut

annotation documentation statistics over GLOBE_COVER land classes

source <xs:element name="statisticsDEMLand"> <xs:annotation> <xs:documentation>statistics over GLOBE_COVER land classes</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coherMin" type="xs:float"/> <xs:element name="coherMax" type="xs:float"/> <xs:element name="coherMean" type="xs:float"/> <xs:element name="coherStdDev" type="xs:float"/> <xs:element name="heightErrorMin" type="xs:float"/> <xs:element name="heightErrorMax" type="xs:float"/> <xs:element name="heightErrorMean" type="xs:float"/> <xs:element name="heightErrorStdDev" type="xs:float"/> <xs:element name="pointsMCFResPos" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFResNeg" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFSingleCut" type="xs:float" minOccurs="0"/> <xs:element name="pointsMCFMultiCut" type="xs:float" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/statisticsDEMLand/coherMin





diagram

type xs:float


source <xs:element name="coherMin" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/coherMax

diagram

type xs:float


source <xs:element name="coherMax" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/coherMean

diagram

type xs:float


source <xs:element name="coherMean" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/coherStdDev

diagram

type xs:float


source <xs:element name="coherStdDev" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/heightErrorMin





diagram

type xs:float


source <xs:element name="heightErrorMin" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/heightErrorMax

diagram

type xs:float


source <xs:element name="heightErrorMax" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/heightErrorMean

diagram

type xs:float


source <xs:element name="heightErrorMean" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/heightErrorStdDev

diagram

type xs:float


source <xs:element name="heightErrorStdDev" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/pointsMCFResPos





diagram

type xs:float


source <xs:element name="pointsMCFResPos" type="xs:float" minOccurs="0"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/pointsMCFResNeg

diagram

type xs:float


source <xs:element name="pointsMCFResNeg" type="xs:float" minOccurs="0"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/pointsMCFSingleCut

diagram

type xs:float


source <xs:element name="pointsMCFSingleCut" type="xs:float" minOccurs="0"/>

element cossc_product/rawDEMInfo/statisticsDEMLand/pointsMCFMultiCut

diagram

type xs:float


source <xs:element name="pointsMCFMultiCut" type="xs:float" minOccurs="0"/>

element cossc_product/rawDEMInfo/statisticsSlantRange





diagram


children percentageLayover percentageShadow percentageMCFResPos percentageMCFResNeg percentageMCFSingleCuts percentageMCFMultiCuts

annotation documentation affected pixel in interferogram

source <xs:element name="statisticsSlantRange"> <xs:annotation> <xs:documentation>affected pixel in interferogram</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="percentageLayover" type="xs:float"/> <xs:element name="percentageShadow" type="xs:float"/> <xs:element name="percentageMCFResPos" type="xs:float"/> <xs:element name="percentageMCFResNeg" type="xs:float"/> <xs:element name="percentageMCFSingleCuts" type="xs:float"/> <xs:element name="percentageMCFMultiCuts" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageLayover

diagram

type xs:float


source <xs:element name="percentageLayover" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageShadow

diagram

type xs:float






source <xs:element name="percentageShadow" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageMCFResPos

diagram

type xs:float


source <xs:element name="percentageMCFResPos" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageMCFResNeg

diagram

type xs:float


source <xs:element name="percentageMCFResNeg" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageMCFSingleCuts

diagram

type xs:float


source <xs:element name="percentageMCFSingleCuts" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsSlantRange/percentageMCFMultiCuts

diagram

type xs:float






source <xs:element name="percentageMCFMultiCuts" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping

diagram


children ratioRadargramRegions phaseAdjustPercentageLowCoh phaseAdjustLowCoh phaseAdjustHighCoh phaseAdjustPercentagePixelChanged phaseAdjustPercentagePixelChangedDEM phaseAdjustPercentagePixelChangedLand

source <xs:element name="statisticsDEMUnwrapping" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="ratioRadargramRegions" type="xs:float"/> <xs:element name="phaseAdjustPercentageLowCoh" type="xs:float"/> <xs:element name="phaseAdjustLowCoh" type="xs:float"/> <xs:element name="phaseAdjustHighCoh" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChanged" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedDEM" type="xs:float"/> <xs:element name="phaseAdjustPercentagePixelChangedLand" type="xs:float"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/ratioRadargramRegions

diagram

type xs:float


source <xs:element name="ratioRadargramRegions" type="xs:float"/>





element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustPercentageLowCoh

diagram

type xs:float


source <xs:element name="phaseAdjustPercentageLowCoh" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustLowCoh

diagram

type xs:float


source <xs:element name="phaseAdjustLowCoh" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustHighCoh

diagram

type xs:float


source <xs:element name="phaseAdjustHighCoh" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustPercentagePixelChanged

diagram

type xs:float


source <xs:element name="phaseAdjustPercentagePixelChanged" type="xs:float"/>





element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustPercentagePixelChangedDEM

diagram

type xs:float


source <xs:element name="phaseAdjustPercentagePixelChangedDEM" type="xs:float"/>

element cossc_product/rawDEMInfo/statisticsDEMUnwrapping/phaseAdjustPercentagePixelChangedLand

diagram

type xs:float


source <xs:element name="phaseAdjustPercentagePixelChangedLand" type="xs:float"/>

element cossc_product/rawDEMInfo/coherenceHistogram

diagram


children bin

annotation documentation coherence distribution. currently 50 bins for 0.0 to 1.0

source <xs:element name="coherenceHistogram"> <xs:annotation> <xs:documentation>coherence distribution. currently 50 bins for 0.0 to 1.0</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:int"> <xs:attribute name="num" use="required"> <xs:annotation> <xs:documentation>running number starting with zero</xs:documentation> </xs:annotation>





<xs:simpleType> <xs:restriction base="xs:unsignedShort"> <xs:minInclusive value="0"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/coherenceHistogram/bin

diagram

type extension of xs:int


attributes Name Type Use Default Fixed Annotation num required documentation running

number starting with zero

source <xs:element name="bin" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:int"> <xs:attribute name="num" use="required"> <xs:annotation> <xs:documentation>running number starting with zero</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:unsignedShort"> <xs:minInclusive value="0"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/coherenceToHeightErrorLUT

diagram

properties isRef 0





content complex

children bin

annotation documentation coherence to height calculation for HEM values

source <xs:element name="coherenceToHeightErrorLUT"> <xs:annotation> <xs:documentation>coherence to height calculation for HEM values</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="bin" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="coh" type="xs:double" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/rawDEMInfo/coherenceToHeightErrorLUT/bin

diagram




coh xs:double required

source <xs:element name="bin" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:double"> <xs:attribute name="coh" type="xs:double" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>

element cossc_product/productQuality





diagram


children datatakeQuality qualityWarningFlag bestNominalResolutionSat1 bestNominalResolutionSat2 bestNominalResolution phaseInformationIncluded

source <xs:element name="productQuality"> <xs:complexType> <xs:sequence> <xs:element name="datatakeQuality"> <xs:annotation> <xs:documentation>for entire datatake (screening results during DEM generation)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap (azimuth)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeCoverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap range</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedCoverage" type="xs:double"> <xs:annotation> <xs:documentation>3dB illumination of echo window</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedRangeCoverage" type="xs:double"/> <xs:element name="commonDoppler"> <xs:complexType> <xs:sequence> <xs:element name="dopplerQuality" type="xs:double"> <xs:annotation> <xs:documentation>fractional</xs:documentation>





</xs:annotation> </xs:element> <xs:element name="dopplerBandwidthQuality" type="xs:double"> <xs:annotation> <xs:documentation>fraction of spectral overlap (coarse)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMin" type="xs:double"> <xs:annotation> <xs:documentation>difference between (bistatic) Doppler centroids</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMax" type="xs:double"/> <xs:element name="midRangeRelDopplerShiftMean" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SyncPulseEvaluation"> <xs:annotation> <xs:documentation>also included for monostatic data (quality is then 1.0)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="evaluationQuality" type="xs:double"/> <xs:element name="useDriftGapQuality" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="qualityWarningFlag" type="xs:boolean"> <xs:annotation> <xs:documentation>Were QA-Warnings encountered during processing (not all are considered)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolutionSat1" type="xs:double"> <xs:annotation> <xs:documentation>SSC ground resolution</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolutionSat2" type="xs:double"> <xs:annotation> <xs:documentation>before filtering and coreg (!)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bestNominalResolution" type="xs:double"> <xs:annotation> <xs:documentation>for CoSSC = min (1,2) for satellite data security regulations</xs:documentation> </xs:annotation> </xs:element> <xs:element name="phaseInformationIncluded" type="xs:boolean"> <xs:annotation> <xs:documentation>always TRUE ( for satellite data security regulations)</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productQuality/datatakeQuality





diagram


children coverageQuality rangeCoverageQuality illuminatedCoverage illuminatedRangeCoverage commonDoppler SyncPulseEvaluation

annotation documentation for entire datatake (screening results during DEM generation)

source <xs:element name="datatakeQuality"> <xs:annotation> <xs:documentation>for entire datatake (screening results during DEM generation)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="coverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap (azimuth)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="rangeCoverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap range</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedCoverage" type="xs:double"> <xs:annotation> <xs:documentation>3dB illumination of echo window</xs:documentation> </xs:annotation> </xs:element> <xs:element name="illuminatedRangeCoverage" type="xs:double"/> <xs:element name="commonDoppler"> <xs:complexType> <xs:sequence> <xs:element name="dopplerQuality" type="xs:double"> <xs:annotation> <xs:documentation>fractional</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dopplerBandwidthQuality" type="xs:double"> <xs:annotation> <xs:documentation>fraction of spectral overlap (coarse)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMin" type="xs:double">





<xs:annotation> <xs:documentation>difference between (bistatic) Doppler centroids</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMax" type="xs:double"/> <xs:element name="midRangeRelDopplerShiftMean" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="SyncPulseEvaluation"> <xs:annotation> <xs:documentation>also included for monostatic data (quality is then 1.0)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="evaluationQuality" type="xs:double"/> <xs:element name="useDriftGapQuality" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productQuality/datatakeQuality/coverageQuality

diagram

type xs:double


annotation documentation overlap (azimuth)

source <xs:element name="coverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap (azimuth)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/datatakeQuality/rangeCoverageQuality

diagram

type xs:double


annotation documentation overlap range

source <xs:element name="rangeCoverageQuality" type="xs:double"> <xs:annotation> <xs:documentation>overlap range</xs:documentation> </xs:annotation>





</xs:element>

element cossc_product/productQuality/datatakeQuality/illuminatedCoverage

diagram

type xs:double


annotation documentation 3dB illumination of echo window

source <xs:element name="illuminatedCoverage" type="xs:double"> <xs:annotation> <xs:documentation>3dB illumination of echo window</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/datatakeQuality/illuminatedRangeCoverage

diagram

type xs:double


source <xs:element name="illuminatedRangeCoverage" type="xs:double"/>

element cossc_product/productQuality/datatakeQuality/commonDoppler

diagram

properties isRef 0





content complex

children dopplerQuality dopplerBandwidthQuality midRangeRelDopplerShiftMin midRangeRelDopplerShiftMax midRangeRelDopplerShiftMean

source <xs:element name="commonDoppler"> <xs:complexType> <xs:sequence> <xs:element name="dopplerQuality" type="xs:double"> <xs:annotation> <xs:documentation>fractional</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dopplerBandwidthQuality" type="xs:double"> <xs:annotation> <xs:documentation>fraction of spectral overlap (coarse)</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMin" type="xs:double"> <xs:annotation> <xs:documentation>difference between (bistatic) Doppler centroids</xs:documentation> </xs:annotation> </xs:element> <xs:element name="midRangeRelDopplerShiftMax" type="xs:double"/> <xs:element name="midRangeRelDopplerShiftMean" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productQuality/datatakeQuality/commonDoppler/dopplerQuality

diagram

type xs:double


annotation documentation fractional

source <xs:element name="dopplerQuality" type="xs:double"> <xs:annotation> <xs:documentation>fractional</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/datatakeQuality/commonDoppler/dopplerBandwidthQuality

diagram

type xs:double






annotation documentation fraction of spectral overlap (coarse)

source <xs:element name="dopplerBandwidthQuality" type="xs:double"> <xs:annotation> <xs:documentation>fraction of spectral overlap (coarse)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/datatakeQuality/commonDoppler/midRangeRelDopplerShiftMin

diagram

type xs:double


annotation documentation difference between (bistatic) Doppler centroids

source <xs:element name="midRangeRelDopplerShiftMin" type="xs:double"> <xs:annotation> <xs:documentation>difference between (bistatic) Doppler centroids</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/datatakeQuality/commonDoppler/midRangeRelDopplerShiftMax

diagram

type xs:double


source <xs:element name="midRangeRelDopplerShiftMax" type="xs:double"/>

element cossc_product/productQuality/datatakeQuality/commonDoppler/midRangeRelDopplerShiftMean

diagram

type xs:double


source <xs:element name="midRangeRelDopplerShiftMean" type="xs:double"/>





element cossc_product/productQuality/datatakeQuality/SyncPulseEvaluation

diagram


children evaluationQuality useDriftGapQuality

annotation documentation also included for monostatic data (quality is then 1.0)

source <xs:element name="SyncPulseEvaluation"> <xs:annotation> <xs:documentation>also included for monostatic data (quality is then 1.0)</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="evaluationQuality" type="xs:double"/> <xs:element name="useDriftGapQuality" type="xs:double"/> </xs:sequence> </xs:complexType> </xs:element>

element cossc_product/productQuality/datatakeQuality/SyncPulseEvaluation/evaluationQuality

diagram

type xs:double


source <xs:element name="evaluationQuality" type="xs:double"/>

element cossc_product/productQuality/datatakeQuality/SyncPulseEvaluation/useDriftGapQuality

diagram

type xs:double


source <xs:element name="useDriftGapQuality" type="xs:double"/>

element cossc_product/productQuality/qualityWarningFlag





diagram

type xs:boolean


annotation documentation Were QA-Warnings encountered during processing (not all are considered)

source <xs:element name="qualityWarningFlag" type="xs:boolean"> <xs:annotation> <xs:documentation>Were QA-Warnings encountered during processing (not all are considered)</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/bestNominalResolutionSat1

diagram

type xs:double


annotation documentation SSC ground resolution

source <xs:element name="bestNominalResolutionSat1" type="xs:double"> <xs:annotation> <xs:documentation>SSC ground resolution</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/bestNominalResolutionSat2

diagram

type xs:double


annotation documentation before filtering and coreg (!)

source <xs:element name="bestNominalResolutionSat2" type="xs:double"> <xs:annotation> <xs:documentation>before filtering and coreg (!)</xs:documentation> </xs:annotation>





</xs:element>

element cossc_product/productQuality/bestNominalResolution

diagram

type xs:double


annotation documentation for CoSSC = min (1,2) for satellite data security regulations

source <xs:element name="bestNominalResolution" type="xs:double"> <xs:annotation> <xs:documentation>for CoSSC = min (1,2) for satellite data security regulations</xs:documentation> </xs:annotation> </xs:element>

element cossc_product/productQuality/phaseInformationIncluded

diagram

type xs:boolean


annotation documentation always TRUE ( for satellite data security regulations)

source <xs:element name="phaseInformationIncluded" type="xs:boolean"> <xs:annotation> <xs:documentation>always TRUE ( for satellite data security regulations)</xs:documentation> </xs:annotation> </xs:element>

complexType componentType





diagram

children name type qualityInfo file instrument

used by element cossc_product/productComponents/component

attributes Name Type Use Default Fixed Annotation componentClass xs:string required documentation helps to decide

how the component is archived imageData, quicklook, browseComponent, annotation, auxRasterFiles, mapPlot, undef1, ... , undef9

source <xs:complexType name="componentType"> <xs:sequence> <xs:element name="name" type="string255"> <xs:annotation> <xs:documentation>unique name that is used to address the component</xs:documentation> </xs:annotation> </xs:element> <xs:element name="type"> <xs:annotation> <xs:documentation>PGS data type used to specify the exact content of the component file.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="string255"/>





</xs:simpleType> </xs:element> <xs:element name="qualityInfo" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="qualityInspection"> <xs:annotation> <xs:documentation>ITP processor internal automatic quality control result: e.g. AUTO_APPROVED or NOT_APPROVED. The latter may result from limit violations which are not necessarily impairing the product quality but are brought to a QA operators attention.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="string255"> <xs:enumeration value="AUTO_APPROVED"/> <xs:enumeration value="OPERATOR_APPROVED"/> <xs:enumeration value="NOT_APPROVED"/> <xs:enumeration value="UNDEFINED"/> <xs:enumeration value="LIMITED_APPROVAL"/> <xs:enumeration value="WAIT_FOR_APPROVAL"/> <xs:enumeration value="APPROVED"/> <xs:enumeration value="WAIT_FOR_CORRECTION"/> <xs:enumeration value="PARTS_UNPROCESSIBLE"/> <xs:enumeration value="UNPROCESSIBLE"/> <xs:enumeration value="REJECTED"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="qualityRemark" type="string1024" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="file" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>pointer to component file</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="location"> <xs:complexType> <xs:sequence> <xs:element name="host" type="xs:string"> <xs:annotation> <xs:documentation>Host defaults to: . </xs:documentation> </xs:annotation> </xs:element> <xs:element name="path" type="xs:string"/> <xs:element name="name" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="size" type="xs:long"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="instrument"> <xs:annotation> <xs:documentation>distinguish in-between components that are based on single or joint acquisitions</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="satIDs" type="xs:string"> <xs:annotation> <xs:documentation>TSX-1, TDX-1, TSX-1 + TDX-1, simulated data, TSX-2, TDX-1 + TSX-2, TSX-1 + TSX-2, undefined</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of a two-satellite component monostatic, bistatic, alternatingBistatic, undefined</xs:documentation>





</xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistatic"/> <xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="iopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of an one-satellite component monostatic, bistaticActive, bistaticPassive, undefined</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistaticActive"/> <xs:enumeration value="bistaticPassive"/> <xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="componentClass" type="xs:string" use="required"> <xs:annotation> <xs:documentation>helps to decide how the component is archived imageData, quicklook, browseComponent, annotation, auxRasterFiles, mapPlot, undef1, ... , undef9</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType>

element componentType/name

diagram

type string255



annotation documentation unique name that is used to address the component

source <xs:element name="name" type="string255"> <xs:annotation> <xs:documentation>unique name that is used to address the component</xs:documentation> </xs:annotation> </xs:element>

element componentType/type





diagram

type restriction of string255



annotation documentation PGS data type used to specify the exact content of the component file.

source <xs:element name="type"> <xs:annotation> <xs:documentation>PGS data type used to specify the exact content of the component file.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="string255"/> </xs:simpleType> </xs:element>

element componentType/qualityInfo

diagram


children qualityInspection qualityRemark

source <xs:element name="qualityInfo" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="qualityInspection"> <xs:annotation> <xs:documentation>ITP processor internal automatic quality control result: e.g. AUTO_APPROVED or NOT_APPROVED. The latter may result from limit violations which are not necessarily impairing the product quality but are brought to a QA operators attention.</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="string255"> <xs:enumeration value="AUTO_APPROVED"/> <xs:enumeration value="OPERATOR_APPROVED"/> <xs:enumeration value="NOT_APPROVED"/> <xs:enumeration value="UNDEFINED"/>





<xs:enumeration value="LIMITED_APPROVAL"/> <xs:enumeration value="WAIT_FOR_APPROVAL"/> <xs:enumeration value="APPROVED"/> <xs:enumeration value="WAIT_FOR_CORRECTION"/> <xs:enumeration value="PARTS_UNPROCESSIBLE"/> <xs:enumeration value="UNPROCESSIBLE"/> <xs:enumeration value="REJECTED"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="qualityRemark" type="string1024" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>

element componentType/qualityInfo/qualityInspection

diagram

type restriction of string255


facets maxLength 255 enumeration AUTO_APPROVED enumeration OPERATOR_APPROVED

enumeration NOT_APPROVED enumeration UNDEFINED enumeration LIMITED_APPROVAL enumeration WAIT_FOR_APPROVAL enumeration APPROVED enumeration WAIT_FOR_CORRECTION

enumeration PARTS_UNPROCESSIBLE

enumeration UNPROCESSIBLE enumeration REJECTED

annotation documentation ITP processor internal automatic quality control result: e.g. AUTO_APPROVED or NOT_APPROVED. The latter may result from limit violations which are not necessarily impairing the product quality but are brought to a QA operators attention.

source <xs:element name="qualityInspection"> <xs:annotation> <xs:documentation>ITP processor internal automatic quality control result: e.g. AUTO_APPROVED or NOT_APPROVED. The latter may result from limit violations which are not necessarily impairing the product quality but are brought to a QA operators attention.</xs:documentation> </xs:annotation> <xs:simpleType>





<xs:restriction base="string255"> <xs:enumeration value="AUTO_APPROVED"/> <xs:enumeration value="OPERATOR_APPROVED"/> <xs:enumeration value="NOT_APPROVED"/> <xs:enumeration value="UNDEFINED"/> <xs:enumeration value="LIMITED_APPROVAL"/> <xs:enumeration value="WAIT_FOR_APPROVAL"/> <xs:enumeration value="APPROVED"/> <xs:enumeration value="WAIT_FOR_CORRECTION"/> <xs:enumeration value="PARTS_UNPROCESSIBLE"/> <xs:enumeration value="UNPROCESSIBLE"/> <xs:enumeration value="REJECTED"/> </xs:restriction> </xs:simpleType> </xs:element>

element componentType/qualityInfo/qualityRemark

diagram

type string1024



source <xs:element name="qualityRemark" type="string1024" minOccurs="0"/>

element componentType/file

diagram


children location size

annotation documentation pointer to component file

source <xs:element name="file" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>pointer to component file</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="location"> <xs:complexType> <xs:sequence> <xs:element name="host" type="xs:string"> <xs:annotation> <xs:documentation>Host defaults to: . </xs:documentation> </xs:annotation> </xs:element> <xs:element name="path" type="xs:string"/>





<xs:element name="name" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="size" type="xs:long"/> </xs:sequence> </xs:complexType> </xs:element>

element componentType/file/location

diagram


children host path name

source <xs:element name="location"> <xs:complexType> <xs:sequence> <xs:element name="host" type="xs:string"> <xs:annotation> <xs:documentation>Host defaults to: . </xs:documentation> </xs:annotation> </xs:element> <xs:element name="path" type="xs:string"/> <xs:element name="name" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element>

element componentType/file/location/host

diagram

type xs:string


annotation documentation Host defaults to: .

source <xs:element name="host" type="xs:string"> <xs:annotation> <xs:documentation>Host defaults to: . </xs:documentation> </xs:annotation> </xs:element>

element componentType/file/location/path





diagram

type xs:string


source <xs:element name="path" type="xs:string"/>

element componentType/file/location/name

diagram

type xs:string


source <xs:element name="name" type="xs:string"/>

element componentType/file/size

diagram

type xs:long


source <xs:element name="size" type="xs:long"/>

element componentType/instrument





diagram


children satIDs coopMode iopMode

annotation documentation distinguish in-between components that are based on single or joint acquisitions

source <xs:element name="instrument"> <xs:annotation> <xs:documentation>distinguish in-between components that are based on single or joint acquisitions</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="satIDs" type="xs:string"> <xs:annotation> <xs:documentation>TSX-1, TDX-1, TSX-1 + TDX-1, simulated data, TSX-2, TDX-1 + TSX-2, TSX-1 + TSX-2, undefined</xs:documentation> </xs:annotation> </xs:element> <xs:element name="coopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of a two-satellite component monostatic, bistatic, alternatingBistatic, undefined</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistatic"/> <xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="iopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of an one-satellite component monostatic, bistaticActive, bistaticPassive, undefined</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistaticActive"/> <xs:enumeration value="bistaticPassive"/>





<xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

element componentType/instrument/satIDs

diagram

type xs:string


annotation documentation TSX-1, TDX-1, TSX-1 + TDX-1, simulated data, TSX-2, TDX-1 + TSX-2, TSX-1 + TSX-2, undefined

source <xs:element name="satIDs" type="xs:string"> <xs:annotation> <xs:documentation>TSX-1, TDX-1, TSX-1 + TDX-1, simulated data, TSX-2, TDX-1 + TSX-2, TSX-1 + TSX-2, undefined</xs:documentation> </xs:annotation> </xs:element>

element componentType/instrument/coopMode

diagram

type restriction of xs:token


facets enumeration monostatic enumeration bistatic enumeration alternatingBistatic

enumeration undefined

annotation documentation instrument mode of a two-satellite component monostatic, bistatic, alternatingBistatic, undefined

source <xs:element name="coopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of a two-satellite component





monostatic, bistatic, alternatingBistatic, undefined</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistatic"/> <xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element>

element componentType/instrument/iopMode

diagram

type restriction of xs:token


facets enumeration monostatic enumeration bistaticActive enumeration bistaticPassive enumeration alternatingBistatic

enumeration undefined

annotation documentation instrument mode of an one-satellite component monostatic, bistaticActive, bistaticPassive, undefined

source <xs:element name="iopMode" minOccurs="0"> <xs:annotation> <xs:documentation>instrument mode of an one-satellite component monostatic, bistaticActive, bistaticPassive, undefined</xs:documentation> </xs:annotation> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="monostatic"/> <xs:enumeration value="bistaticActive"/> <xs:enumeration value="bistaticPassive"/> <xs:enumeration value="alternatingBistatic"/> <xs:enumeration value="undefined"/> </xs:restriction> </xs:simpleType> </xs:element>

complexType parameterType





diagram

children parameter parameterVector

source <xs:complexType name="parameterType"> <xs:sequence> <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="string1024"> <xs:attribute name="name" type="string255" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="parameterVector" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="element" type="string1024" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="string255" use="required"/> <xs:attribute name="nelements" type="string80" use="required"/> <xs:attribute name="startElement" type="string80"/> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType>

element parameterType/parameter

diagram





name string255 required

source <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="string1024"> <xs:attribute name="name" type="string255" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>





element parameterType/parameterVector

diagram


children element

attributes Name Type Use Default Fixed Annotation name string255 required nelements string80 required startElement string80

source <xs:element name="parameterVector" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="element" type="string1024" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="string255" use="required"/> <xs:attribute name="nelements" type="string80" use="required"/> <xs:attribute name="startElement" type="string80"/> </xs:complexType> </xs:element>

element parameterType/parameterVector/element

diagram

type string1024



source <xs:element name="element" type="string1024" minOccurs="0" maxOccurs="unbounded"/>

element generalHeader





diagram





properties content complex

children itemName mission source destination generationSystem generationTime referenceDocument revision revisionComment remark

used by element cossc_product

attributes Name Type Use Default Fixed Annotation fileName string128 required documentation Contains the

name of the file in which the product / data / interface item is provided.

fileVersion string20 optional documentation In case, that the provision of more than one version of the same product / data / interface file is operationally foreseen, the file version gives the current version number. It is incremented by 1 whenever the same file is sent again in an updated form. The start value is 1.

status string20 optional documentation In case, that the provision of more than one version of the same product / data / interface file is operationally foreseen, the status parameter indicates the status of the current file version. It may be PRELIMINARY, if another update is foressen, or FINAL, if the final file version is delivered.

annotation documentation TS-X Ground Segment General Header Structure

source <xs:element name="generalHeader"> <xs:annotation> <xs:documentation>TS-X Ground Segment General Header Structure</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="itemName" type="string80"> <xs:annotation>





<xs:documentation>Contains the name of the exchanged product / data / interface item Examples: Orbit Product; Attitude Product; IOCS Aux Product</xs:documentation> </xs:annotation> </xs:element> <xs:element name="mission" type="string20"> <xs:annotation> <xs:documentation>Indicates the mission, for which the product / data file is provided. It is fixecd to "TSX-1" for the first TerraSAR-X satellite </xs:documentation> </xs:annotation> </xs:element> <xs:element name="source" type="string20"> <xs:annotation> <xs:documentation>Specifies the sensor, source or originator for the provided product / data file e.g. MOS, PGS, IOCS</xs:documentation> </xs:annotation> </xs:element> <xs:element name="destination" type="string20"> <xs:annotation> <xs:documentation>Specifies the destination to which the provided product / data file goes, e.g. MOS, PGS, IOCS, GS, User, Multiple</xs:documentation> </xs:annotation> </xs:element> <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>Specifies the system which generated the product / data file, e.g. TMSP</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string80"> <xs:attribute name="version" type="string20" use="required"> <xs:annotation> <xs:documentation>Specifies the system version with which the product / data file was generated, e.g. 1.2</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="generationTime" type="xs:dateTime"> <xs:annotation> <xs:documentation>Reports the UTC time at which the product / data file was generated or published.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="referenceDocument" type="string255" minOccurs="0"> <xs:annotation> <xs:documentation>Specifies the reference document, in which the product / data item is specified with respect to its content and format, e.g. reference to Station Support Data Specification including issue and revision numbers "TX-GS-DD-3202-1-0" </xs:documentation> </xs:annotation> </xs:element> <xs:element name="revision" type="string20" minOccurs="0"> <xs:annotation> <xs:documentation>A handle to distinguish between different project phases (e.g. integration, testing, commissioning phase, operations) in order to separate test data from operational data in the TerraSAR-X Product Library. Examples: PGS_INTEGRATION, GS_INTEGRATION, COMMISSIONING_PHASE, OPERATION</xs:documentation> </xs:annotation> </xs:element> <xs:element name="revisionComment" type="string1024" minOccurs="0"> <xs:annotation> <xs:documentation>Remark field for a narrative description of the revision field entry above.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="remark" type="string1024" minOccurs="0"> <xs:annotation> <xs:documentation>Remark field for a further narrative description of the product / data file.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:attribute name="fileName" type="string128" use="required"> <xs:annotation>





<xs:documentation>Contains the name of the file in which the product / data / interface item is provided.</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="fileVersion" type="string20" use="optional"> <xs:annotation> <xs:documentation>In case, that the provision of more than one version of the same product / data / interface file is operationally foreseen, the file version gives the current version number. It is incremented by 1 whenever the same file is sent again in an updated form. The start value is 1. </xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="status" type="string20" use="optional"> <xs:annotation> <xs:documentation>In case, that the provision of more than one version of the same product / data / interface file is operationally foreseen, the status parameter indicates the status of the current file version. It may be PRELIMINARY, if another update is foressen, or FINAL, if the final file version is delivered.</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element>

element generalHeader/itemName

diagram

type string80


facets maxLength 80

annotation documentation Contains the name of the exchanged product / data / interface itemExamples: Orbit Product; Attitude Product; IOCS Aux Product

source <xs:element name="itemName" type="string80"> <xs:annotation> <xs:documentation>Contains the name of the exchanged product / data / interface item Examples: Orbit Product; Attitude Product; IOCS Aux Product</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/mission

diagram

type string20






facets maxLength 20

annotation documentation Indicates the mission, for which the product / data file is provided. It is fixecd to "TSX-1" for the first TerraSAR-X satellite

source <xs:element name="mission" type="string20"> <xs:annotation> <xs:documentation>Indicates the mission, for which the product / data file is provided. It is fixecd to "TSX-1" for the first TerraSAR-X satellite </xs:documentation> </xs:annotation> </xs:element>

element generalHeader/source

diagram

type string20


facets maxLength 20

annotation documentation Specifies the sensor, source or originator for the provided product / data file e.g. MOS, PGS, IOCS

source <xs:element name="source" type="string20"> <xs:annotation> <xs:documentation>Specifies the sensor, source or originator for the provided product / data file e.g. MOS, PGS, IOCS</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/destination

diagram

type string20


facets maxLength 20

annotation documentation Specifies the destination to which the provided product / data file goes, e.g. MOS, PGS, IOCS, GS, User,





Multiple

source <xs:element name="destination" type="string20"> <xs:annotation> <xs:documentation>Specifies the destination to which the provided product / data file goes, e.g. MOS, PGS, IOCS, GS, User, Multiple</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/generationSystem

diagram



facets maxLength 80

attributes Name Type Use Default Fixed Annotation version string20 required documentation Specifies

the system version with which the product / data file was generated, e.g. 1.2

annotation documentation Specifies the system which generated the product / data file, e.g. TMSP

source <xs:element name="generationSystem"> <xs:annotation> <xs:documentation>Specifies the system which generated the product / data file, e.g. TMSP</xs:documentation> </xs:annotation> <xs:complexType> <xs:simpleContent> <xs:extension base="string80"> <xs:attribute name="version" type="string20" use="required"> <xs:annotation> <xs:documentation>Specifies the system version with which the product / data file was generated, e.g. 1.2</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element>

element generalHeader/generationTime





diagram

type xs:dateTime


annotation documentation Reports the UTC time at which the product / data file was generated or published.

source <xs:element name="generationTime" type="xs:dateTime"> <xs:annotation> <xs:documentation>Reports the UTC time at which the product / data file was generated or published.</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/referenceDocument

diagram

type string255



annotation documentation Specifies the reference document, in which the product / data item is specified with respect to its content and format, e.g. reference to Station Support Data Specification including issue and revision numbers "TX-GS-DD-3202-1-0"

source <xs:element name="referenceDocument" type="string255" minOccurs="0"> <xs:annotation> <xs:documentation>Specifies the reference document, in which the product / data item is specified with respect to its content and format, e.g. reference to Station Support Data Specification including issue and revision numbers "TX-GS-DD-3202-1-0" </xs:documentation> </xs:annotation> </xs:element>

element generalHeader/revision





diagram

type string20


facets maxLength 20

annotation documentation A handle to distinguish between different project phases (e.g. integration, testing, commissioning phase, operations) in order to separate test data from operational data in the TerraSAR-X Product Library. Examples: PGS_INTEGRATION, GS_INTEGRATION, COMMISSIONING_PHASE, OPERATION

source <xs:element name="revision" type="string20" minOccurs="0"> <xs:annotation> <xs:documentation>A handle to distinguish between different project phases (e.g. integration, testing, commissioning phase, operations) in order to separate test data from operational data in the TerraSAR-X Product Library. Examples: PGS_INTEGRATION, GS_INTEGRATION, COMMISSIONING_PHASE, OPERATION</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/revisionComment

diagram

type string1024



annotation documentation Remark field for a narrative description of the revision field entry above.

source <xs:element name="revisionComment" type="string1024" minOccurs="0"> <xs:annotation> <xs:documentation>Remark field for a narrative description of the revision field entry above.</xs:documentation> </xs:annotation> </xs:element>

element generalHeader/remark





diagram

type string1024



annotation documentation Remark field for a further narrative description of the product / data file.

source <xs:element name="remark" type="string1024" minOccurs="0"> <xs:annotation> <xs:documentation>Remark field for a further narrative description of the product / data file.</xs:documentation> </xs:annotation> </xs:element>

simpleType string1024

type restriction of xs:string

used by elements parameterType/parameterVector/element parameterType/parameter componentType/qualityInfo/qualityRemark generalHeader/remark generalHeader/revisionComment


source <xs:simpleType name="string1024"> <xs:restriction base="xs:string"> <xs:maxLength value="1024"/> </xs:restriction> </xs:simpleType>



used by elements cossc_product/productInfo/productType cossc_product/productInfo/productVariant attribute generalHeader/@fileName



simpleType string20


used by elements generalHeader/destination generalHeader/mission generalHeader/revision generalHeader/source





attributes generalHeader/@fileVersion cossc_product/commonAcquisitionInfo/acquisitionMode/@satID cossc_product/processingInfo/bistaticProcessing/syncPulseEvaluation/@satID cossc_product/processingInfo/bistaticProcessing/averageFastTimeCorrection/@satID generalHeader/@status generalHeader/generationSystem/@version

facets maxLength 20




used by elements cossc_product/baselineInfo/orbitHeader/generationSystem componentType/name componentType/qualityInfo/qualityInspection generalHeader/referenceDocument componentType/type

attributes parameterType/parameter/@name parameterType/parameterVector/@name



simpleType string80


used by elements cossc_product/baselineInfo/orbitHeader/accuracy cossc_product/commonAcquisitionInfo/acquisitionMode/antennaReceiveConfiguration cossc_product/commonAcquisitionInfo/operationsInfo/appliedToID cossc_product/commonAcquisitionInfo/acquisitionMode/cooperativeInstrumentMode cossc_product/commonAcquisitionInfo/cooperativeMode cossc_product/commonAcquisitionInfo/acquisitionMode/datatakeStartTime cossc_product/commonAcquisitionInfo/acquisitionMode/datatakeStopTime cossc_product/commonAcquisitionInfo/acquisitionMode/elevationBeamConfiguration cossc_product/baselineInfo/orbitHeader/firstStateTime/firstStateTimeUTC generalHeader/generationSystem cossc_product/processingInfo/inputData/ifAuxGenerationTime cossc_product/processingInfo/inputData/ifAuxProductMajorVersion cossc_product/processingInfo/inputData/ifAuxProductMinorVersion cossc_product/commonAcquisitionInfo/acquisitionMode/imagingMode cossc_product/commonAcquisitionInfo/inSARmasterID generalHeader/itemName cossc_product/baselineInfo/orbitHeader/lastStateTime/lastStateTimeUTC cossc_product/commonAcquisitionInfo/acquisitionGeometry/lookDirection cossc_product/commonAcquisitionInfo/missionID cossc_product/processingInfo/inSARProcessing/observationMode cossc_product/commonAcquisitionInfo/operationsInfo/operationsTypeSat1 cossc_product/commonAcquisitionInfo/operationsInfo/operationsTypeSat2 cossc_product/commonAcquisitionInfo/acquisitionGeometry/orbitDirection cossc_product/processingInfo/inputData/orderType cossc_product/commonAcquisitionInfo/acquisitionMode/polarizationMode cossc_product/commonAcquisitionInfo/acquisitionMode/polarizationList/polLayer cossc_product/commonAcquisitionInfo/operationsInfo/processingPriority cossc_product/rawDEMInfo/rawDEMname cossc_product/baselineInfo/orbitHeader/recProcessingTechnique cossc_product/commonAcquisitionInfo/acquisitionMode/rangeBandwidthClass/rgBW cossc_product/commonAcquisitionInfo/satelliteIDsat1 cossc_product/commonAcquisitionInfo/satelliteIDsat2 cossc_product/baselineInfo/orbitHeader/sensor





cossc_product/baselineInfo/orbitHeader/stateVecFormat cossc_product/baselineInfo/orbitHeader/stateVectorRefFrame cossc_product/baselineInfo/orbitHeader/stateVectorRefTime cossc_product/commonAcquisitionInfo/operationsInfo/TAPtakeID

attributes cossc_product/baselineInfo/orbitHeader/coordSystemTransfrom/rotMatrixCoeff/@i cossc_product/baselineInfo/orbitHeader/coordSystemTransfrom/rotMatrixCoeff/@j parameterType/parameterVector/@nelements parameterType/parameterVector/@startElement cossc_product/baselineInfo/orbitHeader/generationSystem/@version

facets maxLength 80






A. Annex

A.1 Experimental Product Beam Definition Parameters

The following sub-chapters show in detail the stripmap (SM), tanDEM and spotlight elevation beam definition. Similar to the TerraSAR-X mission, a pre-defined set of beams is considered to be in the full performance range. The following table summarizes the beams available for nominal science ordering:

Beam ID Look angle coverage [deg]

strip (single) 003 – 014 18.20 – 41.34

strip(dual) 003 – 014 18.35 – 41.25

tanDEM all 26.10 – 43.88 and 53.44 – 54.79

spot 010 – 100 18.19 – 49.53

Note that for the following calculation of the incidence angle an orbit height of 512 km has been used. Since the incidence angle depends also on the orbit height and Earth position to be acquired, it can differ slightly from the values indicated in these tables.

A.2 SM single polarization elevation beams

The strip beams are used for bistatic and pursuit monostatic SM single polarization acquisitions. The beams strip_001 to strip_014 are designed with a swath width margin of 1.6 km, all other beams have no further margin.

Beam ID

Min. look angle [deg]

Max. look

angle [deg]

Min. incidence

angle [deg]

Max. incidence

angle [deg]

Ground swath

width [km]

Ground swath overlap to next

swath [km]

strip_001 13.25 16.54 14.34 17.91 31.7 7.6

strip_002 15.76 18.95 17.06 20.54 31.7 7.6

strip_003 18.20 21.29 19.71 23.09 31.7 7.6

strip_004 20.56 23.54 22.29 25.56 31.7 7.6

strip_005 22.84 25.71 24.79 27.95 31.7 7.6

strip_006 25.03 27.79 27.20 30.24 31.7 7.6

strip_007 27.14 29.78 29.53 32.45 31.7 7.6

strip_008 29.16 31.69 31.76 34.57 31.7 7.6

strip_009 31.10 33.50 33.91 36.60 31.7 7.6





strip_010 32.94 35.23 35.97 38.55 31.7 7.6

strip_011 34.69 36.88 37.94 40.41 31.7 7.6

strip_012 36.37 38.44 39.83 42.19 31.7 7.6

strip_013 37.96 39.93 41.64 43.89 31.7 7.6

strip_014 39.47 41.34 43.36 45.52 31.7 6.8

strip_015 40.94 42.63 45.07 47.02 30.1 6.0

strip_016 42.30 43.90 46.64 48.51 30.1 6.0

strip_017 43.59 45.11 48.14 49.93 30.1 6.0

strip_018 44.81 46.11 49.58 51.12 27.1 5.4

strip_019 45.86 47.09 50.82 52.30 27.1 5.4

strip_020 46.85 48.03 52.01 53.43 27.1 5.4

strip_021 47.80 48.93 53.16 54.52 27.1 5.4

strip_022 48.71 49.78 54.26 55.57 27.1 5.4

strip_023 49.57 50.59 55.31 56.58 27.1 5.4

strip_024 50.39 51.37 56.33 57.55 27.1 5.4

strip_025 51.18 52.11 57.31 58.49 27.1 5.4

strip_026 51.93 52.82 58.26 59.39 27.1 5.4

strip_027 52.64 53.49 59.17 60.26 27.1 3.0

strip_028 53.40 54.03 60.14 60.95 21.0 7.2

strip_029 53.81 54.55 60.68 61.64 25.5 4.0

strip_030 54.44 55.14 61.50 62.43 25.5 7.2

strip_031 54.95 55.50 62.17 62.91 20.8 -

A.3 SM dual polarization elevation beams

The SM dual polarization beams are derived from the SM single polarization beams and sub-divided into stripNear and stripFar beams. Therefore stripNear and stripFar beams cover only half the swath width with respect to SM single polarization beams.

The stripNear and stripFar beams are used for bistatic SM dual polarization and for alternating bistatic SM single (and dual) polarization acquisitions. Their beam definition is shown in the following table. The beams stripNear/Far_001 to stripNear/Far_014 are designed with a swath width margin of 1.6 km, all other beams have no further margin.

Beam ID

Min. look

angle [deg]

Max. look

angle [deg]

Min. incidence

angle [deg]

Max. incidence

angle [deg]

Ground swath

width [km]

Ground swath overlap to next swath

[km]

stripNear_001 13.41 15.15 14.51 16.40 16.7 4.6

stripFar_001 14.67 16.39 15.88 17.74 16.7 4.6





stripNear_002 15.91 17.60 17.23 19.07 16.7 4.6

stripFar_002 17.14 18.80 18.56 20.38 16.7 4.6

stripNear_003 18.35 19.98 19.88 21.66 16.7 4.6

stripFar_003 19.53 21.14 21.17 22.93 16.7 4.6

stripNear_004 20.70 22.28 22.45 24.18 16.7 4.6

stripFar_004 21.85 23.40 23.71 25.41 16.7 4.6

stripNear_005 22.98 24.50 24.94 26.62 16.7 4.6

stripFar_005 24.08 25.58 26.16 27.80 16.7 4.6

stripNear_006 25.17 26.63 27.35 28.96 16.7 4.6

stripFar_006 26.23 27.67 28.52 30.10 16.7 4.6

stripNear_007 27.27 28.68 29.67 31.22 16.7 4.6

stripFar_007 28.29 29.66 30.80 32.32 16.7 4.6

stripNear_008 29.29 30.63 31.90 33.39 16.7 4.6

stripFar_008 30.26 31.57 32.98 34.44 16.7 4.6

stripNear_009 31.21 32.49 34.04 35.47 16.7 4.6

stripFar_009 32.14 33.39 35.08 36.48 16.7 4.6

stripNear_010 33.05 34.27 36.10 37.47 16.7 4.6

stripFar_010 33.94 35.13 37.09 38.43 16.7 4.6

stripNear_011 34.80 35.96 38.06 39.37 16.7 4.6

stripFar_011 35.65 36.78 39.02 40.30 16.7 4.6

stripNear_012 36.47 37.57 39.95 41.20 16.7 4.6

stripFar_012 37.27 38.35 40.86 42.08 16.7 4.6

stripNear_013 38.05 39.10 41.75 42.95 16.7 4.6

stripFar_013 38.81 39.84 42.62 43.79 16.7 4.6

stripNear_014 39.56 40.55 43.47 44.61 16.7 4.6

stripFar_014 40.28 41.25 44.30 45.42 16.7 3.8

stripNear_015 41.03 41.89 45.17 46.15 15.1 3.0

stripFar_015 41.72 42.55 45.96 46.93 15.1 3.0

stripNear_016 42.38 43.19 46.73 47.68 15.1 3.0

stripFar_016 43.03 43.82 47.49 48.42 15.1 3.0

stripNear_017 43.67 44.44 48.23 49.14 15.1 3.0

stripFar_017 44.28 45.03 48.96 49.84 15.1 3.2

stripNear_018 44.88 45.53 49.66 50.44 13.5 2.7

stripFar_018 45.40 46.05 50.28 51.05 13.5 2.7

stripNear_019 45.92 46.55 50.90 51.64 13.5 2.7

stripFar_019 46.42 47.03 51.50 52.23 13.5 2.7

stripNear_020 46.91 47.51 52.08 52.80 13.5 2.7

stripFar_020 47.39 47.97 52.66 53.36 13.5 2.7





stripNear_021 47.86 48.43 53.23 53.92 13.5 2.7

stripFar_021 48.32 48.87 53.78 54.46 13.5 2.7

stripNear_022 48.76 49.31 54.32 54.99 13.5 2.7

stripFar_022 49.20 49.73 54.86 55.51 13.6 2.7

stripNear_023 49.62 50.14 55.38 56.02 13.6 2.7

stripFar_023 50.04 50.54 55.89 56.52 13.6 2.7

stripNear_024 50.44 50.94 56.39 57.01 13.6 2.7

stripFar_024 50.84 51.32 56.89 57.49 13.6 2.7

stripNear_025 51.23 51.70 57.37 57.96 13.6 2.7

stripFar_025 51.61 52.07 57.85 58.43 13.6 2.7

stripNear_026 51.97 52.42 58.31 58.89 13.6 2.7

stripFar_026 52.34 52.77 58.77 59.33 13.6 2.7

stripNear_027 52.69 53.12 59.22 59.77 13.6 2.7

stripFar_027 53.03 53.45 59.66 60.20 13.6 -

A.4 tanDEM elevation beams

Especially for the TanDEM-X mission, a new set of beams has been defined for the first and second acquisition year. The first year beams (*_a1*) overlap half the swath of their neighboring second year beams (*_a2*) to achieve optimum DEM homogeneity during the mosaicking process. These beams are only used for bistatic and pursuit monostatic SM single polarization acquisitions DTs. The tanDEM beams from 005 to 090 cover a look angle range similar to strip beams 007-016. The tanDEM beams over 53° are foreseen to be used for Antarctica acquisitions. No margin for the swath widths is specified.

Beam ID

Min. look

angle [deg]

Max. look

angle [deg]

Min. incidence

angle [deg]

Max. incidence

angle [deg]

Ground swath width [km]

Ground swath

overlap to next swath

[km]

tanDEM_a1_010 27.40 29.98 29.81 32.66 31.0 4.0

tanDEM_a1_020 29.65 32.16 32.30 35.10 31.8 4.0

tanDEM_a1_030 31.85 34.25 34.75 37.44 32.2 4.0

tanDEM_a1_040 33.96 36.20 37.11 39.65 32.0 4.0

tanDEM_a1_050 35.93 38.07 39.34 41.76 32.2 4.0

tanDEM_a1_060 37.81 39.76 41.47 43.71 31.3 4.0

tanDEM_a1_070 39.52 41.34 43.43 45.53 30.9 4.0

tanDEM_a1_080 41.12 42.74 45.26 47.15 29.1 4.0

tanDEM_a1_090 42.52 43.88 46.89 48.48 25.7 -

tanDEM_a1_antarctica1 53.81 54.55 60.68 61.64 25.5 4.0

tanDEM_a1_antarctica2 54.44 55.14 61.50 62.43 25.5 -





tanDEM_a2_005 26.10 28.72 28.38 31.27 30.7 4.0

tanDEM_a2_015 28.39 30.92 30.91 33.72 31.2 4.0

tanDEM_a2_025 30.61 33.04 33.36 36.08 31.6 4.0

tanDEM_a2_035 32.74 35.05 35.75 38.35 31.8 4.0

tanDEM_a2_045 34.77 36.95 38.03 40.50 31.8 4.0

tanDEM_a2_055 36.69 38.72 40.19 42.51 31.4 4.0

tanDEM_a2_065 38.47 40.35 42.22 44.38 30.8 4.0

tanDEM_a2_075 40.12 41.82 44.11 46.08 29.6 4.0

tanDEM_a2_085 41.60 43.10 45.82 47.57 27.5 -

tanDEM_a2_antarctica1 53.44 54.18 60.20 61.16 24.9 3.3

tanDEM_a2_antarctica2 54.09 54.79 61.03 61.96 24.8 -

A.5 SL/HS elevation beams (single and dual polarization)

The SL/HS beams cover the incidence angle range between 15° and 60° with a minimum ground swath width of over 15 km and an overlap of more than 10 km. These specifications are for nominal SL acquisitions. For imaging modes with higher resolution or higher transmitted bandwidth the swath size and overlap may differ. The spot beams are used for (alternating) bistatic spotlight single and dual polarization acquisitions.

For SL single and dual polarization the ground range and azimuth extent of a scene is 10 km by 10 km. For HS single and dual polarization the azimuth extent is reduced to 5 km. In the 300MHz HS mode the azimuth and range size of the scene may be further reduced due to timing constraints.

All spotlight modes share the same beams which are designed with a ground swath width of 17.8 km. The overlap to the next beam is 12.7 km with a margin of 2.5 km. Thus, the ordered scene coordinates can be placed in the center of SL/HS products.

Beam ID

Min. look angle [deg]

Max. look angle [deg]

Min. incidence angle [deg]

Max. incidence angle [deg]

spot_001 13.57 15.41 14.68 16.69

spot_002 14.09 15.93 15.25 17.25

spot_003 14.62 16.44 15.82 17.80

spot_004 15.13 16.95 16.38 18.36

spot_005 15.65 17.46 16.94 18.91

spot_006 16.17 17.96 17.50 19.46

spot_007 16.68 18.46 18.06 20.00

spot_008 17.19 18.96 18.61 20.54

spot_009 17.69 19.45 19.16 21.08

spot_010 18.19 19.94 19.71 21.62

spot_011 18.69 20.43 20.25 22.15

spot_012 19.19 20.91 20.79 22.68





spot_013 19.68 21.39 21.33 23.20

spot_014 20.17 21.87 21.86 23.72

spot_015 20.65 22.34 22.39 24.24

spot_016 21.13 22.81 22.92 24.75

spot_017 21.61 23.27 23.44 25.26

spot_018 22.08 23.73 23.96 25.77

spot_019 22.55 24.19 24.48 26.27

spot_020 23.02 24.64 24.99 26.77

spot_021 23.48 25.09 25.50 27.27

spot_022 23.94 25.54 26.00 27.76

spot_023 24.40 25.98 26.50 28.24

spot_024 24.85 26.42 27.00 28.73

spot_025 25.30 26.85 27.49 29.21

spot_026 25.74 27.29 27.98 29.68

spot_027 26.18 27.71 28.47 30.16

spot_028 26.62 28.14 28.95 30.62

spot_029 27.05 28.56 29.43 31.09

spot_030 27.48 28.97 29.90 31.55

spot_031 27.91 29.38 30.37 32.01

spot_032 28.33 29.79 30.84 32.46

spot_033 28.75 30.19 31.30 32.91

spot_034 29.16 30.59 31.76 33.35

spot_035 29.57 30.99 32.21 33.79

spot_036 29.98 31.38 32.66 34.23

spot_037 30.38 31.77 33.11 34.66

spot_038 30.78 32.16 33.56 35.09

spot_039 31.17 32.54 33.99 35.52

spot_040 31.56 32.91 34.43 35.94

spot_041 31.95 33.29 34.86 36.36

spot_042 32.33 33.66 35.29 36.77

spot_043 32.71 34.02 35.71 37.19

spot_044 33.09 34.38 36.13 37.59

spot_045 33.46 34.74 36.55 38.00

spot_046 33.82 35.10 36.96 38.40

spot_047 34.19 35.45 37.37 38.79

spot_048 34.55 35.80 37.78 39.18

spot_049 34.91 36.14 38.18 39.57

spot_050 35.26 36.48 38.58 39.96

spot_051 35.61 36.82 38.97 40.34

spot_052 35.95 37.15 39.36 40.72

spot_053 36.30 37.48 39.75 41.09





spot_054 36.63 37.80 40.13 41.46

spot_055 36.97 38.13 40.51 41.83

spot_056 37.30 38.45 40.89 42.20

spot_057 37.63 38.76 41.26 42.56

spot_058 37.95 39.07 41.63 42.91

spot_059 38.27 39.38 42.00 43.27

spot_060 38.59 39.69 42.36 43.62

spot_061 38.91 39.99 42.72 43.97

spot_062 39.22 40.29 43.08 44.31

spot_063 39.52 40.59 43.43 44.65

spot_064 39.83 40.88 43.78 44.99

spot_065 40.13 41.17 44.12 45.32

spot_066 40.43 41.45 44.47 45.65

spot_067 40.72 41.74 44.81 45.98

spot_068 41.01 42.02 45.14 46.31

spot_069 41.30 42.29 45.48 46.63

spot_070 41.58 42.57 45.81 46.95

spot_071 41.87 42.84 46.13 47.27

spot_072 42.15 43.11 46.46 47.58

spot_073 42.42 43.37 46.78 47.89

spot_074 42.69 43.63 47.09 48.20

spot_075 42.96 43.89 47.41 48.50

spot_076 43.23 44.15 47.72 48.80

spot_077 43.49 44.40 48.03 49.10

spot_078 43.75 44.65 48.34 49.40

spot_079 44.01 44.90 48.64 49.69

spot_080 44.27 45.15 48.94 49.98

spot_081 44.52 45.39 49.24 50.27

spot_082 44.77 45.63 49.53 50.55

spot_083 45.02 45.87 49.82 50.83

spot_084 45.26 46.10 50.11 51.11

spot_085 45.50 46.33 50.40 51.39

spot_086 45.74 46.56 50.68 51.67

spot_087 45.98 46.79 50.96 51.94

spot_088 46.21 47.02 51.24 52.21

spot_089 46.44 47.24 51.52 52.48

spot_090 46.67 47.46 51.79 52.74

spot_091 46.90 47.67 52.06 53.00

spot_092 47.12 47.89 52.33 53.26

spot_093 47.34 48.10 52.60 53.52

spot_094 47.56 48.31 52.86 53.77





spot_095 47.77 48.52 53.12 54.03

spot_096 47.99 48.73 53.38 54.28

spot_097 48.20 48.93 53.64 54.53

spot_098 48.41 49.13 53.89 54.77

spot_099 48.62 49.33 54.14 55.02

spot_100 48.82 49.53 54.39 55.26

spot_101 49.02 49.72 54.64 55.50

spot_102 49.22 49.91 54.89 55.74

spot_103 49.42 50.10 55.13 55.97

spot_104 49.62 50.29 55.37 56.20

spot_105 49.81 50.48 55.61 56.44

spot_106 50.00 50.66 55.84 56.67

spot_107 50.19 50.84 56.08 56.89

spot_108 50.38 51.02 56.31 57.12

spot_109 50.56 51.20 56.54 57.34

spot_110 50.75 51.38 56.77 57.56

spot_111 50.93 51.55 57.00 57.78

spot_112 51.11 51.73 57.22 58.00

spot_113 51.28 51.90 57.44 58.22

spot_114 51.46 52.07 57.66 58.43

spot_115 51.63 52.23 57.88 58.64

spot_116 51.80 52.40 58.10 58.85

spot_117 51.97 52.56 58.31 59.06

spot_118 52.14 52.72 58.53 59.27

spot_119 52.31 52.88 58.74 59.47

spot_120 52.47 53.04 58.95 59.68

spot_121 52.64 53.20 59.16 59.88

spot_122 52.80 53.35 59.36 60.08

doc.: td-gs-ps-3028 · the following documents are fully applicable together with this document....

Documents