s1tiling.libs.otbwrappers.ProjectDEMToS2Tile
- class s1tiling.libs.otbwrappers.ProjectDEMToS2Tile(cfg: Configuration)[source]
Bases:
ExecutableStepFactory
Factory that produces a
ExecutableStep
that projects DEM onto target S2 tile as described in Project DEM to S2 tile.It requires the following information from the configuration object:
ram_per_process
tmp_dir
fname_fmt – optional key: dem_on_s2
out_spatial_res
interpolation_method – OTB key converted to GDAL equivalent
nb_procs
nodatas.DEM
It requires the following information from the metadata dictionary:
tile_name
tile_origin
New methods & Specialized methods
__init__
Constructor
Register temporary files from previous step for removal.
Returns the parameters to use with gdalwarp to projected the DEM onto the S2 geometry.
Set S2 related information, that should have been carried around...
Methods inherited from parent
Directory used to store temporary files before they are renamed into their final version.
Duplicates, completes, and returns, the meta dictionary with specific information for the current factory regarding tasks analysis.
This specialization of
StepFactory.build_step_output_tmp_filename()
will automatically insert.tmp
before the filename extension.Abstract method used to test whether a
StepFactory
has all its external requirements fulfilled.Instanciates the step related to the current
StepFactory
, that consumes results from the previous input steps.Returns the names of typical result files in case their production is required (i.e. not in-memory processing).
Accessor to where output files will be stored in case their production is required (i.e. not in-memory processing).
Attributes and properties
Property image_description, used to fill
TIFFTAG_IMAGEDESCRIPTION
Step Name property.
Property ram_per_process
- _do_create_actual_step(execution_parameters: Dict, input_step: AbstractStep, meta: Dict) ExecutableStep
This Step creation method does more than just creating the step. It also executes immediately the external process.
- _update_filename_meta_post_hook(meta: Dict) None
Hook meant to be overridden to fix product metadata by overriding their default definition.
Called from
update_filename_meta()
- _update_filename_meta_pre_hook(meta: Dict) Dict
Hook meant to be overridden to complete product metadata before they are used to produce filenames or tasknames.
Called from
update_filename_meta()
- build_step_output_filename(meta: Dict) str | List[str]
Returns the names of typical result files in case their production is required (i.e. not in-memory processing).
This specialization uses
gen_output_filename
naming policy parameter to build the output filename. See the Available naming policies.
- build_step_output_tmp_filename(meta: Dict) str | List[str]
This specialization of
StepFactory.build_step_output_tmp_filename()
will automatically insert.tmp
before the filename extension.
- check_requirements() Tuple[str, str] | None
Abstract method used to test whether a
StepFactory
has all its external requirements fulfilled. For instance,OTBStepFactory
’s will check their related OTB application can be executed.- Returns:
None
if requirements are fulfilled.- Returns:
A message indicating what is missing otherwise, and some context how to fix it.
- complete_meta(meta: Dict, all_inputs: List[Dict[str, AbstractStep]]) Dict [source]
Register temporary files from previous step for removal.
- create_step(execution_parameters: Dict, previous_steps: List[List[Dict[str, AbstractStep]]]) AbstractStep
Instanciates the step related to the current
StepFactory
, that consumes results from the previous input steps.1. This methods starts by updating metadata information through:
complete_meta()
on theinput
metadatas.2. Then it updates the GDAL image metadata information that will need to be written in the pipeline output image through
update_image_metadata()
.3. Eventually the actual step creation method is executed according to the exact kind of step factory (
ExecutableStepFactory
,AnyProducerStepFactory
,OTBStepFactory
) through the variation point_do_create_actual_step()
.While this method is not meant to be overridden, for simplity it will be in
Store
factory.Note: it’s possible to override this method to return no step (
None
). In that case, no OTB Application would be registered in the actualPipeline
.
- property image_description: str | List[str]
Property image_description, used to fill
TIFFTAG_IMAGEDESCRIPTION
- output_directory(meta: Dict) str
Accessor to where output files will be stored in case their production is required (i.e. not in-memory processing)
This property is built from
gen_output_dir
construction parameter. Typical values for the parameter are:os.path.join(cfg.output_preprocess, '{tile_name}'),
wheretile_name
is looked intometa
parameterNone
, in that case the result will be the same astmp_directory()
. This case will make sense for steps that don’t produce required products
- parameters(meta: Dict) List[str] [source]
Returns the parameters to use with gdalwarp to projected the DEM onto the S2 geometry.
- property ram_per_process
Property ram_per_process
- tmp_directory(meta) str
Directory used to store temporary files before they are renamed into their final version.
This property is built from
gen_tmp_dir
construction parameter. Typical values for the parameter are:os.path.join(cfg.tmpdir, 'S1')
os.path.join(cfg.tmpdir, 'S2', '{tile_name}')
wheretile_name
is looked intometa
parameter
- update_filename_meta(meta: Dict) Dict
Duplicates, completes, and returns, the meta dictionary with specific information for the current factory regarding tasks analysis.
This method is used:
while analysing the dependencies to build the task graph – in this use case the relevant information are the file names and paths.
and indirectly before instanciating a new
Step
Other metadata not filled here:
get_task_name()
which is deduced from out_filename by defaultout_extended_filename_complement()
It’s possible to inject some other metadata (that could be used from
_get_canonical_input()
for instance) thanks to_update_filename_meta_pre_hook()
.This method is not meant to be overridden. Instead it implements the template method design pattern, and expects the customization to be done through the specialization of the hooks: