Skip to main content
  • EN

Sorry if the question does not express what I want to achieve, but of the top of my head I did not know how to ask differently.

The issue I have is, that features provided by the very left reader are used to identify raster files they intersect with, which afterwards are mosaicked and processed. There are a lot of raster files and a lot of features coming from the reader, and I would like to run this entire process rather feature by feature, instead of feeding all the features into the process.

What is the best way to achieve that?

 

image

One way would be with a Parent-Child workspace setup, where the parent workspace contains a WorkspaceRunner, which kicks off the child workspace (the processing in your screenshot). For each feature that enters the WorkspaceRunner transformer, the child process will be ran. See this article for an example: Batch Processing Using the WorkspaceRunner (safe.com)

One way would be with a Parent-Child workspace setup, where the parent workspace contains a WorkspaceRunner, which kicks off the child workspace (the processing in your screenshot). For each feature that enters the WorkspaceRunner transformer, the child process will be ran. See this article for an example: Batch Processing Using the WorkspaceRunner (safe.com)

Is it possible to work with parent-child workspace setup when the processing should happen in an ETL tool? Sorry for not mentioning that earlier.

Reply


Community Stats

30,126
Posts
114,374
Replies
37,765
Members
Terms & ConditionsCookie 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.