Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: CDE - CCC Bar Chart - Minimum won't change from 0

  1. #1
    Join Date
    Jun 2011
    Posts
    15

    Question CDE - CCC Bar Chart - Minimum won't change from 0

    I've been wrestling with a CCC Bar chart trying to get the minimum value set above 0 but it just wont change. I've set both base and ortho axis "OriginisZero" (still not clear on which is which) to false and set min and max values for both. Still, the axis starts from 0. Is there something else that I need to change? As it is, my line graph is squished up to the top so far it's impossible to read.

    Any help is much appreciated!

  2. #2
    Join Date
    Jun 2011
    Posts
    15

    Default

    disregard my please for help - I just found I was missing "orthoaxis" and was looking at "ortho2axis"

  3. #3
    Join Date
    Mar 2012
    Posts
    645

    Default

    Regarding the base vs ortho naming.

    Take a look at the following table.
    Code:
    +-------------------+-------------+------------+
    | AXIS TYPE         /     chart orientation    |
    +-------------------+-------------+------------+
    | axis orientation  / [vertical]  | horizontal |
    +===================+=============+============+
    | x                 /     base    |   ortho    |
    +-------------------+-------------+------------+
    | y                 /     ortho   |   base     |
    +-------------------+-------------+------------+
    The axis orientation, "x" or "y", is synonymous with horizontal or vertical, respectively.

    When the chart orientation is vertical, the default, "base" refers to the same axis as "x" and "ortho" to the same as "y".
    If we rotate the chart, setting orientation to horizontal, then "base" will refer to the same axis as "y" and "ortho" to the same as "x".

    The axes "base" and "ortho" always showing the "domain" and the "counter-domain".
    On a bar chart, for example, "base" always represents the values of the "category" visual role (for certain fixed series, multi-chart, ...) while "ortho" always represents the values of the "value" visual role.

    Using one or the other is a matter of deciding whether the axis option to be specified should be anchored to the visual role concept or to the orientation concept.

    For example, a rule that says that: when an axis is vertically oriented, the space between ticks should be at least 1.1 em, should be coded like:

    Code:
    yAxisLabelSpacingMin: 1.1
    However, for a rule that specifies the formatting of the tick values, for the "value" dimension, should instead be coded like:

    Code:
    orthoAxisTickFormatter: function(v, precision) { ... }
    In either case, if the chart orientation is changed, all extension points will still refer to the desired axes.

    Most of the time we want to extend axes based on the axis type concept (base/ortho). Rarely, we mean "whatever axis that is aligned horizontally".

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.