Try to upgrade the transformer SpatialFilter in the Navigator window and see if this helps:

Thanks @sigtill but unfortunately same result (I tried to upgrade Spatial Relator instead of Spatial Filter).My workaround (at least for now) is to 'Generate List' within SpatialRelator, exposing all attributes. Next, I have exposed a 'relationship'-attribute value within the list holding the correct value and renamed it to the original attribute.

There were issues with the spatial relator and attribute handling but I thought they were resolved in 2019.1 Although this looks like a slightly different flavour

https://knowledge.safe.com/questions/86471/spatial-relator-attribute-handling-replacing-value.html

@egomm I hesitated to add my issue to that topic. Indeed this topic/outcome of SpatialRelator is somewhat different but it adds to the problem with this transformer within v2019. Maybe admin should merge this topic with yours.

Hi @gisaalter Please send your workspace and some sample data to https://www.safe.com/support/report-a-problem/ Thanks!

previous issue (pointed out by @egomm ) was conflict between an operand and a non existing operand.

Logically that is no conflict, therefore the requestor prevails. I would say the transformer did it's intended job then (of course non intended result).

I wonder in this issue, as I've done it myself, is weather you should not clear the results of your previous relators.

Try removing the previous relators attributes prior to sending their results to the next.