SAR Data Package
Product file naming convention describes the product processing level so that a user does not have to analyze product metadata to understand key properties. The product filename components are shown in Figure 1. The Product ID is a unique identifier of the acquired scene and is assigned during scene ordering and acquisition.
The constituent elements are explained in more detail in Table 1
|XN_||sensor||X2/X4/X5||specific sensor that has acquired the scene|
|PPL_||product processing level||SLC/GRD||variant of processing level|
|IM_||imaging mode||SM/SMH/SL/SLH||stripmap, stripmap-high, spotlight, spotlight-high|
|PRID_||product id||eg. 6403||data take ID|
|YYYYMMDD||UTC start date||eg. 20190211||YYYYMMDD format|
|Thhmmss||UTC start time||eg. T131415||Thhmmss format|
SAR images can be ordered either from archive (previously collected imagery) or as a planned future acquisition. Products are geo-coded and radiometrically corrected.
ICEYE’s focus is currently on the integrity of complex and amplitude images. This will expand over the next year as we introduce a phase history data product and other products derived from complex and amplitude images.
A basic ICEYE product is represented by a set of SAR image binary data, corresponding image metadata and it is delivered as a singular product package. Products are characterized by the payload configuration (such as imaging mode and look direction) used by the respective satellite, as well as the level of processing that has been applied to the SAR scene. With respect to the data geometric projection and representation, products are differentiated into two primary types: geo-referenced Single Look Complex (SLC) and Amplitude Images (Also known as Ground Range Detected (GRD) scenes). SAR image binary data, delivered as digital numbers or quadrature components, can be converted to radar brightness \(\beta_0\) and mean radar cross section \(\sigma_0\) using the annotated calibration factor in the image metadata.