Why the default axis min for box whisker plot is always at 0

Why the default axis min for box whisker plot is always at 0

Posted by: Yifan_Zhang on 1 May 2020, 4:05 pm EST

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 1 May 2020, 4:05 pm EST

  The box whisker plot always have the y-axis min value at 0 by default not the actual data min. Is this by design? But for other charts the axis min will be the actual data min, even for box whisker plot when it’s show as mean line, the axis min value is set to be the data min value.

  This is really causing some trouble when data value is far from 0, see this example: https://jsfiddle.net/605jvbra/

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 1 May 2020, 4:06 pm EST

  Repost the link: https://jsfiddle.net/605jvbra/

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 4 May 2020, 1:55 am EST

  Hi Yifan,

  You can manually set the y-axis min according to your data and the chart data with large values will be displayed correctly:

  https://jsfiddle.net/xLj4uyo7/

  Also, I tried with other series, like simple series, MovingAverage, etc and by default their y-axis min was set to 0.

  Regards,
  
  Ashwin

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 4 May 2020, 2:53 pm EST

  Thanks for the reply. I understand we can manually set the min. But it would also require us to add additional procedures to deal with data change and updates, etc. Is there any specific reason why it is not automatically using the data min like other charts (e.g., bar chart, line chart, scatterplot)? Thank you.

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 5 May 2020, 1:29 am EST

  Hi,

  I have asked the developers on this. The internal tracking id of the case is 434140. I will update you once I will hear from them.

  ~regards

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 6 May 2020, 1:39 pm EST

  Thanks. Looking forward to hearing back from you soon.

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 28 July 2020, 4:20 am EST

  Hi Yifan,

  The issue has been fixed in the latest nightly build of Wijmo. You may verify the same using the sample link below:

  https://stackblitz.com/edit/js-jvukft

  This fix will be included in the next stable release.

  PS: Nightly builds have not passed through the QA cycles as all of our release builds do. So, it is not recommended to use nightly builds in production.

  ~regards

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 28 July 2020, 1:22 pm EST

  Awesome. Thank you for the fix!