Re: [visualization-api] Treemap chart : unable to have 2 nodes with same ID but different parents

[Daniel LaLiberte]

Ribardiere ,

I don't know of a reason that the ids have to be globally unique, other than it was assumed to be a reasonable assumption, so I agree with your assessment.  It doesn't seem so difficult to fix, but I won't know until I have time to look into it.  We might have to construct global unique ids for every node by using all the ancestors, for example.  Thanks for your posting about this issue.

dan

On Wed, Jan 2, 2013 at 3:45 PM, Ribardiere Olivier <olivier.r...@gmail.com> wrote:

Hi,

In a Treemap chart, 2 nodes should be able to have the same name if they don't have the same parent.

function drawVisualization() {
  // Create and populate the data table.
  var data = google.visualization.arrayToDataTable([
    ['Child' , 'Parent', 'Size', 'Color'],
    ['Global',    null,                0,                               0],
    ['Child1',   'Global',             0,                               0],
    ['Child2',   'Global',             0,                               0],
    ['ChildA',   'Child1',            10,                               0],
    ['ChildB',   'Child1',            10,                               0],
    ['ChildA',   'Child2',            10,                               0],
    ['ChildB',   'Child2',            10,                               0]
  ]);

  // Create and draw the visualization.
  var treemap = new google.visualization.TreeMap(document.getElementById('visualization'));
  treemap.draw(data, {
    minColor: 'red',
    midColor: '#ddd',
    maxColor: '#0d0',
    maxDepth: 2,
    headerHeight: 15,
    fontColor: 'black',
    showScale: true});
}

Following code raises "More than one row with the same ID (ChildA)", it should not.

Olivier

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/azc-Uov2mDMJ.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

--

Daniel LaLiberte  - 978-394-1058

dlaliberte@Google.com   562D 5CC, Cambridge MA

daniel.laliberte@GMail.com 9 Juniper Ridge Road, Acton MA

[Tayeb Karim]

Each cell in a data table has a Value(used as the id) and FormattedValue(what is shown).

IIRC, this used to be documented but I don't see it in the Treemap page.

The following example does as you wish;

function drawVisualization() {
  // Create and populate the data table.
  var data = google.visualization.arrayToDataTable([
    ['Child' , 'Parent', 'Size', 'Color'],
    ['Global',    null,                0,                               0],
    ['Child1',   'Global',             0,                               0],
    ['Child2',   'Global',             0,                               0],

    [{v:'ChildA1', f:'ChildA'},   'Child1',            10,                               0],
    [{v:'ChildB1', f:'ChildB'},   'Child1',            10,                               0],
    [{v:'ChildA2', f:'ChildA'},   'Child2',            10,                               0],
    [{v:'ChildB2', f:'ChildB'},   'Child2',            10,                               0]

-
---
Tayeb Al Karim
t...@google.com

[asgallant]

All nodes with children must have globally unique id's, or else their child nodes won't be able to distinguish which node is their parent.  Since trees are programmatically extensible, it makes sense to enforce unique id's on all nodes, regardless of whether or not they have any child nodes at draw time (as a previously child-less node may have children on redraw).  The solution proposed by tay is probably the best way to handle the problem, absent significant modifications to the TreeMap code that determines the parent-child relationships.

Ribardiere ,

dan

To unsubscribe from this group, send email to google-visualization-api+unsub...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

--

Daniel LaLiberte  - 978-394-1058

dlali...@Google.com   562D 5CC, Cambridge MA

daniel.l...@GMail.com 9 Juniper Ridge Road, Acton MA

[Daniel LaLiberte]

Drew,

You are right that there would be a problem referencing the parents if they are not globally unique.  A reference to a parent would have to use a fully qualified path starting from the root instead of just using the non-unique parent id.  This could be done, but is the added complexity worth it?

dan

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/efVJtGVWHDcJ.

To post to this group, send email to google-visua...@googlegroups.com.

To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

--

Daniel LaLiberte  - 978-394-1058

dlaliberte@Google.com   562D 5CC, Cambridge MA

daniel.laliberte@GMail.com 9 Juniper Ridge Road, Acton MA

[asgallant]

Using a fully qualified path adds an extra burden to the programmer to build the path.  If the only reason to offer them externally is to allow different nodes to have the same name, I don't think it's worth the effort, since we can achieve the same effect without fully qualified paths.  Maybe if you find a need for them internally to the API, they can be offered as an option externally for the users who do need them, but unless someone can come up with a use case where they are legitimately necessary, I wouldn't put much effort into it.

dan

Ribardiere ,

dan

To unsubscribe from this group, send email to google-visualization-api+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

--

Daniel LaLiberte  - 978-394-1058

dlali...@Google.com   562D 5CC, Cambridge MA

daniel.l...@GMail.com 9 Juniper Ridge Road, Acton MA

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/efVJtGVWHDcJ.

To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualization-api+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

[Scott Busche]

I came across this issue today and Tay's response from two years ago worked wonderfully. Why hasn't the option of passing a value and formatted value for ID been documented yet?

...

[Daniel LaLiberte]

Hi Scott,

The ability to specify value and formatted value applies to any value, not just for the id in the treemap.   See the documentation for arrayToDataTable: https://developers.google.com/chart/interactive/docs/reference#google.visualization.arraytodatatable where it is mentioned, but it is not up to date.  More documentation on the various ways of specifying datatables are documented at https://developers.google.com/chart/interactive/docs/reference#dataparam and in the separate page: https://developers.google.com/chart/interactive/docs/datatables_dataviews . 

--

You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.

To post to this group, send email to google-visua...@googlegroups.com.

Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/d/optout.

--

Daniel LaLiberte  - 978-394-1058

dlaliberte@Google.com   5CC, Cambridge MA

daniel.laliberte@GMail.com 9 Juniper Ridge Road, Acton MA