Skip to main content

Hi,

 

I've created a workspace that reads multiple dwg-files, goes through some cookie cutting and outputs the results to a pdf. The cookie cutter is dependant on a variable.

 

I've managed to setup a second workspace that runs the above for each feature in a dataset. It all works. The problem is that the dwg-files are beeing read every time which takes some time.

 

So my question is, is there a way to read the dwg-files in the second workspace and just pass them through the workspacerunner? Tried for some time now and can't figure it out.

 

Thankful for any advice!

What do do mean exactly that the DWG files are being read every time? do you mean per feature in your dataset? How have you set up the second workspace? Could you give us a screen shot?

 

 


Thank you for your reply :)

 

Below is a screenshot from workspace 1. The bookedmarked files are the dwg-files that I mentioned.

workspace

 

 

Here is the workspace runner.workspacerunner

 

So the workspacerunner runs workspace 1. Which means that the dwg-files are read for every feature that the Tester-node outputs (which is 15 in my current case).

 

 

Please ask questions if I'm not clear 🙂 Thanks!


Ahhh I see, well in that case I would probably remove the WorkspaceRunner and try and do it all in one workspace? Is that an option? FME has a lot of features which should help with the process. On the output you can use the fanout setting to create multiple pdf files based on an attribute.

Heres are very small example of how you could perform the clips.

 


I don't think it's an option. If I would do it all in one go I would get all the buffers from the 15 features which would mess up the styling nodes and the exports would wrong.

 

I might just stick with it taking some time 🙂 At least I don't have to do anything :D


I don't think it's an option. If I would do it all in one go I would get all the buffers from the 15 features which would mess up the styling nodes and the exports would wrong.

 

I might just stick with it taking some time 🙂 At least I don't have to do anything :D

Yeah that might be the best option. To speed it up you can make sure your WorkspaceRunner is set not to wait and set then number of consecutive workspaces to be 7. Ha! your PC might struggle a little though, but worth a test. If 7 is to high you can go down to 4. This will have the processes run in parallel.


It should be possible to use a spatial relator in the parent workspace to work out which DWG files and send this as a parameter to the child workspace, probably easier to set up if the readers are swapped for FeatureReaders in the child workspace


It should be possible to use a spatial relator in the parent workspace to work out which DWG files and send this as a parameter to the child workspace, probably easier to set up if the readers are swapped for FeatureReaders in the child workspace

Hi @ebygomm​ . Thanks for your reply!

 

This would be awesome! Could you push me in the right direction on how to send that type of data as a parameter? I'll poke around with using FeatureReaders in the child workspace 🙂 Thanks once again!


Hi @ebygomm​ . Thanks for your reply!

 

This would be awesome! Could you push me in the right direction on how to send that type of data as a parameter? I'll poke around with using FeatureReaders in the child workspace 🙂 Thanks once again!

So something like this in your parent workspace. The child workspace needs to have a parameter set for the source DWG files. Set this up as a single reader for all the DWG files in the child

Capture


Reply