Filter component

[jokd]

Is your feature request related to a problem? Please describe.
I am building a plugin (or control) that shows a "double" slider when a certain layer is visible, enabling the user to filter features in a layer based on the values of the sliders. While at it I also created a slider that simply toggles an array of layers(eg an array of orthophotos from different years) so instead of picking layers in the legend you can use the slider. Considering this and other ways of filtering a layer, maybe we should create a filter component that handles various types of layer filtering, providing a consistent UI experience and ease developing different filter functions.

Describe the solution you'd like
A button in the legend or submenu that triggers a filter window (for layers with a configured filter)

Describe alternatives you've considered
Using a function specific ui solution.

A mockup of what it could look like but with a more suitable icon. Black icon if there is a filter and origo blue when a filter is active. That way you can easily see that a filter is active without keeping the window open.

[johnnyblasta]

Perhaps use #fa-sliders or #fa-filter as icon for button.

[Grammostola]

Could you specify the scope? Layer types, is this a per-layer feature? Pre-defined with the map or definable for the user? With new ui components? Part of the api?

[jokd]

I should clarify a bit. The issue is whether a general filter component/orchestrator is a good idea for the origo core. That component should handle any kind of custom filter that is setup and simply present a simple interface to add a custom "filter function" to Origo and won't have any filter functionality on its own but rather handle registering filters, handling their status and adding ui elements and listeners. Eg a button in the legend for layers that have filter possibilties and present a floating element with configured content and rendered filters.
What this filter window will show and its functionality is up t the chosen filter which will have its own render method etc.
The attached image in the issue was an example of a slider filter registered in the filter component and configured to be applied to the Byggnadsår layer.
Filter functionality, scope setup etc is all up to the different filters and could be handled in the API. WMS filtering, vector data filtering, layer toggling etc are example of possible filters. Even content styling could be possible with the same solution.