Hi,

 

 

a couple of things come into play here:

1. By default, FME writes out features as soon as they hit the writer. But there are some transformers that cannot let features pass until it has processed all of them, these are called blocking transformers. Examples include the Sorter. If you have blocking transformers in your workspace, then the features won't hit the writer until the workspace terminates.
2. Windows will not always show the true file size until the file has been closed. So if you have a running translation that takes a while, the Windows Explorer might report the output file size as 0 bytes until the workspace terminates and the file is closed.

David

---

What you say in # 2 makes sense, David, and I suspected this was the case. However, I'm wondering what happens if FME crashes before  the workspace terminates normally. Is there some buffer process at work here?

 

 

This can happen when you add a new record to an Access table and then try and view it in another program (like a Python script opening the table); the new record is cached and does not actually get written until you close the database. If it is the same with FME then my script might process for two days, then crash, and nothing gets actually written to the file. I would feel better if I knew that FME (outside of #1 above) ALWAYS writes each feature to the file when they hit the writer.

 

 

Thanks

---

Hi,

 

 

I far as I know FME will not wait untill 200,000 records gets processed. It will write when 2000 records hits the writer (until you have some blocking transformers like feature holder or any such in between the process)...

 

 

Pratap

---