Skip to main content
Solved

Help replacing this bloc of transformers with a shorter one

L
Forum|alt.badge.img

Hello,

I am working on input datasets having different schemas. In the end of my translation, I have to inspect obtained results. I had therefore to use a testfilter and 3 (AttributeManagers + Inspectors) as shown in the screenshot. The attributes managers perform some schema mapping depending on input features (this include removing and adding attributes)

 

Is there a way to reduce the amount of used Attribute managers and Inspectors ? My workspace is getting really big and I need to optimize it.

Thank you very much.

Best answer by redgeographics

Depending on exactly what you do in the AttributeManagers you might get away with replacing all 3 and the TestFilter with a single AttributeManager and make use of conditional statements (basically a Testfilter inside the AttributeManager). That might be a beast to set up and maintain though.

Perhaps a SchemaMapper could be useful too, again it depends on what you're doing exactly.

View original
Did this help you find an answer to your question?
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

david_r
Celebrity
  • david_rCelebrity
  • October 12, 2018

If you need to visually simplify the workspace, there are two simple solutions:

  1. Collapsing bookmarks, introduced in FME 2018
  2. Custom transformer

They both have their advantages and disadvantages, so be sure to skim through the docs before committing to either.

redgeographics
Celebrity
Forum|alt.badge.img+59
  • redgeographicsCelebrity
  • Celebrity
  • Best Answer
  • October 12, 2018

Depending on exactly what you do in the AttributeManagers you might get away with replacing all 3 and the TestFilter with a single AttributeManager and make use of conditional statements (basically a Testfilter inside the AttributeManager). That might be a beast to set up and maintain though.

Perhaps a SchemaMapper could be useful too, again it depends on what you're doing exactly.

FME rocks! \m/
fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • October 16, 2018
redgeographics wrote:

Depending on exactly what you do in the AttributeManagers you might get away with replacing all 3 and the TestFilter with a single AttributeManager and make use of conditional statements (basically a Testfilter inside the AttributeManager). That might be a beast to set up and maintain though.

Perhaps a SchemaMapper could be useful too, again it depends on what you're doing exactly.

SchemaMapper would definitely move the complexity of the renaming out into an external Excel or CSV file. And you'd have only a couple transformers as your reward. A set of tutorials (this thing is powerful) starts at https://knowledge.safe.com/articles/1136/schemamapper-transformer-tutorial.html

 

 

Helpful Members This Week

Community Stats

32,056
Posts
121,718
Replies
39,682
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

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
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.