Skip to main content
Solved

Retain component attribution after aggregation/deaggregation


dustin
Influencer
Forum|alt.badge.img+30

I have a set of points and lines that I need to collectively scale down using the Scaler. I am combining all features using the Aggregator, scaling down, and then Deaggregating. The features are retaining the original attributes, but all features are getting the attribute values from just one of the features. I am needing the features to retain their original attribute values after the Deaggregator.

Best answer by jdh

In the aggregator create a list, with all attributes, in the deaggregator set the parameter List Attribute to Explode to the list you created in the aggregator.

View original
Did this help you find an answer to your question?

5 replies

ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • January 10, 2019

Assign a unique id to every component prior to aggregating. In the aggregator drop incoming attributes and build a list with the unique id. After whatever processing you need to do, deaggregate, then use the part number to access the relevant unique id from the list. Then you can merge the original attributes back to the transformed features using the unique id.

 

Another option is to include every attribute in your list, then after deaggregation explode the list and then test to only keep the features where the part number equals the element index.


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • Best Answer
  • January 10, 2019

In the aggregator create a list, with all attributes, in the deaggregator set the parameter List Attribute to Explode to the list you created in the aggregator.


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • January 10, 2019
ebygomm wrote:

Assign a unique id to every component prior to aggregating. In the aggregator drop incoming attributes and build a list with the unique id. After whatever processing you need to do, deaggregate, then use the part number to access the relevant unique id from the list. Then you can merge the original attributes back to the transformed features using the unique id.

 

Another option is to include every attribute in your list, then after deaggregation explode the list and then test to only keep the features where the part number equals the element index.

Both of those would work, but since FME 2016.1 (I think), there is no need to be that complicated, as the deaggregator has a parameter to explode an attribute list along with the geometry.


dustin
Influencer
Forum|alt.badge.img+30
  • Author
  • Influencer
  • January 10, 2019
jdh wrote:

In the aggregator create a list, with all attributes, in the deaggregator set the parameter List Attribute to Explode to the list you created in the aggregator.

Thank you., this worked beautifully. I was using a pre-existing Deaggregator that was placed in the file before 2016, so I didn't see that option until I upgraded the transformer.


ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • January 10, 2019
jdh wrote:

Both of those would work, but since FME 2016.1 (I think), there is no need to be that complicated, as the deaggregator has a parameter to explode an attribute list along with the geometry.

Ah so it does, it's while since I used the deaggregator


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings