I'm not sure if this was always the case, but lately I've noticed that certain transformers (VertexCreator, AreaOnAreaOverlayer) are storing any invalid geometries it comes accross into .ffs files. This is nice for debugging, but it's not always what I want. Is there any way to tell FME if I don't want those features stored?
Question
Certain Transformers output .ffs files
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+19- Supporter
Hi,
Not that I know of, but maybe a Safer might shade some more light on this.
FME does store its files in ffs, usually in the temp location, for internal usage.
+22- Safer
Hi @yola -- we'd need to know a bit more about your situation (are you running from within Workbench or in FME Server or from the command line? And is this FME 2016?) but I strongly suspect that what you are seeing is due to the Rejected ports now on those transformers in FME 2016. If you are running within Workbench, we make a recording of anything going out a not-connected Rejected port. This is to help you inspect that later. If you don't like this, the easiest thing to do is just connect *anything* after the Rejected port. A Junction is a great one for example. That will have the effect of suppressing the auto-recording, and otherwise, doing nothing.