I’m a huge fan of Speckle’s super easy to use element filtering. I use the filter / isolate / hide in view / auto color by parameter value all the time to visualize and check parameter values.
It would be extremely helpful to be able to filter elements by more than one criterion.
E.g. “show all doors on ground floor of type “double flush” with a fire rating of “x” and an opening of 2.0m”.
Has this been discussed before? 
Hi Henrik. Thanks for the suggestion! It has indeed been requested and discussed before and it’s on the list of improvements we want to make in the viewer this year . I’m noting you down as interested in the feature! We might reach out when we start working on it.
3 Likes
Hi Henrik. We have just released an updated filtering panel with support for what you’re requesting. You can read the announcement here: Advanced filtering in the web viewer | Speckle
I’d love if you could give it a go and leave any feedback here :).
2 Likes
Benjamin,
Thanks for getting back to me. I finally came around to testing Speckle some more with a current Revit project.
Overall, I like the improved filtering feature a lot. Stacking multiple filters to drill down deeper for specific elements is now super easy and intuitive.
Here are some suggestions on how filtering could be further improved:
- More filter operators like “Contains” or “Does not contain” to be able to search within strings or “Less Than”, “More Than”, “Range” to be able to search in numeric values - this has already been implemented in Intelligence Dashboards
- Having the option to chain filters with logical AND, OR conditions to control how filter rules interact with each other
- The ability to save and load predefined filter sets would be extremely handy. You could, for example, set up a filter to color doors by different fire ratings and save this as a predefined filter. That way, project leads (who often times have no clue which parameter holds the fire rating value) could get a quick and easy overview
Best regards
Henrik
1 Like
Thanks for the great feedback, Henrik!
This will be landing in frontend soon, hopefully in the next month.
We haven’t considered this before, but it does seem like it would be useful. Consider the request logged.
Agree that this would be a good addition, it’s on the roadmap, but I’m not sure when it’s likely to be done. @benjavo may know more.
We’ll let you know when there has been some progress on these.
Heh, we’ve been considering this for model validation (IDS importing, etc.) for dashboards - sounds like we should talk 
Concern has been that, to date, very useful logic functions can become increasingly difficult to use quickly.
Sorry, I should have said “I haven’t considered this”
Let’s sync on this, I’m interested to see the issue you describe with usability
@Andrew_Wallace @jonathon
Thanks for the feedback! Good to know that parts of my suggestions are already being considered. I’ll keep an eye out! 
@jonathon I agree that when chaining filter criteria with different conditions the filter logic can become quite tricky very quickly. It’s probably also a challenge how to convey this logic to the user from u UI perspective. I think Revizto has solved this quite elegantly with filter groups:
1 Like
Indeed, filter groups or something like it is what we’ve sketched, but speaking with many users… love them… this stretches the mind for some
1 Like