Yesterday I used the FME clipper transformer to curve out unwanted portions in a polygon feature class from another polygon feature class. Both feature classes are in two separate Esri file geodatabases. It is a very simple geoprocessing operation, but it runs very very slow, measured in hours, some even became hung. Tested this in several feature class datasets, the same behavior - terribly slow. On the other hand, using the Erase geoprocessing tool in ArcGIS desktop, it finishes in 2 - 5 minutes for all the tested datasets. The results between FME and Esri Erase tool are exactly the same. So wondering why the FME clipper is so slow. I have been successfully promoting FME in my company in the last few months, but this came as a big slap on my face. I am at FME 2019.2.
FME clipper transformer is very very slow compared to ESRI Eraser geoprocessing tool.
+11- Safer
Hi @aguan ,
Sorry to hear that you've run into this. I've created a case for you so that we can follow up on it. Would you be able to reply to the case email with a workspace and sample dataset that takes a long time to process or hangs for you? It would also help to get a logfile and if you have any screenshots or time comparisons for the Erase tool for the given dataset. You should receive the case email on the same email as your login for the Community.
Once we get your workspace and data we can take a closer look to see if we may have any suggestions to speed things up, and we can add your case to an existing project to improve the Clipper transformer.
+11- Contributor
Hi @aguan ,
Sorry to hear that you've run into this. I've created a case for you so that we can follow up on it. Would you be able to reply to the case email with a workspace and sample dataset that takes a long time to process or hangs for you? It would also help to get a logfile and if you have any screenshots or time comparisons for the Erase tool for the given dataset. You should receive the case email on the same email as your login for the Community.
Once we get your workspace and data we can take a closer look to see if we may have any suggestions to speed things up, and we can add your case to an existing project to improve the Clipper transformer.
@jovitaatsafe, I found this issue is with the Proxy setting on the FME server. After I set the proxy IP address in System Configuration -> Network & Email, the job works now. You can close the case now. Thanks.
+11- Safer
@aguan glad to hear it! I'll go ahead and close the case then.
It may not be relevant for you now in FME 2019.2, but my colleague passed along a suggestion to add two SpatialSorters before the Clipper in FME 2021 as something to try in the future when you update. This method seemed to improve Clipper speeds for another user with a similar scenario.
+11- Contributor
@aguan glad to hear it! I'll go ahead and close the case then.
It may not be relevant for you now in FME 2019.2, but my colleague passed along a suggestion to add two SpatialSorters before the Clipper in FME 2021 as something to try in the future when you update. This method seemed to improve Clipper speeds for another user with a similar scenario.
@jovittasafe, I am terrible sorry. I was looking at the wrong question I asked. Please do not close the case. I am still working on this issue. I will see if I can use the SpatialSorters to improve.
+11- Safer
@jovittasafe, I am terrible sorry. I was looking at the wrong question I asked. Please do not close the case. I am still working on this issue. I will see if I can use the SpatialSorters to improve.
Hi @aguan , no problem! I see the other question and that makes more sense now (:
The case is reopened, let me know how the SpatialSorters work for you. If they don't improve things, please send me your workspace and supporting documents (sample data, log, screenshots) by responding to the case email. Thanks!
Reply
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.