Skip to main content
Best Answer

How to chain data between workspaces

  • February 25, 2021
  • 2 replies
  • 124 views
matthieuv
Enthusiast
Forum|alt.badge.img+28

I want to make an Automation where the flow goes first trough an workspace which reads data from an database. Depending on the feature type it then goes to different Automation Writers. Each of these ports are then connected to its own workspace so it can be run parallel. Eventually they merge back to another workspace which writes back the data to the database.

 

The problem I have now is that thousands of features reach the Automation Writer thus kicking of the next workspace thousands of time. Obviously that is not what I want. What is best practice to collect and group these features and pass them on as one feature.

 

I tried using the Aggregator Transformer and adding the parameters to a list, but it seems that it is not supported by GeoJSON.

 

I use FME Server 2020.2

Best answer by redgeographics

You could use a FeatureWriter in your first workspace to write to a temporary file before kicking off the Automation writer (the FeatureWriter will output a single feature for this purpose). The downside of this is that you'll add some additional writing/reading overhead.

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.

2 replies

redgeographics
Celebrity
Forum|alt.badge.img+62
  • redgeographicsCelebrity
  • Celebrity
  • Best Answer
  • February 26, 2021

You could use a FeatureWriter in your first workspace to write to a temporary file before kicking off the Automation writer (the FeatureWriter will output a single feature for this purpose). The downside of this is that you'll add some additional writing/reading overhead.

FME rocks! \m/
matthieuv
Enthusiast
Forum|alt.badge.img+28
  • matthieuvEnthusiast
  • Author
  • Enthusiast
  • February 26, 2021

You could use a FeatureWriter in your first workspace to write to a temporary file before kicking off the Automation writer (the FeatureWriter will output a single feature for this purpose). The downside of this is that you'll add some additional writing/reading overhead.

I was thinking of something similar as a solution. But I hoped I was just missing some option.

 

It would be cool if the automation writer had the option to work like the Holder and then send everything at once.

Community Stats

32,182
Posts
122,181
Replies
39,856
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.