It seems that StatisticsCalculator doesn´t work well when I group features by numeric (only numbers: 0-9]+) field keys. I attach a sample.
Page 1 / 1
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:
Hi @j4, i tested your Workspace in my FME Desktop 2018 and the error continue.
You can do the suggestion @david_r. :)
Thanks,
Danilo
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
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
I wonder if this is related to the bug that I caught in early September. I might have to try what @david_r proposed.
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.
Interestingly the workspace works in 2016 (just replacing the inspectors)
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:
/ @j4 / @femo
Hi,
Could you kindly explain the bug... I received the same count in both inspectors... i.e.17891. (2017.0 version)
Pratap
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!
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!