Pular para o conteúdo principal

(O) Criando um gráfico tipo "Stephen Few" no QlikView

This chart as a replacement for a traditional gauge.
A traditional gauge takes up a large amount of space to encode, usually, only one value. A bullet chart is linear and can encode more than one value.
The main components of a bullet chart (from Stephen Few's perceptualedge.com)
are as follows:
  • A text label
  • A quantitative scale along a single linear axis
  • The featured measure
  • One or two comparative measures (optional)
  • From two to five ranges along the quantitative scale to declare the featured measure's qualitative state (optional)
There is no native bullet chart in QlikView. However, we can create one by combining a couple of objects. Items 1, 2, 4, and 5 can be achieved with a linear gauge chart. The bar, item 3, can then be overlaid using a separate and transparent bar chart.

Hands-On

  •  Load the following script:

LOAD * INLINE [
    Country, Sales, Target
    USA, 1000, 1100
    UK, 800, 1000
    Germany, 800, 700
    Japan, 1000, 1000
];
  •  Add a new gauge chart. You should add a title and enter text for Title in chart. Click on Next.
  • There is no dimension in this chart. Click on Next.
  • Enter the following expression: Sum(Target)
  • Click on Next.
  • There is no sorting (because there is no dimension), so click on Next.
  • On the Style tab, select a linear gauge and set the orientation to horizontal.Click on Next.
  • There are a few changes needed in the Presentation tab:
     
  • There should be two segments by default, add a third segment by clicking on
    the Add button. The settings for each segment are as follows:
  • Apply appropriate colors for each segment (for example, RAG or Dark/Medium/
    Light gray).
  • Click on Finish.
  •  Most of the bullet chart elements are now in place. In fact, this type of linear chart may be enough for some uses. Now we need to add the bar chart.
  • Add a new bar chart. Don't worry about the title (it will be hidden). Turn off Show Title in Chart. Click on Next.
  • There is no dimension in this chart either. Click on Next.
  • Add the following expression: Sum(Sales)
  • Click on Next.
  • There is no sort (as there is no dimension). Click on Next.
  •  Select a plain bar type. The orientation should be horizontal. Leave the style at the default of Minimal. Click on Next.
  •  Set the following axis settings:
  •  Click on Next.
  •  On the Color tab, set Transparency to 100%. Set the first color to a dark color.
    Click on Next.
  • Continue to click on Next until you get to the Layout tab. Set the shadow to No
    Shadow and the border width to 0. Set the Layer to Top. Click on Next.
  • Turn off the Show Caption option. Click on Finish.
  •  Position the bar chart over the gauge so that the scales match (Ctrl + arrow keys are useful here). The bullet chart is created.
 Conclusion

By matching the Static Max setting of the bar and the gauge (to the sum of target * 1.2), we ensure that the two charts will always size the same. The 1.2 factor makes the area beyond the target point of 20 percent of the length of the area before it. This might need to be adjusted for different implementations.

It is also crucial to ensure that the layer setting of the bar chart is at least one above the layer of the gauge chart. The default layer (on the Layout tab) for charts is Normal so, in that situation, you should change the bar chart's layer to Top. Otherwise, use the Custom option to set the layers.

Using techniques such as this to combine multiple QlikView objects can help us create many other visualizations.

Thanks and see you on the next post!

PS: This article has adapted from the original: "Discover the strategies needed to tackle the most challenging tasks facing the QlikView developer (Stephen Redmond)"

Comentários

Postagens mais visitadas deste blog

(T) Como indexar uma tabela Fato - (Best Practice)

A base de qualquer projeto de bi é ter um bom dw/data mart. Podemos falar em modelagem star-schema durante dias, sem falar nas variações do snowflake, mas o objetivo principal deste artigo é apontar algumas negligências que tenho percebido no tratamento da tabela fato. Tabela esta que é o principal pilar da casa que reside um modelo star-schema.

Ouço muitas vezes os clientes reclamando do desempenho das consultas enviadas contra o seu dw/data mart, ou do tempo de resposta das análises solicitadas ao bi. Isto é realmente inaceitável, não só numa perspectiva de implantação do projeto, mas também de desempenho da entrega das informações.

Como eu mencionei anteriormente o meu objetivo neste artigo, é alertar sobre a importância da indexação da tabela fato: o que deveria ser, porque é necessário, porque chaves compostas são boas e más, e porque você deveria se preocupar com isso.

Então, vejamos:

|a| Indexação padrão (default):
De forma rápida, todas as colunas de chave estrangeira (FK) devem …

(A) Tucson Best Buy Analysis

“Data! Data! Data!” he cried impatiently.  “I can’t make bricks without clay.” —Arthur Conan Doyle
The Ascendance of Data

We live in a world that’s drowning in data. Websites track every user’s every click. Your smartphone is building up a record of your location and speed every second of every day. “Quantified selfers” wear pedometers-on-steroids that are ever recording their heart rates, movement habits, diet, and sleep patterns. Smart cars collect driving habits, smart homes collect living habits, and smart marketers collect purchasing habits. The Internet itself represents a huge graph of knowledge that contains (among other things) an enormous cross-referenced encyclopedia; domain-specific databases about movies, music, sports results, pinball machines, memes, and cocktails; and too many government statistics (some of them nearly true!) from too many governments to wrap your head around.
Buried in these data are answers to countless questions that no one’s ever thought to ask. In…