# New implementation of functor filter in OTB !!!!

**URL:** <https://discourse.itk.org/t/new-implementation-of-functor-filter-in-otb/2024>\
**Category:** Engineering\
**Created:** [July 9, 2019, 4:08am UTC](https://discourse.itk.org/t/new-implementation-of-functor-filter-in-otb/2024 "2019-07-09T04:08:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![blowekamp](https://discourse.itk.org/user_avatar/discourse.itk.org/blowekamp/32/79_2.png) [@blowekamp](https://discourse.itk.org/u/blowekamp)\
**Post date:** [July 9, 2019, 2:33pm UTC](https://discourse.itk.org/t/new-implementation-of-functor-filter-in-otb/2024/3 "2019-07-09T14:33:29Z")

</div>

This thread appears related:

> [@New implementation of functor filter in OTB](https://discourse.itk.org/t/new-implementation-of-functor-filter-in-otb/1382):
>
> Hi all, I am working on a new functor filter implementation in OTB, and feedbacks suggest that this is something that could be interesting for ITK. Basically you can use it very simply with any functor with operator() or lambda that has any number of arguments. It will deduce all the types at compile time (supporting scalar pixels, VariableLengthVector, Neighborhoods …). You can find the details here [https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/merge\_requests/268](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/merge_requests/268), but here is a bit of tea…

Perhaps this is continuing the effort?

---

_[View the full topic](https://discourse.itk.org/t/new-implementation-of-functor-filter-in-otb/2024)._