Skip to main content
Solved

why distance marker is waiting for all features to come?

  • November 3, 2016
  • 4 replies
  • 35 views

f.kemminje
Contributor
Forum|alt.badge.img+11

Hi Friends,

The problem is distance marker's preserve behavior. I have 14 lakhs features. But distance marker waits till last feature to come. after 9 lakh fme gives memory issue and comes out. I dont know why Distance marker to wait. because this is not group function. it can send the each features points as soon as it completes each feature. and write immediately. if the distance marker will preserve the incoming features, then definitely memory issue will come. how can i do that ?

Best answer by takashi

Hi @fkemminje, you are right. The DistanceMarker_2013 contains a Sorder within its work flow before the OUTPUT port, and therefore the resulting point features will be cached before outputting. In order to prevent the caching, remove the Sorter from the custom transformer definition. The order of output points will be modified by the Sorter only if you have set "Yes" to the "Output starting and ending points" parameter.

Alternatively, the LineDivider from the FME Hub might also help you. This transformer will not cache the features.

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.

4 replies

Forum|alt.badge.img
  • November 3, 2016
Not tested but I don't see any blocking transformers inside the DistanceMarker code.

 

Are you using any Group By option?

 

 

 


f.kemminje
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • November 4, 2016

Hi Larry, group by option not available in DistanceMarker_2013 transformer. Please test once. transformer is waiting all the features to in. and then processing all the features


takashi
Celebrity
  • Best Answer
  • November 4, 2016

Hi @fkemminje, you are right. The DistanceMarker_2013 contains a Sorder within its work flow before the OUTPUT port, and therefore the resulting point features will be cached before outputting. In order to prevent the caching, remove the Sorter from the custom transformer definition. The order of output points will be modified by the Sorter only if you have set "Yes" to the "Output starting and ending points" parameter.

Alternatively, the LineDivider from the FME Hub might also help you. This transformer will not cache the features.


f.kemminje
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • November 4, 2016

Thanks Takashi, I used Linedivider.

,

I used line devider. Thanks Takashi