Skip to main content
Question

Cliper - making low level intersections -

  • October 24, 2018
  • 3 replies
  • 13 views
M
Forum|alt.badge.img+1

Hi, i am cliping 7.000.000 fetaures and after 5.000.000 milions of read fetaures it stucks - program starts to make some low level intersections. I woul like to perform 30 independent dwg files from shapes with 7 milion of features. I do it with tester transformer. In ARGIS modelbuilder i used to do this with Feature iterator - are there any similar options?

Program runs very slow for 2 days and it is unable to perform cliped outputs. I think there is a memory issue, can you help me? i have 32gb ram availible and new i7 processor. FME softeware is 32 bit.

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.

3 replies

david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • October 24, 2018

How are the Clippers configured? Is it possible to configure them for "Clippers first", if that isn't already the case? That could have a huge impact on performance and memory consumption.

Also, you should consider using 64-bit FME. Unfortunately 32-bit software (including FME) cannot use more than about 2 GB of RAM, so your 32 GB of RAM sits mostly unused in this scenario. 64-bit software does not have this limitation and could help speed things up by using all of your available memory.

If nothing else works, you could iterate over the input features using a master workspace that runs the clipping workspace using e.g. the WorkspaceRunner. You can there parametrize which block to process using a published parameter. But my tip is to start with the top two recommendations first.

M
Forum|alt.badge.img+1
  • miharobar
  • Author
  • 17 replies
  • October 24, 2018

How are the Clippers configured? Is it possible to configure them for "Clippers first", if that isn't already the case? That could have a huge impact on performance and memory consumption.

Also, you should consider using 64-bit FME. Unfortunately 32-bit software (including FME) cannot use more than about 2 GB of RAM, so your 32 GB of RAM sits mostly unused in this scenario. 64-bit software does not have this limitation and could help speed things up by using all of your available memory.

If nothing else works, you could iterate over the input features using a master workspace that runs the clipping workspace using e.g. the WorkspaceRunner. You can there parametrize which block to process using a published parameter. But my tip is to start with the top two recommendations first.

Thanks for the quick answer,

 

 

I have set the clipper to "clippers first", I have to see what it can be done in the company for upgrading to 64 bit FME.

 

 

Bye, Miha

 

 

 

nielsgerrits
VIP
Forum|alt.badge.img+60
  • nielsgerritsVIP
  • 2940 replies
  • October 24, 2018
I would use 2 workspaces to do this.

 

First workspace to initiate a second one using a workspacerunner.

 

Second workspace to run per clipper. Read (FeatureReader!) only the to be clipped features that intersect with the clipper, clip them, write them to dwg, write a status succesful to the clipper table. This way you can stop and start the process without trashing the already done work.
Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...

Community Stats

32,084
Posts
121,835
Replies
39,721
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.