Configuration
Request Configuration file
The request configuration file passed to S1Processor is in .ini
format. It is expected to contain the following entries.
Note
S1LIAMap and S1IAMap work with a subset of the following configuration keys. Unsupported keys will simply be ignored.
You can use this this template
, as a starting point.
[PATHS]
section
Option |
Description |
---|---|
|
Where S1 images are downloaded thanks to EODAG.
|
|
Where products are generated. |
|
Where (non Local) Incidence Maps and sin(IA) products are generated. Its
default value is |
|
Where Local Incidence Maps and sin(LIA) products are generated. Its
default value is |
|
Where intermediary files are produced, and sometimes cached for longer periods. |
|
Path to Geoid model. If left unspecified, it’ll point automatically to the geoid resource shipped with S1 Tiling. |
|
Path to DEM ( |
|
Path to DEM files. |
|
Filename format string to locate the DEM file associated to an
identifier within the [PATHS].dem_dir directory.
|
|
DEM identifier to inject in the products GeoTIFF metadata under
|
|
(deprecated) Use [PATHS].dem_dir. Path to SRTM files. |
|
Where precise orbit orbit files (EOF) are expected to be found, or where
they would be downloaded on the fly.
Default value is See also Q: How can I configure precise orbit files retrieval?. |
[DataSource]
section
Option |
Description |
---|---|
|
If |
|
Designates where the EODAG configuration file is expected to be found.
From S1Tiling point of view, EODAG configuration file will list the
authentification credentials for the know providers and their respective
priorities.
For instance, given a PEPS account, peps:
auth:
credentials:
username: THEUSERNAME
password: THEPASSWORD
|
|
Number of parallel downloads (+ unzip) of source products. Warning Don’t abuse this setting as the data provider may not support too many parallel requests. |
|
The Region of Interest (ROI) for downloading is specified in
[DataSource]
roi_by_tiles : 33NWB
|
|
Defines the list of platforms from where come the products to download
and process.
Valid values are Warning A single value is expected in NORMLIM scenarios. |
|
Defines the polarisation mode of the products to download and process.
Only six values are valid: |
|
Download only the products acquired in ascending ( Warning Each relative orbit is exclusive to one orbit direction, orbit_direction and relative_orbit_list shall be considered as exclusive. |
|
Download only the products from the specified relative orbits. By default (when left unspecified), no filter is applied. Warning Each relative orbit is exclusive to one orbit direction, orbit_direction and relative_orbit_list shall be considered as exclusive. Warning A single value is expected in NORMLIM and Ellipsoid Incide Angle scenarios. |
|
Initial date in |
|
Final date in |
|
Percentage of tile area to be covered for a single or a pair of Sentinel-1 products to be retained. The number is expected as an integer in the [1..100] range. |
[Mask]
section
Option |
Description |
---|---|
|
This option allows you to choose if you want to generate border masks of
the S2 image files produced. Values are |
[Processing]
section
Option |
Description |
||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Tells whether DEM and Geoid files are copied in a temporary directory, or if symbolic links are to be created. For performance reasons with OTB, it’s better to regroup the minimal subset of the DEM files required for processing. Symbolic links work fine most of the time, however if the files are on a remote shared filesystem (GPFS, NAS…), performances will be degraded. In those cases, it’s better to copy the required DEM files on a local filesystem. Geoid file will be also copied (or symlinked),
but in Two values are supported for this option: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Defines the calibration type: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Activate the thermal noise removal in the images. Values are |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Noise removal may set some pixel values to 0. However, 0, is currently reserved by S1Tiling chain as a “no-data” value introduced by Margin Cutting and Orthorectification. This parameter defines which value to use instead of 0 when noise is removed. By default: 1e-7 will be used. |
||||||||||||||||||||||||||||||||||||||||||||||||
|
No-data value to use in IA files |
||||||||||||||||||||||||||||||||||||||||||||||||
|
No-data value to use in LIA files |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Pixel size (in meters) of the output images |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Path and filename of the tile shape definition (ESRI Shapefile). If left unspecified, it’ll point automatically to the Features.shp shapefile resource shipped with S1 Tiling. |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Grid spacing (in meters) for the interpolator in the orthorectification process. For more information, please consult the OTB OrthoRectification application. A nice value is |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Interpolation method used in the orthorectification process. For more information, please consult the OTB OrthoRectification application. Default value is set to nearest neighbor interpolation ( |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Tiles to be processed. The tiles can be given as a list:
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
Running mode:
Ex.: mode : debug logging
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
Number of processes to be running in parallel
Note For optimal performances, |
||||||||||||||||||||||||||||||||||||||||||||||||
|
RAM allowed per OTB application pipeline, in MB. |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Numbers of threads used by each OTB application. Note For optimal performances, |
||||||||||||||||||||||||||||||||||||||||||||||||
|
When LIA sine map are produced, we may also desire the angle values in degrees (x100). Possible values are:
Note This option will be ignored when no LIA sine map is required. The LIA
sine map is produced by S1LIAMap program, or
when calibration mode is |
||||||||||||||||||||||||||||||||||||||||||||||||
|
By default, S1IAMap program produce a map of the incidence angle to the WGS84 ellipsoid in degrees x 100. This option permis to select which of the 4 IA maps will be generated.
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
DEM files projected on S2 tiles are required to produce LIA maps. This parameters permits to select the resampling method that gdalwarp will use. The possible values are: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Permits to override the analysis on whether top/bottom lines shall be
forced to 0 in cutting step. Possible values are:
Warning This option is not meant to be used. It only makes sense in some very specific scenarios like tests. |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Set of filename format templates that permits to override the default filename formats used to generate filenames. The filename formats can be overridden for both intermediary and final products. Only the final products are documented here. Filename formats for intermediary products are best left alone. If you change any, make sure to not introduce ambiguity by removing a field that would be used to distinguish two unrelated products. Available fields come from
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
File format pattern for concatenation products, for β°, σ° and γ° calibrations. Default value: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
File format pattern for concatenation products when NORMLIM calibrated. Default value: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
File format pattern for IA cos(IA), sin(IA) and tan(IA) files Default value: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
File format pattern for LIA and sin(LIA) files Default value: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
File format pattern for filtered files Default value: Default value: |
||||||||||||||||||||||||||||||||||||||||||||||||
|
Set of directory format templates that permits to override the default directories where products are generated. The directory formats can only be overridden for final products. The only fields available are:
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
Set of extra options to create certain products. Creation options take a
first and optional pixel type (
|
[Filtering]
section
Note
Multitemporal filtering is not yet integrated in S1Tiling.
Option |
Description |
---|---|
|
The following spatial speckling filter methods from OTB
Despeckle application are supported:
|
|
Sets the window radius for the spatial filtering. |
|
Deramp factor – for Frost filter only. |
|
Number of looks – for all but Frost => Lee, Gammamap and Kuan |
|
If not caring for non-filtered product (and if filter method is
specified), then the orthorectified and concatenated products won’t be
considered as mandatory and they will not be kept at the end of the
processing.
This (exclusion) feature cannot be used alongside
[Mask].generate_border_mask (i.e.
Warning Note: This feature is only supported after LIA calibration as of V1.0 of S1Tiling. See Issue #118. |
[Metadata]
section
You can place in this section any extra key : value
information that you
want written in the GeoTIFF metadata of S1Tiling products.
Log configuration
Default logging configuration is provided in S1Tiling
installing directory.
It can be overridden by dropping a file similar to
../s1tiling/logging.conf.yaml
in the same directory as the one
where the request configuration file is. The file
is expected to follow logging configuration
file
syntax.
Warning
This software expects the specification of:
When mode contains logging
, we make sure that
file
and important
handlers
are added to
the handlers of root
and distributed.worker
loggers
. Note that this is the default configuration.
When mode contains debug
the DEBUG
logging
level is forced into root
logger, and $OTB_LOGGER_LEVEL
environment
variable is set to DEBUG
.
Working on clusters
Todo
By default, S1Tiling works on single machines. Internally it relies on
distributed.LocalCluster
a small adaptation would be required to
work on a multi-nodes cluster.
Warning
When executing multiple instances of S1Tiling simultaneously, make sure to use different directories for:
logs – running S1Tiling in different directories, like
$TMPDIR/
on TREX, should be enoughstoring input files, like for instance
$TMPDIR/data_raw/
on TREX for instance.