Skip to main content
Question

Workspace runner replacement

  • July 29, 2013
  • 8 replies
  • 31 views
I
Forum|alt.badge.img+1
Hi,

 

 

I am reading DGN files to write line segments in oracle spatial, in the same workbench I am using this table to join those line segments and write the out put geometries in another spatial table.

 

 

Now my problem is I want to keep these two processes in the same workbench and want that the table which holds the line segments should be populated fully before the line joining process starts, I can use workspace runner but in such case I have to divide these two process. Can anybody please suggest any work around.
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.

8 replies

david_r
Celebrity
  • david_rCelebrity
  • July 29, 2013
Hi,

 

 

there is unfortunately no easy and foolproof way of doing this, except by using the WorkspaceRunner.

 

 

It is possible to hack something together using the SQLExecutor and/or the FeatureHolder, but you risk that it will be ugly and difficult to maintain.

 

 

There has been prior discussions on this forum regarding this functionality, and one suggestion that surfaced was that the writers should also have an optional output port, so that it was possible to chain them (a bit like the Logger in FME2013).

 

 

I'm not sure if this feature request has been logged with Safe already, but it could be a good idea for you to pass this on to them regardless. The more people who request this functionality, the more likely it is to be implemented in the future.

 

 

David
takashi
Celebrity
  • takashiCelebrity
  • July 29, 2013
Hi Imran,

 

 

I agree with David.

 

One more consideration, can you adopt the workflow like this?

 

 

Takashi
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
fallingdog
Contributor
Forum|alt.badge.img+6
  • fallingdogContributor
  • Contributor
  • August 19, 2019
Hi,

 

 

there is unfortunately no easy and foolproof way of doing this, except by using the WorkspaceRunner.

 

 

It is possible to hack something together using the SQLExecutor and/or the FeatureHolder, but you risk that it will be ugly and difficult to maintain.

 

 

There has been prior discussions on this forum regarding this functionality, and one suggestion that surfaced was that the writers should also have an optional output port, so that it was possible to chain them (a bit like the Logger in FME2013).

 

 

I'm not sure if this feature request has been logged with Safe already, but it could be a good idea for you to pass this on to them regardless. The more people who request this functionality, the more likely it is to be implemented in the future.

 

 

David

I like the reader output port option!!! I did try and use the SQLExecutor and/or the FeatureHolder pattern for my problem but it did not appear to write the features before the SQLExecutor...

fmelizard
Safer
Forum|alt.badge.img+21
  • fmelizardSafer
  • Safer
  • August 20, 2019

I like the reader output port option!!! I did try and use the SQLExecutor and/or the FeatureHolder pattern for my problem but it did not appear to write the features before the SQLExecutor...

@fallingdog Since FME 2016 there has been a FeatureWriter transformer which does exactly what @david_r suggested. See FME 2016 Sneak Peek: The FeatureWriter Transformer and https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm

fallingdog
Contributor
Forum|alt.badge.img+6
  • fallingdogContributor
  • Contributor
  • August 20, 2019

@fallingdog Since FME 2016 there has been a FeatureWriter transformer which does exactly what @david_r suggested. See FME 2016 Sneak Peek: The FeatureWriter Transformer and https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm

Thanks @danatsafe!

fallingdog
Contributor
Forum|alt.badge.img+6
  • fallingdogContributor
  • Contributor
  • August 20, 2019

@fallingdog Since FME 2016 there has been a FeatureWriter transformer which does exactly what @david_r suggested. See FME 2016 Sneak Peek: The FeatureWriter Transformer and https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/Transformers/featurewriter.htm

@danatsafe is there a way to get the feature writer to return the feature and an ID (key) that is populated by the target database when the feature is written to an output port? right now I am using a feature reader after the feature writer....
fmelizard
Safer
Forum|alt.badge.img+21
  • fmelizardSafer
  • Safer
  • August 22, 2019
@danatsafe is there a way to get the feature writer to return the feature and an ID (key) that is populated by the target database when the feature is written to an output port? right now I am using a feature reader after the feature writer....

In this case you will need a FeatureReader after the FeatureWriter to get those keys.

fallingdog
Contributor
Forum|alt.badge.img+6
  • fallingdogContributor
  • Contributor
  • August 22, 2019

In this case you will need a FeatureReader after the FeatureWriter to get those keys.

Great sounds like I am doing it right! Thanks @danatsafe!

Community Stats

32,120
Posts
121,954
Replies
39,772
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.