Counter visualization

[arikfr]

Counter visualization

[amirnissim]

@arikfr, @ranbena how about we call this 'Goal' visualization?

[amirnissim]

@arikfr any thoughts on how the dataset should look like? maybe something like:
SELECT foo as "::goal" ...

[arikfr]

@amirnissim

• "Goal" is too specific. Better to have a counter with goal option.
• I don't want to keep using the "::" convention. To make it easier, we can add heuristics to pick what column contains the data, but anyway it should have settings like all the charts visualization.

[amirnissim]

for the query:

select 13 as "count";

[amirnissim]

first draft. please share your thoughts @arikfr @ranbena.

[ranbena]

1. Does it work well with the other widgets in a dashboard? (currently can't access rd)
2. The arrow and number look like they represent change and not diff from goal. Should consult UX.

[arikfr]

I think the visualization is a bit confusing, my suggestion:
Show it as : "Number (Target)" in your example 13 (15). If the number<target show it in red, otherwise green.

[amirnissim]

I was inspired by @itaimiller design for tabla

[arikfr]

Itai is a great inspiration, but he tried convey different information :-) "9% ^" in this screenshot means increase of 9% over some period of time. That's not the kind of information you show...

If you prefer you can show +X (green) -X (red) without the arrows. Maybe like this:

First row: [VALUE]
Second row: -X (TARGET)

[amirnissim]

@arikfr I initially tried value (goal) and it looked confusing to me.
It's still not clear to me what the use case would be, @ranbena should have a real example.
Maybe if the use case is "current VS target" we should simply show the delta: +10 or -5 as the main number.

[arikfr]

What about my second suggestion?

[joeysim]

I think we shouldn't have a predefined visualization target value but rather return both values from the query itself, allowing us to basically support both visualizations in one (a - number vs. static number and b - number vs. change coming from a time shifted query)

[arikfr]

+1 for @joeysim.

[amirnissim]

how about this (pushed):

select 17 as "counter", 16 as "target";

select 13 as "counter", 16 as "target";

[arikfr]

SUPER!

Just covert the column picker into a drop down... although even as is it's great. So only if you have time.

[shishirsharma]

If we put a monthly target, There is no point of showing up or down. Monthly targets might be really big/can be hard to achieve. There should be a visualisation like this one here

http://1.bp.blogspot.com/_XPquV_XKF1c/SSHwj6uuDzI/AAAAAAAAAbc/a5DFj7izu9Q/s400/g1.jpg

[arikfr]

@shishirsharma makes sense. It's better if you open a new issue for it (or even better: a pull request 😉).