Skip to main content
  • EN

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?

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 @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.

 

Reply


Community Stats

30,357
Posts
115,370
Replies
38,093
Members
Terms & ConditionsCookie settings
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.