Skip to main content
Question

related candidates is 0 when using group by settings

  • March 14, 2018
  • 3 replies
  • 24 views
A
Forum|alt.badge.img

Hi all,

FME amateur here!

I'm trying to increase the performance of my model. The performance is vastly improved when I use the Group By setting and Parallel Processing in my SpatialRelator.

The SpatialRelator is followed by an Attribute Creator which uses a conditional query (combination the number of related_candiates and dataset name) to set a value.

Without the Group By and Parallel Processing FME will correctly tell me the number of related features in the related_candidates field. However when I put the Group By setting on - every value in the related_candidates field is 0.

Does anyone how to fix this?

Ta

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

lars_de_vries
Forum|alt.badge.img+10

Looking at your Test Condition, I cannot say for sure that the _related_candidates output indeed is larger than 0 or not.

I would suggest, for testing purposes, to first test whether there are truely no related candidates by using only the statement _related_candidates > 0. If there are still no related candidates, than you'll need to check whether the attribute SUBURB is available on both base and candidate features.

If the attribute is available on both base and candidate features, than you'll need to check whether the values are identical and do not differ in casing.

I hope this helps you to solve your problem.

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • March 14, 2018
Do the Requestor features and the Supplier features both have the attribute "SUBURB" which you've set to the Group By parameter?

 

 

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
A
Forum|alt.badge.img
  • anne_shanahan
  • Author
  • 7 replies
  • March 14, 2018
Thank you! I didn't realise the attribute SUBURB needed to be present in both datasets! There are multiple suppliers - none of which have SUBURB. I guess this eliminates the use of the Group By setting?

 

 

Community Stats

32,087
Posts
121,855
Replies
39,729
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.