In broad terms, yes. I always describe a custom transformer as a collection of transformers that pretends to be a new one. The usage you're describing, reusing a certain static combination of transformers with varying inputs and/or parameters is exactly what custom transformers are designed for.
Personally, I think what you are describing would not be a job for a custom transformer. It sounds more like something where you could develop an entire workspace and then control what parameters it is run with via a workspace runner, fmeserverjobsubmitter or automation or similar.
Yes, depending on your environment you can create linked custom transformers which means you can have a central location for all your customer transformers and just make changes to those.
If using a reader or a writer in a custom transformer it must be a FeatureReader/Writer. And also consider that reading/writing data to disk during a workflow can add quite a bit of processing overhead.
In broad terms, yes. I always describe a custom transformer as a collection of transformers that pretends to be a new one. The usage you're describing, reusing a certain static combination of transformers with varying inputs and/or parameters is exactly what custom transformers are designed for.
Do people tend to create these transformers via FME Workbench/Desktop? I've been trying to use the plugin builder SDK and docs but have been struggling a little bit since I haven't completely grasped all the concepts in FME.
Yes, depending on your environment you can create linked custom transformers which means you can have a central location for all your customer transformers and just make changes to those.
If using a reader or a writer in a custom transformer it must be a FeatureReader/Writer. And also consider that reading/writing data to disk during a workflow can add quite a bit of processing overhead.
So here's an example of the mess I'm trying to avoid / automate.
My thought was I could encapsulate this Reader / Writer / GeometryFilter into one transformer and I can stitch the features in code, given an parameter input of the file names and the output folder name.
I'm learning now that it's possible to make custom transformers in the UI as well as using the SDK, but I come from a coding background, so I started with the SDK.
Personally, I think what you are describing would not be a job for a custom transformer. It sounds more like something where you could develop an entire workspace and then control what parameters it is run with via a workspace runner, fmeserverjobsubmitter or automation or similar.
Interesting. How would you make it flexible to files with different feature names? Pardon the ignorance, just getting started with this ecosystem. Attached is an example workflow, the feature types are dynamic based on the content of the file, so I'd need a way to reflect those and I only know of doing that in code
Do people tend to create these transformers via FME Workbench/Desktop? I've been trying to use the plugin builder SDK and docs but have been struggling a little bit since I haven't completely grasped all the concepts in FME.
Yes, almost exclusively with FME Workbench.
Interesting. How would you make it flexible to files with different feature names? Pardon the ignorance, just getting started with this ecosystem. Attached is an example workflow, the feature types are dynamic based on the content of the file, so I'd need a way to reflect those and I only know of doing that in code
Take a look at this tutorial on how to develop dynamic Workflows in FME. FME can handle dynamic schema and table names.
https://community.safe.com/s/article/dynamic-workflow-tutorial-introduction
So here's an example of the mess I'm trying to avoid / automate.
My thought was I could encapsulate this Reader / Writer / GeometryFilter into one transformer and I can stitch the features in code, given an parameter input of the file names and the output folder name.
I'm learning now that it's possible to make custom transformers in the UI as well as using the SDK, but I come from a coding background, so I started with the SDK.
You can change the way the input features come into the workspace so they all come in at one feature type. When adding a reader you can check this to make all features come into one.
Here's the tutorial on working with fme in a dynamic way: https://community.safe.com/s/article/dynamic-workflow-tutorial-introduction
