Skip to main content
Question

Input Ordered parameter doesn't work in FME 2017?

  • March 19, 2017
  • 2 replies
  • 8 views
takashi
Celebrity

Hi there, I don't think the Input Ordered parameter (Input is Ordered by Group in older versions) works properly in FME 2017.0 build 17271. See the following movies and attached workspace: - created with FME 2016.1.3.2 build 16717

Run the attached workspace with FME 2016.1.3.2 build 16717. Looks good.

Run the same workspace with FME 2017.0.0.1 build 17271. The PointCloudCombiner seems to cache all input features before starting processing, even if the Input is Ordered by Group parameter is set to Yes.

Am I missing something?

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
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.

2 replies

fmelizard
Safer
Forum|alt.badge.img+21
  • fmelizardSafer
  • Safer
  • March 20, 2017

Hi @takashi. I was able to reproduce what you reported with the Input is Ordered by Group parameter set to Yes in FME 2017.0 build 17259 and FME 2017.0.0.1 build 17271. I filed a report for Development to investigate and will let you know when I receive a reply from them, known issue 76579. Thanks!

takashi
Celebrity
  • takashiCelebrity
  • Author
  • March 22, 2017

Hi @takashi. I was able to reproduce what you reported with the Input is Ordered by Group parameter set to Yes in FME 2017.0 build 17259 and FME 2017.0.0.1 build 17271. I filed a report for Development to investigate and will let you know when I receive a reply from them, known issue 76579. Thanks!

Hi @NatalieAtSafe, thanks for filing the problem report.

 

The parameter in the Aggregator seems to work as expected, but the NumericRasterizer seems to have this issue too. I'm afraid that more transformers could have the same issue. Perhaps have to check all transformers which have the Input Ordered parameter.

 

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?

Community Stats

32,206
Posts
122,292
Replies
39,887
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.