SpatialFilter: output per predicate

How would you propose to deal with a single feature, that receives multiple predicates?

Send them through every appropriate port, thus creating duplicates? Or only through the first matching port?

I’d say the former. But you could have the latter as an option. 

I could see this working like the TestFilter. So you would order the tests in the order that you want, assigning the tests to different or same ports. 

A SpatialTestFilter

Yeah, perhaps this would be a new transformer? Renaming the current SpatialFilter to SpatialTester?

I expect a Zipster t-shirt for this. 

Thanks ​@p_c_20 for the idea!
I’m curious if using the AttributeFilter on the output attribute for the predicate would work for you? If this doesn’t work for you, could you explain a little bit more about why you’re wanting one port per predicate.

I see from the follow-up comments though that maybe the real issue is wanting to have control of the order the Spatial Predicate Test?

Thanks ​@andreaatsafe for update it!

Hi, ​@andreaatsafe ! With the caveat that I haven’t had coffee yet…..

What I like is flexibility. Different tasks throw up different use cases - and of course, it’s not just for me (how selfish would that be?); these things have to work for the largest possible number of members of a massive community. 

So, with that in mind - yes, I think control over the order would be a good thing. 

I do, however, wonder if there is still a case for saying, ‘which of these predicates do these features satisfy?’

Similar to ‘pass against one/pass against all’ you could have setting which enables ‘output all successes’, giving one port per predicate outcome. 
 

Admittedly, I don’t believe I have plumbed the full depths of SpatialFilter, so maybe I can hack this together using existing functionality somehow.