This workflow works on S1 StripMap and Cosmo data. It represents the main processing for this data and needs as inputs : two SLC images and an only DEM file. The inputs should be filled into the configuration file descripted in the next chapter.
This workflow works on S1 StripMap, TSX/PAZ/TDX and Cosmo data. It represents the main processing for this data and needs as inputs : two SLC images and an only DEM file. The inputs should be filled into the configuration file descripted in the next chapter.
This chain is divided into four parts :
This chain is divided into four parts :
...
@@ -123,4 +123,4 @@ Five sections compose the configuration file :
...
@@ -123,4 +123,4 @@ Five sections compose the configuration file :
The processing chain needs metadata to launch the applications. Thus the path to the input images must be into the native directory for each kind of products (i.e SAFE directory for Sentinel-1 products). The DEM has to be a unique file but can be built with several tiles by using some gdal commands, for example.
The processing chain needs metadata to launch the applications. Thus the path to the input images must be into the native directory for each kind of products (i.e SAFE directory for Sentinel-1 products). The DEM has to be a unique file but can be built with several tiles by using some gdal commands, for example.
For that moment the Metadata_Correction is not used (activate always sets to false) and the ground geometry for interferogram does not provide satisfactory results.
For that moment the Metadata_Correction is not used (activate always sets to false). For your information, `Metadata_Correction` chain is never used (activate always sets to false) and will be removed, soon.