Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
Could you add the python that starts the workbench. – GIS-Jonathan May 16 '12 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. – Z77 May 16 '12 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. – Z77 May 16 '12 at 10:48

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.ScreenShot

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")

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.