[fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”]
Here is an interesting technique: using two y-axis to display the same data at different resolutions. Yellow (BMI) and blue (Weight) lines should overlap (there is a one-to-one correspondence between BMI and Weight for a given height), but they don’t because they are using a higher resolution for Y2. That’s clever. We can choose to see more detail (BMI) or less detail (kg).
- to replicate Y1 (it helps reading the chart);
- to show one-to-one correspondences (Celsius/Fahrenheit, km/miles)
- Everything else is potentially manipulative.
You must make sure those correspondences are preserved. That’s not the case here: 26.5 is not the right BMI for 74 kg (for this height). If I remove the green line, for the same BMI I get 82.3 kg. So, different correspondences for different resolutions. Hence the title of this post.
I wanted to focus on this, but there are other issues (terrible smoothing algorithm; is the green line (Goal) assigned to Y1 or Y2? You can never know).
How do you use the secondary y-axis?