This workflow works on S1 StripMap and Cosmo data. It spreads the main processing with multitemporal SAR images.
This workflow works on S1 StripMap, TSX/PAZ/TDX and Cosmo data. It spreads the main processing with multitemporal SAR images.
An input path indicates where to find all SAR images and a selection can be made with dates. One reference image is fixed by users and other images are processed as secondary image. This chain deals with DEM differently by creating automatically the corresponding DEM from a folder filled with SRTM files and a shapefile that contains the SRTM tile grid with the tiles location (lat,lon). The SRTM files must be hgt files and shapefiles are provided with DiapOTB. The SRTM tile grid shapefile is useful to select automatically the SRTM tiles needed in order to compute the interferograms on the area corresponding to the SAR images.
An input path indicates where to find all SAR images and a selection can be made with dates. One reference image is fixed by users and other images are processed as secondary image. This chain deals with DEM differently by creating automatically the corresponding DEM from a folder filled with SRTM files and a shapefile that contains the SRTM tile grid with the tiles location (lat,lon). The SRTM files must be hgt files and shapefiles are provided with DiapOTB. The SRTM tile grid shapefile is useful to select automatically the SRTM tiles needed in order to compute the interferograms on the area corresponding to the SAR images. Only SRTM files can be used here with the given shapefile.
@@ -47,7 +47,7 @@ Five sections compose the configuration file :
* **Geoid :** Path to Geoid file
* **Master_Image :** Filename of the master image
* **Master_Image :** Filename of the master image. For TSX/PAZ/TDX products, this field requires a relative path to reference image from Input_path as root.
* **Start_Date :** Start date, format('20151222')
...
...
@@ -56,7 +56,7 @@ Five sections compose the configuration file :
* **End_Date :** End date, format('20171119')
* **Exclude :** Time to exclude ('-9999' by default, no exlusion)
* **Exclude :** Time to exclude ('-9999' by default, no exlusion)
* **Input_Path :** Path to input folder
...
...
@@ -120,8 +120,8 @@ Five sections compose the configuration file :
* **Interferogram_mlran :** Ml factor on range for output inteferegram (only for interferogram).
* **Interferogram_mlazi :** Ml factor on azimut for output inteferegram (only for interferogram).
...
...
@@ -147,10 +147,10 @@ Five sections compose the configuration file :
* **Filtered_Interferogram_mlazi :** Ml factor on azimut for filtered inteferegram
* **Filtered_parameter_alpha :** alpha parameter for Goldstein filtering
The processing chain needs metadata to launch the applications. Thus, input images must be into the native directory for each kind of products (i.e SAFE directory for Sentinel-1 products).
The processing chain needs metadata to launch the applications. Thus, input images must be into the native directory for each kind of products (i.e SAFE directory for Sentinel-1 products). For your information, `Metadata_Correction` chain is never used (activate always sets to false) and will be removed, soon.
