I have fme wb which does fanout with gdb. It means that in the end as output sets of data I get few new created gdb. But If I start this fme wb within python script It does not do fanout. Just write data in one gdb. i do not understand where could be a problem?
3
-
Could you add the python that starts the workbench.– GIS-JonathanCommented May 16, 2012 at 10:24
-
But code is for long. Just this part is: print os.system(), in brackets comes string with path of fme.exe and path of workbench.– Z77Commented May 16, 2012 at 10:44
-
Interesting is that if the fanout gdb are created with just fme wb first, and then I start python which start fme wb and overwrite them, then everything is working regulary. And this is not what I want.– Z77Commented May 16, 2012 at 10:48
Add a comment
|
1 Answer
I tried this on my system and for me it worked and did the fanout whether I started from python or not. Maybe you could check your fanout parameters against mine.
Here is a sample workspace. And here is the code I used in python: import os print os.system("c:/apps/FME2012/fme.exe C:/Stack/none2filegdb.fmw")
