I know I'm being lazy by not thoroughly researching the available documentation, but maybe there's a simple yes/no answer to my question: can I directly export a .fmw workbench transformation to a Python module(s)? The closest analog I can think of is like in ArcGIS, where you can export a ModelBuilder diagram into a Python script.
FME doesn't offer this option.
FME doesn't offer this option.
If your whole transformation is located inside a custom transformer, i.e. a tab beside "Main", you can right-click on that custom transformer tab, and choose "Export as custom transformer". This will export it as a single FMX file. No Python though.
Cheers
Thank you, @redgeographics and @lifalin2016. Seems like having the ability to export a FMX to Python would be a great feature. Trying to retrofit FMX with functionality like list comprehension is really cumbersome to work with. Maybe I'm missing something really basic, but my understanding is that you can add Python API calls to a FMX, not the other way around (i.e., calling FMX functionality from a standalone Python module). Is that true?
Thank you, @redgeographics and @lifalin2016. Seems like having the ability to export a FMX to Python would be a great feature. Trying to retrofit FMX with functionality like list comprehension is really cumbersome to work with. Maybe I'm missing something really basic, but my understanding is that you can add Python API calls to a FMX, not the other way around (i.e., calling FMX functionality from a standalone Python module). Is that true?
The catch is the licensing. This will only work on your own machine with a valid FME license. And you can only distribute your app to other machines with a similar FME license.
Thanks @lifalin2016. I'm at that cusp of FME Workbench expertise where I'm spending more time trying to fit it into a programming environment that I'm familiar with rather than sitting down and figuring out how to set up workflows entirely within FME .
Thanks @lifalin2016. I'm at that cusp of FME Workbench expertise where I'm spending more time trying to fit it into a programming environment that I'm familiar with rather than sitting down and figuring out how to set up workflows entirely within FME .
Best regards,
Rudy