Skip to main content
Question

Clipper holds file handle

  • February 16, 2019
  • 1 reply
  • 8 views

Forum|alt.badge.img

Hello,

 

I have a custom transformer.

 

My flow is that it takes path to set of raster files. Then it clips some of those, merge together using raster mosaicer and save in different location. Then I want to delete file from source location and move on.

 

Problem is that using SystemCaller rmdir I get information that those files that were clipped cannot be deleted because they are being used by another process.

 

When I set a breakpoint just before SystemCaller, when files are already clipped and merged I couldn't delete those files in windows explorer as well. There was information that FME.EXE is using those files.

 

If I remove clipper transformer then I don't have that problem. So I assume that clipper somehow holds handle to those files.

Do you know a workaround for this problem?

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.

1 reply

takashi
Celebrity
  • 7843 replies
  • February 16, 2019

Some raster processing such as clipping may not finish until writing the resulting rasters with the writer. I think it's the reason why you failed to remove the source file in the workflow.

If you write the resulting rasters with the FeatureWriter, probably you can remove the source files with the SystemCaller after writing.