Skip to main content
Question

StatisticsCalculator bug?

  • October 6, 2017
  • 12 replies
  • 22 views

jorge_rosales
Contributor
Forum|alt.badge.img+8

It seems that StatisticsCalculator doesn´t work well when I group features by numeric (only numbers: [0-9]+) field keys. I attach a sample.

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.

12 replies

david_r
Celebrity
  • 8394 replies
  • October 6, 2017

Agree that looks like a bug, I was also able to reproduce it. It looks like numeric values loses their trailing zeroes, so that values like 1, 10 and 100 gets grouped together as one.

Another workaround is to cast pk_celda to string by inserting a StringFormatter before the StatisticsCalculator:


danilo_fme
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • 2077 replies
  • October 6, 2017

Hi @j4, i tested your Workspace in my FME Desktop 2018 and the error continue.

You can do the suggestion @david_r. :)

Thanks,

Danilo


LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • 1542 replies
  • October 6, 2017

Hi @j4, thanks for pointing this out to us, I have let our development team know and they are going to take a look at what is going on here. I will post any updates here.

-Liz


jorge_rosales
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • 44 replies
  • October 6, 2017

Hi @j4, thanks for pointing this out to us, I have let our development team know and they are going to take a look at what is going on here. I will post any updates here.

-Liz

Thank you.

 

 


runneals
Supporter
Forum|alt.badge.img+28
  • Supporter
  • 322 replies
  • October 9, 2017

I wonder if this is related to the bug that I caught in early September. I might have to try what @david_r proposed.


david_r
Celebrity
  • 8394 replies
  • October 9, 2017

I wonder if this is related to the bug that I caught in early September. I might have to try what @david_r proposed.

Let us know how it goes, hopefully it can help Safe find a solution.

runneals
Supporter
Forum|alt.badge.img+28
  • Supporter
  • 322 replies
  • October 9, 2017
Let us know how it goes, hopefully it can help Safe find a solution.
Nice! That worked!

ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3434 replies
  • October 12, 2017
Interestingly the workspace works in 2016 (just replacing the inspectors)

 

 

 

 

 

 

 


fmelizard
Safer
Forum|alt.badge.img+20
  • Safer
  • 3719 replies
  • October 12, 2017

Agree that looks like a bug, I was also able to reproduce it. It looks like numeric values loses their trailing zeroes, so that values like 1, 10 and 100 gets grouped together as one.

Another workaround is to cast pk_celda to string by inserting a StringFormatter before the StatisticsCalculator:

Yep, this WAS a bug alright. Sorry about that. It was specific to this transformer and only happened with integers in the group by. Fix going in right now. Will be released as part of a 2017.1.1 hotfix wrap up (and therefore will bein 2017.1.2 and 2018.x as well. Thanks for the good diagnosis @david_r -- sorry for the problem @egomm

 

/ @j4 / @femo

pratap
Contributor
Forum|alt.badge.img+12
  • Contributor
  • 605 replies
  • October 13, 2017

Hi,

Could you kindly explain the bug... I received the same count in both inspectors... i.e.17891. (2017.0 version)

Pratap


LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • 1542 replies
  • October 19, 2017

Great news @j4, the bug has been fixed in the latest hot fix 2017.1.1.1, which you can download at safe.com/downloads, it is also fixed in any future versions. Thanks again for catching this!


danilo_fme
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • 2077 replies
  • October 19, 2017

Great news @j4, the bug has been fixed in the latest hot fix 2017.1.1.1, which you can download at safe.com/downloads, it is also fixed in any future versions. Thanks again for catching this!

Yes, good news. I saw this news on Twitter account :)