Refactoring with FunctorImageFilter
This issue aims at tracking refactoring with FunctorImageFilter
.
-
otb::QuaternaryFunctorImageFilter
is no longer used by any code and can be removed -
otb::TernaryFunctorImageFilter
is used by:- Indices module (needs deeper refactoring)
- Simulation module (refactoring should be straightforward)
-
otb::BinaryFunctorImageFilter
is not used and can be removed (itk::BinaryFunctorImageFilter
is used, but not an issue for us) -
otb::UnaryFunctorImageFilter
is used in:- Common
- Unmixing
- AppFiltering
- AppClasification
- AppImageUtils
- AppSegmentation
- Projection
-
otb::UnaryImageFunctorWithVectorImageFilter
- OpticalCalibration
- Simulation
- Projection
- ImageManipulation
-
otb::UnaryFunctorVectorImageFilter
only used by:- Statistics
-
otb::UnaryFunctorNeighborhoodVectorImageFilter
:- Used by Edge, ImageManipulation, DimensionalityReduction
- Need to solve #1802 (closed) first
-
otb::UnaryFunctorNeighborhoodImageFilter
:- OpticalCalibration
- Labelling
- ImageManipulation
-
otb::BinaryFunctorNeighborhoodImageFilter
:- ChangeDetection
- RoadExtraction
- Need to solve #1802 (closed) first
Edited by Cédric Traizet