Histogram visual categorizes last bin wrongly?

Hi there! Is there a bug in the Histogram visual? I have a small DataSet containing numbers from 29 to 65. I have configured the Histogram bins starting from 25 and bin size 5. So the bins should be:

  • [25, 30[
  • [30, 35[
  • [60, 65[
  • [65, 70[

And this is how for example Excel or Google Sheets will set the bins. But Quicksight’s last bin will be [60, 65] - bin size being 6!

Please check the example dashboard here:
Ages_Histogram

Hi @pekkamalmirae and welcome to the QuickSight community!
From my understanding, the bin size would still be accurate, if anything came up as ‘60’, it would just be included in the prior bin that’s 55-60. Since you’re starting your histogram off at 25, the rest of the visual will follow suit in the same pattern.
Have you cross-checked your data to confirm if it’s being mapped correctly? Your Arena view shows that there are 6 numbers that fall within 60-65 (which should be between 61-65), is that correct or is one of those 6 numbers listed as ‘60’?

1 Like

Hi @Brett, and thank you for your answer!
My dataset has one column (Age) with the following values: 29, 41, 43, 48, 54, 54, 55, 58, 60, 60, 60, 61, 62, 65.

As you can see from my Arena view, bin with [55, 60[ contains only two values, so 60 is not included there. And the last bin [60, 65[ contains six values, at this time also containing the value 65. From my understanding, the 65 should be in its own bin [65, 70[

When I put the same values in Google Sheets and create the histogram with same settings as in QuickSight, the last number gets its own bin:

1 Like

Hi @pekkamalmirae,
This is really interesting behavior that I haven’t run in to before with Histograms but it would make sense to just add one more grouping. I’ll tag this as a feature request for visibility to our support team!

Thank you